Ramblings from the Creator of WilsonDotNet.com
Compare the time it takes to call a method in your ContextBound object with the time it takes to call a standard class. Then you'll discover why O/R mappers that use this approach are sooo slooow.
ContextBound objects vs. normal objects are very slow. Unfortunately, this is the only easy way to do this type of call interception right now (there are some other ways to do it, such as re-jitting stuff on the fly...but they are a lot more difficult).
Also ContextBoundObjects are no longer under development by Microsoft. They will not be thrown away, but nothing new is going to be done to them (so says Don Box at a conference I can't remember...I want to say the Chris Sells XML conference), and they won't support them if something breaks.
Justin's remarks aren't exactly true - remoting is getting some work done in whidbey. Also, I believe that Microsoft will support remoting if it just 'breaks'. At the PDC, Don Box launched is initial talks with the mantra that remoting as we know it is dead, but after a relatively large uproar from the developer community, he toned down that message by several decibels. By the end of the conference, Don was suggesting that Microsoft would continue to support remoting, and that if you wished to keep using it, 'go in peace'.
Hi, Your blog contains good info. Keep it up.
there is a beta product out there called loom.net that helps you design fault tolerance into your system. i believe the guy doing it is also sponsored by microsoft....you can download it easy enough (i forgot the exact url but you can google for it). it has some sweet content describing how it can be done and it can give you a rough preview of how it might be implemented into .net at some point in the future (conjecture but you gotta imagine it will at some point). also i have been trying to get an article or two published about using attributes to assign behavior (and validation) to class properties, method parameters and such. we are using it where i am at and it is pretty cool. i can share with you some of my thoughts on it if you like.
Check this out. <A href="http://www.microsoft.com/downloads/details.aspx?FamilyID=80df04bc-267d-4919-8bb4-1f84b7eb1368&DisplayLang=en">Microsoft Enterprise Instrumentation Framework</a>
Lets try that again shall we... http://www.microsoft.com/downloads/details.aspx?FamilyID=80df04bc-267d-4919-8bb4-1f84b7eb1368&DisplayLang=en
EIF and most all the MS Application Blocks are just way overkill. Log4Net is almost always better, due to simplicity, than EIF.
Hai, up to this is good need more