So, we're quite some time ahead now since .net 2.0 was a sure shot.
Now looking at the current windows versions in use and the list of .net versions and it seems 3.5 is a smart idea to target when devices run anything below Windows 8, or the latest .net version for anything above and including Windows 8.
Anyone else able to chip in on this theory?
1DarkDTkHTm5ouTPrZ6bUHpH345x4uiAfV
For compatibility, obviously 2.0
(Nov 23, 2016 07:16 AM)$lick Wrote: For compatibility, obviously 2.0
That won't run on newer devices, as that requires .Net 3.5, which is not included by default anymore
1DarkDTkHTm5ouTPrZ6bUHpH345x4uiAfV
DO NOT DEAL WITH THIS MEMBER
I like the overall improvement and features that they added to the .net 4 framework. Can't speak about .net 2.0 or any other due to the fact I rarely use the older frameworks.
DO NOT DEAL WITH THIS MEMBER
I always use the latest.
You can always use 2.0 I think as with backwards compatibility it will work on any system.
(Nov 23, 2016 08:48 AM)Ninja Wrote: I always use the latest.
You can always use 2.0 I think as with backwards compatibility it will work on any system.
2.0 is provided by the 3.5 package (CLR2), which isn't installed by default on windows 10... :(
1DarkDTkHTm5ouTPrZ6bUHpH345x4uiAfV
DO NOT DEAL WITH THIS MEMBER
(Nov 23, 2016 08:50 AM)DarkDelta Wrote: 2.0 is provided by the 3.5 package (CLR2), which isn't installed by default on windows 10... :(
It really doesn't matter as .NET 4.* is backwards compatible with older version of .NET, I'm not sure if it goes all the way back to 1.1, but 2.0 will run on a system that has just 4.* installed as long as it has the following configuration file. No one can give you a 100% guarantee that you application will run on older/newer version you will have to test the application yourself.
If you are developing a new application and targeting .NET 2.0 you shouldn't have a problem, as if you are using an application made a long time ago then that's where you may face problems.
Code <configuration>
<startup>
<supportedRuntime version="v2.0.50727" />
<supportedRuntime version="v4.0" />
</startup>
</configuration>
Quote:The .NET Framework 4.5 and its point releases are backward-compatible with apps that were built with earlier versions of the .NET Framework. In other words, apps and components built with previous versions will work without modification on the .NET Framework 4.5. However, by default, apps run on the version of the common language runtime for which they were developed, so you may have to provide a configuration file to enable your app to run on the .NET Framework 4.5. For more information, see the Version compatibility for apps section earlier in this article.
I would've thought by now someone would have stopped this thread in its cold tracks by simply stating ....
Code Use Newer Visual Studio if like .. Just Target The Specific Framework ie. vf2.0 - vf4.62
{ Vi Veri Universum Vivus Vici }
(Nov 23, 2016 10:10 AM)#Kat Wrote: I would've thought by now someone would have stopped this thread in its cold tracks by simply stating ....
Code Use Newer Visual Studio if like .. Just Target The Specific Framework ie. vf2.0 - vf4.62
It's not about VS, it's about the runtime, and current versions in use, and what can be considered as the minimum version now.
I'm thinking that 3.5 is the current minimum version that'll run everywhere.
1DarkDTkHTm5ouTPrZ6bUHpH345x4uiAfV
I'd still say 2.0 is still the most compatible. I haven't had issues running a 2.0 framework application on windows 10. At the very least it will pop up a dialog saying it needs 2.0 installed. One click of a button and it installs it within a couple minutes. Most users shouldn't even have that come up as there is still a lot of applications that require 2.0 Id assume?
DO NOT DEAL WITH THIS MEMBER
I would say that it depends on what kind of project you develop.
Sometimes framework 2.x could be a better option rather than using the latest framework for your applications.
(Nov 23, 2016 03:14 PM)Marwix Wrote: I would say that it depends on what kind of project you develop.
Sometimes framework 2.x could be a better option rather than using the latest framework for your applications.
2.x isn't delivered as a standalone .net version, 3.5 has 2.0 (it's both CLR2, basically 3.5 is 2.0 with extras)
I think 3.5 is the new minimum version to be honest!
1DarkDTkHTm5ouTPrZ6bUHpH345x4uiAfV
(Nov 23, 2016 04:34 PM)Zilog80 Wrote: Maybe it helps:
https://blogs.msdn.microsoft.com/astebne...of-the-os/
Basically as I thought, 3.5 if you target Win7 and below.
4.x.x if you want to target Win8 and above
1DarkDTkHTm5ouTPrZ6bUHpH345x4uiAfV
(Nov 23, 2016 04:48 PM)DarkDelta Wrote: Basically as I thought, 3.5 if you target Win7 and below.
4.x.x if you want to target Win8 and above
Meh, why would someone on windows 7 not have .net 4.0?
.net 4.0 is perfectly fine to develop in.
|