web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / How to replace Microso...
Microsoft Dynamics CRM (Archived)

How to replace Microsoft.XRM.SDK.dll from version 6.0 to 8.2 in C# plugin

(0) ShareShare
ReportReport
Posted on by MSCRM learner 170

Hi,

I have created a solution which is having a plugin in C# referring the Microsoft.XRM.SDK.dll version 6.0.

Many of our customers with CRM version 2013, 2015, 2016 and dynamics 365 have this solution installed. One of the customer has complained to replace the dll to latest version. (because of https://crmgiant.eu/errors/important-information-about-your-microsoft-dynamics-crm-online-service-acs-for-authentication/).

Please let me know how to update the dll to latest version 8.2 in the C# plugin.

Do I need to refer the 8.2 dll in C# plugin code and again register the plugin, create managed solution...

and then import the upgrade solution on the client's CRM.

OR is there any other way of doing this?

Also one more point - the same solution, I have already installed for customers having CRM version 2013. So the question is upgrading the dll to 8.2, will it  get supported by CRM 2013 ?

Thanks in advance.

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    imayur Profile Picture
    imayur 630 on at

    Hi,

    Remove all previous Xrm assemblies from references in solution explorer.

    the go Tools menu ->  Nuget Package Manager -> Package manager console

    enter below command in package manager console and press enter make sure you have selected plugin project in paackage manager console dropdown and press enter

    Install-Package Microsoft.CrmSdk.XrmTooling.CoreAssembly -Version 8.2.0.2

    alternative to package manager you can download Dynamics CRM SDk and remove old Xrm assemblies from project and from From SDK bin folder add newer ones from SDK.

    the resolve references in code and build. Done!

  • MSCRM learner Profile Picture
    MSCRM learner 170 on at

    Thanks Mayur for the response.

    So my question is do I need to update the plugin code as stated by you and then register the  plugin, create managed solution and then import the upgrade solution on the client's CRM OR is there any other way of doing this?

    Also one more point - the same solution, I have already installed for customers having CRM version 2013. Upgrading the dll to 8.2, will it  get supported by CRM 2013 ?

  • Suggested answer
    imayur Profile Picture
    imayur 630 on at

    I don't think code needs replacement unless some functions in your code are deprecated in new SDK. You just need to remove old 2013 dlls and replace with new ones which are compatible with your crm version. then clean and build.

    Solution with 8.2 dlls will not support 2013 CRM because 2013 CRM runs on .NET 4 and later CRM version needs .NET 4.5 above. So you have to maintain different versions of solutions.

  • MSCRM learner Profile Picture
    MSCRM learner 170 on at

    Thanks Mayur for your prompt response and answering to the question that I need to maintain different versions of solutions.

    Let's say for the CRM version >2013, I build the C# plugin, after that do I need to register the plugin, create managed solution and then import the upgrade solution on the client's CRM OR is there any other way of doing this?

    I am asking this particularity for plugins which require dll upgrade.

  • Suggested answer
    imayur Profile Picture
    imayur 630 on at

    I think you have taken wrong for Solutions(I meant Visual Studio Solution). Just use plugin registration tool to add/update plugins/dlls.

    Its all about your CRM support for framework and SDK.

    4064.1111.JPG

    If you are migrating plugin to higher version. Open your Plugin project update you Xrm Dlls resolve references if needed or probably need to use newer functions if some are deprecated then Clean and build. and register new plugin into CRM. If your Plugin project is migrated to higher CRM version probably it wont work in previous CRM versions because .net framework dependency or you plugin will crash (Exceptions). Its not recommended to register old or new dlls into CRM because of framework or SDK dependencies.

    So you need maintain different projects  depending on SDK support for different CRM versions.

  • MSCRM learner Profile Picture
    MSCRM learner 170 on at

    Thank you Mayur.

    I am referring here the MSCRM solution. The C# plugin is at the end referred in MSCRM solution. Let's say I have created a  mscrm solution only for CRMs higher than 2013 version which is having a plugin created in C#. Now if I update the C# plugin to newer version of dll then do I need to follow the below steps -

    1. Register the plugin again.

    2. Create managed MSCRM solution.

    And then import the upgrade solution at client side

    Is this the correct way to upgrade the plugin in CRM ?

  • Suggested answer
    imayur Profile Picture
    imayur 630 on at

    Both are valid/recommended approaches to update and add new plugin

    If you export plugin assembly in solution it may include SDK messaging steps associated with it, so you don't need to define the plugin steps again.

    If you want to deploy plugin from one instance to another instance solution is the best approach. If you want to add/update only dll or  plugin steps then use plugin registration tool.

  • MSCRM learner Profile Picture
    MSCRM learner 170 on at

    Thank you so much Mayur.

    Actually I already have lots of customers running with the CRM solution which I need to upgrade now for the C# plugin. So it is required to update the solution at one place and then import the upgrade to all the customers so that all of them will then have the latest SDK dll in the plugin in the solution. So as per your opinion I need to create an upgrade solution which will have the updated plugin with latest dlls and import it to all the customers.. right?

  • Verified answer
    imayur Profile Picture
    imayur 630 on at

    right! As long as the plugin made in SDK supports you customer CRM version.

  • MSCRM learner Profile Picture
    MSCRM learner 170 on at

    Thanks for your response Mayur. Will follow the same and start working on creating the upgrade solutions.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans