1. 6

  2. 3

    There were two things that bugged me the most about VS2015:

    1. VsHub had a memory leak, this was most noticable when debugging a program (this actually cause a system crash once)
    2. IntelliSense crashed within minutes of opening my main project (Postage, https://github.com/workflowproducts/postage), so I had only basic syntax highlighting

    It seems (so far anyway) that both of these issues are fixed in VS2017. Microsoft has really done well these past few years.

    1. 2

      The performance improvements and live unit testing are particularly interesting. I’ll be sure to give it a test later tonight.

      Here’s a pretty comprehensive feature list: https://blogs.msdn.microsoft.com/visualstudio/2017/03/07/visual-studio-2017-productivity-performance-and-partners/

      1. 1

        Live unit testing would definitely motivate me to write more tests. The UX around running tests in the IDE is pretty suboptimal IMO (thinking of the Test Explorer pane here) so any improvements will be huge.

        1. 1

          Update: Downloaded it last night, but my projects are failing to build because the dotnet.exe binary is throwing an error code. I’m in talks with support.

        2. 1

          “CMake support for C++. Support for CMake is now available in Visual Studio 2017. You can start coding by directly loading your CMake projects in Visual Studio. It is easy to switch between configurations provided by CMake and further configuration is also supported via CMakeSettings.json file that sits in the same folder as CMakeLists.txt file.”

          All my applications have a Visual Studio project on Windows and CMakeLists.txt file on everything else. It would be great to use CMake on every platform (And yes I know technically I could generate a Visual Studio project from the CMake file on Windows already, but there were still two projects in each application.