Release: 0.7.10 #818
Merged
Release: 0.7.10 #818
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This pull request was automatically created by the d365fo.tools-Generate-Text action'
…eline Fix import rsat certificate pipeline
…mdlets implemented
Impl flight
Impl dataverse tester
This pull request was automatically created by the d365fo.tools-Generate-Text action'
This pull request was automatically created by the d365fo.tools-Generate-Text action'
Update build tools
Improve entra integration
Add documentation for default values in d365fo.tools module
The installation documentation for SqlPackage says: Installing SqlPackage as a global tool makes it available on your path as sqlpackage and is the recommended method to install SqlPackage for Windows, macOS, and Linux. In line with Microsoft's expectations, also search %PATH% if sqlpackage is not found in the d365fo.tools default path ($Script:SqlPackagePath). If it is found in the %PATH% then update the default path with the actual path to sqlpackage.exe. Author: Colin Daley Date: 2024-03-24
Also search %PATH% for sqlpackage.exe
If a module that is read by the disk metadata provider references a binary-only module, the "ListModulesInDependencyOrder()" method causes an exception error that is intercepted by the Get-D365Module function in line 172. As a result, the order of the modules cannot be determined taking the dependencies into account and "ListModules" is used instead. The problem can be easily avoided by adding the model manifest of the runtime metadata provider to the "CreateDiskProvider" method in line 165. This ensures that the disk provider has all the information it needs to determine the sequence for all modules based on the dependencies.
…time-error Disk provider binary-only module reference fix
This will enable cmdlets that call Invoke-Process to act on the standard and error output of the invoked process.
This updates the default version of SqlPackage that d365fo.tools installs to 162.2.111.2 (the first .NET 8 version). In addition, it replaces the -SkipExtractFromPage parameter and the corresponding web scraping logic with the -Latest parameter and the evergreen link https://aka.ms/sqlpackage-windows Note that unlike the behavior from when the web scraping logic was still working, the latest version of SqlPackage is NOT installed by default. Instead, the fixed version 162.2.111.2 is installed (which may be updated to later versions in the future). Reasons for this change in behavior are discussed in #747. fixes #747
This pull request was automatically created by the d365fo.tools-Generate-Text action'
…365fo.tools into 747-update-sqlpackage
Update Invoke-D365InstallSqlPackage to install latest version of SQLPackage
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.