Hey there! First of all, amazing work on an amazing project! Hope this project will gain momentum with time!
Now back to the issue. My situation is that I have a Blazor Webassembly application which follows the default project/file structure generated by Visual Studio: Client, Server(ASP) and Shared.
This means that the application heavily relies on the server and cannot be run independently.
Do you have any suggestions or potential improvements to allow bundling default Blazor web apps? In my mind, running the server as a child process serving all the necessary documents should be enough for the app to look like a complete package.
However, upon including and trying to run the server out of its "Server" project in a separate "Desktop" project I witnessed the browser not being able to access the server at all, pointing at some ASP.NET controller assembly resolution shenanigans which I wasn't able to resolve, unfortunately.
What do you think, can there exist an out of the box solution?
Hey there! First of all, amazing work on an amazing project! Hope this project will gain momentum with time!
Now back to the issue. My situation is that I have a Blazor Webassembly application which follows the default project/file structure generated by Visual Studio: Client, Server(ASP) and Shared.
This means that the application heavily relies on the server and cannot be run independently.
Do you have any suggestions or potential improvements to allow bundling default Blazor web apps? In my mind, running the server as a child process serving all the necessary documents should be enough for the app to look like a complete package.
However, upon including and trying to run the server out of its "Server" project in a separate "Desktop" project I witnessed the browser not being able to access the server at all, pointing at some ASP.NET controller assembly resolution shenanigans which I wasn't able to resolve, unfortunately.
What do you think, can there exist an out of the box solution?