Microsoft.CrmSdk.XrmTooling.PackageDeployment.Wpf 9.1.0.42

The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org. Prefix Reserved
There is a newer version of this package available.
See the version list below for details.
dotnet add package Microsoft.CrmSdk.XrmTooling.PackageDeployment.Wpf --version 9.1.0.42
NuGet\Install-Package Microsoft.CrmSdk.XrmTooling.PackageDeployment.Wpf -Version 9.1.0.42
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Microsoft.CrmSdk.XrmTooling.PackageDeployment.Wpf" Version="9.1.0.42" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Microsoft.CrmSdk.XrmTooling.PackageDeployment.Wpf --version 9.1.0.42
#r "nuget: Microsoft.CrmSdk.XrmTooling.PackageDeployment.Wpf, 9.1.0.42"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Microsoft.CrmSdk.XrmTooling.PackageDeployment.Wpf as a Cake Addin
#addin nuget:?package=Microsoft.CrmSdk.XrmTooling.PackageDeployment.Wpf&version=9.1.0.42

// Install Microsoft.CrmSdk.XrmTooling.PackageDeployment.Wpf as a Cake Tool
#tool nuget:?package=Microsoft.CrmSdk.XrmTooling.PackageDeployment.Wpf&version=9.1.0.42

This package contains the following official Microsoft assemblies and has been authored by the Microsoft Common Data Service SDK team.
- Dynamics 365 Package Deployer

There are no supported framework assets in this package.

Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
9.1.0.129 22,862 2/24/2023
9.1.0.116 4,074 12/15/2022
9.1.0.104 18,047 6/18/2022
9.1.0.88 26,875 12/9/2021
9.1.0.84 10,639 11/4/2021
9.1.0.72 30,044 4/12/2021
9.1.0.45 15,900 10/25/2020
9.1.0.42 10,718 7/15/2020
9.1.0.39 949 7/10/2020
9.1.0.38 1,065 7/3/2020
9.1.0.36 2,658 6/10/2020
9.1.0.35 3,666 5/19/2020
9.1.0.32 3,963 4/23/2020
9.1.0.26 2,419 4/3/2020
9.1.0.24 10,634 1/17/2020
9.1.0.20 3,588 12/12/2019
9.1.0.3 10,841 9/11/2019
9.0.2.29 5,759 7/25/2019
9.0.2.27 890 7/23/2019
9.0.2.25 1,771 7/17/2019
9.0.2.16 9,175 5/22/2019
9.0.2.12 20,599 2/25/2019
9.0.2.11 4,403 2/7/2019
9.0.2.9 1,972 1/26/2019
9.0.2.7 8,039 10/24/2018
9.0.2.5 6,680 9/17/2018
9.0.2.4 5,145 7/6/2018
9.0.2.3 4,413 4/25/2018
9.0.0.7 12,254 11/15/2017
9.0.0.5 1,253 10/23/2017
9.0.0.4-Preview 2,494 8/29/2017
8.2.0.4 14,803 3/22/2017

These assemblies require application development using the Microsoft .NET Framework 4.6.2 or later.

         For information about downloading the tool, see https://docs.microsoft.com/dynamics365/customer-engagement/developer/download-tools-nuget

9.1.0.42:
Fix in Data import to compensate for Import files created during a window of time where new virtual fields generated by CDS were incorrectly identified as valid fields.
 This issue would cause schema validation to fail during import of complex data for some types of "attributeOf" type fields.
Up-taking fixes for Sovereign cloud discovery connectivity for login controls

9.1.0.39:
Fixed a bug in runtime settings parsing that would mis identify a = in the value as a key value separator.
Fixed an issue where data import could hang without error

9.1.0.36:
 Fix for an issue where importing business units that included a lookup for their own team (looped back to the entity) would not be populated on update.
 Fixed a general issue were related LookUp ID's that were discovered in the target system were not properly linked.
 Behavior Change: when using BatchMode, Create will always include the ID of the record from the source system, even if not explicitly included as a field in the exported system.

9.1.0.35:
Fix for an issue reported where related objects were not being correctly identified by name and thus not correctly linked to importing records
This only impacted imports where the related entity did not have comparison keys

9.1.0.32:
 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
 Enabled Batch mode for Data Import by default.

9.1.0.27:
   Updated visual for waiting icon.
   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.


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

9.1.0.23:
   Added Improvements to Async solution import logic
   Corrected an issue where logs were being placed in the wrong directory

9.1.0.3:
   ADAL 3.19+ is now required for this library.  ADAL 2.x clients will need to be updated to use ADAL 3.x+
   Added Support for Current User ID login when using Online flows with oAuth (Login control/connection string support )
   Added Support for ClientID Secret Auth when using oAuth flows. (connection string support )

9.0.2.30:
   Enhanced PD logs and temporary file delete logic.

9.0.2.29:
   Enhanced PD logs and raise fail event immediately when AfterPackageImport returns fail.
   Fixed Missing BindRedirect issue for Newtonsoft assemblies used in packages.

9.0.2.26:
   Enhanced PD to pass more error details to invoker of PD lib

9.0.2.25:
   Added support for France and New US Geo's
   Added new behavior to return the full login error when initial connect fails in LastException.

9.0.2.24:
   Published PackaDeployerException class which can be used by package developers
   Enhanced PD to bubble up error details to invoker of PD lib with progress status in case of failure - internal only

9.0.2.23:
   Internal updates - No Public changes
   
9.0.2.22:
   Internal updates - No Public changes
   
9.0.2.21:
   Logging updates for async import error scenario.

9.0.2.20:
   Logging Updates
   Added support for default async mode for DeleteAndPromote, regardless of how a given package is configured.
   Reverted change for RaiseFail event which done in version 9.0.2.19.  Now it will not cause PD to stop with an overall failure and stick to old behavior of continuing package installation.

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.

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

9.0.2.14:
 Corrected an error that occurs when a Async Upgrade Fails due to a recoverable server issue.  PD will attempt to recovery correctly vs aborting and requiring a restart.

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

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.
             
9.0.2.4:
 Updated install flows to more correctly trigger failures on failures within user code or data import.
 Added support several configuration settings dealing with timeouts and dials.
 Thease settings are set in the app.config of the host process
 StaleImportProgressOverride -
       This setting is the number of times a solution import be polled for progress.  This is rolling property, the count resets each time a solution moves forward.
         Default setting is 50
       Note: this property only applies when solutions import mode is sync.

     SolutionStatusPollingFrequencyOverride -
       This setting is the delay between check for solution progress.
         Default setting is :  5 (seconds)
       Note: this property only applies when solutions import mode is sync.

     SolutionImportBlockedRetryCountOverride -
       This setting is the number of retries that will be attempted when a solution import is blocked by a concurrent metadata operation.
         Default setting for this is 10

     SolutionImportBlockedWaitOverride -
       This setting is the number of seconds that a retry will wait before attempting another solution import.
         Default setting for this is 60 (seconds)

     UseAsyncForSolutionImport -
       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.
         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:
Updated to include CAB compression DLL's.
     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.
   9.0.0.5: 9.0
Initial Release
   9.0.0.2-preview:
     Updated for 9.x assemblies and Xrm.Tooling 3.x

   8.2.0.4
Initial release of PD client as Nuget. US English only Client.