Microsoft.CrmSdk.XrmTooling.PackageDeployment.Core 9.1.0.33

• .NETFramework 4.6.2

  • Microsoft.CrmSdk.XrmTooling.CoreAssembly (>= 9.0.2.8)

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.
    
9.1.0.33:
       Altering the default client engine to move coreobjects to a non static type,
       Staging for merger of MTPD code with mainline PD.
       Added in memory configuration parsing logic
       Optimized dependency checking logic

     9.1.0.27:
           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.21:
          Many Logging improvements
           Fixed an issue with Async Solution Import.
           Includes fixes from DMT: Fixed bug with preprocessing that would cause an apparent runaway, removed check for display name on attributes, updated batch mode system.

     9.1.0.20:
         Introduced binding redirect for Microsoft.IdentityModel.Clients.ActiveDirectory dll.
         Package developers can define error type as application error or publisher error - internal only.

     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.
 
     9.0.2.26:
         Enhanced PD to pass more error details to invoker of PD lib
 
     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:
   Note .net 4.6.2 is now required as a baseline
           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.
               The 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.
       The default setting for this is 10

           SolutionImportBlockedWaitOverride -
               This setting is the number of seconds that a retry will wait before attempting another solution import.
       The 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.
               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
           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.9: Added missing Xrm.Tooling.Connector DLLs due to some packages requiring them.
         9.0.0.8: Added missing CAB DLLs
         9.0.0.7: 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:
         Using Xrm.Tooling 3.x and CRM 9.x assemblies

         Intial release of the 2.2.2 core PD module.