visualstudio-docs VS MSBuild.SDK.SystemWeb

I created VS solution with an asp.net core backend and React frontend as separate projects following this tutorial/template. It's an old GitHub link because I created the project before the official page was updated.

There are some hints in this document, like the OS needing to lock down installed app files:

https://learn.microsoft.com/en-us/windows/msix/desktop/deskt...

Or this issue: https://github.com/MicrosoftDocs/visualstudio-docs/issues/33...

Microsoft C++ Style Guide Example

I opened an issue in Github. You can see the answer I got: https://github.com/MicrosoftDocs/visualstudio-docs/issues/8404

It should work for .net framework as well, check out https://github.com/MicrosoftDocs/visualstudio-docs/issues/5291. As per UI way, you've demonstrated it to us in your question :) Click on "Why can't I select a different C# version?" and read through.

For example to debug a multithreaded application you have these kind of things https://github.com/MicrosoftDocs/visualstudio-docs/blob/main/docs/debugger/walkthrough-debugging-a-parallel-application.md

Did you go for the "install while downloading" option? You can try a full download instead: https://github.com/MicrosoftDocs/visualstudio-docs/blob/main/docs/install/create-an-offline-installation-of-visual-studio.md

I have some projects stuck on that, but not a lot. For web stuff, https://github.com/CZEMacLeod/MSBuild.SDK.SystemWeb does most of the heavy lifting, although things like publishing are broken.

I’ve had great luck with this on older ASP.NET projects https://github.com/CZEMacLeod/MSBuild.SDK.SystemWeb

You can use this unofficial project to modernize your .NET Framework project and take advantage of things like PackageReferences.

Sdk at least works with .net standard so shared projects can be converted to that, we also had some success using the MSBuild.SDK.SystemWeb sdk nuget package for our MVC5 projects which I found from the github issue discussions on adding official support for it on older projects.

I've been a bit luckier in that regard, but I'm not sure if your path wouldn't have taken less effort. I use https://github.com/hvanbakel/CsprojToVs2017 (dotnet migrate-2019 wizard) to modernize the projects, then further tweak them by hand. For ASP.NET projects, it's indeed a very difficult road. WebForms outright doesn't exist, and Core is very different from MVC in some areas. https://github.com/CZEMacLeod/MSBuild.SDK.SystemWeb helps somewhat.