windows-installer

问题 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

问题 The extension Visual Studio Installer Projects was dropped at some point - about 10 years ago. Protests from many developers caused Microsoft to change its mind and the extension was reintroduced and then left unchanged as far as I know. I have worked with it for a long time - actually to package applications built outside Visual Studio (i.e. Delphi and Java stuff). This worked well until recently. Now a dependency is somehow detected for .NET Framework 4.7.2, but my colleagues assured me

问题 I've got a C#/WPF application that is one step up from simple - it's got the main application, a couple of libraries, and then some NuGet packages. If I look in the project's bin/release/netcoreapp3.1 directory, there's a single EXE, a couple of JSONs, and a bunch of DLLs (some of which have PDBs). Nothing too crazy. The client wants an installer which doesn't sound like an unreasonable request. I first try the installer that comes with Visual Studio 2019 and am astounded at how useless it is

问题 I've got a C#/WPF application that is one step up from simple - it's got the main application, a couple of libraries, and then some NuGet packages. If I look in the project's bin/release/netcoreapp3.1 directory, there's a single EXE, a couple of JSONs, and a bunch of DLLs (some of which have PDBs). Nothing too crazy. The client wants an installer which doesn't sound like an unreasonable request. I first try the installer that comes with Visual Studio 2019 and am astounded at how useless it is

问题 I have written a C# WPF application. I have now created an MSI that will install the application. However, the file size is gigantic. The application contains many video and image files, which have combined to make the MSI a whopping 1GB in size. I have tried to reduce the file size with Orca. I have used "Save As" to create a brand new MSI and have also exported the database tables and then imported them to another MSI. In both cases, the file size is reduced to less than 1MB, but then the

问题 I'm a total noob on Wix (and installers in general) so please forgive me. My goal is to be able to traverse a directory, search for all, say, *.exe files and copy them to a predefined destination folder. Thing is, I don't know what these files are and their names so I can't type them out one by one in the wxs file... hence wildcards. Now, I ended up with something like this: ... <Directory Id='TARGETDIR' Name='SourceDir'> <Directory Id='ProgramFilesFolder' Name='PFiles'> <Directory Id='MyDir'

问题 I'm a total noob on Wix (and installers in general) so please forgive me. My goal is to be able to traverse a directory, search for all, say, *.exe files and copy them to a predefined destination folder. Thing is, I don't know what these files are and their names so I can't type them out one by one in the wxs file... hence wildcards. Now, I ended up with something like this: ... <Directory Id='TARGETDIR' Name='SourceDir'> <Directory Id='ProgramFilesFolder' Name='PFiles'> <Directory Id='MyDir'

问题 I want to add customized dialog box for uninstallation of my application. I have also tried the following: <InstallUISequence> <Show Dialog="RemoveDlg" OnExit="success">REMOVE="ALL"</Show> </InstallUISequence> Is it possible or not in wix? Can anyone help me out with this? 回答1: While you can certainly author dialogs that are specific to product removal, uninstallations started from the remove button in Add or Remove Programs (now Programs and Features) are run without the UI sequence, and

问题 We have developed an application that is distributed through Windows Installer, created with the use of WiX, where our customers can upgrade from any older version to the newest. Our latest version however, deletes 2 dll's, and this is only rectified through a reinstall. Details on the NuGet packages Microsoft.IdentityModel.Protocol.Extensions was upgraded from Nuget Version 1.0.2.206221351 and File version 1.0.20622.1351 to Nuget version 1.0.4.403061554 and File version 1.0.4.54. Similar

问题 In my MSI , I have added 2 custom actions to execute in deferred. I cant see these 2 custom actions in the verbose log to see whether these have executed or not. I can see for all other standard and custom actions executed in immediate mode, but not for deferred. Is this expected behavior ? Please help 回答1: WiX & VBScript : Here are some answers showing how you can use VBScript custom actions in MSI properly - combine that with the logging approach shown below and you should find all