Geeks With Blogs
Wes Weeks

When developing for CRM, we like to keep our business login contained within its own class to be shared and used by other parts of the system.  Most all of our CRM implementations have other applications accessing CRM in one way or another so this approach works well.  This was fairly straight forward wtih the 3.0 callout model, you just had to put them in the same directory with your custom callout  (C:\Program Files\Microsoft CRM\Server\bin\assembly\  in most cases) .

The way around this is to either put your assemblies in the GAC, or drop the assemblies in the bin directory of the CRM Web application (which is the route we chose).

Another caveat is your assemblies MUST be signed.  This was a bit of a pain to get working because we had a few unsigned third party assemblies and a signed assemblie can only reference other signed assemblies.  Probably the biggest issue was the Plugin deployment tool registered the unsigned assemblies without any issue, and we were without any error messages explaining why our code wasn't running.  In CRM 3.0 you could use unsigned assemblies by setting a config setting to 'allowUnsignedAssemblies' to true.

Hope these two pointers helps you out with your development...

Posted on Monday, February 23, 2009 3:39 PM Microsoft CRM | Back to top

Comments on this post: Using external assemblies with CRM 4.0 Plugins

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © Wes Weeks | Powered by: