What the hell Microsoft!?
-
I too have lot of issues with VS 2015. In C#, right click a variable to rename, got 'Object reference not set to instance exception'. And a lot more issues with the editor.
Yes, I've seen that one too! :sigh:
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
What kind of project do you have? Can you separate the test totally from the rest? Maybe this? Upgrade Visual Studio 2010 unit test projects[^]
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
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...
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
Point taken with Vista. But 8 is doable. I currently use 8 at work, and it is manageable. It's no 7, though. :)
Slacker007 wrote:
But 8 is doable. I currently use 8 at work, and it is manageable
Agreed. Not all that, but when you get used to it it's just a small step back from 7.
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
Use the Update for Microsoft Visual Studio 2015 (KB3110221)[^], Sander.
What do you get when you cross a joke with a rhetorical question? The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism. Do questions with multiple question marks annoy you???
If anything, that made it worse. I now get a "Visual Studio is busy" error every time I start VS and the Test Explorer is still open... :sigh:
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
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. Not good for Microsoft, and they know it.
Slacker007 wrote:
Businesses are not adopting Windows 10, at least none that I know of
One of my clients is currently going through W10 testing for all of its products. This is an international company with 10s of 1000s of users. The testing is going surprisingly well. I might have to get serious about developing UWA systems.
This space for rent
-
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...
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
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.
-
Slacker007 wrote:
Businesses are not adopting Windows 10, at least none that I know of
One of my clients is currently going through W10 testing for all of its products. This is an international company with 10s of 1000s of users. The testing is going surprisingly well. I might have to get serious about developing UWA systems.
This space for rent
Good to hear.
-
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!? :mad: 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!? :mad: 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?
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
I have got a similar problem in my Visual Studio 2015 Community!!! It happens in the solution where I have got many projects, about 20. Precisely, I have got there 20 ASP.NET Core 1.0 projects. It is crashing when I simply just open my solution. I can see that it loads projects in random order and crashes. When it crashed I tried to debug it in another Visual Studio 2015 instance but with no result, I think I saw there only something related with json but don't know if it was related with json files in my solutions or projects or internal Visual Studio itself. The way around (worked for me): Note: Really be careful if you are using GIT. If you move the projects around you should commit only when your projects are where they are meant to be. 1) Close your Visual Studio 2015 2) Create a temp folder inside your solution, on the same level where your projects are 3) Move majority projects there - maybe all except one, especially keep the one where is the solution file. 4) Open your Solution 5) This should open Visual Studio 2015 without crashing and you will see in your Solution Explorer obviously that some projects are unavailable 6) Move the projects back from temp folder back to their previous place 7) You can reload (right click the project) the one you need or all of them. It should not crash. I personally like Visual Studio 2015 very much and hope that eventually whatever is broken will be fixed and don't have to use this retarded work around.. ..yep, it started with Update 1, I think the Update 73 should fix it. :)
-
Good to hear.
Granted, that's the only client doing this ;)
This space for rent
-
Granted, that's the only client doing this ;)
This space for rent
My company (our shop) is going to start testing Windows 10 in about 6 months. I actually want Windows 10 to work, because I make my living with the Microsoft stack and a "new" stable OS, would be nice.
-
Cristian Amarie wrote:
Disable perftip, diagnostic tools
Where do you go to disable these?
If it's not broken, fix it until it is
Tools > Options > Debugging > General for "Enable Diagnostic Tools while debugging" and "Show elapsed PerfTip when debugging" Text Editor > C/C++ > Advanced => Intellisense Auto Tune Max Cached Transation -> False Max Cached Translation Units -> 2 (my setting, not 15)
-
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.
I'm admin on one machine. On the other I run as admin.
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
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. :sigh:
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? --Zachris Topelius 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
-
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!? :mad: 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!? :mad: 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?
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
At least you got it to install! :) Mine just hanged at the install phase, and completely buggered up all my other OS settings. I ended up having to re-install the entire OS after facing system slowdown, repeated crashes etc.
'The time has come,' the Walrus said, 'To talk of many things: Of shoes -- and ships -- and sealing wax -- Of cabbages -- and kings -- And why the sea is boiling hot -- And whether pigs have wings.' -- The Walrus and the Carpenter (by Lewis Carroll)
-
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!? :mad: 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!? :mad: 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?
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
I had basically the exact same problem. Even uninstalling and reinstalling with the Update didn't work. I had to uninstall everything then reinstall everything without the update, once I got that up an running I installed the update, then I had a build problem after the update that I did not have before. The build problem turned out to be an import to a non existent static class in VB, for some reason the compiler didn't say that, it just crashed. I discovered it through eliminating everything until I could build then going line by line through that code file. Update 1 is a MESS.
-
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!? :mad: 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!? :mad: 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?
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
If anything, that made it worse. I now get a "Visual Studio is busy" error every time I start VS and the Test Explorer is still open... :sigh:
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
I must be lucky then, as I have had no issues whatsoever.
What do you get when you cross a joke with a rhetorical question? The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism. Do questions with multiple question marks annoy you???
-
I have got a similar problem in my Visual Studio 2015 Community!!! It happens in the solution where I have got many projects, about 20. Precisely, I have got there 20 ASP.NET Core 1.0 projects. It is crashing when I simply just open my solution. I can see that it loads projects in random order and crashes. When it crashed I tried to debug it in another Visual Studio 2015 instance but with no result, I think I saw there only something related with json but don't know if it was related with json files in my solutions or projects or internal Visual Studio itself. The way around (worked for me): Note: Really be careful if you are using GIT. If you move the projects around you should commit only when your projects are where they are meant to be. 1) Close your Visual Studio 2015 2) Create a temp folder inside your solution, on the same level where your projects are 3) Move majority projects there - maybe all except one, especially keep the one where is the solution file. 4) Open your Solution 5) This should open Visual Studio 2015 without crashing and you will see in your Solution Explorer obviously that some projects are unavailable 6) Move the projects back from temp folder back to their previous place 7) You can reload (right click the project) the one you need or all of them. It should not crash. I personally like Visual Studio 2015 very much and hope that eventually whatever is broken will be fixed and don't have to use this retarded work around.. ..yep, it started with Update 1, I think the Update 73 should fix it. :)
Nope, fixed it by uninstalling Update 1 :D
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
