5 ms·

I would personally prefer you to fix the multitude of things that don't work well in Visual Studio and library issues that are continually pushed back as "won't

I would personally prefer you to fix the multitude of things that don't work well in Visual Studio and library issues that are continually pushed back as "won't fix" or "upgrade to .Net5/6" as opposed to always racing forwards to the horizon. Even those of us who are actively migrating applications are stuck with web forms, netfx and dotnet core 2/3 and will be for years, so it would be nice that we felt some love rather than being left behind. MS are starting to feel like Apple where you only have value if you can keep up.

GiorgioG 5y ago
Nobody gets promoted for fixing bugs.
lloydatkinson 5y ago
> Even those of us who are actively migrating applications are stuck with web forms, netfx and dotnet core 2/3 and will be for years Well, the job market is pretty hot right now so I hear.
sedatk 5y ago
It's not perfect but MS has been investing in a scheme to make upgrades as easy as possible for the last five years, .NET Standard being the prime example. This way, we've been able to migrate our project progressively while keeping it up to date. We've been able to use .NET Core versions of libraries as long as they support .NET Standard 2.0. This is way better than "migrate fully or die".
symlinkk 5y ago
Why can’t you upgrade to the latest version? Sounds like tech debt. And Visual Studio is almost dead, why aren’t you on Visual Studio Code?
- Smaug123 5y ago
  … huh? Visual Studio is extremely not dead, they are literally about to release a 64-bit version after a massive rework. VS Code is a text editor which you can extend into being an IDE. Visual Studio is an IDE. There are many reasons why one might be unable to upgrade to the latest version of any given thing. For an example close to my heart of why one might be unable to upgrade to .NET 6 (or indeed to later versions of the .NET 5 SDK), there's the showstopping https://github.com/NuGet/Home/issues/10389 https://github.com/NuGet/Home/issues/10389.
- tester756 5y ago
  >And Visual Studio is almost dead, why aren’t you on Visual Studio Code? That's incredibly weird take in my opinion. Whenever I use VS Code, then I feel huge gap between this and real VS with Roslynator extension.
password4321 5y ago
I was surprised to see there wasn't much discussion of this Joel Spolsky classic here: https://www.joelonsoftware.com/2002/01/06/fire-and-motion/ https://www.joelonsoftware.com/2002/01/06/fire-and-motion/ Think of the history of data access strategies to come out of Microsoft. ODBC, RDO, DAO, ADO, OLEDB, now ADO.NET – All New! [...] the end result is just cover fire. The competition has no choice but to spend all their time porting and keeping up Maybe Microsoft got out-fire-and-motioned by Node.js for a while but they're working extra hard cranking out new stuff.

GiorgioG 5y ago

Nobody gets promoted for fixing bugs.

lloydatkinson 5y ago

> Even those of us who are actively migrating applications are stuck with web forms, netfx and dotnet core 2/3 and will be for years Well, the job market is pretty hot right now so I hear.

sedatk 5y ago

It's not perfect but MS has been investing in a scheme to make upgrades as easy as possible for the last five years, .NET Standard being the prime example. This way, we've been able to migrate our project progressively while keeping it up to date. We've been able to use .NET Core versions of libraries as long as they support .NET Standard 2.0. This is way better than "migrate fully or die".

symlinkk 5y ago

Why can’t you upgrade to the latest version? Sounds like tech debt. And Visual Studio is almost dead, why aren’t you on Visual Studio Code?

Smaug123 5y ago
… huh? Visual Studio is extremely not dead, they are literally about to release a 64-bit version after a massive rework. VS Code is a text editor which you can extend into being an IDE. Visual Studio is an IDE. There are many reasons why one might be unable to upgrade to the latest version of any given thing. For an example close to my heart of why one might be unable to upgrade to .NET 6 (or indeed to later versions of the .NET 5 SDK), there's the showstopping https://github.com/NuGet/Home/issues/10389 https://github.com/NuGet/Home/issues/10389.
tester756 5y ago
>And Visual Studio is almost dead, why aren’t you on Visual Studio Code? That's incredibly weird take in my opinion. Whenever I use VS Code, then I feel huge gap between this and real VS with Roslynator extension.

password4321 5y ago

I was surprised to see there wasn't much discussion of this Joel Spolsky classic here: https://www.joelonsoftware.com/2002/01/06/fire-and-motion/ https://www.joelonsoftware.com/2002/01/06/fire-and-motion/ Think of the history of data access strategies to come out of Microsoft. ODBC, RDO, DAO, ADO, OLEDB, now ADO.NET – All New! [...] the end result is just cover fire. The competition has no choice but to spend all their time porting and keeping up Maybe Microsoft got out-fire-and-motioned by Node.js for a while but they're working extra hard cranking out new stuff.