VS 15.8: New project from template results in empty solution

[arpadbarta]

After upgrading VS to 15.8 and .Net Core to 2.1.400 newly created project with the Blazor template results in empty solutions. Trying to add generated projects fails with incomplete project files.

Changing the .Net Core version in global.json to 2.1.400 solves the problem and generated projects can be added.

[MarkStega]

Confirming the same behavior on my system

[danroth27]

I'm not able to reproduce this on my machine.

@mlorbetske Any ideas on what could cause this?

[ShadowDancer]

@danroth27
If you installed sdk manually it works, if You updated it via visual studio You have 2.1.400 sdk, but not 2.1.300 generated from template. If You try installing sdk then installer only prompts for repair. For some reason projects are kicked out of solution, but I can add them by hand.

[MarkStega]

I can't remember if I deleted the file or if it wasn't generated when I created my working project. Now if I create a new ASP.Net Core project with either Blazor template I get a global.json file in the root of the solution that has

{
  "sdk": {
    "version": "2.1.300"
  }
}

@danroth27 I bet you have the 2.1.300 sdk installed on your system. I do not.

[danroth27]

@danroth27 I bet you have the 2.1.300 sdk installed on your system. I do not.

Yeah, I have more SDK versions installed than I care to admit 😝. Let me try uninstalling 2.1.300 and see what that does.

[danroth27]

OK, I'm seeing this issue now with the multi-project templates.

[mlorbetske]

@phenning any ideas?

[danroth27]

I looked at this with @phenning and it seems to be caused by the global.json file that we drop with the template. It only affects the multi-project templates though.

[phenning]

Note that we do actually create the individual projects, and that manually updating global.json to point to 2.1.400, or deleting it allows the projects to be loaded.

[danroth27]

At this point I think we should remove the global.json files from our templates. I don't think they are adding any value.

[River39]

editing the global.json and settings the "version" to "2.1.400" fixed the issue for me.

[danroth27]

This should now be fixed by dotnet/blazor#1386