❔ Which should I use for windows application net framework 4.8 or net 5.0
I currently need to use a tool called WinAPIDriver it supports currently pre release 5.0 net core and the other version is 4.8 , would it be a good idea to use 5.0 net core since it's outdated? I can't use high version, or should I stick to 4.8 framework?
15 Replies
GitHub
Releases · microsoft/WinAppDriver
Windows Application Driver. Contribute to microsoft/WinAppDriver development by creating an account on GitHub.
Framework 4.8 is more outdated than Core 5.0, so use Core if you can
My 2 cents: Always stick to the core lineup. Avoid Fx when possible
A lib supporting .NET 5.0 isn't necessarily outdated, they might have just targeted .NET 5 when developing it. You could likely use it in .NET 7 even
my collegue at work is insisting to use 4.8 because the net 5 core version of winapp driver is still in prerelease, I've tested it myself works for what I want to use..
I was just thinking soon they ll go to net 6 or 7 this application so why notdo 5.0?
how do I deal with this situation
as I also think net5.0 is better for the future of the project
I mean this has become office politics now
eh ikr 😄 but from you experience
am I wrong?
or
No, I'd say your choice would be perfectly valid, I'd try to avoid Fx with a 10 mile pole whenever possible
like not trying to start a fight he doesn't seem to know difference between net core and net framework, so this is why im here
trying to follow best practices 🙂
If your colleague is above you, there's not a lot you can do. Just make sure that when presenting the idea you try to sell it to them as their idea to use .NET 5
Otherwise there's a chance they go butthurt defensive and double down on Fx
Thanks for advice ❤️
$.net
.net framework as always been named .net framework (the runtime) / run only on windows on x86/x64 cpi
.net has always been a marketing term
so:
.net is still a thing (it's still marketed)
.net framework is dead
.net core is a runtime that replaced the dead .net framework / run on Windows / Mac / Linux - and several CPU arch such as ARM/ARM64
.net core (the runtime) got renamed to match the marketed term too
so now .net represent both the runtime and the platformI would approach it by saying that if you use the library that targets .NET, that enables you to write the application in .NET 6 or .NET 7, but if you use the version that targets .NET Framework 4.8, you are tied to that version for your application.
And it's a pain to convert it later
Was this issue resolved? If so, run
/close - otherwise I will mark this as stale and this post will be archived until there is new activity.