Please offer a working solution to NOT associate PowerShell Source files (e.g. ps1)
Posted: Mon May 20, 2019 3:43 pm
Good evening
We're evaluating Sapien PowerShell Studio and it's very annyoing that it is associating common PowerShell Script file types to the Sapien PowerShell Studio.
The reason is obvious: we develop PowerShell Script to use them. If we doubleclick a Script, then it must be executed in the vast majority of cases and not edited.
It's a shame that Sapien does not offer to disable the kidnapping of the common script file type allocation - we guess that we talk about a professional IDE and it's not that hard to add this customization to the setup procedure (and to not overwrite it on later updates )
Other Users have reported the same problem, for example: viewtopic.php?f=12&t=13859&sid=6ec3a39b ... 8b51af1983
Your supporter proposed a "solution" which is just a very unprofessional, annoying workaround: it's usually a bad idea to create an unwanted system state and fix it afterward if it can be prevented right from the start.
Additionally, the workaround does not work at all on our computers, as the original poster already has explained. Even if your supporter wrote that he had tested it, it's obvious that the workaround does not always work and must be fixed after each Sapien Update
Yes, it is really annoying for a commercial product that your customers have to discuss such trivial and easy to implement 'features'. If it's too hard for Sapien to modify the Setup, then you can find a working and final workaround on the other thread: you're setup must just add 3 lines of code and it would be nice if you could add a Reg-File so that the 'disable file association' registry key can be set by a double click.
Do you have any plans to fix it?
Thanks a lot!, all the best,
Klaudia
We're evaluating Sapien PowerShell Studio and it's very annyoing that it is associating common PowerShell Script file types to the Sapien PowerShell Studio.
The reason is obvious: we develop PowerShell Script to use them. If we doubleclick a Script, then it must be executed in the vast majority of cases and not edited.
It's a shame that Sapien does not offer to disable the kidnapping of the common script file type allocation - we guess that we talk about a professional IDE and it's not that hard to add this customization to the setup procedure (and to not overwrite it on later updates )
Other Users have reported the same problem, for example: viewtopic.php?f=12&t=13859&sid=6ec3a39b ... 8b51af1983
Your supporter proposed a "solution" which is just a very unprofessional, annoying workaround: it's usually a bad idea to create an unwanted system state and fix it afterward if it can be prevented right from the start.
Additionally, the workaround does not work at all on our computers, as the original poster already has explained. Even if your supporter wrote that he had tested it, it's obvious that the workaround does not always work and must be fixed after each Sapien Update
Yes, it is really annoying for a commercial product that your customers have to discuss such trivial and easy to implement 'features'. If it's too hard for Sapien to modify the Setup, then you can find a working and final workaround on the other thread: you're setup must just add 3 lines of code and it would be nice if you could add a Reg-File so that the 'disable file association' registry key can be set by a double click.
Do you have any plans to fix it?
Thanks a lot!, all the best,
Klaudia