Quote Originally Posted by yereverluvinuncleber View Post
You can add suspicion as to how MS likes to deprecate technologies as it suits them. I am sure they would have fully deprecated .NET if their misguided attempts toward a tablet ecosystem had gone down as planned. It felt as if that plan was actually put in action for a while and not yet fully abandoned...

How else could MS force you to accept their latest strategy?
I personally think that is an unfair argument, the fact VB6 still runs on Windows 10. Considering VB6 was created around 1998 and officially support ended in 2008 the fact it still runs over 10 years later on operating systems that didn't even exist back then shows just how much MS values backwards comparability. Just about every version of .Net is still supported (even 1.0) and the existence of .Net core doesn't mean you can't continue to use .Net Framework.

Most new versions of the framework are almost 100% source compatible with earlier versions, although core can cause some problems due to it being a fairly major rewrite. Saying that though I have managed to take a couple of .Net 2.0 winform apps and convert them to Core 3.0 with no code changes and only about 30 minutes of changes to the .csproj files, most of which was just getting the correct packages installed.

Compare that to the likes of Apple who frequently throw away backwards comparability and force changes onto people....