Microsoft.Xrm.Tooling.PackageDeployment.Powershell

Author(s)

• Microsoft Common Data Service Team

Cmdlets

Get-CrmPackages Import-CrmPackage

Dependencies

This module has no dependencies.

Release Notes

Current Release:

3.3.0.888
Updates to internal architecture of PD.  
Corrected a possible bug in solution install leg that would result in a "Null Object" Error
Added in memory configuration parsing logic
Optimized dependency checking logic


3.3.0.882:
Cleaned up extra lines in logging output.
Adding Logging for time taken during configuraiton parsing to aid in performance info.
Uptook New CDS SDK drop.
Updated the Import-CrmPackage cmdlet to accept the output of the Get-CrmPackage cmdlet.
This will allow a used of the powershell module to use Get-CrmPackage to find the package that they want, then pass that package info directly to Import-CrmPackage.


3.3.0.879:
   Fixed an issue preventing logs from being generated correctly,  Logs should once again write to the log directory

3.3.0.874:
   Added Improvements to Async solution import logic
   Updated for current xrm sdk
Includes updates from the CMT.

3.3.0.862
ADAL 3.19+ is now required for this module.  ADAL 2.x clients will need to be updated to use ADAL 3.x+

3.3.0.858
Added support for France and New US Geos
Added new behavior to return the full login error when initial connect fails in LastException.
Fixed https activation issue introduced by .net 4.8. - This should no longer require http activation to be enabled on windows.
Fixed issue where a long running cloned connection loses its access token.

3.3.0.844
(Nuget-9.0.2.19)
Logging Updates
Added support for forcing all packages to run Sync mode, regardless of how a given package is configured.
Modified RaiseFail event for RaiseFail generated from the package.  New behavior will cause PD to stop with an overall failure.

3.3.0.841 - (Nuget-9.0.2.16):
Added native support for handing throttling messages from server.
Improved handling of retry logic for blocked imports due to concurrent metadata import

#### VERSION RESET HERE TO NOW FOLLOW BUILD VERSIONS OF THIS MODULE...

NOTE: Notes Below are synced to Nuget Release Found here: https://www.nuget.org/packages/Microsoft.CrmSdk.XrmTooling.PackageDeployment.PowerShell/
9.0.2.12:
Correcting Dependency Info on Package
Fixed bug in CrmServiceClient which would cause some OnPrem connections to fail with an error "Item already added to List"
Minor Perf Improvements
 
9.0.2.11:
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.

9.0.2.9:
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.
         
9.0.2.8:
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.

9.0.2.7:
Picked up updated CrmServiceClient (Microsoft.Xrm.Tooling.Connector)

9.0.2.5:
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

9.0.2.4:
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.

9.0.2.3:
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

9.0.0.7:
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.

9.0.0.5:
9.0 Initial Release

9.0.0.2-preview:
Breaking Change!
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

8.2.0.4 -
Initial release