[vNext] Add option to 'Publish' instead of deploy

[DamianSuess]

Publish project option

[DamianSuess]

Deprecating feature

[Reveon]

Having a publish option would be great for ASP.NET apps. For example, in my case, I have a Blazor WebAssembly app hosted on ASP.NET. After building and deploying, the 'wwwroot' folder from my Blazor project isn't transferred to the Raspberry Pi since build itself doesn't account for that folder.

Currently, the only way to make this work is to publish the app, take the 'wwwroot' folder from the Blazor Wasm project, copy it to the debug folder in the host ASP.NET project, and then run the Build and Deploy.

Otherwise great work!

[DamianSuess]

That's good to know someone would find use in that feature. It's in there (from what I recall) but partially commented out and untested.

If this is something you would find useful, we could add it.

[Reveon]

If it's not too much effort for you to finish it, then yes, it would be great to have that.

[DamianSuess]

Let's open it up and try to get it in for the 2023-Q4 release.
This upcoming release aims to support multiple connection profiles. So it should be able to make the cut.