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.
crappy summary for the slashdot crowd. we know what visual studio is - what we want to know is what, if anything, changed
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.
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
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!
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.
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.
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.
But you should be able to create an offline installer
You might as well just have posted, "I don't know anything about software development."
"Old man yells at systemd"
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...
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
http://saveie6.com/
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.
http://saveie6.com/
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.
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.
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.
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