From the Radzen app, an associate has added to an existing solution an Asp.net core 2.2 project, and two web site projects, one each for client and meta.
This doesn't seem very visual studio friendly because web site projects wont actually be compiled, and arent really even recognized as a first class project type, and I think is going to require a bunch of post build event scripts in Asp,Net core 2.2 project to run the steps listed on the Manual "Deploy" page (That is conflating the topics of build and deploy and creating its own confusion).
A solution to this would be to just add the client and meta folders as subfolders of the asp.net core 2.2 project, then we can use existing msbuild tasks or azure dev ops tasks without having to go out of bounds, and would get the benefit of having a single WebDeploy compatible package that can be deployed via the usual means.
Is this or something like it possible? Have we setup the solution and projects in some suboptimal way?