Lack Of ServicedComponents Knoweledge
I wanted to jump right into Jesse’s ServicedComponets thread, but instead I decided to sit back and try to understand the real problem here. After a couple days, and plenty of different ideas tossed around in my mind, I think I distilled the problem down to its basic components.
- System.EnterpriseServices (and COM+ before that) is not understood by the mainstream Microsoft platform developers.
- We (that is Microsoft and the Non-MS Evangelist community) are not doing a good job teaching the mainstream developer the major architectural shift required to properly use System.EnterpriseServices.
As someone who attends plenty of .Net User Groups, I can tell you that when this topic is covered, the people that get it are bored, and the majority that needed to learn it are confused. A 40 minute session is not enough time to truly understand the paradigm shift. There are a bunch of topics that I can think of (including System.EnterpriseServices) that require a session on the real world situations that the topic is supposed to help resolve. We get so caught up in showing how to use this new technology, that we forget to teach the others the business reason behind the innovation. I’m guilty of this myself, and from now on, I’m going to make a greater effort to teach the theory in lieu of the technology.
And to make matters worse (for System.EnterpriseServices) the XML Web Services and Server Components Development exams (70-310/70-320) barely touch upon System.EnterpriseServices. It seems to me that to get the MCSD cert, besides the Solution Architecture Exam (70-300), they should add an exam that covers just System.EnterpriseServices. To truly be a architect you really should know COM+ like the back of your hand.
Don XML