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 :
Microsoft Dynamics CRM (Archived)

Issue with deploying plugins using dynamics 365 version 9 assemblies

(0) ShareShare
ReportReport
Posted on by 7

I am trying to deploy plugins & workflows using dynamics 365 developer toolkit (onprem). We are using latest version 9 xrm sdk assembilies and .net framework 4.6.2 using visual studio 2017 for our plugins & workflows.

Previously with version 8.2, we could download crm sdk which had bin folder and all the needed tools. Configuring tool paths to these in visual studio worked  for deployment without any errors. But with version 9 we don't have sdk download anymore and we can get all the tools as nuget packages. What do I set tool path for sdk bin folder now for version 9 in visual studio. Just to see if it works I copied bin folder from version 8.2 and replaced all version 9 dll's and that didn't worked.

I know we could use plugin registration tool, but just wondering if any one was able to deploy successfully with developer toolkit crmpackage deploy option targeting version 9 assembilies. 

*This post is locked for comments

I have the same question (0)
  • Nflannery Profile Picture
    360 on at

    What is the error you are getting?

  • PrashantAdepu Profile Picture
    7 on at

    I am getting this error

    Could not load file or assembly 'CrmLibraries, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference.

  • Suggested answer
    Pawar Pravin Profile Picture
    5,237 on at

    Hi Prashant,

    Please check your assembly version, it should be like :

    pastedimage1562736023671v1.png

  • PrashantAdepu Profile Picture
    7 on at

    I checked the assembly version and they are version 9 assemblies (9.0.37.948). Not sure why the error mentions 'CrmLibraries version 8.0'. Between we upgraded from version 8.2 to 9 and verified all the assemblies point to version 9. Not sure if microsoft dynamics 365 developer toolkit work with version 9 assemblies.

  • Cristalls Profile Picture
    45 on at

    Hi. Try downloading the latest tools using the information in this link then try again. docs.microsoft.com/.../download-tools-nuget

  • Coty Profile Picture
    89 on at

    I'm having similar issues.  The OP posted a particular question:  in the version 9 SDK there is no BIN folder.  These are the available folders:

    ConfigMigration

    CoreTools

    PackageDeployment

    PluginRegistration

    I am using VS 2019.

    If I set the Tools path, under Tools > Options > Dynamics 365 Developer Toolkit > Tools Path.  To the following, VS 2019 crashes.

    pastedimage1591622511777v1.png

    I've been struggling with this for days now....

  • Coty Profile Picture
    89 on at

    Just an update on things I have tried - If I use any DLL from v9 at all, VS 2019 crashes.

    - Using the v8 folders, but updating all DLLs to v9 that had a match.

    - Added all files from all 4 folders into one folder from the v9 download.

    - Updated just the Registration tool path to v9

    - Updated just the Bin tool path to v9  (Tried combined bin, just v9 bin, or all files folder I created)

    Last ditch effort - I took the v8 BIN and started coping over DLLs one by one - to see which file crashed the program:

    Microsoft.Xrm.Sdk.dll - GOOD

    microsoft.xrm.sdk.workflow.dll - GOOD

    Microsoft.Crm.Sdk.Proxy.dll - GOOD

    Microsoft.IdentityModel.Clients.ActiveDirectory.dll - GOOD

    Microsoft.Xrm.Sdk.Deployment.dll - GOOD

    Microsoft.Xrm.Tooling.Connector.dll - CRASHED - Reverted back to v8.

    Microsoft.Xrm.Tooling.CrmConnectControl.dll - CRASHED - Reverted back to v8.

    Microsoft.Xrm.Tooling.Ui.Styles.dll - GOOD

    Copied these 3 files which CRASHED it again.

    CrmSvcUtil.exe

    CrmSvcUtil.exe.config

    CrmSvcUtil.xml

    Manually updated CrmSvcUtil.exe.config.  This file holds version information for the CrmSvcUtil.exe program which uses the DLLs i replaced above.  The net result of the change is to use the v9 config file, but change the following 2 lines in the file back to use the old DLL versions:

        
        
    
    
        
        
    

    CrmSvcUtil.xml - this file copies over fine and it doesn't crash.  There's a lot of new entries in the v9 version of the file however referencing Microsoft.Crm.Services.Utility.{new namespace}.

    After all of these changes - I copied the CrmSvcUtil.exe v9 into the BIN - still CRASHED.

    This is the crash error in the event log:

    Application: devenv.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.FormatException
    at System.Version VersionResult.SetFailure(ParseFailureKind, System.String)
    at System.Version.TryParseComponent(System.String, System.String, VersionResult ByRef, Int32 ByRef)
    at System.Version.TryParseVersion(System.String, VersionResult ByRef)
    at System.Version.Parse(System.String)
    at System.Version..ctor(System.String)
    at Microsoft.CrmDeveloperTools.OptionsWindow.PathSettingViewModel.ValidateSettings(System.String ByRef)
    at Microsoft.CrmDeveloperTools.OptionsWindow.PathSettingDialogPage.OnApply(PageApplyEventArgs)
    at Microsoft.VisualStudio.Shell.DialogPage DialogSubclass.WndProc(System.Windows.Forms.Message ByRef)
    at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr, Int32, IntPtr, IntPtr)
    at Microsoft.VisualStudio.Shell.Interop.IVsUIDataSource.Invoke(System.String, System.Object, System.Object ByRef)
    at Microsoft.Internal.VisualStudio.PlatformUI.DataSource.Invoke(System.String, System.Object, System.Object ByRef)
    at Microsoft.VisualStudio.PlatformUI.VsCommand.Execute(System.Object)
    at MS.Internal.Commands.CommandHelpers.CriticalExecuteCommandSource(System.Windows.Input.ICommandSource, Boolean)
    at System.Windows.Controls.MenuItem.InvokeClickAfterRender(System.Object)
    at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
    at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
    at System.Windows.Threading.DispatcherOperation.InvokeImpl()
    at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
    at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)
    at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
    at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
    at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
    at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
    at System.Windows.Threading.DispatcherOperation.Invoke()
    at System.Windows.Threading.Dispatcher.ProcessQueue()
    at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
    at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
    at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
    at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
    at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
    at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
    at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)

    PluginRegistration Tool Directory:

    I copied all the files over one by one - here are the files that caused a Crash:

    PluginCommonControls.dll

    CrmLibraries.dll

    I removed this file:

    Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms.dll

    Note - this is not really a solution yet.  I can set my tools paths now in VS without it crashing using these 2 modified folders I created but mixing and matching the DLLs made it so I can't connect correctly to my CRM instance.  I'm just putting this here in case this information helps someone troubleshoot.

    Thanks.

  • LakMat Profile Picture
    5 on at

    Any luck with this issue? After one year on I am still having this problem and used version 8 till now. Recently it stopped working saying FCB 'EnableRegionalDisco' is disabled when I am trying to connect to an organisation and when googled this problem they said update to the latest version of dll and it works. But visual studio is still crashing with new version 9 dlls. Any of you are having same problem?

  • Paul2014 Profile Picture
    5 on at

    pastedimage1631480420178v1.png

    trying to install this package to no avail can someone help? 

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