I hate that I can't edit a partial or a layout without a complete re-build. It was honestly better before hot reload days when views didn't need compiled
@@dougfunk01 Hmm, hot reloading changes to your layout and partials should work. I tried out a few simple cases with .NET 9 and Visual Studio 17.12 and it seemed to work fine. Could you please open a Visual Studio feedback ticket with details on the specific problem you're seeing so we can investigate further?
Chapters is not a new concept in youtube! The channel author should adopt this concept and apply it. Given the fact that these videos are educational and marketing content, it emphazies the need of a chapters availability more ever!
Is it possible to configure Blazor in .NET 9 to automatically transition from SSR (Server-Side Rendering) to WASM (WebAssembly) for interactivity, similar to the behavior shown in the InteractiveAuto render mode, but without relying on the server rendering via WebSocket (Interactive Server phase)?
I've been working APIs on .NET 7 and 8, but when switching to 9 the browser does not show the swagger. I tried in several computer with the same results, is there anything that has changed?
I installed VS 17.12 last night and today my 8.0 Blazor projects stopped building. Apparently, the VS update DELETED the 8.0 LTS SDK off my system!!! Why would it do that? And the 9.0.100 SDK has a bug in one of its target files preventing the build. I had to manually re-install 8.0.404 and set up a global.json file just to get my solution working again. ApplyCompressionNegotiation task failed because it's in the target file twice.
yeah, it purged 8.0 SDK for me as well, it was kinda surprising. However migration went smoothly on my project, I managed to run it on .NET 9 with no issues so far.
@@danroth27 Took 13 hours of banging my head against my desk, but I figured it out. It didn't like that I had a wwwroot in a child class library project where all my blazor pages were. I was sharing that with the wasm and server projects and it couldn't combine them since the upgrade. Worked fine with the 8.0 sdk. I updated the reported issue with the VS team and told them to close the issue.
For Blazor Server: What happens when socket connections are exhausted at the server side? I mean when the socket connection limit is reached, 64k theoretical max?
In context to the Maui and WebApp project template. How would I share local Identity user authentication between Maui and Web? As I understand it the SignInManager has a dependency on HttpContext which would not work for logging in a user in Maui.
The way I did it is to use WebAuthenticator with a URL to my web login screen. On successful login I return a JWT to the mobile app. SignInManager is only used in my Web side components.
@@rlangton76 Would this work with local accounts? What I am hoping to do is reuse the AspNetUsers table and as much of the register and login plumbing as possible. My goal is to create a Maui Blazor desktop app that can login to a local sqlite database using IdentityUser
The blazor hybrid not give me best experience like react, angular. It take time to hot reload and some time hot reload is bug and some time i got problem about browser cache wasm file. I still waiting to see stable blazor version that i can use full stack dotnet on my projects
All the presentations and demos of Blazor look great, everything is fantastic, everything is easy, everything is magical... and then you crash into a real life project with Blazor and you just want to run away. So, you have WASM, Server Side, now together, now client render, now Interactive, now Automatic... a component inside a component inside another component and keep nesting components to the infinite... And now I going to create another component just for a label... Anyone feels the same? It's a pain. I'm sick of the counter page and the weather forecast page template... years and years with the same demos...
I agree, why do we need 16 render modes that are very difficult to troubleshoot. Working with Blazor and Maui has been a very painful learning experience. Just hoping I can get across the finish line with the app I'm building, but some of these strange behaviors take me weeks to figure out and come to some hacky resolution.
This is so not true! if you having a bad experience why don't you use just WebAssembly? it is the best experience you can get! super fast, beautiful and really magical.
I often wonder why nobody is yet talkikng about project progress designed to convert legacy frameworks to Blazor. There's a reason why many people are (mistakenly I think) compare Blazor to Silverlight. Start talking up how MS is investing in conversion frameworks from say Webforms and Winforms to Blazor and you'll get a real ROI in terms of PR. People want more than just "trust us, we'll not Silverlight Blazor". Investing commitments will walk that talk.
2:23 Aspire
14:09 Detect render mode
16:46 Reconnection for Interactive Server Rendering
18:53 Blazor hybrid app
24:55 MapStaticAssets() instead of UseStaticFiles()
25:33 @Assets
28:50 OpenAPI support
33:12 SignalR
34:40 HybridCache
One of the biggest headaches in developing with .Net in VS 2022 is hot reload. Any improvements there?
Agree. Hot reload is almost unusable.
They know about it but nothing is being done.
I hate that I can't edit a partial or a layout without a complete re-build. It was honestly better before hot reload days when views didn't need compiled
@@SimpMcSimpySo, you have inside information from within Microsoft backing up your statement? If not, it’s just am assumption based on … nothing….
Couldn't agree more! Very painful!
@@dougfunk01 Hmm, hot reloading changes to your layout and partials should work. I tried out a few simple cases with .NET 9 and Visual Studio 17.12 and it seemed to work fine. Could you please open a Visual Studio feedback ticket with details on the specific problem you're seeing so we can investigate further?
congratulation to the team with delivering those improvements! Thanks
Chapters is not a new concept in youtube! The channel author should adopt this concept and apply it. Given the fact that these videos are educational and marketing content, it emphazies the need of a chapters availability more ever!
Is it possible to configure Blazor in .NET 9 to automatically transition from SSR (Server-Side Rendering) to WASM (WebAssembly) for interactivity, similar to the behavior shown in the InteractiveAuto render mode, but without relying on the server rendering via WebSocket (Interactive Server phase)?
.net 9 is out. Long live .net X
then .net 11 and then .net 1
In 26:11 you're mentioning that you're new TagHelper for generating ImportMap for cshtml files, what is that tag helper?
I've been working APIs on .NET 7 and 8, but when switching to 9 the browser does not show the swagger. I tried in several computer with the same results, is there anything that has changed?
How and where would you implement identity like the .net 8 template does with a tickmark in the template wizard?
Did one project load all 3 interfaces? Web,Desktop,app?
I installed VS 17.12 last night and today my 8.0 Blazor projects stopped building. Apparently, the VS update DELETED the 8.0 LTS SDK off my system!!! Why would it do that? And the 9.0.100 SDK has a bug in one of its target files preventing the build. I had to manually re-install 8.0.404 and set up a global.json file just to get my solution working again. ApplyCompressionNegotiation task failed because it's in the target file twice.
yeah, it purged 8.0 SDK for me as well, it was kinda surprising. However migration went smoothly on my project, I managed to run it on .NET 9 with no issues so far.
@travordennis Can you share the GitHub issue number for the .NET 9 SDK issue you hit? I'd like to follow up to make sure it's getting addressed.
@@danroth27 Took 13 hours of banging my head against my desk, but I figured it out. It didn't like that I had a wwwroot in a child class library project where all my blazor pages were. I was sharing that with the wasm and server projects and it couldn't combine them since the upgrade. Worked fine with the 8.0 sdk. I updated the reported issue with the VS team and told them to close the issue.
is there support for .NET Aspire on IIS?
No. .NET Aspire doesn't support running web apps on IIS or IIS Express.
For Blazor Server: What happens when socket connections are exhausted at the server side? I mean when the socket connection limit is reached, 64k theoretical max?
Aspire is great, but its not new to dotnet 9 - would have appreciate chapters so I could easily skip it to the actual new stuff.
Is ther any docs on how to make this work in MVC?
In context to the Maui and WebApp project template. How would I share local Identity user authentication between Maui and Web? As I understand it the SignInManager has a dependency on HttpContext which would not work for logging in a user in Maui.
The way I did it is to use WebAuthenticator with a URL to my web login screen. On successful login I return a JWT to the mobile app. SignInManager is only used in my Web side components.
@@rlangton76 Would this work with local accounts? What I am hoping to do is reuse the AspNetUsers table and as much of the register and login plumbing as possible. My goal is to create a Maui Blazor desktop app that can login to a local sqlite database using IdentityUser
So... is merging blazor server with webassembly into one single project canceled or something?
where i cand see the code of this session?
I think this will greatly improve YARP performance
The blazor hybrid not give me best experience like react, angular. It take time to hot reload and some time hot reload is bug and some time i got problem about browser cache wasm file. I still waiting to see stable blazor version that i can use full stack dotnet on my projects
is there any plan to support hash routing?
What happened with Blazor United???!
It took 2 years to have the hybrid and web trmplate
All the presentations and demos of Blazor look great, everything is fantastic, everything is easy, everything is magical... and then you crash into a real life project with Blazor and you just want to run away. So, you have WASM, Server Side, now together, now client render, now Interactive, now Automatic... a component inside a component inside another component and keep nesting components to the infinite... And now I going to create another component just for a label... Anyone feels the same? It's a pain.
I'm sick of the counter page and the weather forecast page template... years and years with the same demos...
I agree, why do we need 16 render modes that are very difficult to troubleshoot. Working with Blazor and Maui has been a very painful learning experience. Just hoping I can get across the finish line with the app I'm building, but some of these strange behaviors take me weeks to figure out and come to some hacky resolution.
Is that component inside component loop same for other react etc.?
Just choose a render mode and stick with it. Don't switch to another unless you have a definite use case.
@@MB-or1kh if you have blazor hybrid app supporting both web and mobile there are legitimate reasons to have to use multiple render modes
This is so not true! if you having a bad experience why don't you use just WebAssembly? it is the best experience you can get! super fast, beautiful and really magical.
I often wonder why nobody is yet talkikng about project progress designed to convert legacy frameworks to Blazor. There's a reason why many people are (mistakenly I think) compare Blazor to Silverlight. Start talking up how MS is investing in conversion frameworks from say Webforms and Winforms to Blazor and you'll get a real ROI in terms of PR. People want more than just "trust us, we'll not Silverlight Blazor". Investing commitments will walk that talk.
I tried Blazor in the past, no hot reload make me crazy.
Still no hot reload today, then its a pass again for me.
@@kalist8938
There is hot reload in Blazor, the server side HR works great, the wasm one a bit slow.