This package contains the official SDK tools authored by the Microsoft Dynamics 365 team.
The included command line tools are installed in the project's bin\coretools folder.
See the version list below for details.
Install-Package Microsoft.CrmSdk.CoreTools -Version 220.127.116.11
dotnet add package Microsoft.CrmSdk.CoreTools --version 18.104.22.168
<PackageReference Include="Microsoft.CrmSdk.CoreTools" Version="22.214.171.124" />
paket add Microsoft.CrmSdk.CoreTools --version 126.96.36.199
This package contains tools for the Dynamics 365 (online and on-premises). These tools may be used for application and solution development. The Microsoft .NET Framework 4.5.2 must be installed on the computer where these tools are to execute.
For information about downloading the tools, see https://docs.microsoft.com/dynamics365/customer-engagement/developer/download-tools-nuget
Updated for 188.8.131.520 CDS/XRM release
Fixed an issue in SolutionPackager.exe where it was incorrectly adding a visualizations node to savedqueries nodes
184.108.40.206: Updated for 220.127.116.119 CDS/XRM release
Updated with Xrm.Tooling.Connector support
Added new dependencies for Xrm.Tooling.Connector.dll
18.104.22.168: Adding missing file for interactive use of CrmServiceUtil. Will enabled the /il switch.
22.214.171.124: 9.0 Initial Release
9.0 Initial Release
Major updates to solution packager to support new component types. *note: SolutionPackager 8.x is not compatible with all component types in 9.x +
New interfaces to support certificate based auth.
Added support to skip discovery
Added Clone connection support of OAuth based connections
Added New Authentication type to support externally hosted auth.
**Note: Interface for Xrm.Tooling.Connector is *NOT* Final. there are new API interfaces that will be surfaced before GA.
Seveal preformance updates.
Fix to memory leak in Microsoft.Xrm.Tooling.Connector.TraceLoggerBase. Trace Listener collection would not be released within a process over a very long time frame over multiple connections. This would manifest as increasing memory consumption over a very long period.
Fix cleans this up on the .dispose() call on the CrmServiceClient.
Note: if you have built your own logger based on the Microsoft.Xrm.Tooling.Connector.TraceLoggerBase, you must call .dispose() when you are done with it to clean up the listener collection assigned to it.
Addressed an issue with customers who use optionset type generators and or linq class access that do not have a handler to define type enum’s for optionsets. This update will provide support for older behaviors in addition to supporting developer who use enum based optionset generators
Updated to correct version of crmsvcutil for the current version of CRM that exposes all command line switches
Fixes in dependency mapper and that caused issues with some solutions
126.96.36.199: Fix of dependency issue in nuget package. Now properly requires .net 4.5.2 as a baseline
188.8.131.52 Refreshed from current release
Fixed site map packing issue in solutionpackager.exe
8.2.0: Removed Deprecated Assemblies and Executables. Updated to current bits.
184.108.40.206: Updated the Microsoft.IdentityModel.Clients.ActiveDirectory assemblies as required by the Xrm Tooling assemblies.
8.1.0: CRM Online 2016 Update 1
8.1-preview: Pre-release CRM Online 2016 Update 1
220.127.116.11: UR1 (Update Rollup 1) with customer related hotfix
8.0.2: UR1 (Update Rollup 1)
8.0.1: GA (General Availability)
8.0.0: RTM release
* The CrmSvcUtil.exe program has been updated with additional command line parameters. For more information, run the program with no parameters to see the online help.
This package has no dependencies.
GitHub repositories (2)
Showing the top 2 popular GitHub repositories that depend on Microsoft.CrmSdk.CoreTools:
An open-source library for building Dynamics CRM XRM solutions using Script#, jQuery & Knockoutjs.
xRM CI Framework provides you with the tools automate the build and deployment of your CRM Solution. Using the framework to implement a fully automated DevOps pipeline will allow you to deploy more frequently with added consistency and quality.