-
-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set-PSFLoggingProvider - PowerShell 7 - A parameter cannot be found that matches parameter name 'FilePath'. #628
Comments
output of get-error is below for this session nothing in I
|
Get-Error will be default only show the last error. Get-Error -Newest 3 |
I did just try it on another machine and it worked as expected 🤔 nothing different in |
We did add support for AuditMode in WDAC - a pseudo-CLM where things still work, but get logged what would not have worked. Fascinating, the entire dynamic parameter system appears broken on your console :( [PSFramework.Logging.ProviderHost]::Providers This should return an empty dictionary then |
Looks like my module has trouble with this new audit mode |
Appreciate the help troubleshooting this morning - let me know if you need a tester! |
A little background: |
Heya @jpomfret - turns out I was a bit optimistic about my own ability to test it (and timeline to fix this). |
So... I have got a new laptop since I opened this issue and now on the new one with PowerShell |
Getting errors when using logging code in PowerShell vs Windows PowerShell - I'm unable to add a
FilePath
for the provider and therefore my scripts aren't logging to files.This can be replicated by running the following example from the docs
https://psframework.org/documentation/quickstart/psframework/logging.html
PowerShell v7.4.1
PowerShell v5.1.22621.2506
The text was updated successfully, but these errors were encountered: