windows-installer

问题 Project Info: We are creating an installer project that allows users to choose a servername and databasename. After installation of the main program a corresponding database will be created. Installer project : Has an additional UI screen with two textboxes, containing servername and databasename. An custom action will be executed on installation and has the servername and databasename defined as custom action data. Main application: An installer class wires the after-installation event. This

问题 I am using the windows installer to install/upgrade an installation. Using Visual Studio I can manually change the version number and then select yes when asked to change the ProductCode. This creates an installer that is capable of overwriting the existing installation provided that the following properties are set on the installer project RemovePreviousVersions True DetectNewerInstalledVersion True Now in my build server I can change the version number to the appropriate new version in the

问题 I'm creating a Windows application that needs to add an entry to the Send-To explorer context menu, and needs to do so for all users. Since the Send-To folder is specific for each user, with no common folder for all users, I'm left with two choices: I can go over all user profiles, as well as the default user profile, find the SendTo folder and add the shortcut to it. This will ensure the shortcut is deleted during uninstall. Or, I can make sure the shortcut is in the SendTo folder each time

问题 I have built an executable shell that using MEF loads assemblies (MEF Parts) and displays / acts accordingly to the loaded functionality. I now want to deploy this application as a ClickOnce install. Does anyone have a strategy for this, at the moment I have seen 2 strategies. Build and installer for the parts and add it as a Redistributal Component to the shell application - this means that the 2 installations are basically welded together and it means that MEF is basically pointless Build a

问题 I have a program on a kiosk with an associated service that updates the program by periodically checking on the web for a newer version of the MSI. If it finds one, it will install it, the program may still be running. To get around the DLL conflicts of the above solution, I rename the assemblies in the MSI with by version so a new version can install while the old is running. The application will poll the install directory for newer version assemblies and if it finds one restart as soon as

问题 I'm trying to show a custom status message in default wix's ProgressDlg, following this answer: WiX: dynamically changing the status text during CustomAction So far, I got this code in my custom action: public class CustomActions { [CustomAction] public static ActionResult CustomAction1(Session session) { Debugger.Launch(); session.Log("Begin CustomAction1"); MessageTest(session); return ActionResult.Success; } private static void MessageTest(Session session) { for (int i = 0; i < 10; i++) {

问题 I would like to protect the MSI file against modification. It could be easily done with ORCA or with MSI API. It is sad because anyone can modify/add/remove windows installer custom actions or properties who have admin rights. Is there any way to set an MSI file to some read-only mode or somehow protect its content? 回答1: The short answer is no, you cannot prevent someone from editing a .msi file. There are various approaches you can take to minimize the likelihood of someone doing so, or

问题 I have a WiX based MSI that installs a service and some shortcuts (and lots of other files that don't). The shortcut is created as described in the WiX docs with a registry key under HKCU as the key file. This is an all users install, but to get past ICE38, this registry key has to be under the current user. When the service starts (it runs under the SYSTEM account) it notices that that registry key isn't valid (at least of that user) and runs the install again to "repair". In the Event Log I

问题 I have a WiX based MSI that installs a service and some shortcuts (and lots of other files that don't). The shortcut is created as described in the WiX docs with a registry key under HKCU as the key file. This is an all users install, but to get past ICE38, this registry key has to be under the current user. When the service starts (it runs under the SYSTEM account) it notices that that registry key isn't valid (at least of that user) and runs the install again to "repair". In the Event Log I

问题 I have easily installed Node.js before on Macs and other PCs, but the PC I have now at work restricts the running of .msi files. Is there a way to manually install and configure node.js and npm on Windows 7? I have access to Powershell. 回答1: Installing nodejs (and npm) on a Windows 7 machine does not require any "magic" if you have Admin access on the target machine and do not care about setting up the expected "uninstall", various Windows performance counters, event tracing or Start menu