Currently in order to add asp.net mvc to an existing asp.net webforms project is not exactly pain free. Here's an example

http://www.devcurry.com/2013/05/adopting-aspnet-mvc-enhancements-in.html which actually includes having to add in some guid. Obviously lots of people have existing web forms sites/applications that are not going anywhere but would also like to integrate mvc into them as well. Currently, I would not call this user experience pleasant. I would be nice to be able to easily add mvc to an existing web forms site. It could be a NuGet package, a right-click on the web form site that has "add mvc to this"

When trying to handle errors in ASP.NET, you have to jump through a series of unintuitive and often poorly documented hoops to catch an exception and handle it in a sensible way. The non-senisble and default way to handle exceptions would be to redirect to a static HTML file that responds with an HTTP 200 Status Code, which is so wrong it's crazy that it's even available as an option, nonetheless set as the default.

It's also extremely confusing that IIS and ASP.NET each tries to handle errors on their own way, with their own corresponding, diverging and confusing configuration options in web.config. Being able to handle errors in one place, preferably through programmatic means so overrides can take the HTTP context into account and act on it, is not only wanted, but needed.

Please ensure that the error handling story in the next version of ASP.NET and IIS is a good one. The current one is a nightmare.

I would like to explain the motivation for the idea first, then save the actual idea for last.
I made two observations which lead me to this idea. First, I noticed how much developers, where I have worked, are disappointed when a website hotfix requires a .Net code change. Whereas with procs, they are delighted because of how easy it is to modify the small unit of code and deploy. Second, I noticed that many IT managers and code-savvy end users are comfortable with making complex queries in SQL, or doing a complex formula in Excel, but when it comes to writing even a simple line of C#, they draw a firm line there. They don't even entertain the thought.

So I gave this some thought. How is it that such a powerful and clean language as C# is not often preferred over old SQL or painful Excel formulas?
I realized the problem is not with the language. It's not that C# is too hard. SQL cursors are actually more complex that C# loops. It is the packaging of it. The code merging, the solution compiling, the references, the build server, the deployment package, the versioning etc.

Consider that with SQL Server, I can, on a whim, open up Management Studio and...
within 2 minutes, I can write a query to (maybe not the best example...) update all customer purchase data and update the "total" column to equal the amount + tax.
within 3 minutes I can also save this as proc which instantly makes it accessible to other users of the system.
within 4 minutes I can also turn this into a scheduled job to run every night.

I could do this easily in any shop that uses SQL Server. But I couldn't possibly do anything like this with asp.net even in the most well run .net shop. I’m not suggesting that developers should be making quick snappy changes directly in production. What I’m suggesting is that technology platform should not prevent me from doing so. We enjoy these privileges with SQL, why not C#.

Let me paint a picture of what my suggestion might look like:
Step 1- Open the client. A UI similar to IIS.
Step 2- Right click on the web server node, pick “new WebService”, call it "ProductWS", put it on port 80.
Step 3- Right click on the Web Service node, pick “new Method”, call it "GetProductPrices".
Step 4- Start typing out a method.
Step 5- Run it right in the IDE (like how you run scripts in Management Studio). It would run in isolation, much like a unit test method would run. If the results are good, hit Save.
Step 6- Right click on web server node, pick “new job”, set schedule to run this method every day at 8pm.

Now anyone can access this code externally at http://codehost/ProductWS/GetProductPrices
Or access it within the server by simply calling GetProductPrices. All class structures, 3rd party dlls and service references would also reside on this hosting platform. Almost like a local GAC.
I think this idea would lend itself well for hosting web services and scheduled tasks/jobs. I don’t think it would necessarily be good for hosting UI.