3 ms·
It's undoubtedly the Azure stuff. They had bad mirrors and redirects up for quite a while for VS SP1. Twitter revealed others with the same problem. That ruined
by drivebyacct2 15y ago
It's undoubtedly the Azure stuff. They had bad mirrors and redirects up for quite a while for VS SP1. Twitter revealed others with the same problem. That ruined the first install. The second install was okay with debugging a MVC project but the Azure emulator caused an uncaught exception in the .NET runtime. There was no indication of where the error was occurring, and like I said, no real troubleshooting steps available. I wish I could remember the error message. It was as if the runtime was just mocking me with it's complete lack of help.