21–30 of 121 posts
Earlier quoted context omitted.
Piss-poor caching mechanism that can't spit out static frontpages with relative ease. Still getting 504's.
Here are direct links. Looks like they haven't updated the names in the URL's, but this downloads the 2017 RC. https://aka.ms/vs/15/release/vs_Community.exe https://aka.ms/vs/15/release/vs_Enterprise.exe https://aka.ms/vs/15/release/vs_Professional.exe https://aka.ms/vs/15/release/vs_TestProfessional.exe
Why twist yourself in knots to be the "next X" when you can be content supplying the "next X" with a platform for expansion.
I've always been hesitant to install RC's on my machine. Does anyone know how nicely the RC's generally play with other instances of VS / if they've improved that along with the improved install/uninstall process in 2017?
I've always been hesitant to install RC's on my machine. Does anyone know how nicely the RC's generally play with other instances of VS / if they've improved that along with the improved install/uninstall process in 2017?
Project.json for .net core is gone, there's xproj file. How to change settings, like target framework, per-framework dependencies, build options, pre/post build steps, etc? I don't see any tooling support for that.
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.