Slashdot Mirror


Microsoft Releases Visual Studio 2017 (visualstudio.com)

Reader Anon E. Muss writes: Microsoft on Tuesday released Visual Studio 2017. The latest version of the venerable Integrated Development Environment supports a variety of languages (C/C++, C#, VB.net, F#, Javascript/Typescript, Python, etc.) and targets classic "Win32" desktop, Universal Windows Platform (UWP, also known as "Metro"), .NET, ASP, node.js, etc.). A "Community Edition" is available at no cost for individual developers and those working on open source software. "Professional" and "Enterprise" editions are available for corporate developers, at prices sure to shock whoever has to sign the check.

26 of 195 comments (clear)

  1. we know what vs is - did anything change? by xxxJonBoyxxx · · Score: 4, Insightful

    crappy summary for the slashdot crowd. we know what visual studio is - what we want to know is what, if anything, changed

    1. Re:we know what vs is - did anything change? by Anonymous Coward · · Score: 5, Informative
    2. Re:we know what vs is - did anything change? by chispito · · Score: 5, Insightful

      If you have to ask, the changes probably don't matter to you.

      Fantastic point. All news is dumb because if it were important to us, we would already know it.

      --
      The Daddy casts sleep on the Baby. The Baby resists!
    3. Re:we know what vs is - did anything change? by david_thornley · · Score: 2

      a) yes, it always has.

      Ask a C++ developer sometime about Intellisense. We're using VS 2013 (I'd love to be on 2015, but not all of our third-party library suppliers are there yet), and Intellisense mostly works, if you don't mind taking a ten-second break now and then.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
  2. Re:64-bit by scb147 · · Score: 5, Informative

    Microsoft,

    It's 2017 and Visual Studio is still 32-bit.

    Sincerely,
    Developers

    My MSDN account shows both 32-bit and 64-bit are available for Professional.

  3. $500 is Shocking??? by turp182 · · Score: 4, Informative

    The Professional version is $500 (license, not subscription):
    https://www.visualstudio.com/v...

    That seems very reasonable.

    Enterprise is quite a bit more ($6K for new, $2.6K to renew), but it is part of the MSDN Enterprise (previously Ultimate I believe, that's what my license is called at this time), you get access to almost everything MS has ever made (want Windows 3.1 or DOS 6, it's there, want enterprise SQL Server, it's there).

    Here's the link to the prices:
    https://www.visualstudio.com/v...

    --
    BlameBillCosby.com
    1. Re:$500 is Shocking??? by dontbemad · · Score: 5, Insightful

      I think what is shocking to the vocally anti-Microsoft (and proprietary software in general, for that matter) crowd on slashdot is that people can get away with charging MONEY for SOFTWARE.

      It never ceases to amaze me how, despite the fact that the majority of us on this website make our money in tech or software, the idea of charging money for those services is revolting to some.

    2. Re:$500 is Shocking??? by OzPeter · · Score: 3, Informative

      Does this mean I can get Visual Studio 2016 for a cheaper price now since it is considered old and obsolete?
      what about VS 2015 or older? Cheaper is better.

      There is no VS2016. As for VS2015 I doubt you can even buy it now unless you get through an MSDN subscription.

      But anyway for 100% of non-corporate usage the community editions handle everything you can throw at them and are free. The Pro only starts to make sense when you want to tie into a Team Foundation Server in a corporate environment.

      --
      I am Slashdot. Are you Slashdot as well?
    3. Re:$500 is Shocking??? by Kjella · · Score: 3, Funny

      $500 is Shocking???

      The submitter is probably measuring that in Ramen noodles while being a squatter on campus like his idol, because software wants to be like, free, man. And I'd show him our SQL Server Enterprise bill, but I fear he'd go into cardiac arrest. For us Visual Studio is just a rounding error for SSIS/SSAS/SSRS development.

      --
      Live today, because you never know what tomorrow brings
    4. Re:$500 is Shocking??? by OzPeter · · Score: 2

      This.

      And if you think SQL Server licensing is bad for your health, do not under any circumstances look at licensing BizTalk.

      But really, for your sanity as well, don't use BizTalk. ("Ha ha, ho ho, hee hee," I say with a crazy look in my eye...)

      I'm petty sure all the SAP people are simply rolling their eyes right now.

      --
      I am Slashdot. Are you Slashdot as well?
    5. Re:$500 is Shocking??? by Interfacer · · Score: 2

      I know the business guys use SAP here and no doubt it is expensive. Not sure how much though. I look after the process automation software in a pharmaceutical company, and the annual licensing of just our tech support is enough to buy a house. A big house. In a good neigborhood. And that is cheap compared to initial purchase of our software. Engineering licenses alone are something like 15K per seat.

  4. Re:64-bit by Ambassador+Kosh · · Score: 4, Informative

    The IDE is 32bit. The compile, debug, profile etc chain are 32bit and 64bit.

    There is probably no reason for the IDE to be 64bit since it does not come even close to use enough memory to justify that. I have opened a few visual studio projects in 2017 and most of them don't use more than 200 MB. Resource usage so far is about half that of VS 2015.

    --
    Computer modeling for biotech drug manufacturing is HARD! :)
  5. Step-by-step impressions (intro + downloading) by CustomSolvers2 · · Score: 2

    I use and like VS quite a lot, but am not precisely an early adopter. At the moment, I am mostly using the 2012 version and, eventually (= when forced to do so), the 2015 one. Actually, I am not even sure why I stopped using VS 2010 because it was quite reliable. I have seen some problems with 2012, but have gradually got used to them. I haven't used 2015 much, but don't think that I like it: it consumes too many resources, even for my a-bit-old-but-quite-powerful desktop computer.

    I am currently downloading the 2017 Community (clarification which is perhaps still required: fully-functional free version, which has nothing to do with the old VS Express) and everything looks OK so far. The downloading interface seems nicer than the previous ones. Microsoft promised this version to be much more modular and apparently they delivered. I am saying apparently because the options are there, although the size is still quite big anyway (over 7 GB after having chosen the most basic options).

    --
    Custom Solvers 2.0 = Alvaro Carballo Garcia = varocarbas.
  6. How do I turn the telemetry off this time? by Opportunist · · Score: 5, Informative

    In the last VS I had to add a compiler option to stop you from sneaking your snooping crap into my code, what is it going to be this time?

    Yours,

    An Ex-VS user.

    --
    We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    1. Re:How do I turn the telemetry off this time? by Opportunist · · Score: 4, Insightful

      And it's just me who wonders why they add something like this, without any documentation of the calls whatsoever, and only admit it sheepishly when we basically find them with their hand in the cookie jar?

      If you add calls me my binaries, I sure as FUCK expect you to tell me up front. If not, tell me one good reason why I should EVER trust your compiler again.

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
  7. Re:64-bit by PhrostyMcByte · · Score: 4, Informative

    It's 2017 and Visual Studio is still 32-bit.

    Unless you have specific use cases 64-bit doesn't always mean better. Most apps don't need the extra address space, and jumping to 64-bit means doubling your pointer sizes, which increases memory usage, reduces locality, and puts a larger burden on cache.

    In VS's case they did the math and 32-bit was better. They've said this for years now. It's not a bad thing.

  8. FYI: No ISO download by rastos1 · · Score: 3, Informative

    But you should be able to create an offline installer

    1. Re:FYI: No ISO download by MobyDisk · · Score: 2

      FYI: Final result, without using --lang, is ~16.3GB (17,595,078,265 bytes) and 4,606 files.

  9. Re:64-bit by SirSlud · · Score: 2

    You might as well just have posted, "I don't know anything about software development."

    --
    "Old man yells at systemd"
  10. Re:64-bit by ebyrob · · Score: 5, Interesting

    Try installing that "64-bit" version. Pretty sure devenv.exe is still going in "Program Files(x86)".

    See: https://docs.microsoft.com/en-...
    About **still** using msvsmon.exe to debug 64-bit in 32-bit VS...

  11. Visual C++ for Linux! by Billly+Gates · · Score: 3, Interesting

    No I am not making this up either. Also a beta version of Visual Studio for Mac is available too as well as better Android and IOS support. VS since 2015 also comes with Java and Android emulators as well via Hyper-V.

    MS is getting quite serious about being cross platform

  12. Re:Coumminty edition is FREE! Not crippled by Billly+Gates · · Score: 4, Informative

    The community edition is not the crippled express editions. You can even make professional software with it too. THe only difference is the MSDN subscription and corporate Team Foundation features for teams and groups.

    THe Community Edition even comes with Git and Git tools to use for things like Github.

    So why is everyone whining? Things are not free to make and like Redhat there is CentOS for those who do not need enterprise support but is there for those that do.

  13. Re:64-bit by DrXym · · Score: 2, Insightful
    I've run out of memory in large projects on other IDEs. I don't think it would be of the question that you could burn through 3.5GB if you had a workspace with lots of projects in different configs and targets with runtimes in memory all at the same time.

    Given that Windows has more or less become defacto 64-bit with just a few 32-bit outliers on tablets, it doesn't make much sense to remain 32-bit any more.

  14. Re:Microsoft is good once again by DrXym · · Score: 2
    VS Code is actually quite good and cross platform. I've used it extensively on Linux and gdb plugin is pretty handy.

    My main criticism of it is is that it's a pain in the ass to configure. Just like Atom, Brackets, Sublime etc., it does away with a proper settings dialog and configuration is by editing a JSON-esque file. Even if this makes sense for advanced configuration it really sucks just to configure some simple thing.

  15. Re: 64-bit by judoguy · · Score: 5, Interesting
    VFP was for serous database programmers. VB was for looks.

    I used to get hired to create VFP layers to bridge SQL Server, AS400 and other databases to other apps because it just worked and worked well.

    Wasn't a "real" Windows app in some UI ways, but when you needed to push/pull data to and from disparate back ends and integrate that data into COM based Outlook, Word, Excel and other Windows based applications, there was nothing better. We'd have C# guys come in and try to migrate VFP apps and they'd whine at the requirements to do things that are simple in VFP.

    In 35 years of heavy relational database focused consulting on different platforms, nothing was as easy to use or as powerful as VFP.

    So there!

    --
    Peace is easy to achieve, just surrender. Liberty is much harder get/keep.
  16. Re: 64-bit by dunkelfalke · · Score: 2

    It is not just about memory. Twice as many registers, 64 bit integers, faster syscalls and so on.

    --
    "It's such a fine line between stupid and clever" -- David St. Hubbins, Spinal Tap