Issue 506 Problem with API Module #528
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
When attempting to invoke the basic `Connect-Safeguard` command, one could get the following error, depending on your environment (Windows and PowerShell version):
> Metadata file 'System.Security.Cryptography.dll' could not be found.
safeguard-ps.psm1:82
I believe, when running under Windows with PowerShell 5.1, it's using just the regular .NET Framework, so no explicit reference to `System.Security.Cryptography.dll` is needed. Unlike with PowerShell Core.
After fixing that problem, we immediately ran into another error that may again be a difference between PowerShell and PowerShell Core.
> Unexpected character '$'
string accessTokenUri = $"https://{_appli...
It seems the C# string interpolation is not supported, at least in this version of PowerShell. So we'll just use the old `string.Format()` method.
|
See #506. |
MichaelThompson
approved these changes
Sep 9, 2024
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.
When attempting to invoke the basic
Connect-Safeguardcommand, one could get the following error, depending on your environment (Windows and PowerShell version):I believe, when running under Windows with PowerShell 5.1, it's using just the regular .NET Framework, so no explicit reference to
System.Security.Cryptography.dllis needed. Unlike with PowerShell Core.After fixing that problem, we immediately ran into another error that may again be a difference between PowerShell and PowerShell Core.
It seems the C# string interpolation is not supported, at least in this version of PowerShell. So we'll just use the old
string.Format()method.