← Back to context

Comment by qingcharles

4 days ago

This thing has barely changed in the ~30 years I've been using it. There's definitely room for some more improvements.

11 comments

qingcharles

Reply
sumtechguy  4 days ago

You can divide visual studio into 4 era's. The vs6 (we smashed all of our dev tooling together and its integrated decently) era, the vs2002/vs2003/vs2005 (we broke it all and you will like it and never speak of C++ again), vs2010 era (we fixed all of that from 2002 sorry about that), vs2017/vs2022 (it updates from the internet and takes forever to install and now does everything).

The problem is MS is unwilling to stick with anything dev wise. The whole ecos system is a littered realm of half forgotten techs that may or may not be supported anymore. Wrapped with very confusing messaging to the devs what to use.

  • tracker1  4 days ago

    I prefer VS Code... though MS has for better or worse kept the .Net tooling relatively weak. I'll use Rider or VS on a few occasions... then retreat back to Code as much as I can.

    For split web projects, definitely work on the web ui in VS Code.

  • jcotton42  4 days ago

    VS2017 was the introduction of the modern VS installer that is way faster than the prior ones.

    • malkia  4 days ago

      Also (since 2015) forward/backward (to a degree) CRT compatibility.

      https://learn.microsoft.com/en-us/cpp/porting/binary-compat-...

      This saved so much time, space and support - where previously we had to recompile stuff, and if you had Maya/MotionBuilder/etc plugin it had to use the right compiler.

      Also now even with newer IDE you can instruct the project to use older (or even better - a specific) version of the toolchain.