3 ms·

Microsoft are much better than Apple at this, heck just look the latest fixed on connect. http://connect.microsoft.com/VisualStudio/feedback/details/802165/cra

Microsoft are much better than Apple at this, heck just look the latest fixed on connect. http://connect.microsoft.com/VisualStudio/feedback/details/802165/crash-during-pgo-using-amd64-x86 http://connect.microsoft.com/VisualStudio/feedback/details/8... I've had issues which I've posted in newsgroups and forums, that have been turned into bug tickets. Some teams appear better at this than others mind.

voltagex_ 13y ago
Yet you can still do this and hang Visual Studio 2012, and maybe 2013: * On a new machine (or maybe a new profile, I haven't checked), enable PowerShell's AllSigned option * Open Visual Studio and open an MVC4 project, bonus points if it's close to the template in terms of installed NuGet packages * Watch as Visual Studio hangs indefinitely. This has been reported a number of times to Microsoft, but I don't think it was fixed in Update 4. What's happening is PowerShell, running inside Visual Studio is prompting for something to do with a signed PowerShell Script, but Visual Studio hasn't loaded enough of the UI to let you accept the warning/prompt.
- sitharus 13y ago
  As a .NET developer, I can confirm this is the case with VS 2013.