CrmSdk. XrmTooling. PackageDeployment. PowerShell
This package contains the official Microsoft assemblies for Package Deployer Powershell and has been authored by the Microsoft Dynamics CRM SDK team.
See the version list below for details.
Install-Package Microsoft.CrmSdk.XrmTooling.PackageDeployment.PowerShell -Version 18.104.22.168
dotnet add package Microsoft.CrmSdk.XrmTooling.PackageDeployment.PowerShell --version 22.214.171.124
<PackageReference Include="Microsoft.CrmSdk.XrmTooling.PackageDeployment.PowerShell" Version="126.96.36.199" />
paket add Microsoft.CrmSdk.XrmTooling.PackageDeployment.PowerShell --version 188.8.131.52
This package contains assemblies for Dynamics 365 (online and on-premises). These assemblies require application development using the Microsoft .NET Framework 4.5.2 or later.
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)
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.
Corrected a spelling issue on the return of Get-CrmPackages, Property PackageInfo.PacakgeAssemblyLocation was renamed to PackageInfo.PackageAssemblyLocation
Updated install flows to more correctly trigger failures on failures within user code or data import.
UseAsyncForSolutionImport - added to commandlet
This setting controls the default behavior of the import operations for Package Deployer.
If set to true, Package deployer will attempt to use an Async Pattern for all solution operations where possible to do, given the server configuration.
The default setting for this is false ( sync mode )
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
Added new dependencies for Xrm.Tooling.Connector.dll
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
Fixed a bug in Configuration Migration tool Lookup processing logic that was causing incorrect linking where the data set includes records that require related lookup records that share the same default name.
184.108.40.206: 9.0 Initial Release
Refactor of this package to support module invocation instead of assembly registration. This is done to support direct inclusion from nuget by ALM \ SDL tasks.
To register module, run the RegisterXRMPackageDeployment.ps1
220.127.116.11 - Intial release
- No dependencies.
This package is not used by any popular GitHub repositories.