3 ms·

Your support experience sounds really bad. I'd file the bug here: http://connect.microsoft.com/VisualStudio http://connect.microsoft.com/VisualStudio (which de

Your support experience sounds really bad. I'd file the bug here: http://connect.microsoft.com/VisualStudio http://connect.microsoft.com/VisualStudio (which despite the name is also the right place to report library issues)

d0 13y ago
It's always been bad. I'm the chief technical contact for a system with 50 developers and about 11,500 users. We've raised 20 cases which we couldn't work around and had one officially released solution (bug in IE11). We either have to work around or push a registry fix at great cost to thousands of users worldwide as an out of band patch that we package ourself. For example there was a regression in ClickOnce with download prompting between IE8 and IE9 due ot the download bar throwing away some compatibility settings. Overnight, when IE9 became mandatory in Windows Update, we had 2000 users down. We got all the users to roll back to IE8. It took 6 months for a registry fix to be sent out to us from a 3rd line support executive after being on the phone daily about it. This is still not fixed in IE11. We've rewritten all our ClickOnce launch points to work around the regression. This took one developer 2 months of work. The regression appeared in the RTM IE9, not the previews. As for that being the correct place, it's obviously not as the issue was raised there, marked private and closed as not reproducible despite test cases being issued. Not a single contact back from Microsoft bar "closing as can't reproduce". Our rep suggested contacting another support team. Even they aren't helpful. I need a new job, writing C on Unix...
- _stephan 13y ago
  Looks like Microsoft has some deep structural problems with its developer support. Let's hope the right persons at Microsoft see this thread.
  - voltagex_ 13y ago
    I have a 100% reproducible (hang/freeze) bug in Visual Studio, with crash dump and everything. It's in 2012, so it'll probably never be fixed. The one developer who responded ignored the information I provided, anyway. I can no longer find the bug on the dashboard.
ximeng 13y ago
If you browse through connect there's some really unhelpful responses from Microsoft and many people trying very hard to report problems in the most helpful possible way without getting a response. The idea is good but execution is weak.

d0 13y ago

It's always been bad. I'm the chief technical contact for a system with 50 developers and about 11,500 users. We've raised 20 cases which we couldn't work around and had one officially released solution (bug in IE11). We either have to work around or push a registry fix at great cost to thousands of users worldwide as an out of band patch that we package ourself. For example there was a regression in ClickOnce with download prompting between IE8 and IE9 due ot the download bar throwing away some compatibility settings. Overnight, when IE9 became mandatory in Windows Update, we had 2000 users down. We got all the users to roll back to IE8. It took 6 months for a registry fix to be sent out to us from a 3rd line support executive after being on the phone daily about it. This is still not fixed in IE11. We've rewritten all our ClickOnce launch points to work around the regression. This took one developer 2 months of work. The regression appeared in the RTM IE9, not the previews. As for that being the correct place, it's obviously not as the issue was raised there, marked private and closed as not reproducible despite test cases being issued. Not a single contact back from Microsoft bar "closing as can't reproduce". Our rep suggested contacting another support team. Even they aren't helpful. I need a new job, writing C on Unix...

_stephan 13y ago
Looks like Microsoft has some deep structural problems with its developer support. Let's hope the right persons at Microsoft see this thread.
- voltagex_ 13y ago
  I have a 100% reproducible (hang/freeze) bug in Visual Studio, with crash dump and everything. It's in 2012, so it'll probably never be fixed. The one developer who responded ignored the information I provided, anyway. I can no longer find the bug on the dashboard.

ximeng 13y ago

If you browse through connect there's some really unhelpful responses from Microsoft and many people trying very hard to report problems in the most helpful possible way without getting a response. The idea is good but execution is weak.