99% of my Blazor problems are solved by using Rider on MacOS instead of Visual Studio on Windows. I will use Rider on Windows for this going forward...
Comments
Log in with your Bluesky account to leave a comment
Using VS for any kind of .NET development feels so weird nowadays after years of using Rider. On customer AVD I need to use it and I'm struggling every time. For example clicking "Find all references" and "Find All" results opens source files in a completely different window than I want...
I understand if you’ve moved on and can’t be bothered, but if you wanted to expand on the specifics I would love to know what the issues are. Sadly I suspect we know about them all :(
Here, GitHub, or my first name dot last name at microsoft dot com. You can probably even message on teams 🤷♂️
Source generators sometimes produce incorrect code that makes the project uncompilable, so you must track down the culprit (last time a @typeparam for unknown reason). I see this problem in Rider as well, of course. Weird intellisense crashes in razor editor. (1/3)
Hot reloading doesn't work 90% of the time.
@rendermode ServerInteractive" sometimes produces exceptions related to something with JavaScript (invalid character in string). Re-run it a couple of times (or clean obj/bin folders), and it magically works again for some reason. (2/3)
It's not a deal breaker for me, but it's super frustrating because I work with someone with little experience in C#/.NET, and I always have to make excuses. "It's usually not this bad."
My impression is that the quality is not on par with the rest of the tooling.
It's amazing how much of a difference the IDE can make! Everyone has their own preferences and workflows. I personally prefer a more lightweight code editor for anything but game development.
Wait is rider that good for blazor? I don’t always work on blazor projects (mainly js, with nuxt) but I do contribute to some blazor projects at work and do not like the workflow with VS or VS code and blazor.
Blazor is in such an odd spot for me. Dotnet dev for ~15 years. But it doesn’t matter how hard I try. It always becomes clear to me that the only reason it exists is for language convenience & even then with heavy consequences. Yet every comment on .NET videos rave about it. I’m missing something
Comments
Here, GitHub, or my first name dot last name at microsoft dot com. You can probably even message on teams 🤷♂️
Source generators sometimes produce incorrect code that makes the project uncompilable, so you must track down the culprit (last time a @typeparam for unknown reason). I see this problem in Rider as well, of course. Weird intellisense crashes in razor editor. (1/3)
@rendermode ServerInteractive" sometimes produces exceptions related to something with JavaScript (invalid character in string). Re-run it a couple of times (or clean obj/bin folders), and it magically works again for some reason. (2/3)
My impression is that the quality is not on par with the rest of the tooling.
I only use my mac at home. At my office I use Windows. Blazor was not my choice, I'm just along for the ride 😁
I got so frustrated with Blazor earlier this year I moved to Next.JS and not looked back. Integrated into Aspire too.
APIs are all still C#, just the FE. The hot reload/ iteration cycle is perfect for FE dev work.