SQL Watch commands cannot be used in PowerShell 7 #7414
Merged
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
Cannot be used in PowerShell 7+
|
Odd failure of |
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.
Tempoary fix until we address import process.
Type of Change
Purpose
The DLL used is not supported in dotnet Core, only .NET 4.6 making this command only compatible with Windows PowerShell.
SQL Watch commands in addition to any command trying to use the
Microsoft.SqlServer.Dac.dllare now going to throw a message that PowerShell Core is not supported if they are on Windows.The commands are only imported at this time if they are Windows but we do not address the Edition of PowerShell in our import process. Our import process needs to have an additional check on PowerShell Edition so we can properly exclude these commands on import and lessen the confusion.