locked
crmimpersonator and strongly typed classes RRS feed

  • Question

  • hi 

    i've been developing customizations for crm 3 for a while, now i have to start developing to version 4 and have a big confusion about authentication and crmimpersonator...

    for what i've been reading, crmimpersonator must be implemented to make authentication compatible with both on-premise and ifd deployment. the big problem i found is that crmimpersonator requires the sdk assembly, this makes the use of dynamic entities mandatory... i think this is nonsense and makes development far more complicated than using strongly typed entities.

    is there any way of authenticating against ifd and using strongly typed entities at a time?

     thanks.
    Thursday, April 29, 2010 2:35 PM

Answers

  • Perosnally I don't think the development overhead of using the sdk assemblies and DynamicEntity is too great - the sdk assemblies also include methods, classes amd constructors that ease development.

    However, if you want to keep using the WSDL references, you could try:

    1. Keep the references to the sdk assemblies, and use the standard code with CrmImpersonator and ExtractCrmAuthenticationToken
    2. Create your WSDL CrmService class as usual, and create an instance of CrmAuthentication token
    3. Read the values of the CallerId, CrmTicket and OrganizationName properties from the result of the ExtractCrmAuthenticationToken method, and write them into your new token in step 2

    Microsoft CRM MVP - http://mscrmuk.blogspot.com  http://www.excitation.co.uk
    • Marked as answer by Jim Glass Jr Monday, May 3, 2010 3:26 PM
    Friday, April 30, 2010 9:51 AM
    Moderator