Hacker News Reader

God, I'm wrapping up a MVC3 app, I can't wait to sprint away and never, ever, ever come back. During this project I've, installed Visual Studio 3 times and my current installation leaves me still unable to debug Azure deployments and Microsoft has no fix for me but to reinstall Windows and start over.

.NET and csharp are a joy, but I'll never touch a pure-Microsoft stack or anything I can't (easily) run in Mono ever again.

View on HN

What's the culprit do you think? Azure stuff? I've never seen problems like that with MVC3 (but given the gamut of all the crazy things I've seen I don't doubt you)

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.

Azure is terrible no doubt. However, we build on top of ASP.NET MVC and haven't had any complaints.

Reply on news.ycombinator.com