-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Unable to find type [System.Windows.Media.Stretch] #27
Comments
It is very possible that the necessary .NET classes are not part of .NET core in PowerShell 7. I'm assuming if you run the command in Windows PowerShell it works just fine. I may have to refactor the module not to export |
Because this is a .NET limitation, obviously I can't fix it. I've updated the module and v2.4.0 no longer exports this command in PowerShell 7. That's the best I can do. |
It is actually the same in Windows Powershell. I included the error from both. |
I missed that. That shouldn't be the case. I have never had an issue in Windows PowerShell (testing on multiple systems), but I got the same problem on PowerShell 7. Given that .NET Core is a subset of the .NET Framework in Windows PowerShell, this doesn't surprise me. I can't think why this would fail in Windows PowerShell. Are you running something like a Home or Student edition? Not that it should make a difference. I can't imagine the Danish culture is causing a problem. Update the module to 2.4.0 and try again in Windows PowerShell. I changed a parameter to use a string instead of the .NET class. Let's see if you get the same error. The command definitely won't run in PowerShell 7. |
I can confirm that it works in Windows PowerShell now. Thanks :-) |
Problem Report
Show-GuiCalendar does not work (on my machine)
What is the syntax or expression you are using?
Show-GuiCalendar 12/2018 2/2019 -highlight 12/24/18,12/25/18,12/31/18,1/1/19,1/18/19,2/14/19,2/22/19
What Happens?
What do you think should happen?
A GUI calendar should open
Environment Information
The text was updated successfully, but these errors were encountered: