Can you drop any hints as to when we'll get details on the WebAPI/MVC merger? When I heard the news I was both really happy, and quite worried :)
So many questions at the moment, and with a new web service in full production I start to think about possible risks.
* Can we expect major changes to the WebAPI framework architecture? Already invested quite a bit code in the current architecture with delegating/operation handlers etc. I don't mind refactoring if there are some good gains.
* Can we expect to use MVC tech in our Web APIs? Routes obviously, but what about things like AuthorizeAttribute, some per-request context (something like MVC's HttpContext), action filters? We've spent time writing functionality for WebAPI that already
exists in MVC (for ex. authorization).
* Will MVC itself get benefits from WebAPI? DelegatingHandler, OperationHandler etc? :)
* Then I guess MVC and WebAPI will have quite a few common classes.
* Will this affect the frequency of WebAPI drops? Only one preview has been released of MVC 4, I guess we have to wait for the first beta now?
* And I guess being bundled with MVC also means the release is more closely tied to .NET 4.5.
Just something like "expect detailed information in x weeks" would be great and help me with planning. We have a big release coming up in ~4 months, and if all of this is still a long way out I will probably stick with and release a service
with WebAPI preview 6.
But I really hope this will bring us a more mature and better framework. There are definitely some similiarities between the two frameworks and I think each can benefit from the other.