Our great sponsors
-
blazor-ui
A collection of examples related to Telerik UI for Blazor Components: https://www.telerik.com/blazor-ui
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
SqlClient
Microsoft.Data.SqlClient provides database connectivity to SQL Server for .NET applications.
-
ASP.NET Core
ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Telerik also exists for Blazor :) https://www.telerik.com/blazor-ui
No, it is fully supported and in active development. https://github.com/dotnet/winforms
I was doing some simple internal tooling with EF. You know the deal, toss in a new row into a table to do something or other, simple CRUD stuff. I was making it in WASM just for the sake of trying out the framework. Turns out this is a thing: https://github.com/dotnet/SqlClient/issues/599 , which prevents EF from running. The wiki page being referenced is gone though, so I don't know the reason why it'd be incompatible. To me it doesn't make that much sense, since a console application would be functionally the same, just outside a browser.
I never said WebForms are better. My experience with those ended around 2012 when I moved to backend. I know that asp.net was fluctuating with different concepts (mvc, razor, etc) but recently researching what Microsoft is considering latest and suggested to use - turned out it's "Razor pages" (and not mvc). When I went thru couple of courses on 'razor pages' topic they turned out to be closer in architecture to old webforms. at least in my opinion.