This post originated from an RSS feed registered with .NET Buzz
by Christian Weyer.
Original Post: The future of .NET's context architecture
Feed Title: Christian Weyer: Web Services & .NET
Feed URL: http://www.asp.net/err404.htm?aspxerrorpath=/cweyer/Rss.aspx
Feed Description: Philosophizing about and criticizing the brave new world ...
The one or the other of you might already know it. But it is so important
that I want to explicilty point it out here. I just listened to Don Box's heavily
discussed MSDNTV show and it was full of interesting information - of
course ... but what I want to repeat here is a small sidenote in his section on
"Extensibility makes abstraction expensive". He talked about the extensibilty
mechanisms and hooks in MTS/COM+ and why they are not meant to be for the public
and they are actually bad ... then he shifted over to .NET:
" .. in .NET we have the so called the .NET context architecture, which
is undoc'ed [...] we're gonna kill it. [...] We will keep it working
forever, but it's a dead end ..."
He further explained that interop with MTS/COM+ was the primary goal of this
implementation (which I guess they wanted to completely hide by marking it
internal, but eventually it got public somehow ...) - I suppose we should live
with it and avoid things like this or that - or at least try to avoid building
'rock-solid' architectures on top of it. So we all hope to see and hear more
about future plans and how all of this is related to the magic Indigo at PDC in LA.
Previous Topic
