Phht, whats he doing on here

, kidding.. nice to hear something from the asp.net guys, been a bit shady recently bar the new previews..
I know its a big topic but I still think theres place for a server side declarative language for asp.net (other than that of webforms).. I'm talking something more light weird.. a reall simple interface for rendering and then abstractions made from that.. doing inline code is ok but its going really far back in order to fix some gripes that isn't so much related to server side declarative code.. just more that the default one webforms uses isn't so well executed..
Plus, you guys need to push for deeper changes in asp.net, you're making a neat layer on top of a lot of crap (not all of it), but god theres a lot of messy stuff going on in asp.nets plumbing.. it would be nice if you guys had your own viewpage that didn't sit on top of the webforms page..
Also, I've gotta ask why routing forces you to return a http handler.. I've written route handlers that I ended up doing something like:
IHttpHandler GetHttpHandler(RequestContext requestContext)
{
return new DummyHandler(x =>
{
.. code here to fire on ProcessRequest ..
};
}
Seems if you just let the route handle processing the request, then you could easily get the functionality to call a ihttphandler by writing a basic route handler that created the http handler and pushed the http context to it.. but you could also just run processing directly from the routehandler without needing to create a dummy http handler.
Anyway! cool to hear from you.