C#•11mo ago

✅ 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?

NNada Hello everyone, we need some advice. We are computer science students working on...

ero•2/15/25, 6:00 PM

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.

ero•2/15/25, 6:01 PM

you should not choose .net 6 or .net 7, as both are out of support

ero•2/15/25, 6:01 PM

(and it's a bit concerning that your supervisor suggested those in the first place)

TeBeCo•2/15/25, 6:10 PM

as a rule of thumb for webapp, go with latest
=====

TeBeCo•2/15/25, 6:10 PM

and upgrade when a version goes out

TeBeCo•2/15/25, 6:11 PM

aspnetcore is "mainstream enough" to be mostly easily upgradable for the entire api part

TeBeCo•2/15/25, 6:12 PM

if you're doing anything serious I wouldn't pick Razor/Blazor/Mvc for rendering

TeBeCo•2/15/25, 6:12 PM

i'd stick to React/Vue/Angular/NextJs for pure rendering

TeBeCo•2/15/25, 6:13 PM

==========

Our internship supervisor recommended using .NET 6 because he said it's more stable

sadly this is not an argument based on anything beside "his opinion"

TeBeCo•2/15/25, 6:13 PM

he would need to provide concrete fact on what's stable and what's not

NadaOP•2/15/25, 7:26 PM

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!

TeBeCo•2/15/25, 7:27 PM

Anyway, would you recommend going with the latest .NET version, or is it better to stick with the long-term support (LTS) version for more stability? (I mean .NET 8 or 9, since both are still supported).

regarding dotnet ecosystem, latest is fine

TeBeCo•2/15/25, 7:27 PM

it's less possible for NPM/NodeJs

TeBeCo•2/15/25, 7:27 PM

as long as you don't install tons of thirdpart, which are mostly useless, you're fine

TeBeCo•2/15/25, 7:27 PM

issue comes from third part most of the time on upgrade

TeBeCo•2/15/25, 7:28 PM

there's no legit reason to stay on LTS only

TeBeCo•2/15/25, 7:28 PM

unless you DO HIT a limitation

TeBeCo•2/15/25, 7:28 PM

which you only find out by ... hitting it

TeBeCo•2/15/25, 7:28 PM

quite rare

TeBeCo•2/15/25, 7:28 PM

for example

TeBeCo•2/15/25, 7:28 PM

don't use Newtonsoft / restsharp / nswag

TeBeCo•2/15/25, 7:28 PM

they are often used for whatever reason

TeBeCo•2/15/25, 7:29 PM

and will drag you down for different reason

TeBeCo•2/15/25, 7:29 PM

NSwag is "good" expect on major update

TeBeCo•2/15/25, 7:29 PM

the 2 other are just deprecated

TTeBeCo if you're doing anything serious I wouldn't pick Razor/Blazor/Mvc for rendering

Thalnos•2/16/25, 3:51 AM

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

TeBeCo•2/16/25, 5:36 AM

well mvc is .... dead (i mean mvc the thing with view), api controller are fine

TeBeCo•2/16/25, 5:37 AM

razor page is the simplification of mvc
it's ok if you build a simple site, not too much complex and want to keep it all c# (like a blog that that like 3-10 page)

TeBeCo•2/16/25, 5:40 AM

blazor is way more modern and have 3 model

TeBeCo•2/16/25, 5:40 AM

client side equivalent to spa

TeBeCo•2/16/25, 5:40 AM

server side but require active websocket

TeBeCo•2/16/25, 5:41 AM

hybrid (similar to nextjs) mixing wasm and server side so still websocket

TeBeCo•2/16/25, 5:42 AM

so blazor might be ok depending on many "if"

TeBeCo•2/16/25, 5:42 AM

if you're ok depending on websocket, that's fine

TeBeCo•2/16/25, 5:43 AM

because of websocket it's ok if your infra sustain your traffic (the number of active connection)

TeBeCo•2/16/25, 5:43 AM

in your case it's just a demo so it's probably fine

TeBeCo•2/16/25, 5:43 AM

but what about mobile experience?
do you need it for your project as a show case or not

TeBeCo•2/16/25, 5:46 AM

also

TeBeCo•2/16/25, 5:46 AM

blazor got a huge push from net5 net6 net7 net8

TeBeCo•2/16/25, 5:47 AM

but there was a recent interview with the main vision lead of blazor that made things awkward

TeBeCo•2/16/25, 5:47 AM

it's unclear what's the real investment in keeping blazor evolving

TeBeCo•2/16/25, 5:48 AM

https://youtube.com/watch?v=2uLGXe95kTo

YouTubeNick Chapsas

I Confronted Microsoft About Blazor's Future

Use code LAUNCH20 at checkout to get 20% off any Blazor course or bundle: https://bit.ly/4grVqp1
Subscribe to my weekly newsletter: https://nickchapsas.com

Become a Patreon and get special perks: https://www.patreon.com/nickchapsas

Hello, everybody. I'm Nick, and in this video, I will have a chat with Daniel Roth, the lead of Blazor about its ...

TeBeCo•2/16/25, 5:48 AM

better to watch it than trust my words

TeBeCo•2/16/25, 5:49 AM

.

using blazor still give you the benefits of possibly have a better end to end security since you don't have to deal with multiple/split release
you immediately get same site and xsrf etc ....

Thalnos•2/16/25, 8:17 AM

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

Thalnos•2/16/25, 8:18 AM

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?

TeBeCo•2/16/25, 8:19 AM

i wouldn't recommend maui except ultra rare scenario

Thalnos•2/16/25, 8:19 AM

why tho?

TeBeCo•2/16/25, 8:19 AM

blazor is mostly fine given av few restriction or analysis of the audience as said

TeBeCo•2/16/25, 8:20 AM

brb in 1 hour

✅ Need Advice: Choosing the Right .NET Version for Our Project

Similar Threads

Similar Threads

Similar Threads