Support for .NET 6

[danatcofo]

• NET 6 Support
• Target a specific project in the electronize build/start command using /dotnet-project <projectName>.csproj

NOTE: the .NET6 runtime has targeted System.Drawing.Common at windows architectures and will cause warnings. This should be addressed at some time.

https://docs.microsoft.com/en-us/dotnet/core/compatibility/core-libraries/6.0/system-drawing-common-windows-only

[danatcofo]

appveyor is failing on net6 not being supported... looking into that.

[danatcofo]

Updated the appveyor to run a dedicated script appveyor.cmd and removed the 'custom' runs on that script due to lack of support for win7/single file build on the Visual Studio 2022 image.

[robalexclark]

Does anyone know if this can the merged into main?

[danatcofo]

I have this and most of the other PRs merged in a fork branch. Working fine for me there.

[GregorBiswanger]

The next big update is coming soon!

[lukebordonaro]

I tried out a local build of the source branch for this PR and noticed a quirk:

If I specify a aspCoreBackendPort in my manifest, I am unable to connect to the ASP.NET Core server. electronize start logs Now listening on: http://localhost:<myport>, but navigating to that URL gives a 404.

Interestingly, if I start with electronize start /watch, I am navigate to http://localhost:<myport> and get properly redirected to my SpaProxyServerUrl.

I wonder if this is related: dotnet/aspnetcore#38185

---

Actually I was wrong 😄. At the same time I added the custom port, I removed

app.UseSpa(spa => ...);

from my program.cs, thinking it was un-needed with the new .csproj SPA settings. Guess I was wrong!

[danatcofo]

Yah I didn't implement that functionality into the change set. I haven't even figured out or researched how to do that yet.