51–60 of 121 posts
Earlier quoted context omitted.
Wondering if the Live Unit Testing came from the acquisition/integration of the Alive project. Very interesting indeed.
It might be, but Alive was much more than just if the tests pass or not
Earlier quoted context omitted.
That went away a while ago, unfortunately... though I think yaml may have been better, the json-like structure was much easier than the xml mess for vs projects. Hoping they added an "empty" project that is just files, closest were some of the web projects, but even then, node projects always felt like an alien afterthought... haven't seen how they are in vs2017, guessing they brought in the ntvs stuff into mainline.
project.json is still official way of configuring the projects. Dotnet cli uses that, msbuild is not there yet i think. Empty project is done with "donnet new", and it's really small and light ...
The new installer is nice. Installed just a C++ environment in 5 minutes!!
Wow that's huge. My last VS2015 install took hours.
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 :)
Please don't. They make way too many awesome tools outside of Microsoft's area of interest, like CLion, Kotlin, RubyMine etc.
Anyone know if this will work with Unity 3D?
It seems so: Game development with Unity The Unity engine integrates into one unparalleled platform to create 2D and 3D games and interactive content. Create once and publish to 21 platforms, including all mobile platforms, WebGL, Mac, PC and Linux desktop, web or consoles. Write code quickly and with precision using IntelliSense. Navigate through your scripts easily and use powerful refactoring capabilities. Identif…
https://www.unrealengine.com/blog/unreal-engine-4-14-release...
Does this also mean a new C/C++ runtime library is available (i.e. vcruntime150)?
VS 2015: IDE version 14, DLL version 140, toolset version 140, compiler version 19.0 (the C++ compiler is older than the Visual part of Visual C++). VS 2017: IDE version 15, DLL version 140 (same!), toolset version 141, compiler version 19.1
We still recommend that you build everything with VS 2017 consistently, as this will give you the most performance and correctness. However, you can mix in object files, static libraries, and DLLs compiled with previous versions all the way back to 2015 RTM, and things will continue to work (although you won't necessarily activate fixes in the newer version).
For more info, read the comments on https://blogs.msdn.microsoft.com/vcblog/2016/08/24/c1417-fea... where I mentioned WCFB02.
Looks like MS is making mostly small changes, focusing on improving the features they already have instead of introducing lots of new changes.
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.
The naming has been awful with this release in particular. Having two Visual Studio (20)15s out at the same time is very confusing. Almost as bad as the Skype vs Skype for Business marketing boondoggle.
Remember when .NET could refer to virtually every product Microsoft made?
I was half expecting them to call it Visual Studio Surface. Then you could run Surface on your Surface on any Surface on the planet.
The new installer is nice. Installed just a C++ environment in 5 minutes!!