windows-installer

问题 I have an installation file created by electron-builder and faced issue that can't find a way how to run powershell script after installation. The idea is to make some changes in windows registry and set permission for application folder. As far as I understand it should be configured in build section in package.json . In api I found that it is exist afterPack method, but I can't figure it out how to execute powershell file through it. Thank you. 回答1: First, create an afterPack.js file,

问题 I have an installation file created by electron-builder and faced issue that can't find a way how to run powershell script after installation. The idea is to make some changes in windows registry and set permission for application folder. As far as I understand it should be configured in build section in package.json . In api I found that it is exist afterPack method, but I can't figure it out how to execute powershell file through it. Thank you. 回答1: First, create an afterPack.js file,

问题 I have an installation file created by electron-builder and faced issue that can't find a way how to run powershell script after installation. The idea is to make some changes in windows registry and set permission for application folder. As far as I understand it should be configured in build section in package.json . In api I found that it is exist afterPack method, but I can't figure it out how to execute powershell file through it. Thank you. 回答1: First, create an afterPack.js file,

问题 I have an installation file created by electron-builder and faced issue that can't find a way how to run powershell script after installation. The idea is to make some changes in windows registry and set permission for application folder. As far as I understand it should be configured in build section in package.json . In api I found that it is exist afterPack method, but I can't figure it out how to execute powershell file through it. Thank you. 回答1: First, create an afterPack.js file,

问题 I have an installation file created by electron-builder and faced issue that can't find a way how to run powershell script after installation. The idea is to make some changes in windows registry and set permission for application folder. As far as I understand it should be configured in build section in package.json . In api I found that it is exist afterPack method, but I can't figure it out how to execute powershell file through it. Thank you. 回答1: First, create an afterPack.js file,

问题 I have an installation file created by electron-builder and faced issue that can't find a way how to run powershell script after installation. The idea is to make some changes in windows registry and set permission for application folder. As far as I understand it should be configured in build section in package.json . In api I found that it is exist afterPack method, but I can't figure it out how to execute powershell file through it. Thank you. 回答1: First, create an afterPack.js file,

问题 I have a problem where after my InstallShield project is built and I test the install on a clean 64bit Windows 7 machine, it creates a Wow6432Node key within a Wow6432Node key when I check regedit at HKEY_LOCAL_MACHINE\SOFTWARE. Everything registers correctly and the program seems to run fine. I have made sure that my project is the one that is causing this. I don't want to leave it as it is since it would be silly to have the registry like that. Does anyone know what might have caused this

问题 I'm writing a WIX script. I have a custom-action that adds rows dynamically to the Registry table: function AddRegistry() { var registryView = Session.Database.OpenView("SELECT * FROM Registry"); registryView.Execute(); var record = Session.Installer.CreateRecord(6); record.StringData(1) = "Unique123456"; record.IntegerData(2) = 2; record.StringData(3) = "Software"; record.StringData(4) = "my_registry_string"; record.StringData(5) = "value"; record.StringData(6) = "MyComponent"; registryView

问题 I have an MSI installer project that installs a windows service. My version numbering method is best described by this post: What are differences between AssemblyVersion, AssemblyFileVersion and AssemblyInformationalVersion? I am not changing the Version of my install project as that is not changing, and I've had too many issues when doing that. I have already installed my service with the following assembly versions [assembly: AssemblyVersion("4.3")] [assembly: AssemblyFileVersion("4.3.0.0")

问题 Due to user confusion, our app requires separate installers for 32-bit and 64-bit versions of Windows. While the 32-bit installer runs fine on win64, it has the potential to create support headaches and we would like to prevent this from happening. I want to prevent the 32-bit MSI installer from running on 64-bit Windows machines. To that end I have the following condition: <Condition Message="You are attempting to run the 32-bit installer on a 64-bit version of Windows."> <![CDATA[Msix64 AND