Asp.net Core updates in .NET 8 Preview 1
devblogs.microsoft.com
Asp.net Core updates in .NET 8 Preview 1
1–10 of 37 posts
Re: Asp.net Core updates in .NET 8 Preview 1
#2Blazor United looks ambitious but sounds great! The goal feels similar to that of Remix.run and a few other frameworks that are blending SPA/SSR.
I do wonder about the scalability of the Blazor Server mode which requires live and "sticky" SignalR connections.
Re: Asp.net Core updates in .NET 8 Preview 1
#3Microsoft has been on a roll with .NET releases, it's been a 30 minute or so upgrade process for us to go from 5 -> 6 -> 7. Looking forward to the new Blazor model!
Re: Asp.net Core updates in .NET 8 Preview 1
#4Blazor United looks ambitious but sounds great! The goal feels similar to that of Remix.run and a few other frameworks that are blending SPA/SSR. I do wonder about the scalability of the Blazor Server mode which requires live and "sticky" SignalR connections.
I have the same question, will Blazor United SSR still require a persistent SignalR connection? That's kind of a dealbreaker.
Re: Asp.net Core updates in .NET 8 Preview 1
#5I wonder if it'll be possible ever to do Native AOT if you rely on Newtonsoft (which is reflection heavy, last I heard). Yes, yes, I know, use System.Text.Json, but I already have all this code relying on Newtonsoft-y things :(
Re: Asp.net Core updates in .NET 8 Preview 1
#6I have been using Blazor Server for a project at work.....Honestly, it is so much better than using .Net MVC/Core with js sprinkled in.
I developed stuff in java for android, swift for ios, and now mostly work in c#, SQL, .Net MVC/Core, blazor. Microsoft stack feels pretty good to me. Getting a start up job is a bit difficult, I came across two startups using microsoft stack and only one paid SV money.
C#/.Net does have a pretty stable job market but pay is a bit lower.
Re: Asp.net Core updates in .NET 8 Preview 1
#7I wonder if it'll be possible ever to do Native AOT if you rely on Newtonsoft (which is reflection heavy, last I heard). Yes, yes, I know, use System.Text.Json, but I already have all this code relying on Newtonsoft-y things :(
It's worth the work heading to System.Text.Json - even if only to make staying up with .NET easier for yourself.
It had a bit of a rough start but it seems far more interoperable on weird edge cases than Newtonsoft now, so all the "Newtonsoft-y" things you're doing might evaporate.
Re: Asp.net Core updates in .NET 8 Preview 1
#8Blazor United looks ambitious but sounds great! The goal feels similar to that of Remix.run and a few other frameworks that are blending SPA/SSR. I do wonder about the scalability of the Blazor Server mode which requires live and "sticky" SignalR connections.
I’m 50% sure Blazor United is a soccer team
Re: Asp.net Core updates in .NET 8 Preview 1
#9I have been using Blazor Server for a project at work.....Honestly, it is so much better than using .Net MVC/Core with js sprinkled in. I developed stuff in java for android, swift for ios, and now mostly work in c#, SQL, .Net MVC/Core, blazor. Microsoft stack feels pretty good to me. Getting a start up job is a bit difficult, I came across two startups using microsoft stack and only one paid SV money. C#/.Net does h…
What kind of setup do you have to avoid users noticing the drop of their websocket connection due to a deployment? Blazor Server development experience is very good, but even for an intranet application, it can have a poor user experience by default due to the requirement of a persistent connection.
Re: Asp.net Core updates in .NET 8 Preview 1
#10I have been using Blazor Server for a project at work.....Honestly, it is so much better than using .Net MVC/Core with js sprinkled in. I developed stuff in java for android, swift for ios, and now mostly work in c#, SQL, .Net MVC/Core, blazor. Microsoft stack feels pretty good to me. Getting a start up job is a bit difficult, I came across two startups using microsoft stack and only one paid SV money. C#/.Net does h…
The trick is to start the company yourself. :) We're 3 years in and full .NET stack.
Is your project an internal app or public?
I'm cautiously optimistic about Blazor Server but I'm not sure I like the sticky SignalR requirement. The expectation seems to be that the backend server will keep around a lot of state (cough viewstate?) in memory associated to that session. It's a very convenient dev experience for sure, but it seems difficult to scale beyond internal business apps.