Timeline for Bug in PowerShell classes when script is in a folder containing a single-quote?
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 23, 2022 at 17:41 | comment | added | Ramhound | Have you even confirmed it exists in the current version of PowerShell? PowerShell 5.1 hasn’t been updated in four years so it’s not unreasonable to conclude it would be fixed in that version, I said that, four years ago. | |
| Nov 23, 2022 at 17:33 | comment | added | munrobasher | Four years later and the same bug is present :-) I'm not sure it's a design choice. Seems like a plain bug to me | |
| May 17, 2018 at 11:13 | answer | added | harrymc | timeline score: 1 | |
| May 17, 2018 at 11:13 | review | Close votes | |||
| Jun 1, 2018 at 3:03 | |||||
| May 17, 2018 at 11:04 | comment | added | Ramhound | Then I encourage you to report the issue, but based on what read, the behavior you discovered is more or less intended based on design choices. Now I won't argue a way around that intended design choice should exist but it seems the problem surrounding a single quote existing in the directory is because of a long standing design decision within PowerShell itself (and it likely will not be fixed in PowerShell 5.1 so you will have to use PowerShell Core if it is fixed) | |
| May 17, 2018 at 11:01 | comment | added | munrobasher | Whilst this flaw is definitely in the same area, it's not the same bug as referred above. You can run the script using the File Explorer content menu (so that bug has been fixed) but this is a different error with the class statement | |
| May 17, 2018 at 10:56 | comment | added | Ramhound | Possible duplicate of "Open PowerShell window here" File Explorer context-menu command breaks with folder names with apostrophes (single quotes) | |
| May 17, 2018 at 10:55 | comment | added | Ramhound | Problem was already reported and fixed to the PowerShell Core team by the way. I went ahead and flagged this as a duplicate, since the issue was reported, and it referenced a question asked here. My assumption is that by the reported issue being fixed, while slightly different, the problem you discovered will also be fixed. | |
| May 17, 2018 at 10:51 | comment | added | munrobasher | Thx - in Office 365/Azure AD I had to rename the display name to "Liam OReilly" as this appears to be what controls the name of the user's profile directory | |
| May 17, 2018 at 10:51 | comment | added | Ramhound | Scratch that. PowerShell 5.1 appears to be the last (closed source) version. By reporting it to the PowerShell Core team it will be fixed eventually. You should verify the current beta version of PowerShell Core does not have this problem though (before you report it) | |
| May 17, 2018 at 10:44 | comment | added | Ramhound | Honestly the best would be to remove the single quote from the name on the domain side. You can still keep the single quote in the display name, so the only change, would be the directory that is created on a domain connected computer. Otherwise you have to manually modify the registry on each device connected to the domain they log into. As for reporting the bug, report it to the PowerShell Core team, should be fixed in PowerShell 5. | |
| May 17, 2018 at 10:23 | history | asked | munrobasher | CC BY-SA 4.0 |