71–80 of 121 posts
Great to see some Resharper features making it in, have been waiting for MS to acquire Resharper or Jet brains :P; but why acquire when you can make your own Slack and Resharper :)
> have been waiting for MS to acquire Resharper or Jet brains :P; Please don't. They make way too many awesome tools outside of Microsoft's area of interest, like CLion, Kotlin, RubyMine etc.
Visual Studio "15" = Visual Studio 2017 = VC 15.0 Crystal clear. Why didn't Microsoft bump up VC version to 17 to sort of make VC version follow VS version. Would clear out some confusion going forward.
Earlier quoted context omitted.
At the Build conference they had a demo where they "forgot" to install VS before the presentation, and then installed it from an USB stick in about one minute. I'm installing now, but not from USB...
Visual Studio 2017 installer experience is one of our biggest investments, we know this has been a pain for folks and we're committed to doing everything we can here. Check out our detailed blog post on the topic: Visual Studio “15”: Installing Just What You Need https://blogs.msdn.microsoft.com/visualstudio/2016/04/05/vis...
I try to minimize this by installing it on an absolutely clean Windows installation. It's usually the first major thing I install after Windows Update patches and a few minor apps like 7zip and Chrome (used to use WinCdEmu back when I had VS Pro from Sparkfun instead of VS CE). I do this deliberately to try and minimize issues and I still have tons of issues with crashes during the install, and it is pretty much an overnight thing on many systems (or at least multiple hours). It's to the point where I will image the system so I can quickly blow down a clean image and give it another try.
I feel like part of this is the Windows team screwing you. OS upgrades are always tricky and the "system reset" thing does not actually work as fully as people expect that it does (eg it still keeps system files/drivers, config/registry, etc). My success rates were always higher with a 100% clean OS install, format everything and installing from a Media Creation Tool system image. My success rates have also been going up over time, and I'm sure both the VS team and the Windows team are coming at it from both sides, so props.
Keep it up with the DotNet environment too, the open-source direction is really important because it catalyzes the tooling and infrastructure that's been missing from the DotNet ecosystem. I mostly program in Java right now because of the end-to-end tooling and environment flexibility, but I really would prefer to work in C# and in the last 2 years you've made huge strides to making that possible.
I realize this is a totally different team, but right now my single biggest beef with MS products is the fact that major Windows updates usually reset all my settings. Things like ClassicShell need to be reinstalled each time, it forgets all my taskbar preferences, it forgets all my file associations, etc. The last one is particularly aggravating, especially when MS reps claim it's just because apps are setting associations by themselves when you are supposed to do it through the Windows interface. First off that's a terrible UI experience, but it nevertheless does reset anyway even if you do it through the Windows UI. People are going to hate updates a lot less if they don't insist on (metaphorically) playing with all my settings on my stereo. Please whisper that in someone's ear if you ever get the chance.
But overall MS products are really picking up steam after a prolonged era of poor quality. Windows 8.1 was fantastic, 10 is even faster. VS2012 was much better than 2007/2008 and 2015 CE has been great too.
The new installer is nice. Installed just a C++ environment in 5 minutes!!
Visual Studio "15" = Visual Studio 2017 = VC 15.0 Crystal clear. Why didn't Microsoft bump up VC version to 17 to sort of make VC version follow VS version. Would clear out some confusion going forward.
I am beginning to think that Microsoft's bad verison naming is entirely on-purpose. Windows has had terrible naming since NT -- back and forth between names/numbers/years (or nonsense like "Anniversary Update" or "R2"), have a completely different scheme for Server vs Desktop, and if you look at the corresponding kernel versions of these releases[0], the major/minor bump in versions seems completely arbitrary. .NET i…
Earlier quoted context omitted.
MSVC STL dev here. We're doing something different this time around. VS 2015 RTM and Update 1/2/3 were binary-compatible (as usual) while adding lots of features to the compiler and STL (unusual). VS 2017 RTM and its Updates will continue to be binary-compatible while adding features, meaning that our DLLs are still vcruntime140.dll, msvcp140.dll, etc. The versions are admittedly a mess, so here's the magic decoder r…
Thank you. I seem to have completely missed all the VC blog posts about the bincompat decision with regard to Visual Studio "15"/2017. Glad to know that the VC100 to VC140 overhaul that I completed only very recently can still be considered fully up to date with the latest and greatest :).
Earlier quoted context omitted.
I am beginning to think that Microsoft's bad verison naming is entirely on-purpose. Windows has had terrible naming since NT -- back and forth between names/numbers/years (or nonsense like "Anniversary Update" or "R2"), have a completely different scheme for Server vs Desktop, and if you look at the corresponding kernel versions of these releases[0], the major/minor bump in versions seems completely arbitrary. .NET i…
You forgot about Windows 9. ;)
Visual Studio "15" = Visual Studio 2017 = VC 15.0 Crystal clear. Why didn't Microsoft bump up VC version to 17 to sort of make VC version follow VS version. Would clear out some confusion going forward.
No, 2017 written as separate numbers are 2 0 1 7 and adding them up gives 10. Half of 10 is 5 (obviously) and that sum is 15. Get it?
a 0 b := b - a
One of the install options is "Linux development with C++"
Yes our C++ team has been investing into this area for a while now, we're building some really powerful debugging capabilities there as just one thing to mention with remote debug right out to your Linux machine or VM