Re: [WiX-users] ICE08 changed to linker error in 3.6

Thanks for the quick response, Bob. Everything seems to be working correctly. I was missing a condition on a few of these components. We're in the middle of implementing this feature for dual ESRI 9 and 10 support so currently the mutually exclussive conditions I'm temporarily using are just

[WiX-users] ICE08 changed to linker error in 3.6

I'm performing testing for what will be involved in migrating our deployment projects from WiX 3.5 to 3.6. I am currently testing with build 3.6.2928.0. Things have gone well mostly but on one of our products I'm receiving errors from light. Here is one example of the error. error LGHT0369: Com

Re: [WiX-users] Registry Search in x86 installers doesn't work properly on x64 machines

If you ever need to read a section of the registry that differs from the bitness of the process you are executing in you can use this Windows API, RegQueryValueEx (http://msdn.microsoft.com/en-us/library/ms724897(v=vs.85).aspx). You can change the section of the registry being read with the samDes

[WiX-users] Referencing .wxi from .wixlib

Is it possible to reference a .wxi file that is included in a .wixlib from a .wixproj consuming that .wixlib? My specific goal that I'm trying to achieve is a WiX library that contains a generic SQL connection dialog that can be reused. The general scheme is using a .wxi file that defines the

Re: [WiX-users] Why is WiX UI executed after CostFinalize?

http://msdn.microsoft.com/en-us/library/aa368048(v=vs.85).aspx CostFinalize must be run before UI is displayed to allow Features to be selected or Directories to be changed, which most installer UIs allow users to do. If you are changing properties that affect component/feature conditioning in y

Re: [WiX-users] ServiceInstall failure?

Are you explicitly doing any impersonation of the logon user in custom actions yourself? If you are obtaining logon credentials from the user (via dialog or command line) I would implement a custom action to validate those credentials before you make any system changes and prevent the install fro

Re: [WiX-users] OpeFileDialog C# Custom Action

You need to run it under a separate thread with a different aparatment state, see details here. http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/OpenFileDialog-fails-in-Win7-td5538592.html#a5542494 -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.

Re: [WiX-users] Is it possible to show features in the FeatureDlgconditionally?

A couple of additional notes as I've attempted to do this in the past. 1. Setting a feature's level to 0 will disable it so it will not displaly on the feature selection control. This disables the feature permanently - you will never be able to install that feature without uninstalling/reinstall

Re: [WiX-users] Best Practices - Using "*" for GUID automation

Andy, If you have a RemoveExistingProducts action scheduled in one location in your common element and another scheduled elsewhere in your Product consuming the common WiX I'm pretty sure you would get a compilation error. You could set something up in your common WiX fragments/include to condit

Re: [WiX-users] Best Practices - Using "*" for GUID automation

Hi Andy, Either setting After="InstallValidate" or Before="InstallInitialize" will work, you don't need to specify both. I was just giving you the restrictions on sequencing for the upgrade to work. With this setup a rollback to v1.0.0 would not occur if your v1.0.1 MSI fails after RemoveExisti

Re: [WiX-users] Best Practices - Using "*" for GUID automation

This is the expected behavior for that configuration. The problem is that since your component GUIDs don't line up from v1.0.0 to v1.0.1 the upgrade installs the new components and then after InstallFinalize removes the old components because it is not able to properly reference count them using

Re: [WiX-users] OpenFileDialog fails in Win7

I ran into this same problem when trying to use OpenFileDialog(). You need to make a new thread with a different appartment type for the UI to show. Here is a sample of what I did to make it work. // create a new thread with appropriate apartment state to launch UI FileBrowser fileBrowser =

Re: [WiX-users] Wcalog does not log

How is your custom action being called? As Rob said if it's off a push button, or launched through any MSI UI via a DoAction control event logging will not occur. This is a limitation of Windows Installer, it's documented somewhere in the SDK, I forget where. If your custom action is scheduled

Re: [WiX-users] Component Level Versioning?

You can use "companion files" to force your non-versioned files to update properly. http://msdn.microsoft.com/en-us/library/aa367997(VS.85).aspx You'll have to manage the companion relationship between the non-versioned files you want to update and the versioned file you are referencing. This

Re: [WiX-users] Introducing Custom Bitmaps using Visual studio

I'm not familiar with the documentation you listed but I've replaced with the default WiX bitmaps by setting these WiX variables under the Product element when using the WixUI_Common. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Introducing-Cu

Re: [WiX-users] No OpenFileDialog or something like that?

There is no file browsing UI/capability built into Windows Installer. You will need a custom action to display a file browse dialog. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/No-OpenFileDialog-or-something-like-that-tp5216565p5217401.html Sen

Re: [WiX-users] Custom Action execution by feature

You can condition your custom actions based on the action-state of your feature, like so. &SWUSchedTaskFeature=3 &SWUSchedTaskFeature=2 More info... http://msdn.microsoft.com/en-us/library/aa368012(VS.85).aspx -- View this message in context: http://windows-installer-xml-w

Re: [WiX-users] Evaluate property

That seems like it should work. I'm assuming the rest of the values are coming through to your deferred custom action correctly? Have you checked a Windows Installer log to see that the correct value of TOMCATHOME is getting set to the Deploy property when SetDeployParams runs? -- View this mes

Re: [WiX-users] Evaluate property

Can you post the code for your immediate-mode custom action that saves this value for CustomActionData? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Evaluate-property-tp5165399p5167894.html Sent from the wix-users mailing list archive at Nabble.c

Re: [WiX-users] Evaluate property

If you only have access to CustomActionData then I'm assuming your custom action is scheduled for deferred mode. You don't get general property access during a deferred custom action. You need to write an accompanying immediate-mode custom action that stores all the data required into a propert

Re: [WiX-users] NEXT button behavior

I do something very similar in some of our installs. What I do is on the Next button I run my CA that validates the data, in this case a database connection string. If it's valid it moves on to the next dialog. If the connection cannot be validated a SpawnDialog event is triggered to display th

Re: [WiX-users] Condition Table generation

The Condition table is designed for enabling/disabling which features get installed at install-time. It sounds like your intent is to control which features get included into your various MSIs at build-time. For your situation the use of shared install code would enable you to have a similar set

Re: [WiX-users] Condition Table generation

I'm not sure I follow exactly what you'd like to accomplish. WiX has a lot of tools for sharing installation code between projects and conditionally including setup logic with preprocessor variables, etc. I'm confident you'll be able to accomplish what you want with WiX. The Condition table is

Re: [WiX-users] How to NOT Delete Application Directory on Uninstall?

I don't know of any explicit setting to change this default behavior in Windows Installer. The best way to handle it would probably be to have the install manage configuring the permissions on the directory. There is some native permissions options in Windows Installer but they are not very robu

Re: [WiX-users] How to overwrite forcibily a file.

You can make this file a companion file to a file that you know will overwrite/update properly due to the file versioning rules. There is a companion file attribute on the File node within WiX, which forces the file to follow the versioning rules of the specified companion file. Akihiro.Shibuta

Re: [WiX-users] Show Dialog from Custom Action

Using System.Windows.Forms can be done but then your custom action won't be following the UILevel specified by the install session. You could tell that MSI to run silently and your custom action will still be popping up message boxes which is not good. Using MsiProcessMessage is the proper way t

Re: [WiX-users] manual cleanup if msi uninstaller corrupted

You may want to consider just conditioning the LaunchConditions action itself, so that you don't need to update each individual launch condition you have. You would want to add this to both the InstallUI and InstallExecute sequences. The basic idea is that once your MSI is installed you do

Re: [WiX-users] iis extension (fail while processing the website -2147024883 )

This customer may not have a Default Web Site on their system. Also, it also never hurts to get a Windows Installer log to confirm the port number is correct, etc. In our MSIs that use the WiX IIS extension to deploy IIS objects to the Default Web Site we use a custom action that goes and checks

Re: [WiX-users] Enforcing installation dependencies

Just so my comment reads a bit more clearly I'm going to label the products. In your situation you have Product B that depends on Product A being installed. If you are also the author of Product A you can add AppSearch item to search for a specific component from Product B, use an Upgrade table

Re: [WiX-users] Auto-generated vs statically assigned GUIDs

We use auto-generated Product GUIDs almost exclusively where I work. I really haven't found a downside to it, at least for our uses. As for detecting old products, it is still easy to detect them. Instead of looking them up using explicit ProductCodes you use the Upgrade table with the UpgradeC

Re: [WiX-users] Component Rules 101

Windows Installer registers components using the component GUID, ProductCode and key path to the component. So for files, each instance of the component, based on ProductCode registers with its own path. The component can be registered more than once to the same path as well but each instance of

Re: [WiX-users] Need to install 2 products at once

Just to provide another option, in my most recent project, a client/server product which has two services which are shared and installed by both the client and server MSIs. I wanted to single-source the WiX for those services so it could be maintained in once place. I used a WiX fragment for e

Re: [WiX-users] WiX syntax for GUIDs for 32-bit/64-bit components

Thanks for information on FIPS, I'm pretty sure I won't be needing to work with that at all. This product is a server/client configuration. The server is almost entirely .NET, we do have one service that requries a few registry keys but it's not for COM registration or anything just application

Re: [WiX-users] WiX syntax for GUIDs for 32-bit/64-bit components

What is the FIPS switch? I haven't heard of it, so I'm assuming it's not something I'll likely be changing in our builds. We do our builds through Team Build, so whatever default settings are passed to the WiX tools from WiX MSBuild tasks are what I'm using and won't likely be changing anytime s

Re: [WiX-users] Interviewing an installation developer

http://blogs.msdn.com/robmen/archive/2004/05/20/136530.aspx Issue #1 listed in here is a valid point but depending on your needs may not apply. I guarantee you though you'll need to debug those CAs at some point (issue #2 listed) and then you will realize the pain you have caused yourself. If y

Re: [WiX-users] Interviewing an installation developer

The excerise of writing a simple install would probably be fine, though I'm not sure it is necessary. I do agree that knowing the nuts and bolts of Windows Installer is key and knowing what tables/actions do what is critical. The one potential problem I could see with having them author a small

Re: [WiX-users] WiX syntax for GUIDs for 32-bit/64-bit components

How exactly does the Guid="*" work? I've seen and read this in the WiX SDK before. The , , , elements support auto-generation of GUIDs every time you build your project by specifying a * in place of the GUID. The way it reads to me it sounds like the GUID would get randomly changed every time

[WiX-users] WiX syntax for GUIDs for 32-bit/64-bit components

Currently I have some WiX projects that build both an x86 and x64 MSI. Many of our components contain .NET assemblies that target Any CPU so the fact that the components differ at all is just to properly support Windows Installer method of managing x86/x64 components based on the target OS. Now,

Re: [WiX-users] 64-bit *and* 32-bit Registry Keys in same MSI?

I had to do a similar thing in my WiX project which builds both x86 and x64 MSIs. Here is how I did some registry keys that needed to go both registry sections on x64 sytsems. Hope that helps. -- View

Re: [WiX-users] Making a Requirements Dialog

pmdarrow wrote: > > Hi all. I'd like to display a dialog after the feature customization > dialog that gives the user feedback if the requirements for installing > their selected features are fulfilled. For instance, if the user only > selected the database feature, SQL Server is the only requir