> Blazor code executing on the server has the flexibility to do anything you would normally do on the server, such as connecting directly to a database.
Frustrating to see even the splash page off in lalala land.
Write once, deploy no where because surprise, the 3rd party package you were using requires a database connection, or some other server side feature.
This kind of messaging is why Blazor code is a mess; its not a seamless change to run on WASM when its ready, its server side lock-in, making db calls from your code behind file.
..and for anyone who thinks this isn’t webforms back from the dead:
> If you are a Web Forms developer and want to build a new application on .NET Core, we would recommend Blazor which provides the closest programming model. [1]
The sad thing is, the WASM c# end-to-end, using real full dlls in the browser is actually really cool.
...but somehow that got lost along the way.
[1] https://devblogs.microsoft.com/dotnet/net-core-is-the-future...
Frustrating to see even the splash page off in lalala land.
Write once, deploy no where because surprise, the 3rd party package you were using requires a database connection, or some other server side feature.
This kind of messaging is why Blazor code is a mess; its not a seamless change to run on WASM when its ready, its server side lock-in, making db calls from your code behind file.
..and for anyone who thinks this isn’t webforms back from the dead:
> If you are a Web Forms developer and want to build a new application on .NET Core, we would recommend Blazor which provides the closest programming model. [1]
The sad thing is, the WASM c# end-to-end, using real full dlls in the browser is actually really cool.
...but somehow that got lost along the way.
[1] https://devblogs.microsoft.com/dotnet/net-core-is-the-future...