What the hell Microsoft!?
-
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
Try to identify the actual reason for crash...Look for VS log and machine's Event Viewer...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
"It never ceases to amaze me that a spacecraft launched in 1977 can be fixed remotely from Earth." ― Brian Cox
-
Try to identify the actual reason for crash...Look for VS log and machine's Event Viewer...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
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.
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
-
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
Visual studio 2015 pro with update 1 has a known bug. After you install, you will need run the latest update 1.1. You may want to look at this: Download KB 3110221: Servicing Update to Visual Studio from Official Microsoft Download Center[^]
-
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.
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'm using 2015 since first day and update all the news... No tests... Check these: The Visual Studio component cache is out of date. Please restart visual studio. | Microsoft Connect[^] How Visual Studio’s Component Model Cache can be a pain. | .withMartin[^]
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
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
-
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.
Cristian Amarie wrote:
Disable perftip, diagnostic tools
Where do you go to disable these?
If it's not broken, fix it until it is
-
Since the last update Windows 10 is instable. It crashes and doesnt like to reboot. M$ is in trouble - deep trouble.
Press F1 for help or google it. Greetings from Germany
I know some people who work for Microsoft, and the word is that if Windows 10 does not cut the mustard for any reason, then Microsoft will have to re-evaluate their future product line and strategy. So, "in trouble" is an accurate way to put it. :sigh:
-
I know some people who work for Microsoft, and the word is that if Windows 10 does not cut the mustard for any reason, then Microsoft will have to re-evaluate their future product line and strategy. So, "in trouble" is an accurate way to put it. :sigh:
There would need to be problems of Biblical proportions to cause MS to change course at this point. I just don't see it happening.
My long term goal is to live forever. So far, so good...
-
There would need to be problems of Biblical proportions to cause MS to change course at this point. I just don't see it happening.
My long term goal is to live forever. So far, so good...
Agreed. There would need to be an industry wide sea-change of epic proportions that Microsoft completely misses on to cause any significant damage.
There are two types of people in this world: those that pronounce GIF with a soft G, and those who do not deserve to speak words, ever.
-
There would need to be problems of Biblical proportions to cause MS to change course at this point. I just don't see it happening.
My long term goal is to live forever. So far, so good...
They are not getting Windows 10 on as many machines as they had hoped, especially the business market. For instance, our shop has no intention of going to Windows 10, anytime soon. So, "Biblical" proportions, is not out of the question, anymore. Not enough people want\use Windows 10, for it to be a viable OS in today's market. Many people are waiting a year or two, for the bugs to get ironed out. Question is, does Microsoft have the time to wait that long.
-
Agreed. There would need to be an industry wide sea-change of epic proportions that Microsoft completely misses on to cause any significant damage.
There are two types of people in this world: those that pronounce GIF with a soft G, and those who do not deserve to speak words, ever.
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.
-
They are not getting Windows 10 on as many machines as they had hoped, especially the business market. For instance, our shop has no intention of going to Windows 10, anytime soon. So, "Biblical" proportions, is not out of the question, anymore. Not enough people want\use Windows 10, for it to be a viable OS in today's market. Many people are waiting a year or two, for the bugs to get ironed out. Question is, does Microsoft have the time to wait that long.
I don't see why not. Historically they have shown that they're very patient - and they have deep pockets. Even with longer replacement cycles, existing 7/8 machines won't last forever. . .
My long term goal is to live forever. So far, so good...
-
I know some people who work for Microsoft, and the word is that if Windows 10 does not cut the mustard for any reason, then Microsoft will have to re-evaluate their future product line and strategy. So, "in trouble" is an accurate way to put it. :sigh:
-
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
-
Slacker007 wrote:
if Windows 10 does not cut the mustard for any reason, then Microsoft will have to re-evaluate their future product line and strategy.
When would that never have been the case, in all of Microsoft's history?
-
I don't see why not. Historically they have shown that they're very patient - and they have deep pockets. Even with longer replacement cycles, existing 7/8 machines won't last forever. . .
My long term goal is to live forever. So far, so good...
Frank Alviani wrote:
I don't see why not. Historically they have shown that they're very patient
and that is why they are forcing installs now, because they are so patient. :confused: Trust me when I tell you, that they are very concerned about all of this.
-
Neither do I :)
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'm using 2015 since first day and update all the news... No tests... Check these: The Visual Studio component cache is out of date. Please restart visual studio. | Microsoft Connect[^] How Visual Studio’s Component Model Cache can be a pain. | .withMartin[^]
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
I've tried it all. Must've deleted that cache a 100 times by now.
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
-
When has anyone NOT wanted to update to the latest OS? For me and our company (and other companies) it is now, with Windows 10. Only time in MS history, that I can think of.
Slacker007 wrote:
Only time in MS history, that I can think of.
Really? What about Vista? And 8? :~
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 know some people who work for Microsoft, and the word is that if Windows 10 does not cut the mustard for any reason, then Microsoft will have to re-evaluate their future product line and strategy. So, "in trouble" is an accurate way to put it. :sigh:
Slacker007 wrote:
Microsoft will have to re-evaluate their future product line and strategy
Here's a strategy: write software that actually works!
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
