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
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.
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
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.
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!
I really enjoy all of Daniel's recent presentations; very easy to understand and made me accepted/appreciate major Microsoft .NET features.
.net 9 is out. Long live .net X
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.
I think this will greatly improve YARP performance
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
is there any plan to support hash routing?
where i cand see the code of this session?
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.
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