[Feature Request] In the Blazorwasm templates hosted, show how to call graph and a downstream api

[jmprieur]

Is your feature request related to a problem? Please describe.
The Blasorwasm template has all the initialization to call a downstream API, or Graph, but we did not expose pages that actually call them

[jmprieur]

Work to be done in the ComponentsWebAssembly-CSharp project template.

What I initially thought

I initially thought that the work to be done could be the following, however, that does not work because it would require Microsoft.Identity.Web to support netstandard2.1:

• in the Client/Pages sub folder, add the CallWebApi.razor and ShowProfile.razor pages from https://github.com/AzureAD/microsoft-identity-web/tree/master/ProjectTemplates/templates/BlazorServerWeb-CSharp/Pages but change the third line of the copied files to have instead of
• in the Client/Shared sub folder:
  1. add the NavMenu.* pages from https://github.com/AzureAD/microsoft-identity-web/tree/master/ProjectTemplates/templates/BlazorServerWeb-CSharp/Shared, but change the copied file to have the second line of the file be <a class="navbar-brand" href="">BlazorServerWeb-CSharp</a> and not <a class="navbar-brand" href="">ComponentsWebAssembly-CSharp</a>.
  2. delete the NavMenu.razor file (it should have the same content as NavMenu.NoGraphOrApi.razor)
• in the template.json file, add the conditional inclusion of the pages:

  microsoft-identity-web/ProjectTemplates/templates/BlazorServerWeb-CSharp/.template.config/template.json

  Lines 131 to 173 in 5d3c277

  	{
  	"condition": "(!GenerateApi)",
  	"exclude": [
  	"Pages/CallWebApi.razor"
  	]
  	},
  	{
  	"condition": "(!GenerateGraph)",
  	"exclude": [
  	"Shared/NavMenu.CallsMicrosoftGraph.razor",
  	"Pages/ShowProfile.razor"
  	]
  	},
  	{
  	"condition": "(!GenerateApiOrGraph)",
  	"rename": {
  	"Shared/NavMenu.NoGraphOrApi.razor": "Shared/NavMenu.razor"
  	},
  	"exclude": [
  	"Shared/NavMenu.CallsMicrosoftGraph.razor",
  	"Shared/NavMenu.CallsWebApi.razor"
  	]
  	},
  	{
  	"condition": "(GenerateGraph)",
  	"rename": {
  	"Shared/NavMenu.CallsMicrosoftGraph.razor": "Shared/NavMenu.razor"
  	},
  	"exclude": [
  	"Shared/NavMenu.NoGraphOrApi.razor",
  	"Shared/NavMenu.CallsWebApi.razor"
  	]
  	},
  	{
  	"condition": "(GenerateApi)",
  	"rename": {
  	"Shared/NavMenu.CallsWebApi.razor": "Shared/NavMenu.razor"
  	},
  	"exclude": [
  	"Shared/NavMenu.NoGraphOrApi.razor",
  	"Shared/NavMenu.CallsMicrosoftGraph.razor"
  	]
  	}

However

In fact it seems that we cannot really do something for the non-hosted templates, until Microsoft.Identity.Web has a netstandard2.1 platform, which in turns requires MSAL.NET to have one. We have an issue for that: #9

What we could do:

For the hosted templates, we could have pages in the Client that calls the Web api controller, and that would do the work. We probably want to change the test app first (or add a new test app (Blazorwasm2-singleOrg-hosted-calls-graph) based on the template, and then bring this change to the template

In any case needs more spec and more work than I thought. Marking it as blocked.

[jennyf19]

Included in 1.1.0 release.