how to convince the guy who works with me that is worth updating .net framework 3.5?
I work in a small company with 4 other programmers wich one of them is 10 years on the company and know how every of our apps work, and the other 3 are begineers.
So I'm building this app with .net framework 3.5. I'm still a beginner but I know there are benefits to update but I tried talking to the head programmer and he said it is bullshit to update, and I need to focus building the pages of the webapp.
Since he gave me the base code for the app I just need to create the pages.
But it is driving me crazy to use a older version of net framework
Also we are not using any MVC or entity framwork or any frontend framework. is that a problem? should we use any of these?
Sorry I'm a begineer and I'm learning a lot recently
18 Replies
Does people still use this version?
it's not easy to update a legacy codebase to net core. if you're a beginner you won't manage that task. if you're doing a new app then yes, using framework is a bad idea
how much code is the project already? upgrade now if it's not too much boilerplate.
don't listen to people that have a favorite version of something and don't stay current. they are creating a situation where they will not be able to work on new projects and will ultimately become unhirable.
he said it is bullshit to update, and I need to focus building the pages of the webapp.this roughly translates to him saying "i'm only comfortable with version x.y.z, so don't question me and do the work instead of making me improve"
Fx 3.5 is EOL, that should be reason enough
Unless it's some massive project that's not easily upgraded, the guy is just being a graybeard stagnated ass living in the past
Plenty such people in the industry, alas
I think there is no dependencies that the project depends on... all the SQL inserts and select needs to be done by hand by sql strings.
I believe using entity framework is easier right?
100% this haha
just to mention
Jquery was version 1.3
Thankfully there was jquery migrate
runat="server"... is this Webforms?
If so, your upgrade path ends at .NET Framework 4.8 anywayyes webforms
My condolences
is .NET Framework 4.8 up to date right?
-ish
It's the latest version of .NET Framework
And the last version of it
It'll get critical fixes and stuff, but it's the end of the line
.NET is what's under active development
So they will never be .NET Framework 4.9, but there will be .NET 8, 9, and so on
Unless Microsoft decides to fuck around with the naming yet again 
this naming convention for .net confuses me everyday
Yeah
Microsoft sucks ass at naming
so basically there is no way to port a .NET Framework to .NET ?
just rewriting in this case
There is a way, sure
Just not Webforms
Microsoft, rightfully so, ditched it
So .NET Framework 4.8 is the latest version that supports Webforms
.NET Core, .NET, and so on do not
The closest similar tech would be either Blazor Server, or maybe Razor Pages
But they will require a near-full rewrite
Depends of course on how modular your original codebase was, you might be able to bring some code over, sure
that sucks
my idea is basically finish this project and try to port to the newest framework in this case
4.8 it is, then
Unless you want a rewrite in Blazor Server or some such
.NET framework (sometimes called just .NET) is the windows-only legacy version.
.NET Core is cross platform and is optimized better. Starting from version 5, they rebranded it to .NET (dropped Core).