windows-installer

问题 I am facing a problem for several days and after many research I couldn't find anything that fit with my case. Here's the thing : I'm working with Visual Studio 2010 on a solution that contains several projects and a Setup Project. I want the setup project to create a MSI file to update the product from version 1.5 to version 1.6. I followed this tutorial http://www.simple-talk.com/dotnet/visual-studio/updates-to-setup-projects/ and updated also the assembly version and file version numbers

问题 I am facing a problem for several days and after many research I couldn't find anything that fit with my case. Here's the thing : I'm working with Visual Studio 2010 on a solution that contains several projects and a Setup Project. I want the setup project to create a MSI file to update the product from version 1.5 to version 1.6. I followed this tutorial http://www.simple-talk.com/dotnet/visual-studio/updates-to-setup-projects/ and updated also the assembly version and file version numbers

问题 I am creating a ASP.net core 2.0 WEB API project that is required to be deploy as a Windows service on a system using a MSI setup. Is there any way I can do it ? Things that I have already tried: I created an MSI using Setup Project but it doesn't load any dependencies. I tried to create an msi using WIX but it shows error The WiX Toolset v3.11 (or newer) build tools must be installed to build this project I have tried solution which are already answered on this and this. 回答1: Short on time,

问题 I am installing applications programatically in an unattended fashion ( nothing special, just passing the paramters "/VERYSILENT /SUPPRESSMSGBOXES /NORESTART" if exe, or "msiexec /qn /i ALLUSERS=1" while is an msi file ). The problem is after installation suceded I want to open the application I've just installed. Then I am looking for a way to discover the main executable file of an application I've just installed. I've tried monitoring harddisk and also checking on registry but I hasn't

问题 I have InstallShield 2013 Basic MSI project I want to have a CA that will run after the files are being installed but before creating the shortcuts, how can I do that ? I tried to create CA that will run after InstallFile but when running the setup I see that when it get to InstallInitialize it skip all CA excepts the one I added and it run it and after that go back to InstallInitialize and run all custom action it has skipped. 回答1: What you're seeing here in the log is the effect of Deferred

问题 I cannot install my project because the setup.exe gives an ERROR 1001. Unable to get installer types in the C:\Program Files\MyProgram\SI.ArchiveService.ArchiveService.exe assembly Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information. So I viewed the fusion logs and there were 3 errors (I have posted the most relevant at the bottom). The one below is translated back to english, so the wording might be slightly off. But from what I can

问题 MyApp version 1.0 contained the file foo.dll. The version of this file was version 10.5.567. Now MyApp is version 2.0 and the version of foo.dll is 2.0.123. The version is LOWER than the old version. The vendor who wrote this dll decided to go backwards with the file version number. This is not a decision I can change. How do I get WiX to always install this file? The RemoveExistingProducts action is scheduled after the InstallFinalize action and also cannot be changed. InstallShield had an

问题 How do I create custom actions and link it to my WiX setup project? I have: WiX 3.11 Visual Studio 回答1: You need to create a new C# Custom Action Project for WiX v3 in your solution. That should look like this: using System; using System.Collections.Generic; using System.Text; using Microsoft.Deployment.WindowsInstaller; namespace CustomAction { public class CustomActions { [CustomAction] public static ActionResult CustomAction(Session session) { session.Log("Begin CustomAction"); return

问题 I'm building an installer at the moment that targets just 64bit machines. Part of the process involves running Heat.exe to produce a Fragment elements containing part of the deployed application. The problem is the components that are produced by heat produce ICE:80 errors which is WiX complaining that the components target 32bit systems and my installer is trying to load these into: <Directory Id="ProgramFiles64Folder"> Looking at the documentation there is a -platform switch that can be

问题 I had converted msi file into msix using MSIX packaging tool. Now, how should i pass all the inputs which i used to provide/validate in msi installer screens? I had already checked the msix file for any config file to provide inputs but no such file was there. 回答1: Differences between MSIX and MSI packages , deployment wise. 1) Applying additional custom settings, like new registry or files, or modifying defaults from the original package can be done with MSIX modification packages . This is