While I make an assumption on the part of CRM 2011 in this regard, the core reason for CRM 4's implementation of single-instance Plug-In objects is for performance, especially in light of constructors which call out and apply configuration data. In
this way, I'm absolutely certain CRM 2011 would have kept this model going forward--indeed, the fact that the basic structure IPlugin remains unchanged would be a good indicator. It's also important to realize that each IIS worker process has its own
instance of the custom Plugin class, meaning that class-member adjustments in one will not be available to another. It would be wise, considering this, to approach your class-member attributes as "readonly", since that's really the best way to use them
appropriately.
Dave Berry - MVP Dynamics CRM -
http:\\crmentropy.blogspot.com Please follow
the forum guidelines when inquiring of the dedicated CRM community for assistance.
