One of the things I never have quite understood everyone has to build the plugin regristration tool. It’s like some kind of CRM developers rite of passage and a confusing way to get started in the CRM development world.
I guess the reason must be something to do with legal liability or some trifling matter.
I have moved computer so I had to go through the process again, it also gave me the opportunity to download the new 5.05 CRM 2011 SDK with it’s new fancy add ins within in Visual studio (I haven’t tried that yet).
so I tried to build the plugin registration tool and I got the error
Error 1 The type ‘Microsoft.IdentityModel.Protocols.WSTrust.RequestSecurityTokenResponse’ is defined in an assembly that is not referenced. You must add a reference to assembly ‘Microsoft.IdentityModel, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’.
big long errors like this are always a bit tricky to type into google, it’s too many words but I had come up agaisnt this problem before, so I ended up searching my own blog and typing in the word foundation brought up the winning ticket.
Basically I needed to download the Windows Identity Foundation download which you can find here
I downloaded and ran that and the problem was fixed.
There was also a plugin profiler lurking in the directory but I have no idea what that is and can’t find any information about it.
I have to say the CRM 2011 SDK has loads more sections and examples added to it, compared to the first couple of editions. Keep up the good work Microsoft.
Hosk's Dynamic Blog 
The plugin profiler is used to debug the plugin in a much easier manner than ever before when it comes to MS Dynamics CRM. I tried the plugin profiler to debug a plugin in dynamics crm 2011 & it is running very well.
Now life has been made much simpler for plugin developers to debug plugin code with the help of this.
Good going microsoft when it comes to MS Dynamics CRM 2011.
LikeLike