| ▲ | neonsunset 7 days ago |
| This has to do with specific framework and does not translate to the overall experience (for example targeting iOS is pain because Apple deprecates versions quickly, so downstream dependencies have to match this too). You can open and build a back-end application that targets e.g. netcoreapp2.1 (6 years old target) just fine, it might require installing you an archived SDK for the build to succeed (which you can download regardless, it will complain that it is EOL though) but it's an otherwise simple procedure. For library code it's even easier - if you have netstandard2.0 target, it will work anywhere from .NET Framework 4.6.1 to the latest version without requiring any maintenance effort whatsoever. On Windows, Visual Studio will happily work with .NET Framework 3.0 (which is ancient) and more. |
|
| ▲ | thrw42A8N 6 days ago | parent | next [-] |
| If you used pure Node.js, you wouldn't have any problems whatsoever, too. |
| |
| ▲ | neonsunset 6 days ago | parent [-] | | Unlike Node projects, your dependencies don't break - they stay on nuget.org, and the projects compile just like they did when they were first implemented. Upgrading dependencies and project target is subject to the same restrictions as in other good languages. I know for sure that I can clone a random project on Github, hit `dotnet build` and usually expect it to work on the first try. The rate of bitrot for average unmaintained JS project cannot be compared. The average dependency graph of a .NET project is going to be 10 times smaller too. | | |
| ▲ | MrJohz 6 days ago | parent | next [-] | | This is true for NodeJS as well - dependencies on NPM cannot be removed, so at long as NPM keeps running, and as long as you've got a lockfile that precisely specifies all dependencies, you shouldn't run into problems running older projects. (Certainly I have never had an issue with this - the problems, if they occur, are always around upgrading. And like you say, this is subject to much the same issues in every ecosystem). If this isn't enough, there are tools like Yarn which encourage vendoring dependencies to ensure that as long as you have a copy of the repository, the yarn CLI, and a valid version of NodeJS, you can always run the project. | |
| ▲ | thrw42A8N 6 days ago | parent | prev [-] | | Yeah, that's nice, unfortunately it's the built-in Microsoft stuff like WPF that keeps breaking between versions. |
|
|
|
| ▲ | a1o 6 days ago | parent | prev [-] |
| Note Microsoft still removes downloads of previous versions of Visual Studio that aren't the latest - now you can only download VS2022 unless you have some mysterious paid account that has access to those - I don't have in either my personal or my corporate so I don't know the details |
| |
| ▲ | trinix912 6 days ago | parent [-] | | This is true and is a pain if you’re stuck on something like Windows 7/8.1 (or 10 in the future). The installer being a web installer that auto-updates on start also means that downloading an older one doesn’t help at all. The only way seems to be to pirate the Enterprise offline installer which of course isn’t really an option. |
|
