Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Plugins in default solution show modified on as a current date but behavior looks like an older version RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    So, the real question could be, how can you tell what version of the plugin assemblies is actually in effect?

    The assembly is coming from a managed solution.  The default solution contains unmanaged components as well.

    CRM 2013 (6.1.0003.0119)

    Friday, April 8, 2016 3:57 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hmmm.  Could there be 2 copies trying to execute?  The newest Plugin Reg tool can view by entity, check if there is more than one, or if there is an issue with execution order?
    Friday, April 8, 2016 6:29 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    If you look at the default solution, you can see what verson of the plugin assembly that is present and which date it was modified on. If you have the same assembly in both a managed and an unmanaged solution you might have problems...

    Regards

    Rickard Norström Developer CRM-Konsulterna
    http://www.crmkonsulterna.se
    Swedish Dynamics CRM Forum: http://www.crmforum.se
    My Blog: http://rickardnorstrom.blogspot.se

    Monday, April 11, 2016 3:05 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    That is our theory.  That it got into the unmanaged "layer" at some time in the past and is not being replaced by the importing of the managed.  We don't "overwrite customizations" because there are unmanaged customizations that we don't want overwritten.

    So, how do we clear up the issue?

    thanks for looking...
    • Edited by mardukes Monday, April 11, 2016 3:50 PM thanks
    Monday, April 11, 2016 3:49 PM