The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
So last week we got a new Virtual Machine with Visual Studio 2015 installed.
With this project we're coming from 2010, so I was pretty excited as I've worked with 2015 before and it has so much improvements!
Check out the project and... Visual Studio 2015 crashes... It happens.
Open it up again and for some reason I can't open a cshtml file.
Restart. Cache is out of date. Restart. Can't load unit tests (getting it to work required me to unload all non-test projects). Restart. Something else crashed...
WHAT THE HELL MICROSOFT!?
Then I checked out the project on my laptop with the Visual Studio 2015 Community Edition and everything worked like a charm.
Back to the VM and nothing but trouble.
So screw working in a VM I'll work on my laptop (we've got VM's for different VPN clients, different versions of the same tools, etc.).
Let me first update my laptop though, apparently I've got some Visual Studio Update 1 pending.
Installed and... I get the same problems on my laptop!
WHAT THE HELL MICROSOFT!?
I just de-installed Visual Studio on my laptop and I'm now doing a clean install (with Update 1).
If that doesn't work I'm going to look for an older installer without Update 1.
Anyone else has these problems?
VS2015 is a hog compared to VS2013 (which in itself was one, but better than 2010).
Disable perftip, diagnostic tools and stuff like that. Limit also autocomplete background to 2 threads insteaf of maximum (15). Even the full debug symbols load (both MS and private), the browser we supply in the product - I'm talking about Bitdefender full consumer product - which in itself is CEF-based which 1.5+ GB .pdb just for one file, libcef.pdb and still is not that bad as perftip + diagtools.
My biggest 2015 is a pig complaint (vs 2010) is memory use. I could generally run 2 copies of 2010 along with all my other apps and background corporate bloat in 8gb without needing to hit swap. With 2015 I've occasionally found myself swapping with just the one instance running.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
I did. Component cache is out of date. I delete the cache and a few restarts later it's out of date again.
I can't open some files sometimes. No crash or whatever, the file just "does not exist" while it's actually very much there.
The Test Explorer is the most pain. It looks for tests, but just never finds them. I've let it look for an hour, but nothing. No crash, no hang, just no find. It makes unit testing rather difficult...
VS2015 Update 1 is pretty much unusable.
It's a solution with some 20 projects (including test projects).
I can unload all other projects and the test explorer works fine.
This is about being able to do my work like I did with VS2010, but better though.
If VS2015 makes me go through hoops just to unit test my project and gives me a lot of errors on top I'd much rather go back to VS2010...
Silly question maybe... But are you running VS as administrator? and are you administrator on the machine.
One thing that I would try in this situation is to use ProcMon.exe from SysInternals to capture what is going on when you get the errors.
Businesses are not adopting Windows 10, at least none that I know of. As I mentioned earlier, we have no plans to move to Windows 10 until the OS has stabilized, which could be another 6 months to a year.