Visual Studio 2017, Anyone using it yet properly?



  • How stable is it? Does it work? What are the bugs?


  • Garbage Person

    @lucas1 It's fine as far as we can tell.



  • Yeah, honestly it's pretty great. There are a lot of things hidden in the language options and such, but there's all kinds of great stuff in it. It even has docker service fabric projects!



  • @Magus said in Visual Studio 2017, Anyone using it yet properly?:

    It even has docker service fabric projects!

    I know what docker is but WTF is fabric?



  • It works great when I'm not using it at work. There is something about how it starts a new project that our current draconian security policies prevent it from actually completing. I can edit an existing project but not create a new one. So I create one in 2015 close it and open it in 2017 and move right along.

    Sad state of affairs here.

    At home 2017 works wonderfully!



  • @lucas1 Service Fabric is an Azure-based cloudy thing, where you build a giant network of microservices and they replicate as needed. It's kind of nice, and you can treat Docker images as services if needed for some reason, though that feature is new with vs2017.



  • @Magus Worth checking out. I've mostly been doing N-tier style arch for a while.



  • @lucas1 It's basically what you should pick if you have a system that would benefit from mass parallelization. If you aren't doing something like that, it doesn't help. Which is why I don't get why we're using it here for a website.


  • Dupa

    @Magus said in Visual Studio 2017, Anyone using it yet properly?:

    @lucas1 It's basically what you should pick if you have a system that would benefit from mass parallelization. If you aren't doing something like that, it doesn't help. Which is why I don't get why we're using it here for a website.

    It's cool and people wanna learn new stuff?

    That'd be my bet.



  • @Magus None of my work would require that tbh. Most of my performance problems are database so I tend to use a light weight db layer is using .NET over something like EF.

    Dapper does most of what I want and is much faster than EF.

    Thought I do all personal projects in python.



  • @lucas1 Well I've seen people use it for MMOs, and could imagine doing some kind of dwarf fortress thing with it.

    There are times when it really makes a huge difference, but I haven't been inspired enough to use it for anything myself yet.


  • kills Dumbledore

    I've been using 2017 at work since the official release. It's not a massive improvement over 2015, but it's nice and I've had no reason to go back to 15 or earlier



  • Just ran into an interesting thing... I currently have (had) VS2017 installed with only the 14393 SDK (not the 10240 one). Applied the most recent update. And couldn't compile (C++). The vcvarsall script sets things for the most current sdk (15063). Which it didn't install. So after updating, make sure you go back and modify the install to include that. Either that, or change the arguments to vcvarsall. I discovered you can call vcvarsall.bat amd64 10.0.14393.0 to setup a 64bit env for a specific SDK.


  • FoxDev

    @dcon That's... really dumb, actually. I mean, if you're gonna set everything to use a particular SDK, at least have the manners to install that SDK.



  • @RaceProUK said in Visual Studio 2017, Anyone using it yet properly?:

    @dcon That's... really dumb, actually. I mean, if you're gonna set everything to use a particular SDK, at least have the manners to install that SDK.

    That was my feeling! I lost a couple hours trying to figure out WTF had just happened... And since there's no longer a global SDK selector program like there used to be, it was not at all clear how to even target an SDK. (Read the source Luke!)



  • But yeah, I highly recommend looking in the Options, C# language specific section: You'll see a lot of resharper-y things that are just built in now.

    The new exception dialog is weird, but can be rather nice.

    And definitely try out MSTest2 stuff. It's a Nuget package, so you don't need a special test project type anymore, and if you use it, you can turn on live unit testing mode. It's not perfect, but having it built in is just amazing. I'm very interested to see where they take it.



  • I've been using it since it launched, although not for anything serious. It has a rather annoying regression where choosing Add -> new class doesn't automatically select a C# class like it used to :(


  • :belt_onion:

    @dcon said in Visual Studio 2017, Anyone using it yet properly?:

    The vcvarsall script sets things for the most current sdk (15063). Which it didn't install.

    That's weird, it installed 15063 for me, but then I installed it fairly recently. (And it installing 15063 then broke things for me back on VS 2015 because my WDK was version 14393, but I've updated that now so they match.)

    I'm using it for non-driver stuff (WDK doesn't have integration with VS 2015), and... meh? It's pretty good; I don't notice much difference from VS 2015 except that you can open property sheets.



  • @heterodox said in Visual Studio 2017, Anyone using it yet properly?:

    @dcon said in Visual Studio 2017, Anyone using it yet properly?:

    The vcvarsall script sets things for the most current sdk (15063). Which it didn't install.

    That's weird, it installed 15063 for me, but then I installed it fairly recently. (And it installing 15063 then broke things for me back on VS 2015 because my WDK was version 14393, but I've updated that now so they match.)

    I'm using it for non-driver stuff (WDK doesn't have integration with VS 2015), and... meh? It's pretty good; I don't notice much difference from VS 2015 except that you can open property sheets.

    I had a pretty basic VS install - desktop/C++ and UWP options (and one machine also has .net/desktop). After the upgrade, I had to specifically go in and modify the install and check the 15063 sdk. On all my machines.



  • 2017 installed the creators update SDK for me, but Microsoft says that update doesn't come out until tomorrow, despite the fact that I've been hearing about people getting it already. And updating my projects broke the XAML designer until I install the creator update. Not that the visual stuff matters much just yet: I know XAML rather well and am just doing basic structural stuff for now.



  • @Magus said in Visual Studio 2017, Anyone using it yet properly?:

    2017 installed the creators update SDK for me, but Microsoft says that update doesn't come out until tomorrow, despite the fact that I've been hearing about people getting it already. And updating my projects broke the XAML designer until I install the creator update. Not that the visual stuff matters much just yet: I know XAML rather well and am just doing basic structural stuff for now.

    You can download the Creators Update from MSDN now (I grabbed the ISOs last week). I have a nice squeaky clean VM image now. (Haven't updated any physical machines yet)


  • FoxDev

    @Magus It's possible to get the update early if you download a suitable tool from Microsoft



  • I'm honestly fine waiting. It's not that exciting.


  • :belt_onion:

    Yeah, not to pile on but to be specific the public release was April 5th and GA is tomorrow as you said. I grabbed it early as well because it updates Ubuntu to 16.04.


  • :belt_onion:

    Started a new Linux project on VS2017. First impression is that that project type is... still a work-in-progress. For a C file, had to switch run-time type information and thread-safe statics options off; those shouldn't have been passed through on a C file. Had to copy out include directories from my target machine (errr, why are you not interfacing with the local Linux subsystem yet? Seems like that would be a mega win). And warnings/errors don't include line numbers...

    1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\VC\VCTargets\Application Type\Linux\1.0\Linux.Common.targets(248,5): warning : conversion to 'uint16_t' from 'int' may alter its value
    1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\VC\VCTargets\Application Type\Linux\1.0\Linux.Common.targets(248,5): warning : conversion to 'int' from 'ssize_t' may alter its value
    1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\VC\VCTargets\Application Type\Linux\1.0\Linux.Common.targets(248,5): warning : conversion to 'int' from 'size_t' may alter its value
    

    But once it's set up, being able to write my code in VS with Intellisense, hit F7 to build and F5 to debug (the debugger seems to work great)?! I can easily see this quadrupling my productivity. If you think using Vim over SSH and gdb is comparable... you're quite simply a God damn lunatic.



  • @Magus said in Visual Studio 2017, Anyone using it yet properly?:

    It even has docker service fabric projects!

    Why there is a docker thing on VS if docker is linux-only?



  • @wharrgarbl The thing after the if in your statement is false.



  • @Magus said in Visual Studio 2017, Anyone using it yet properly?:

    2017 installed the creators update SDK for me, but Microsoft says that update doesn't come out until tomorrow, despite the fact that I've been hearing about people getting it already. And updating my projects broke the XAML designer until I install the creator update. Not that the visual stuff matters much just yet: I know XAML rather well and am just doing basic structural stuff for now.

    I'm wondering if it didn't install the SDK because I wasn't on 1703 yet... After updating Windows, VS2017 needed another update.


  • :belt_onion:

    @dcon said in Visual Studio 2017, Anyone using it yet properly?:

    I'm wondering if it didn't install the SDK because I wasn't on 1703 yet... After updating Windows, VS2017 needed another update.

    Not sure if that'd make sense; it installed 15063 for me while I was still on 14393.



  • Anyone running into performance problems when debugging with IIS? I find the menus and attach menus tend to get feel clunky.

    I am running ngrok / VS2017 / SQL Server 2016 and normally chrome / opera.


  • :belt_onion:

    @heterodox said in Visual Studio 2017, Anyone using it yet properly?:

    And warnings/errors don't include line numbers...

    This isn't a normal problem; this was a problem with the server pointing the client (in the absence of environment variables saying otherwise) to some antiquated g++ that didn't even support C++11. Now that I have a property sheet pointing it to the right compiler, warnings and errors have file and line number references. :D


Log in to reply