WPF/Silverlight and ASP.NET MVC are very different technologies. For one WPF/Silverlight are client technologies. More like HTML/CSS/JS than MVC.
But what I really wanted to say is that while I like Azure in theory, it's a pain in the butt to use. I used AppHarbor and literally had my first app hosted in 10 minutes, maybe less. With Azure it seems like there's all these things they want me to know. If I want to get up a super simple web site with ASP.NET MVC why are you making me know about all these different types of roles and load balancing and such?
My hope is that this is what Scott Guthrie will fix. ASP.NET MVC is surprisingly clean and pleasant. Silverlight is a triumph of moving WPF off the desktop. I'm really excited about the future of Azure, for once.
But what I really wanted to say is that while I like Azure in theory, it's a pain in the butt to use. I used AppHarbor and literally had my first app hosted in 10 minutes, maybe less. With Azure it seems like there's all these things they want me to know. If I want to get up a super simple web site with ASP.NET MVC why are you making me know about all these different types of roles and load balancing and such?
My hope is that this is what Scott Guthrie will fix. ASP.NET MVC is surprisingly clean and pleasant. Silverlight is a triumph of moving WPF off the desktop. I'm really excited about the future of Azure, for once.