Re: [WiX-users] include 32 bit and 64 bit merge modules

2010-07-23 Thread daniel.knoepfel
Hi I tried to build wix project for 32 and 64 bit resulting in two separate msi. I tried to use the var.Platform variable but I have not yet managed to set it. How can I do that so depending on the variable different merge modules are included. (The dropdown in the visual studio project only

Re: [WiX-users] include 32 bit and 64 bit merge modules

2010-07-23 Thread daniel.knoepfel
Hi Thanks for the information. I already feared this could be the reason. So what I am trying to do is the following: This way, i can hopefully reuse the same wix project. Having the wix project included in the visual studio solution, I can s

[WiX-users] include 32 bit and 64 bit merge modules

2010-07-23 Thread daniel.knoepfel
Hi Our setup includes various merge modules. Initially, they were all these merge modules were fore 32-bit systems. Testing the installed application on 64-bit windows 7 i found out that we would need the 64-bit merge modules. So I added them to the wxs file: Unfort

Re: [WiX-users] Visual Studio Bootstrapper-> define order of prerequisites to be installed

2010-07-23 Thread daniel.knoepfel
Hi I think I just had to change the order of the prerequisites xml. It seems illogical to me though and I havent found it documented anywhere. I would be glad for any verification. Crystal Reports .NET Framework 3.5 SP1 Windows Installer 3.1 __

[WiX-users] Visual Studio Bootstrapper-> define order of prerequisites to be installed

2010-07-23 Thread daniel.knoepfel
Hi Our wix installer makes use of the visual studio 2008 bootstrapper functionality to install Windows Installer 3.1, .NET 3.5 SP1 and Crystal reports. This used to work but suddenly there is an error when i start the setup on a clean machine. After aggreeing to the licence files of crystel re

[WiX-users] Custam Action Install conditions (why is CA executed upon uninstall when condition is set to NOT INSTALLED )

2010-07-20 Thread daniel.knoepfel
Hi I have some problems when it comes to install conditions. There are some custom actions that should only run upon the first installation and not upon uninstall, upgrade, repair, modify..etc. The conditions i tried to use was the following: NOT INSTALLED However, upon uninstall the actio

Re: [WiX-users] Messagebox from custom action with a lot of text

2010-07-19 Thread daniel.knoepfel
Hi Showing a standard message box works more or less, but the focus is not set properly. Well, i have found a workaround, i show a custom modal windows forms dialog, that resembles a messagebox. Just after showing i set the focus. This way, i can ensure the full text is displayed and i have f

Re: [WiX-users] Messagebox from custom action with a lot of text

2010-07-19 Thread daniel.knoepfel
Hi Christopher I currently have the action scheduled after "CreateFolders". I use the CA almost like a startup-condition. There may also be other places where i intend to show a messagebox, but this is not defined yet. I hoped it would be something rather simple, either a flag or set the fo

[WiX-users] Messagebox from custom action with a lot of text

2010-07-19 Thread daniel.knoepfel
Hi In our wix installer a C# custom action, needs to pop up a window to show a message that might be quite long. I currently do it the following way: public void ShowWarningMessageBox(string pMessage) { Record record = new Record(); record.FormatString = pMessage; Session.Message(InstallM

[WiX-users] Having different, localized msi files, and make VS bootstrapper determine the which one to call depending on OS-Language

2010-07-16 Thread daniel.knoepfel
Hi Our wix installer needs to be shipped in several languages. Using Wix localization, the output is one msi file for each language. To install various prerequisites (.NET framework, crystal reports, ... ) we use a bootstrapper that should then call the appropriate msi file depending on the

Re: [WiX-users] Best practice to include customer/user specific files (also when using a bootstrapper)

2010-07-16 Thread daniel.knoepfel
Hi I think your proposal would do. I also played around with the VS Bootstrapper and i find it does its job quite well. Having msi file not embedded in the bootstrapper is something I can live with. I probably stick to it if I find a way to call the different localized msi files, depending o

[WiX-users] Best practice to include customer/user specific files (also when using a bootstrapper)

2010-07-15 Thread daniel.knoepfel
Hi Some parts of our application are very customer/user specific. For example, there will be a varying number of files in the appData-folder depending on the installation. The approach i have used so far is having a custom action copying these files. . An example installation package could look

Re: [WiX-users] Accessing Source directory in Deferred Custom Action (ApDataFolder etc. is working, just not SourceDir)

2010-07-14 Thread daniel.knoepfel
Hi and halleluja I finally managed to access the SourceDir Property in the CustomAction data. The reason i could not access the SourceDir property earlier was simply that I scheduled the customAction to assign the properties to the CustomActiondata to early (It seems UI-sequence and execute seq

Re: [WiX-users] Accessing Source directory in Deferred Custom Action (ApDataFolder etc. is working, just not SourceDir)

2010-07-14 Thread daniel.knoepfel
Hi I still havent figured out how to solve my issue, but i have found a couple of other aspects. As it seems, the built in property: [SourceDir] is, depending at the time of exeuction, sometimes empty. In the execute sequence, if i use a immediate custom action, scheduled after InstallInitiali

Re: [WiX-users] Accessing Source directory in Deferred Custom Action (ApDataFolder etc. is working, just not SourceDir)

2010-07-14 Thread daniel.knoepfel
Hi Since I haven't managed to assign the [SourceDir] value to a customAction Data Property, i tried to assign the data assign the value to a property and then assign that property to the a customAction. However, no success, the assigned property is empty. I am sure it is a simple syntax thing b

Re: [WiX-users] Calling an exe file upon installation (works but either cmd remains open, or installation does not finish)

2010-07-13 Thread daniel.knoepfel
Hi Thanks for your answer. Having a launcher exe seems to be the save way to go. In the meantime, i noticed that on some machine it works as supposed, using the following custom action definiton: However, i think we still have to use the launcher as we have to ensure it has to work on a

Re: [WiX-users] Accessing Source directory in Deferred Custom Action (ApDataFolder etc. is working, just not SourceDir)

2010-07-13 Thread daniel.knoepfel
Hi Thanks for your answer. From how i interpret the log file the action returns success (even if there is an exception), which is no surprise as I return this result via C#. Here are the relevant parts from the log: TestCA.SetProperty 3 MSI (s) (54:54) [

[WiX-users] Accessing Source directory in Deferred Custom Action (ApDataFolder etc. is working, just not SourceDir)

2010-07-13 Thread daniel.knoepfel
Hi I would like to access the "SourceDir" property in a deferred custom action. While i can access other directories via the CustomAction property (see example below). The SourceDir ActionData remains empty. I must be doing something wrong. I sure it's something silly, that only a wix newby ca

[WiX-users] Calling an exe file upon installation (works but either cmd remains open, or installation does not finish)

2010-07-13 Thread daniel.knoepfel
Hi As a wix newby i am having trouble launching a exe file. The process created by the exe file should then run in the background just like a windows service. (We cannot use a windows service however, for reasons I cannot influence) I tried several approaches but none with the desired result. I

[WiX-users] Localization issue: One msi file for several languages

2010-07-06 Thread daniel.knoepfel
Hi I am a Wix newbie and I have a question concerning localization. I need my installer to support english and german. When i now compile my wix project, two msi files are generated, one for each language. In our case, what we would like to have is one single msi file where the different langu