CrmSdk. XrmTooling. PackageDeployment
This package contains the following official Microsoft assemblies and has been authored by the Microsoft Common Data Service SDK team.
See the version list below for details.
Install-Package Microsoft.CrmSdk.XrmTooling.PackageDeployment -Version 126.96.36.199
dotnet add package Microsoft.CrmSdk.XrmTooling.PackageDeployment --version 188.8.131.52
<PackageReference Include="Microsoft.CrmSdk.XrmTooling.PackageDeployment" Version="184.108.40.206" />
paket add Microsoft.CrmSdk.XrmTooling.PackageDeployment --version 220.127.116.11
This package contains assemblies for Dynamics 365 (online and on-premises). These assemblies require application development using the Microsoft .NET Framework 4.6.2 or later.
Correcting Dependancy Info on Package
Fixed bug in CrmServiceClient which would cause some OnPrem connections to fail with an error "Item already added to List"
Minor Pref Improvements
Updated to include Fixed version of CrmServiceClient and login control for new US Geo ( US Gov High )
Added support for Preferring Affinity with a given node to improve cache hit success rate.
.Net 4.6.2 is now required for this assembly.
Fixed a user reported issue that would cause an import patch to fail due to being misapplied.
Fixed a user reported issue that would cause the incorrect version of a solution to be imported under some circumstances during update.
Added better error detection for failed Async Jobs when using Async Solution Import.
Major updates to error logging to make logs more concise and useful.
Corrected an issue which would occur while importing a package that contained an upgrade for a deployed solution, where a prior version upgrade had failed leaving a holding solution. The system will now attempt to apply the current holding solution, and upon success, apply the new upgrade contained.
Picked up updated CrmServiceClient (Microsoft.Xrm.Tooling.Connector)
Added new property for packages developers called CurrentPackageLocation.
This will provide the path to the drop location for your package assets directory to your package.
Corrected use of strong types inside Package Deployer to allow it to work properly with packages that also include overlapping strong typed objects.
Corrected a case where Async Solution Deployment could fail and not be correctly caught by PD.
Updated install flows to more correctly trigger failures on failures within user code or data import.
Importconfig.xml - Solutions node updates.
Added requiredimportmode as an option to force an Async or Sync import behavior for a given solution.
This includes, upgrade or new install.
Valid settings for this property are :
async - Requires the Import of this solution to be done in an async manner if the server supports it.
sync - Requires the import of this solution to be done in a sync manner if the server supports it.
Default behavior follows the default setting for the Package Deployer Core Process.
Updated with Xrm.Tooling.Connector support
Fixed issues that caused unhandled exceptions to be thrown when a package resulted in an error.
Added new notifications in logs and UX for faults (where applicable).
Added logic to detect stuck solution import and abort the import process
18.104.22.168: Fixed a bug in CMT Lookup processing logic that was causing incorrect linking where the data set includes records that require related lookup records which share the same default name.
22.214.171.124: 9.0 Initial Release
Updated for 9.x assemblies and Xrm.Tooling 3.x
Addressed an issue where PD would fail to handle a previously failed upgrade, ending up getting stuck on trying to rerun upgrade on a solution that is already partly through the process. New behavior will cause PD to recognize this state and attempt to complete the upgrade vs calling Import again. Package developer note: When this state occurs the upgrade action (RunSolutionUpgradeMigrationStep) call will NOT be called as its expected that this code would have run on the prior run that failed.
New package function: OverrideSolutionImportDecision support to override import decisions for individual solutions. This function will allow you to skip a solution or force it to update where PD would have skipped, other functions are limited at this time.
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: Assembly version changed to 184.108.40.206
When Logging provider is supplied, it is now being pushed to package log sinks.
Fixed support for using flat file import ( CRM native support ) on non-English organizations
Fixed an infinite wait loop that could occur if DeleteAndPromote call failed during upgrade to CRM with a Connection Timeout error.
Fixed an issue in the upgrade detection logic that incorrectly compared versions of source and target solution, under some conditions a newer version of the solution on import was incorrectly determined to be an older version causing it to be skipped.
Added Binding redirect logic to attempt to handle some versioning issue with supporting assemblies.
Support for new App.Config setting called SuppressImportLog, when true will prevent the detailed log from being written to disk.
Capability notes, *important!:
The function PreSolutionImport(string solutionName, out bool overwriteUnmanagedCustomizations, out bool publishWorkflowsAndActivatePlugins); has been flagged as Obsolete and will no longer be called.
It has been REPLACED by the function:
PreSolutionImport(string solutionName, bool solutionOverwriteUnmanagedCustomizations, bool solutionPublishWorkflowsAndActivatePlugins, out bool overwriteUnmanagedCustomizations, out bool publishWorkflowsAndActivatePlugins);
8.1.0: CRM Online 2016 Update 1
8.1-preview: Pre-release CRM Online 2016 Update 1
8.0.2: UR1 (Update Rollup 1)
- Microsoft.CrmSdk.XrmTooling.CoreAssembly (>= 220.127.116.11)
Showing the top 1 GitHub repositories that depend on Microsoft.CrmSdk.XrmTooling.PackageDeployment:
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.
Read more about the GitHub Usage information on our documentation.