Active Oldest Votes. See more details here. Improve this answer. Knuckle-Dragger Knuckle-Dragger 1, 1 1 gold badge 13 13 silver badges 19 19 bronze badges. For instance, if I have a copy of DISM in a folder and right click on it, "NoWorkingDirectory" would allow me to access the copy in System32 over the one in the directory I right clicked on. See, it's kinda useless because more often than not I want the copy in the folder I clicked on.
The "NoWorkingDirectory" verb property is undocumented so this is just a guess: Cmd. It is not really required for PowerShell. Anders Anders 5 5 silver badges 12 12 bronze badges. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name.
This is exactly what I want, so that is good. Furthermore, the current directory of the program is set to the directory of the file I clicked. This is not what I want; so is there any way to specify that another directory should be used as current directory instead of the container of the clicked file? I realize that I can add an argument to my program with the appropriate current directory and then have the program switch to that directory; I just wonder if there is a standard way of doing this that I'm not aware of.
According to your situation ,there is no way to know what the "current directory" is. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow.
Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? Submit and view feedback for This product This page.
View all page feedback. In this article. However, with later systems, an additional step might be necessary. Because these later versions of Windows are designed to be used in a managed environment, access to the registry could be administratively restricted, requiring a somewhat different approach to installation than described in the previous section.
Setup programs should generally not write directly to the registry. Instead, setup should be accomplished with Windows Installer packages. These tools ensure that software runs well and provides access to capabilities such as per-user class registration.
Shell extension handlers run in the Shell process. Because it is a system process, the administrator of a system can limit Shell extension handlers to those on an approved list by setting the EnforceShellExtensionSecurity value of the Explorer key to 1 as shown here:.
The Shell does not use the value that is assigned to the GUID, but it should be set to make inspecting the registry easier. Your setup application can add values to the Approved subkey only if the person installing the application has sufficient privileges.
If the attempt to add an extension handler fails, you should inform the user that administrative privileges are required to fully install the application. If the handler is essential to the application, you should fail the setup and notify the user to contact an administrator.
0コメント