[WiX-users] Guidance on WiX and NuGet integration

I'm really confused by where NuGet fits in with a WiX deployment (which you can guess by the questions at the end...) Currently we’re really happy with our WiX (3.6) setup (smile)... Our TeamCity build creates the installers using Burn and Neils burn UI customisations for our WinForms products

[WiX-users] Duplicate symbol when using CompilerCore.CreateWixSimpleReferenceRow

Hi, My installer has two projects - a Setup Project which emits an .MSI and contains install metadata, and a Setup Library Project which emits a .wixlib which contains install components. The latter makes use of a compiler extension which generates an MSI table based on some child elements of the

Re: [WiX-users] Guidance on WiX and NuGet integration

NuGet is simply meant as package management for a developer. For example: instead of having to download and install Nunit to be able to use in their Visual Studio solution, they can simply add a NuGet package to their solution. See the following link for some more background information:

Re: [WiX-users] Duplicate symbol when using CompilerCore.CreateWixSimpleReferenceRow

A WixExtension used in the way you describe usually supplies three things: a CompilerExtension (to parse your new elements and attributes), a Table definition (comes from a tables.xml-style file with the definitions of the tables unique to your extension), and a binary-wixlib (containing your

Re: [WiX-users] Duplicate symbol when using CompilerCore.CreateWixSimpleReferenceRow

Hi Blair, Ok, does that mean I've encountered an error in the book, then? The book suggests adding the wixlib to the extension, and I've done that (means I should only have to reference the extension, not the wixlib, right?). However, the sample code in the book does not come with a test install

Re: [WiX-users] Duplicate symbol when using CompilerCore.CreateWixSimpleReferenceRow

John, Yes, you put the wixlib only into the extension, and that allows you to have your setup project only reference the extension and not the wixlib directly. The setup project references the extension in a similar fashion to the toolset-supplied extensions, except that the path (including

Re: [WiX-users] Duplicate symbol when using CompilerCore.CreateWixSimpleReferenceRow

Blair, Yes I have the tables.xml correctly referenced as described above. The error has disappeared. If this pattern is idiomatic for this type of extension, I'm happy. My points above were * The only widely available documentation for this appears to have an error * It would have been

[WiX-users] Burn : SQL Express 2008 R2 certificate problem

Hello, I'm trying to chain many prerequisites to my product : .NET 4.0 or 4.5, IIS and SQL Server Express which has some prerequisites too : .NET 3.5, Windows Installer 4.5, Powershell. It needs to work under Windows Server 2003 SP2, 2008 SP2/2008R2 RTM and 2012 RTM. I'm near the goal, but I

[WiX-users] Resolve Light 1056 Warning

I am creating a WiX installer for an application that requires some Microsoft merge modules. I'm getting several warnings like: warning LGHT1056: The Directory table contains a row with primary key(s) 'SystemFolder' which cannot be merged from the merge module 'C:\_blah\blah\COMCAT.MSM'.

Re: [WiX-users] Resolve Light 1056 Warning

Adding a Name=. attribute to the Directory element will get the . in there. I'll do some experimenting on a toy. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS  66227 Office:  913-341-3434 x791011 jocoo...@jackhenry.com

Re: [WiX-users] Resolve Light 1056 Warning

The Merge Modules have a bug in them. Have the produce fix them... or ignore the warning. On Wed, Jul 10, 2013 at 9:21 AM, Kathy Morey kmo...@profitstars.com wrote: I am creating a WiX installer for an application that requires some Microsoft merge modules. I'm getting several warnings

Re: [WiX-users] Duplicate symbol when using CompilerCore.CreateWixSimpleReferenceRow

You should be able to download the example for that chapter at the Packt publishers (packtpub.com) site. On the page that shows the details about the book, click the tab that says Support and there ought to be a Code Downloads link. -- View this message in context:

Re: [WiX-users] Resolve Light 1056 Warning

I was able to get the .:System32 by using Directory Id=ExperiementFolder Name=. SourceName=System32 Component Id=ProductComponent Guid=* File KeyPath=yes Source=$(var.SolutionDir).nuget\NuGet.exe / /Component /Directory -- John Merryweather Cooper

Re: [WiX-users] WiX 3.6: How do I consolidate languages?

Thanks a lot, Blair. That helps. - Miaohsi -Original Message- From: Blair Murri [mailto:os...@live.com] Sent: Tuesday, July 09, 2013 6:04 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX 3.6: How do I consolidate languages? Not certain (is that

[WiX-users] How can I loop through in C# custom action the Feature tree and detect the install state and install action for each one of the features?

Dear All, I am trying to find a way to loop through the Feature tree and detect the install state and install action for each one of the features in my C# custom action. Below is what I've found that I could use: FeatureInfo FeatureState = session.Features[feature_name]; From the FeatureState

Re: [WiX-users] Duplicate symbol when using CompilerCore.CreateWixSimpleReferenceRow

Yup, did that - that's how I know there's no test installer for it. When I removed that line, the install compiled but without the action. I'll add a test install to the sample, and see what I get. I just haven't had time to do that today, unfortunately. On 10 July 2013 17:47, Nick Ramirez

Re: [WiX-users] Duplicate symbol when using CompilerCore.CreateWixSimpleReferenceRow

Okay, I maybe wasn't fully understanding the problem. :) So, you're saying that you want to use your extension in another WIXLIB (unrelated to the WIXLIB you used to build your extension)...but when you try that, but don't reference the extension in your Setup project too, you get the error Cannot

Re: [WiX-users] Resolve Light 1056 Warning

Thanks, John. That did it for me. -Original Message- From: John Cooper Sent: Wednesday, July 10, 2013 12:50 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Resolve Light 1056 Warning I was able to get the .:System32 by using Directory

Re: [WiX-users] Resolve Light 1056 Warning

FYI It turns out that, although John's suggestion did work, different Microsoft merge modules have different values for some of the standard folders, and so I will be following Rob's suggestion and just ignoring those warnings. Thanks. -Original Message- From: Kathy Morey Sent:

[WiX-users] Dynamically bind UI Control values

Hello WIX Experts,   The following is my scenario:   On a UI Dialog, I have an edit control, some text controls, and push buttons (Back, Next, Cancel) as part of a wizard sequence. The user enters a KEY in the edit control, following which a custom action is to be invoked, which takes the KEY

Re: [WiX-users] Dynamically bind UI Control values

I don't believe Windows installer would support this, even if it did one could use orca to bypass it. If it were me I would use burn and a custom ux/ba. On Jul 10, 2013, at 8:02 PM, Raghu raghu_ti...@yahoo.com wrote: Hello WIX Experts, The following is my scenario: On a UI Dialog, I

Re: [WiX-users] How can I loop through in C# custom action the Feature tree and detect the install state and install action for each one of the features?

I would assume: foreach (FeatureInfo FeatureState in session.Features) { FeatureInfo.Name; // etc. } From: miaohsi.w...@invensys.com To: wix-users@lists.sourceforge.net Date: Wed, 10 Jul 2013 16:05:48 -0400 Subject: [WiX-users] How can I loop through in C# custom action the Feature

Re: [WiX-users] Duplicate symbol when using CompilerCore.CreateWixSimpleReferenceRow

There are several ways to make the *Ref. One way is to author a *Ref/ element. Another is to use CompilerCore.CreateWixSimpleReferenceRow(). Either works the same as the other. The original error appears to be due to missing code in the extension. The second error (caused by trying to

Re: [WiX-users] Dynamically bind UI Control values

Windows Installer simply does not support Raghu's scenario. There are no events you can subscribe to that are triggered by adding chars to a text box. 1st problem: you have to remove the focus from the text box before the text box's content is ever placed into a property you can ever access.