✅ Need Advice: Choosing the Right .NET Version for Our Project
Hello everyone, we need some advice. We are computer science students working on our third-year (final) project, which is a banking website. Our internship supervisor recommended using .NET 6 because he said it's more stable. However, when we checked online, we found that .NET 6 is 'out of support.' We contacted him, and he said it's not a big issue, but if we want to work with another version like .NET 7 or .NET 8, we have the choice.
We're not beginners in web development, but we are beginners in .NET, so we're unsure what to do. On one hand, an older version like .NET 6 might have more tutorials available on YouTube. On the other hand, choosing a supported version like .NET 8 might be a better option.
We'll be using Visual Studio 2022 for development.
What would you recommend for us?
26 Replies
the most recent version of .net is .net 9, which has "standard term" support until may 2026. .net 8 is the latest "long term" support version, lasting until nov 2027.
these figures don't really matter in your situation and i would generally recommend being on the latest version.
there may be more tutorials using .net 6, but generally, features from .net 6 will still work in .net 8 and 9. more recent versions add some more features that might be nice to know about, but you can probably still reach your goal without knowing about them. newer versions also add more stability and better performance.
you should not choose .net 6 or .net 7, as both are out of support
(and it's a bit concerning that your supervisor suggested those in the first place)
Unknown User•3w ago
Message Not Public
Sign In & Join Server To View
Thank you all for your advice! I really appreciate it.
I forgot to mention that we're using Angular for the frontend.
Anyway, would you recommend going with the latest .NET version, or is it better to stick with the long-term support (LTS) version ? (I mean .NET 8 or 9, since both are still supported).
As for my concern about tutorials, I mentioned it because while learning Angular, I was using version 19, but most tutorials were for Angular 16, and there were a lot of differences. I had to do a lot of research and fix bugs with ChatGPT to make things work. That’s why I was worried the same might happen with .NET.
Again, thanks a lot for your help!
Unknown User•3w ago
Message Not Public
Sign In & Join Server To View
could you ellaborate why you would avoid Razor/Blazor/Mvc for something serious and opt for React/Vue/Angular/NextJs instead? And what counts as something serious in the first place
Unknown User•3w ago
Message Not Public
Sign In & Join Server To View
will watch it thanks. My personally prefered tech stack is a Asp.Net Core WebApi backend with a React frontend so I think we share that preference, but I was surprised to hear that razor pages/blazor should be avoided.
Razor pages is fairly new as a replacement of MVC, and Blazor is fairly new too and was praised as that new fancy thing with Webassembly and stuff so I thought both these approaches are up to date and quite popular. Maui integrates Blazor too for hybrid apps that run in browser and natively so it can't be very evil, so I thought @TeBeCo
so If I understand you right then razor pages is fine for some small app when you wanna stick to mostly c# and not wanna learn JS/TS, and blazor is just never a good choice cuz its dying out?
Unknown User•3w ago
Message Not Public
Sign In & Join Server To View
why tho?
Unknown User•3w ago
Message Not Public
Sign In & Join Server To View
I really like Blazor and use it exclusively for my personal projects and work.
But at work we just got a small internal website.
As ToBeCo said you will have to decide if you can live with certain drawbacks of each of the blazor models.
Server Side will require a constant Websocket. That can be problematic, because scaling those is really hard.
I'm not sure at what point you run into problems but I have heard numbers in the hundreds of concurrent users depending on your server.
Blazor WebAssembly poses a longer initial load time, because the browser has to fetch the. Net runtime on the first visit.
Also all your WASM code is accessible to the end user. There are no secrets in your client application code. Thats not too different from other UI technologies but always something you have to keep in mind for security.
Then there is the new auto mode. It will first open a WS connection and run in Server Mode. Then download the runtime in the background and switch to WebAssembly on the next visit / navigation.
This technically alleviates the WASM problem of a slow initial load time. And also the scalability issue of Server. But you win a lot of technical complexity.
Unknown User•3w ago
Message Not Public
Sign In & Join Server To View
Auto uses WS only if the WASM isn't cached in the browser
Unknown User•3w ago
Message Not Public
Sign In & Join Server To View
Most pages should work in WASM only. If you have Server only components on most pages you loose the advantage of auto and should just run Server
Because then as you said we need a WS connection nearly all the time. And that is the exact problem Auto tries to solve
Unknown User•3w ago
Message Not Public
Sign In & Join Server To View
I see thank you guys
what about this, do you suggest Avalonia instead? And why is that?
Unknown User•3w ago
Message Not Public
Sign In & Join Server To View
when I did it was because customer wanted a native app, not a webapp to have the app installed on devices rather than accessing via browser
Unknown User•3w ago
Message Not Public
Sign In & Join Server To View
so in that case what framework is prefered? I went with Maui just because lacking skill to judge how good frameworks are, and because its officially from microsoft
oh yea it was a requirement for me to write the whole app with just one c# codebase for different platforms. I didn't wanna learn Java and Swift
Unknown User•3w ago
Message Not Public
Sign In & Join Server To View
I see so avalaonia wasn't even an option. Any other options besides Maui I could go with?
Unknown User•3w ago
Message Not Public
Sign In & Join Server To View
I'll check it out 🙂
If you have no further questions, please use /close to mark the forum thread as answered