[WiX-users] Confused by "File in use"

[Robert Barnes]

Hi All,

I have created an installer with Wix for one of our products. It works
very well and in general I am happy with it.

However there is one small niggle that I haven't been able to solve
myself - when installing (I always do major upgrades) the installer
detects a file in use by another one of our programs that isn't
actually a part of my product! However this same dll is used by both
my product and the other program - same dll, same name but installed
into two different directories, so the other program is not actually
using the dll that is being installed it is using a copy in a
different path. Why does the installer get confused?

Cheers,
Rob Barnes

--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] ICE61: Upgrade.VersionMax format is wrong

[Castro, Edwin G. (Hillsboro)]

FYI: I found that light.exe has a -sice: argument.

Are the ICE distributed by WiX owned by WiX? Do I need to add a WiX bug?

Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail


> -Original Message-
> From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
> Sent: Thursday, January 14, 2010 10:37 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] ICE61: Upgrade.VersionMax format is wrong
> 
> Just tried building with 3.3.32767.0 and with 3.3.32768.0.
> 
> 3.3.32767.0: No errors
> 3.3.32768.0: error LGHT0204: ICE61: Upgrade.VersionMax 3.3.32768.0
> format is wrong
> 
> Looks like an incorrectly implemented ICE. Can I exclude ICE61?
> 
> Edwin G. Castro
> Software Developer - Staff
> Electronic Banking Services
> Fiserv
> Office: 503-746-0643
> Fax: 503-617-0291
> www.fiserv.com
> Please consider the environment before printing this e-mail
> 
> > -Original Message-
> > From: Simon Dahlbacka [mailto:simon.dahlba...@gmail.com]
> > Sent: Thursday, January 14, 2010 10:01 PM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] ICE61: Upgrade.VersionMax format is wrong
> >
> > just a hunch, can it be that the ICE is (wrongly) using a signed 16-
> > number
> > for the third field?
> >
> > On Fri, Jan 15, 2010 at 5:22 AM, Castro, Edwin G. (Hillsboro) <
> > edwin.cas...@fiserv.com> wrote:
> >
> > > I'm getting the following error from light:
> > >
> > > error LGHT0204: ICE61: Upgrade.VersionMax 3.3.34567.0 format is
> wrong
> > >
> > > The ProductVersion Property documentation <
> > > http://msdn.microsoft.com/en-
> > us/library/aa370859(VS.85).aspx > us/library/aa370859%28VS.85%29.aspx>>
> > > tells me that the first three fields have the following maximums:
> > 255, 255,
> > > 65535. It also tells me that a fourth field is ignored if provided.
> > >
> > > I can't figure out how the format is wrong. I tried building the
> > installer
> > > with the third and fourth fields reversed (3.3.0.34567) and I
> didn't
> > get any
> > > complaints from light. Can anybody explain why 3.3.34567.0 is
> wrong?
> > >
> > > Edwin G. Castro
> > > Software Developer - Staff
> > > Electronic Banking Services
> > > Fiserv
> > > Office: 503-746-0643
> > > Fax: 503-617-0291
> > > www.fiserv.com
> > > P Please consider the environment before printing this e-mail
> > >
> > >
> > > ---
> --
> > -
> > > Throughout its 18-year history, RSA Conference consistently
> attracts
> > the
> > > world's best and brightest in the field, creating opportunities for
> > > Conference
> > > attendees to learn about information security's most important
> issues
> > > through
> > > interactions with peers, luminaries and emerging and established
> > companies.
> > > http://p.sf.net/sfu/rsaconf-dev2dev
> > > ___
> > > WiX-users mailing list
> > > WiX-users@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/wix-users
> > >
> > -
> --
> > ---
> > Throughout its 18-year history, RSA Conference consistently attracts
> > the
> > world's best and brightest in the field, creating opportunities for
> > Conference
> > attendees to learn about information security's most important issues
> > through
> > interactions with peers, luminaries and emerging and established
> > companies.
> > http://p.sf.net/sfu/rsaconf-dev2dev
> > ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> ---
> ---
> Throughout its 18-year history, RSA Conference consistently attracts
> the
> world's best and brightest in the field, creating opportunities for
> Conference
> attendees to learn about information security's most important issues
> through
> interactions with peers, luminaries and emerging and established
> companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users m

Re: [WiX-users] ICE61: Upgrade.VersionMax format is wrong

[Castro, Edwin G. (Hillsboro)]

Just tried building with 3.3.32767.0 and with 3.3.32768.0.

3.3.32767.0: No errors
3.3.32768.0: error LGHT0204: ICE61: Upgrade.VersionMax 3.3.32768.0 format is 
wrong

Looks like an incorrectly implemented ICE. Can I exclude ICE61?

Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail

> -Original Message-
> From: Simon Dahlbacka [mailto:simon.dahlba...@gmail.com]
> Sent: Thursday, January 14, 2010 10:01 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] ICE61: Upgrade.VersionMax format is wrong
> 
> just a hunch, can it be that the ICE is (wrongly) using a signed 16-
> number
> for the third field?
> 
> On Fri, Jan 15, 2010 at 5:22 AM, Castro, Edwin G. (Hillsboro) <
> edwin.cas...@fiserv.com> wrote:
> 
> > I'm getting the following error from light:
> >
> > error LGHT0204: ICE61: Upgrade.VersionMax 3.3.34567.0 format is wrong
> >
> > The ProductVersion Property documentation <
> > http://msdn.microsoft.com/en-
> us/library/aa370859(VS.85).aspx us/library/aa370859%28VS.85%29.aspx>>
> > tells me that the first three fields have the following maximums:
> 255, 255,
> > 65535. It also tells me that a fourth field is ignored if provided.
> >
> > I can't figure out how the format is wrong. I tried building the
> installer
> > with the third and fourth fields reversed (3.3.0.34567) and I didn't
> get any
> > complaints from light. Can anybody explain why 3.3.34567.0 is wrong?
> >
> > Edwin G. Castro
> > Software Developer - Staff
> > Electronic Banking Services
> > Fiserv
> > Office: 503-746-0643
> > Fax: 503-617-0291
> > www.fiserv.com
> > P Please consider the environment before printing this e-mail
> >
> >
> > -
> -
> > Throughout its 18-year history, RSA Conference consistently attracts
> the
> > world's best and brightest in the field, creating opportunities for
> > Conference
> > attendees to learn about information security's most important issues
> > through
> > interactions with peers, luminaries and emerging and established
> companies.
> > http://p.sf.net/sfu/rsaconf-dev2dev
> > ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
> ---
> ---
> Throughout its 18-year history, RSA Conference consistently attracts
> the
> world's best and brightest in the field, creating opportunities for
> Conference
> attendees to learn about information security's most important issues
> through
> interactions with peers, luminaries and emerging and established
> companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Use of Merge Module

[ricky sundrani]

Reposting this question :
Is it possible to use the same merge module twice in the same source file.


   
 
   
 
 

  
 
 


  
  
 

 
  
  
 

 
  

 
  
 
The above code is giving error:
Error 1 The merge module 'merge2' contains a file identifier, 'm', that is
duplicated either in another merge module or in a File/@Id attribute.  File
identifiers must be unique.  Please change one of the file identifiers to a
different value.


Code in the merge module:

 





  

Basically i want to copy the file (file1.txt) in F1 and F2 using the mereg
module.How can it be done?


Best Regards.

Ricky
--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] ICE61: Upgrade.VersionMax format is wrong

[Simon Dahlbacka]

just a hunch, can it be that the ICE is (wrongly) using a signed 16-number
for the third field?

On Fri, Jan 15, 2010 at 5:22 AM, Castro, Edwin G. (Hillsboro) <
edwin.cas...@fiserv.com> wrote:

> I'm getting the following error from light:
>
> error LGHT0204: ICE61: Upgrade.VersionMax 3.3.34567.0 format is wrong
>
> The ProductVersion Property documentation <
> http://msdn.microsoft.com/en-us/library/aa370859(VS.85).aspx>
> tells me that the first three fields have the following maximums: 255, 255,
> 65535. It also tells me that a fourth field is ignored if provided.
>
> I can't figure out how the format is wrong. I tried building the installer
> with the third and fourth fields reversed (3.3.0.34567) and I didn't get any
> complaints from light. Can anybody explain why 3.3.34567.0 is wrong?
>
> Edwin G. Castro
> Software Developer - Staff
> Electronic Banking Services
> Fiserv
> Office: 503-746-0643
> Fax: 503-617-0291
> www.fiserv.com
> P Please consider the environment before printing this e-mail
>
>
> --
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for
> Conference
> attendees to learn about information security's most important issues
> through
> interactions with peers, luminaries and emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Conditionally Setting InstallScope

[Rob Mensching]

No. However, MSI 5.0 (only on Win7) has support for this using a new
mechanism: http://msdn.microsoft.com/en-us/library/dd770204%28VS.85%29.aspx

On Thu, Jan 14, 2010 at 12:47 PM, JKLists  wrote:

> I'm sorry my search skills are failing here; I'm sure this is a common
> question.
>
> Is there a way to conditionally set the InstallScope attribute based on
> passing a property in on the command line?
>
>
>
> --
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for
> Conference
> attendees to learn about information security's most important issues
> through
> interactions with peers, luminaries and emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>


-- 
virtually, Rob Mensching - http://RobMensching.com LLC
--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Help with setting properties from a JScript CA.

[Sebastian Brand (Instyler Software)]

Did you saw the missing T in the word Session.Proper_y(... ?

Best regards,
Sebastian Brand
sebast...@instyler.com

Geisenfelder Str. 53a
85053 Ingolstadt, Germany
EU VAT ID: DE219712370
Phone: +49 841 4544567

www.instyler.com - Instyler Setup: Create WiX-based MSI installations,
elegantly.
www.traveladdin.com - Travel Add-in for Outlook: Add travel and return times
to your calendar.
www.sebastianbrand.com - blogging about software development, deployment and
productivity.




> -Original Message-
> From: Rich Daniel [mailto:rdan...@microsoft.com]
> Sent: Friday, January 15, 2010 02:41
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] Help with setting properties from a JScript CA.
> 
> So, I've got this code that lets me know if certain databases are
installed or
> not:
> 
> function CheckDatabase(serverProperty, databaseProperty, checkProperty)
> {
> var serverName = Session.Property(serverProperty);
> var connectionString = "Provider=SQLOLEDB;Data Source=" + serverName
> + ";Integrated Security=SSPI";
> var connection = new ActiveXObject("ADODB.Connection");
> connection.Open(connectionString);
> var databaseName = Session.Property(databaseProperty);
> var command = "SELECT CASE WHEN DB_ID('" + databaseName + "') IS
> NULL THEN 0 ELSE 1 END";
> var records = connection.Execute(command);
> var exists = Number(records(0));
> Session.Propery(checkProperty) = exists;
> connection.Close();
> }
> 
> And it seems to work like a charm right up to the point I try to execute
> "Session.Propery(checkProperty) = exists;"
> At that point it hits me with a "script error -2146827850, Microsoft
JScript
> runtime error: Object doesn't support this property or method"
> 
> Is there something I'm missing or should I be taking a different approach
> entirely?
> 
> Thanks
> - Rich
> 
>

--
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for
Conference
> attendees to learn about information security's most important issues
> through interactions with peers, luminaries and emerging and established
> companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users


--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] ICE61: Upgrade.VersionMax format is wrong

[Sebastian Brand (Instyler Software)]

Have you tried it without the .0 at the end?

Best regards,
Sebastian Brand
sebast...@instyler.com

Geisenfelder Str. 53a
85053 Ingolstadt, Germany
EU VAT ID: DE219712370
Phone: +49 841 4544567

www.instyler.com - Instyler Setup: Create WiX-based MSI installations,
elegantly.
www.traveladdin.com - Travel Add-in for Outlook: Add travel and return times
to your calendar.
www.sebastianbrand.com - blogging about software development, deployment and
productivity.



> -Original Message-
> From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
> Sent: Friday, January 15, 2010 04:23
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] ICE61: Upgrade.VersionMax format is wrong
> 
> I'm getting the following error from light:
> 
> error LGHT0204: ICE61: Upgrade.VersionMax 3.3.34567.0 format is wrong
> 
> The ProductVersion Property documentation
>  tells me
> that the first three fields have the following maximums: 255, 255, 65535.
It
> also tells me that a fourth field is ignored if provided.
> 
> I can't figure out how the format is wrong. I tried building the installer
with
> the third and fourth fields reversed (3.3.0.34567) and I didn't get any
> complaints from light. Can anybody explain why 3.3.34567.0 is wrong?
> 
> Edwin G. Castro
> Software Developer - Staff
> Electronic Banking Services
> Fiserv
> Office: 503-746-0643
> Fax: 503-617-0291
> www.fiserv.com
> P Please consider the environment before printing this e-mail
> 
>

--
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for
Conference
> attendees to learn about information security's most important issues
> through interactions with peers, luminaries and emerging and established
> companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users


--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] ICE61: Upgrade.VersionMax format is wrong

[Castro, Edwin G. (Hillsboro)]

I'm getting the following error from light:

error LGHT0204: ICE61: Upgrade.VersionMax 3.3.34567.0 format is wrong

The ProductVersion Property documentation 
 tells me that 
the first three fields have the following maximums: 255, 255, 65535. It also 
tells me that a fourth field is ignored if provided.

I can't figure out how the format is wrong. I tried building the installer with 
the third and fourth fields reversed (3.3.0.34567) and I didn't get any 
complaints from light. Can anybody explain why 3.3.34567.0 is wrong?

Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail

--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Exceptions with pyro and -delta

[Kyle Huey]

Hello all,

I've successfully built and applied patches to my MSI with pyro without
-delta, but when I apply -delta, things go south.  Specifically, I get the
following error:

Microsoft (R) Windows Installer Xml Patch Builder version 3.0.5419.0
Copyright (C) Microsoft Corporation. All rights reserved.

Updating file information.
Creating cabinet files.
Creating cabinet 'C:\Users\Kyle Huey\AppData\Local\Temp\_dnnkzrp\#RTM.cab'.
pyro.exe : error PYRO0001 : Unknown error (0xc00e3103)

Exception Type: System.ComponentModel.Win32Exception

Stack Trace:
   at
Microsoft.Tools.WindowsInstallerXml.PatchAPI.PatchInterop.CreateDelta(Stri
ng deltaFile, String targetFile, String targetSymbolPath, String
targetRetainOff
sets, String[] basisFiles, String[] basisSymbolPaths, String[]
basisIgnoreLength
s, String[] basisIgnoreOffsets, String[] basisRetainLengths, String[]
basisRetai
nOffsets, PatchSymbolFlagsType apiPatchingSymbolFlags, Boolean
optimizePatchSize
ForLargeFiles, Boolean& retainRangesIgnored)
   at
Microsoft.Tools.WindowsInstallerXml.BinderFileManager.ResolvePatch(FileRow
 fileRow, Boolean& retainRangeWarning)
   at
Microsoft.Tools.WindowsInstallerXml.CabinetBuilder.CreateCabinet(CabinetWo
rkItem cabinetWorkItem)
   at Microsoft.Tools.WindowsInstallerXml.CabinetBuilder.ProcessWorkItems()

I get the same error on the latest 3.5 build as well.  The internet tells me
that 0xc00e3103 corresponds to the patchapi error ERROR_PATCH_SAME_FILE
(i.e. pyro is trying to generate a diff between two identical files).

Anybody have any ideas on what I'm doing wrong?

Thanks,

- Kyle Huey
--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Help with setting properties from a JScript CA.

[Rich Daniel]

So, I've got this code that lets me know if certain databases are installed or 
not:

function CheckDatabase(serverProperty, databaseProperty, checkProperty) {
var serverName = Session.Property(serverProperty);
var connectionString = "Provider=SQLOLEDB;Data Source=" + serverName + 
";Integrated Security=SSPI";
var connection = new ActiveXObject("ADODB.Connection");
connection.Open(connectionString);
var databaseName = Session.Property(databaseProperty);
var command = "SELECT CASE WHEN DB_ID('" + databaseName + "') IS NULL THEN 
0 ELSE 1 END";
var records = connection.Execute(command);
var exists = Number(records(0));
Session.Propery(checkProperty) = exists;
connection.Close();
}

And it seems to work like a charm right up to the point I try to execute 
"Session.Propery(checkProperty) = exists;"
At that point it hits me with a "script error -2146827850, Microsoft JScript 
runtime error: Object doesn't support this property or method"

Is there something I'm missing or should I be taking a different approach 
entirely?

Thanks
- Rich

--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Assistance with "simple" MSI creation/modification via WiX?

[Sascha Beaumont]

Welcome!

1) You will need separate 32 and 64-bit installers.

2) Starting from scratch will definitely be easier :)

3) If you're starting from scratch, just don't add a UI.


Hope that helps get you started..


On Fri, Jan 15, 2010 at 6:07 AM, Vern Graner  wrote:
> Hello all. :)
>
> I'm new to this list and have been reading for a couple of days now.
> Seems you folks deal with some pretty complex issues surrounding WiX so
> if you know of a more appropriate venue for my "n00b" questions, please
> just let me know. :)
>
> Before I jump in with my questions, here's a bit of context:
>
> I have been tasked with taking an old MSI (built primarily with ORCA by
> a previous employee) and replacing/updating the contents with
> new/additional components. The MSI is fairly small and simple. It only
> needs to deliver about a dozen files that create a paltry TWO system
> services.
>
> As for *my* skill set, I'm not *completely* unfamiliar with using MSI
> files. :) I've created transforms using ORCA and built some simple
> "snapshot" MSI's in the past as well. I've also done quite a bit of
> scripting and have a passing familiarity with programming in various
> languages (gathered over the last 20 years!) :)
>
> So, after "googling" around a bit, I've got most of the tools I think
> I'll need and have used them to successfully extract the original MSI
> using DARK. I then was able to take the WiX source code and
> open/view/edit it in Visual Studio.
>
> After a few minor changes (more or less "hello world" level stuff) I was
> able to re-compile the XML source using CANDLE, then link the result
> using LIGHT to create an MSI. So far so good. :)
>
> Though I have been able to get this far, I'm now unsure of how to move
> forward on the next steps on this project. For example:
>
> 1) I need to deliver 64-bit components - can I do this from a "32-bit"
> MSI that "detects" the target platform and chooses the correct
> components and target locations (i.e. "%SYSTEMROOT%\SYSTEM32\DRIVERS" vs
> "%SYSTEMROOT%\SysWOW64"), or do I need to create separate 64-bit and a
> 32-bit MSIs, one with each payload?
>
> 2) The XML created by DARK seems to be somewhat... messy (reminds me of
> "save as HTML" under WORD!). ;) As all I need to do is deliver a handful
> of files and a couple of services, would I be better served by starting
> from scratch rather than trying to figure out how the DARK generated XML
> works and then altering it?
>
> 3) The original MSI author created an entire GUI that we have discovered
> is not really necessary as most of the people that use the MSI are using
> it simply for GPO/AD deployment w/a transform. I would like to simplify
> the MSI if at all possible. Is there a straightforward way to "strip
> out" the GUI?
>
> I know some of the above questions call for subjective answers and there
> isn't much in the way of perspective given to help make the call.
> However, I've found most folks in a given field of expertise tend to
> have solved similar issues and can provide insight based on experience.
> I will be happy to have any advice you can share. :)
>
> Thanks for reading this admittedly long post and for any comments or
> help you can offer.
>
> :)
>
> Vern
>
> --
> Vern Graner CNE/CNA/SSE    | "If the network is down, then you're
> Senior Systems Engineer    | obviously incompetent so why are we
> Texas Information Services | paying you? Of course, if the network
> http://www.txis.com        | is up, then we obviously don't need
> Austin Office 512 328-8947 | you, so why are we paying you?" ©VLG
>
> --
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for Conference
> attendees to learn about information security's most important issues through
> interactions with peers, luminaries and emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>

--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Heat Bug with .Net COM

[Neil Sleightholm]

Done:
http://sourceforge.net/tracker/?func=detail&aid=2932337&group_id=105970&;
atid=642714 

Neil

-Original Message-
From: Brian Rogers [mailto:rogers.br...@gmail.com] 
Sent: 14 January 2010 16:55
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Heat Bug with .Net COM

Yes, please file a bug. This is a good thing to track.

Thanks,

Brian Rogers
"Intelligence removes complexity." - Me
http://blogs.msdn.com/icumove <-- NEW


On Wed, Jan 13, 2010 at 5:28 PM, Bob Arnson  wrote:

> On 1/13/2010 4:35 PM, Neil Sleightholm wrote:
> > I think there is a bug in the output generated when a .Net COM
assembly
> > is processed with heat but thought I would run it past the community
> > before raising it.
>
> If the assembly writes it, Heat includes it. Sounds like a reasonable
> thing to drop from the harvested output.
>
> --
> sig://boB
> http://joyofsetup.com/
>
>
>
>

--
> Throughout its 18-year history, RSA Conference consistently attracts
the
> world's best and brightest in the field, creating opportunities for
> Conference
> attendees to learn about information security's most important issues
> through
> interactions with peers, luminaries and emerging and established
companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
>  ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>

--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for
Conference
attendees to learn about information security's most important issues
through
interactions with peers, luminaries and emerging and established
companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Conditionally Setting InstallScope

[JKLists]

I'm sorry my search skills are failing here; I'm sure this is a common 
question.

Is there a way to conditionally set the InstallScope attribute based on 
passing a property in on the command line?


--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Major Upgrades and Versions

[Matt Walker]

I would think that as long as the ProductVersion, the ProductCode and the 
PackageCode changes and the Upgrade table contains the versions to be upgraded 
in the Min/Max version fields, it should act as a Major Upgrade.


Matt Walker
Installation Development
200 Kelly Road | Quakertown, PA 18951
Phone: +1 215.529.9900, x192 | 800.836.5440 
Fax: +1 215.536.9249
http://www.synergissoftware.com/
Adept Engineering Document Management & Workflow
This message (and any associated files) is intended only for the use of the 
individual or entity to which it is addressed and may contain information that 
is confidential, subject to copyright or constitutes a trade secret. If you are 
not the intended recipient you are hereby notified that any dissemination, 
copying or distribution of this message, or files associated with this message, 
is strictly prohibited. If you have received this message in error, please 
notify us immediately by replying to the message and deleting it from your 
computer. Messages sent to and from us may be monitored.
Internet communications cannot be guaranteed to be secure or error-free as 
information could be intercepted, corrupted, lost, destroyed, arrive late or 
incomplete, or contain viruses. Therefore, we do not accept responsibility for 
any errors or omissions that are present in this message, or any attachment, 
that have arisen as a result of e-mail transmission. If verification is 
required, please request a hard-copy version. Any views or opinions presented 
are solely those of the author and do not necessarily represent those of the 
company.



From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Thu 1/14/2010 3:16 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Major Upgrades and Versions



We have an automated build that runs continually. We'd like each MSI produced 
to behave as a major upgrade so that we can apply any newer MSI on a target 
environment easily. Our build process fixes the first two parts of our version 
numbers to predetermined values and allows the remaining two values to vary on 
a per-build basis. I understand I need to change produ...@id  and 
produ...@version with every build while keeping produ...@upgradecode constant 
to implement major upgrades. If produ...@version changes from 1.2.3 to 1.2.4 
will the MSI produced behave as a major upgrade?

Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail

--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Merge Module for msvcr71.dll

[Wilson, Phil]

Well there is no "currently", they are what they are, and that kb article says:

"For Msvcr70.dll or for Msvcr71.dll, you should install the CRT DLL into your 
application program files directory. You should not install these files into 
the Windows system directories. For Msvcr80.dll and for Msvcr90.dll, you should 
install the CRT as Windows side-by-side assemblies."

Phil Wilson 


-Original Message-
From: ricky sundrani [mailto:rickysundr...@gmail.com] 
Sent: Thursday, January 14, 2010 10:28 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Merge Module for msvcr71.dll

There is a link:
http://support.microsoft.com/default.aspx/kb/326922.
What is currently being followed for msvcr71.dll ? WinSxS or application
folder. ?
Also if someone could please help me with the merge module code..
About using the same merge module in the code twice in order to distribute
it to two locations.

On Thu, Jan 14, 2010 at 10:54 PM, Wilson, Phil
wrote:

> Are you sure about that WinSxS location? I believe the 7.1 merge modules
> will install the Dlls in the user's application folder.  I don't think they
> went WinSxS until Visual Studio 2005.
>
> Phil Wilson
>
> -Original Message-
> From: Pally Sandher [mailto:pally.sand...@iesve.com]
> Sent: Thursday, January 14, 2010 3:47 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Merge Module for msvcr71.dll
>
>
>   Id="msvcr71dll"Language="1033"DiskId="1"SourceFile="My_MSM.msm" />
>
>
>  
>
>
> That is all you should Ricky need assuming you're using the VC++ 7 merge
> modules provided with Visual Studio 2003. Your convoluted directory
> structure is totally unnecessary as the merge module is going to put the
> files into the WinSXS area regardless of where you would like it to go.
> You can't install those merge modules in an arbitrary directory even if
> you want to.
>
> Palbinder Sandher
> Software Deployment & IT Administrator
> T: +44 (0) 141 945 8500
> F: +44 (0) 141 945 8501
>
> http://www.iesve.com
> **Design, Simulate + Innovate with the **
> Integrated Environmental Solutions Limited. Registered in Scotland No.
> SC151456
> Registered Office - Helix Building, West Of Scotland Science Park,
> Glasgow G20 0SP
> Email Disclaimer
>
> -Original Message-
> From: Rob Hamflett [mailto:r...@snsys.com]
> Sent: 14 January 2010 09:29
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Merge Module for msvcr71.dll
>
> Doesn't the merge module install the file to the Windows system folder?
> If that's the case then you shouldn't need to install the file anywhere
> else.
>
> Rob
>
> On 14/01/2010 09:16, ricky sundrani wrote:
> > I am trying to use a merge module for msvcr71.dll since its strongly
> > recommended to use merge models for re-distributing c runtime
> libraries.
> > But i want to copy this msvcr71.dll to 2 different folders on
> installation.
> > But using the same merge module reference twice would cause the same
> > file to be included twice in the final msi, which causes conflict in
> > the File table , since file id is the primary key. (Since same file
> > would be included twice
> > )
> > Here is a sample of the code:
> >
> > <
> > Directory Id="TARGETDIR" Name="SourceDir">
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> >   
> >
> > <
> > Merge Id="msvcr71dll" Language="1033" DiskId="1"
> > SourceFile="My_MSM.msm">
> >
> >  > Merge>
> >
> >  > DirectoryRef>
> >
> > <
> > DirectoryRef Id="Folder2">
> >
> > <
> > Merge Id="msvcr71dllF2" Language="1033" DiskId="1"
> > SourceFile="My_MSM.msm">
> >
> >  > Merge>
> >
> > 
> >
> > <
> > Feature Id="ProductFeature1" Title="MergeMod321" Level="1">
> >
> > <
> > MergeRef Id="msvcr71dll"/>
> >
> >  > Feature>
> >
> > <
> > Feature Id="ProductFeature2" Title="MergeMod322" Level="1">
> >
> > <
> > MergeRef Id="msvcr71dllodbc"/>
> >
> >  > Feature/>
> > Above code gives obvious error that File/Id is duplicated(which is the
>
> > file id in the msm.
> >
> >
> >
> > Now i have to use the merge module and i cannot even modify the merge
> > module in anyway and need to copy the file in both the folders.
> >
> > Is there a way to do so?
> >
> > I saw the CopyFile element but that can be used only under a Component
>
> > or File Element.
> >
> >
>
>
> 
> --
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for
> Conference attendees to learn about information security's most
> important issues through interactions with peers, luminaries and
> emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
>
> ---

[WiX-users] Major Upgrades and Versions

[Castro, Edwin G. (Hillsboro)]

We have an automated build that runs continually. We'd like each MSI produced 
to behave as a major upgrade so that we can apply any newer MSI on a target 
environment easily. Our build process fixes the first two parts of our version 
numbers to predetermined values and allows the remaining two values to vary on 
a per-build basis. I understand I need to change produ...@id  and 
produ...@version with every build while keeping produ...@upgradecode constant 
to implement major upgrades. If produ...@version changes from 1.2.3 to 1.2.4 
will the MSI produced behave as a major upgrade?

Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail

--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Assistance with "simple" MSI creation/modification via WiX?

[Vern Graner]

Hello all. :)

I'm new to this list and have been reading for a couple of days now. 
Seems you folks deal with some pretty complex issues surrounding WiX so 
if you know of a more appropriate venue for my "n00b" questions, please 
just let me know. :)

Before I jump in with my questions, here's a bit of context:

I have been tasked with taking an old MSI (built primarily with ORCA by 
a previous employee) and replacing/updating the contents with 
new/additional components. The MSI is fairly small and simple. It only 
needs to deliver about a dozen files that create a paltry TWO system 
services.

As for *my* skill set, I'm not *completely* unfamiliar with using MSI 
files. :) I've created transforms using ORCA and built some simple 
"snapshot" MSI's in the past as well. I've also done quite a bit of 
scripting and have a passing familiarity with programming in various 
languages (gathered over the last 20 years!) :)

So, after "googling" around a bit, I've got most of the tools I think 
I'll need and have used them to successfully extract the original MSI 
using DARK. I then was able to take the WiX source code and 
open/view/edit it in Visual Studio.

After a few minor changes (more or less "hello world" level stuff) I was 
able to re-compile the XML source using CANDLE, then link the result 
using LIGHT to create an MSI. So far so good. :)

Though I have been able to get this far, I'm now unsure of how to move 
forward on the next steps on this project. For example:

1) I need to deliver 64-bit components - can I do this from a "32-bit" 
MSI that "detects" the target platform and chooses the correct 
components and target locations (i.e. "%SYSTEMROOT%\SYSTEM32\DRIVERS" vs 
"%SYSTEMROOT%\SysWOW64"), or do I need to create separate 64-bit and a 
32-bit MSIs, one with each payload?

2) The XML created by DARK seems to be somewhat... messy (reminds me of 
"save as HTML" under WORD!). ;) As all I need to do is deliver a handful 
of files and a couple of services, would I be better served by starting 
from scratch rather than trying to figure out how the DARK generated XML 
works and then altering it?

3) The original MSI author created an entire GUI that we have discovered 
is not really necessary as most of the people that use the MSI are using 
it simply for GPO/AD deployment w/a transform. I would like to simplify 
the MSI if at all possible. Is there a straightforward way to "strip 
out" the GUI?

I know some of the above questions call for subjective answers and there 
isn't much in the way of perspective given to help make the call. 
However, I've found most folks in a given field of expertise tend to 
have solved similar issues and can provide insight based on experience. 
I will be happy to have any advice you can share. :)

Thanks for reading this admittedly long post and for any comments or 
help you can offer.

:)

Vern

-- 
Vern Graner CNE/CNA/SSE| "If the network is down, then you're
Senior Systems Engineer| obviously incompetent so why are we
Texas Information Services | paying you? Of course, if the network
http://www.txis.com| is up, then we obviously don't need
Austin Office 512 328-8947 | you, so why are we paying you?" ©VLG

--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Installing a .NET program that is 64 bit/32-bit agnostic, but does actually care...

[Gordon Watts]

Hi all,

  I've got a app that is written in .NET. To function correctly it needs to 
access the registry. On a 32 bit system this is trivial. On a 64 bit system it 
needs to be run as a 64 bit app (installed in Program Files) in order to access 
these bits of the registry.

 

  But the .NET code is identical. I can build for "Any Platform", for example, 
and it will run just fine as a 64 or 32 bit process. In short, the same 
assmeblies will run on 32-bit and 64-bit platforms, but it is important that 
the assembly not run on the WOW64 on the 64 bit platform. So, just having these 
always install and run as 32-bit binaries will not work for me.

 

  When it comes to the wix scripts, how can I make a single msi file? I would 
really like to avoid dual msi's, one for 32 bit and one for 64 bit. Do I need 
to duplicate the components that go into the 32 bit and 64 bit folders? And 
then have some sort of "switch" in order to select them? Or would it be 
possible to have the same components, and then depending on some installer 
variable, have them installed in the proper place (i.e. the components need be 
in there only once)?

 

  What is the best way to approach this? Also, if I should use a "switch" of 
some sort, it would be great if someone could point me to some sample code of 
how a switch is done as I've never done anything that sophisticated in WiX 
before. J

 

  Many thanks!

 

Cheers,

Gordon.
--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Burn UI question

[John L Krupka]

Does/will the UI for Burn allow me to let the user select products they wish
to install?  For instance, if we distribute SQLExpress with our sysrem, can
I allow the user to select installing both or one of the components?

Also, is Burn mature enough to start using for a new new project?  

thanks
-john
-- 
View this message in context: 
http://n2.nabble.com/Burn-UI-question-tp4394495p4394495.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Merge Module for msvcr71.dll

[ricky sundrani]

There is a link:
http://support.microsoft.com/default.aspx/kb/326922.
What is currently being followed for msvcr71.dll ? WinSxS or application
folder. ?
Also if someone could please help me with the merge module code..
About using the same merge module in the code twice in order to distribute
it to two locations.

On Thu, Jan 14, 2010 at 10:54 PM, Wilson, Phil
wrote:

> Are you sure about that WinSxS location? I believe the 7.1 merge modules
> will install the Dlls in the user's application folder.  I don't think they
> went WinSxS until Visual Studio 2005.
>
> Phil Wilson
>
> -Original Message-
> From: Pally Sandher [mailto:pally.sand...@iesve.com]
> Sent: Thursday, January 14, 2010 3:47 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Merge Module for msvcr71.dll
>
>
>   Id="msvcr71dll"Language="1033"DiskId="1"SourceFile="My_MSM.msm" />
>
>
>  
>
>
> That is all you should Ricky need assuming you're using the VC++ 7 merge
> modules provided with Visual Studio 2003. Your convoluted directory
> structure is totally unnecessary as the merge module is going to put the
> files into the WinSXS area regardless of where you would like it to go.
> You can't install those merge modules in an arbitrary directory even if
> you want to.
>
> Palbinder Sandher
> Software Deployment & IT Administrator
> T: +44 (0) 141 945 8500
> F: +44 (0) 141 945 8501
>
> http://www.iesve.com
> **Design, Simulate + Innovate with the **
> Integrated Environmental Solutions Limited. Registered in Scotland No.
> SC151456
> Registered Office - Helix Building, West Of Scotland Science Park,
> Glasgow G20 0SP
> Email Disclaimer
>
> -Original Message-
> From: Rob Hamflett [mailto:r...@snsys.com]
> Sent: 14 January 2010 09:29
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Merge Module for msvcr71.dll
>
> Doesn't the merge module install the file to the Windows system folder?
> If that's the case then you shouldn't need to install the file anywhere
> else.
>
> Rob
>
> On 14/01/2010 09:16, ricky sundrani wrote:
> > I am trying to use a merge module for msvcr71.dll since its strongly
> > recommended to use merge models for re-distributing c runtime
> libraries.
> > But i want to copy this msvcr71.dll to 2 different folders on
> installation.
> > But using the same merge module reference twice would cause the same
> > file to be included twice in the final msi, which causes conflict in
> > the File table , since file id is the primary key. (Since same file
> > would be included twice
> > )
> > Here is a sample of the code:
> >
> > <
> > Directory Id="TARGETDIR" Name="SourceDir">
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> >   
> >
> > <
> > Merge Id="msvcr71dll" Language="1033" DiskId="1"
> > SourceFile="My_MSM.msm">
> >
> >  > Merge>
> >
> >  > DirectoryRef>
> >
> > <
> > DirectoryRef Id="Folder2">
> >
> > <
> > Merge Id="msvcr71dllF2" Language="1033" DiskId="1"
> > SourceFile="My_MSM.msm">
> >
> >  > Merge>
> >
> > 
> >
> > <
> > Feature Id="ProductFeature1" Title="MergeMod321" Level="1">
> >
> > <
> > MergeRef Id="msvcr71dll"/>
> >
> >  > Feature>
> >
> > <
> > Feature Id="ProductFeature2" Title="MergeMod322" Level="1">
> >
> > <
> > MergeRef Id="msvcr71dllodbc"/>
> >
> >  > Feature/>
> > Above code gives obvious error that File/Id is duplicated(which is the
>
> > file id in the msm.
> >
> >
> >
> > Now i have to use the merge module and i cannot even modify the merge
> > module in anyway and need to copy the file in both the folders.
> >
> > Is there a way to do so?
> >
> > I saw the CopyFile element but that can be used only under a Component
>
> > or File Element.
> >
> >
>
>
> 
> --
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for
> Conference attendees to learn about information security's most
> important issues through interactions with peers, luminaries and
> emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
>
> --
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for
> Conference
> attendees to learn about information security's most important issues
> through
> interactions with peers, luminaries and emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
> *** Confidentiality Notice:

Re: [WiX-users] What is the best-practice for updating an HKLM key?

[Joe]

That worked perfectly. Thanks very much!


   
 
   


Best,

Joe

On Thu, Jan 14, 2010 at 05:12:21PM -, Pally Sandher wrote:
> Regarding the ICE38 errors, it sounds like the directory your Component
> is under is a per-user location. Try moving the Component to a
> per-machine location like SystemFolder (even though you're not writing
> any actual files or folders to the location in your Component) if it's
> not there already. If it is then make sure you're setting the ALLUSERS
> property appropriately as modifying HKLM keys will likely require a
> per-machine installation (see
> http://msdn.microsoft.com/en-us/library/aa367559(VS.85).aspx).
> 
> Good Luck.
> 
> 
> Palbinder Sandher 
> Software Deployment & IT Administrator
> T: +44 (0) 141 945 8500 
> F: +44 (0) 141 945 8501 
> 
> http://www.iesve.com 
> **Design, Simulate + Innovate with the **
> Integrated Environmental Solutions Limited. Registered in Scotland No.
> SC151456 
> Registered Office - Helix Building, West Of Scotland Science Park,
> Glasgow G20 0SP
> Email Disclaimer
> 
> 
> -Original Message-
> From: Joe [mailto:w...@barillari.org] 
> Sent: 14 January 2010 16:35
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] What is the best-practice for updating an HKLM key?
> 
> Hi Wix-users,
> 
> I am curious about the best-practice way to update a registry key in
> HKLM. I would like to set
> 
>  Key="SYSTEM\CurrentControlSet\Control\Print\Providers"
> Type='integer' Action='write' Name="EventLog" Value='7' />
> 
> If I simply set it from a component with other (HKCU) RegistryValues and
> ignore the resulting warning ("warning LGHT1076 : ICE57: Component '...'
> has both per-user and per-machine data with an HKCU Registry KeyPath."),
> then Windows Installer will remove the key _entirely_ when I remove the
> product. Since the key is typically set to something beforehand, that's
> not the behavior I want.
> 
> (Ideally, the key would be restored to its original value on
> uninstallation, but I suspect this would require copying the key to my
> own registry entry, then setting a custom action to call reg.exe to set
> the key back to the original value when the product is
> uninstalled.)
> 
> If I pull the RegistryValue tag into its own component and mark it with
> Permanent="yes", then I get ICE38 errors:
> 
>   
>
> Key="SYSTEM\CurrentControlSet\Control\Print\Providers"
> Type='integer' Action='write' Name="EventLog"
> Value='7' />
>   
> 
> error LGHT0204 : ICE38: Component ProgramRegUpdate installs to user
> profile. It's KeyPath registry key must fall under HKCU.
> 
> I've read on this list that one way to avoid ICE38 is to create a dummy
> registry key and set the keypath to that, but then (a) I'd have a
> permanent dummy key hanging around and (b) that defeats the purpose of
> the KeyPath -- I would like the _actual_ HKLM key to be checked by
> Windows Installer, not the dummy.
> 
> I assume I'm either approaching this the wrong way or I haven't stumbled
> on the best-practice solution. I'm curious if anyone has any pointers.
> 
> Thanks in advance!

--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Merge Module for msvcr71.dll

[Wilson, Phil]

Are you sure about that WinSxS location? I believe the 7.1 merge modules will 
install the Dlls in the user's application folder.  I don't think they went 
WinSxS until Visual Studio 2005.

Phil Wilson 

-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com] 
Sent: Thursday, January 14, 2010 3:47 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Merge Module for msvcr71.dll


  


  


That is all you should Ricky need assuming you're using the VC++ 7 merge
modules provided with Visual Studio 2003. Your convoluted directory
structure is totally unnecessary as the merge module is going to put the
files into the WinSXS area regardless of where you would like it to go.
You can't install those merge modules in an arbitrary directory even if
you want to.

Palbinder Sandher 
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500 
F: +44 (0) 141 945 8501 

http://www.iesve.com 
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456 
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer

-Original Message-
From: Rob Hamflett [mailto:r...@snsys.com] 
Sent: 14 January 2010 09:29
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Merge Module for msvcr71.dll

Doesn't the merge module install the file to the Windows system folder?
If that's the case then you shouldn't need to install the file anywhere
else.

Rob

On 14/01/2010 09:16, ricky sundrani wrote:
> I am trying to use a merge module for msvcr71.dll since its strongly 
> recommended to use merge models for re-distributing c runtime
libraries.
> But i want to copy this msvcr71.dll to 2 different folders on
installation.
> But using the same merge module reference twice would cause the same 
> file to be included twice in the final msi, which causes conflict in 
> the File table , since file id is the primary key. (Since same file 
> would be included twice
> )
> Here is a sample of the code:
>
> <
> Directory Id="TARGETDIR" Name="SourceDir">
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
>   
>
> <
> Merge Id="msvcr71dll" Language="1033" DiskId="1" 
> SourceFile="My_MSM.msm">
>
>  Merge>
>
>  DirectoryRef>
>
> <
> DirectoryRef Id="Folder2">
>
> <
> Merge Id="msvcr71dllF2" Language="1033" DiskId="1" 
> SourceFile="My_MSM.msm">
>
>  Merge>
>
> 
>
> <
> Feature Id="ProductFeature1" Title="MergeMod321" Level="1">
>
> <
> MergeRef Id="msvcr71dll"/>
>
>  Feature>
>
> <
> Feature Id="ProductFeature2" Title="MergeMod322" Level="1">
>
> <
> MergeRef Id="msvcr71dllodbc"/>
>
>  Feature/>
> Above code gives obvious error that File/Id is duplicated(which is the

> file id in the msm.
>
>
>
> Now i have to use the merge module and i cannot even modify the merge 
> module in anyway and need to copy the file in both the folders.
>
> Is there a way to do so?
>
> I saw the CopyFile element but that can be used only under a Component

> or File Element.
>
>



--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for
Conference attendees to learn about information security's most
important issues through interactions with peers, luminaries and
emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



*** Confidentiality Notice: This e-mail, including any associated or attached 
files, is intended solely for the individual or entity to which it is 
addressed. This e-mail is confidential and may well also be legally privileged. 
If you have received it in error, you are on notice of its status. Please 
notify the sender immediately by reply e-mail and then delete this message from 
your system. Please do not copy it or use it for any purposes, or disclose its 
contents to any other person. This email comes from a division of the Invensys 
Group, owned by Invensys plc, which is a company registered in England and 
Wales with its registered office at Portland House, Bressenden Place, London, 
SW1E 5BF (Registered number 166023). For a list of European legal entiti

Re: [WiX-users] What is the best-practice for updating an HKLM key?

[Pally Sandher]

Regarding the ICE38 errors, it sounds like the directory your Component
is under is a per-user location. Try moving the Component to a
per-machine location like SystemFolder (even though you're not writing
any actual files or folders to the location in your Component) if it's
not there already. If it is then make sure you're setting the ALLUSERS
property appropriately as modifying HKLM keys will likely require a
per-machine installation (see
http://msdn.microsoft.com/en-us/library/aa367559(VS.85).aspx).

Good Luck.


Palbinder Sandher 
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500 
F: +44 (0) 141 945 8501 

http://www.iesve.com 
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456 
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer


-Original Message-
From: Joe [mailto:w...@barillari.org] 
Sent: 14 January 2010 16:35
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] What is the best-practice for updating an HKLM key?

Hi Wix-users,

I am curious about the best-practice way to update a registry key in
HKLM. I would like to set



If I simply set it from a component with other (HKCU) RegistryValues and
ignore the resulting warning ("warning LGHT1076 : ICE57: Component '...'
has both per-user and per-machine data with an HKCU Registry KeyPath."),
then Windows Installer will remove the key _entirely_ when I remove the
product. Since the key is typically set to something beforehand, that's
not the behavior I want.

(Ideally, the key would be restored to its original value on
uninstallation, but I suspect this would require copying the key to my
own registry entry, then setting a custom action to call reg.exe to set
the key back to the original value when the product is
uninstalled.)

If I pull the RegistryValue tag into its own component and mark it with
Permanent="yes", then I get ICE38 errors:

  
  
  

error LGHT0204 : ICE38: Component ProgramRegUpdate installs to user
profile. It's KeyPath registry key must fall under HKCU.

I've read on this list that one way to avoid ICE38 is to create a dummy
registry key and set the keypath to that, but then (a) I'd have a
permanent dummy key hanging around and (b) that defeats the purpose of
the KeyPath -- I would like the _actual_ HKLM key to be checked by
Windows Installer, not the dummy.

I assume I'm either approaching this the wrong way or I haven't stumbled
on the best-practice solution. I'm curious if anyone has any pointers.

Thanks in advance!


Joe


--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for
Conference attendees to learn about information security's most
important issues through interactions with peers, luminaries and
emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Heat Bug with .Net COM

[Brian Rogers]

Yes, please file a bug. This is a good thing to track.

Thanks,

Brian Rogers
"Intelligence removes complexity." - Me
http://blogs.msdn.com/icumove <-- NEW


On Wed, Jan 13, 2010 at 5:28 PM, Bob Arnson  wrote:

> On 1/13/2010 4:35 PM, Neil Sleightholm wrote:
> > I think there is a bug in the output generated when a .Net COM assembly
> > is processed with heat but thought I would run it past the community
> > before raising it.
>
> If the assembly writes it, Heat includes it. Sounds like a reasonable
> thing to drop from the harvested output.
>
> --
> sig://boB
> http://joyofsetup.com/
>
>
>
> --
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for
> Conference
> attendees to learn about information security's most important issues
> through
> interactions with peers, luminaries and emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
>  ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Heat.exe and 64-bit compatibility

[Brian Rogers]

Not sure if it is that straight forward. I think the reason we keep punting
this feature is the dependencies heat.exe has on the Wix core project (
http://sourceforge.net/tracker/index.php?func=detail&aid=2012626&group_id=105970&atid=642717
).

Brian Rogers
"Intelligence removes complexity." - Me
http://blogs.msdn.com/icumove <-- NEW


On Wed, Jan 13, 2010 at 5:32 PM, Bob Arnson  wrote:

> On 1/13/2010 8:07 PM, Navid Azimi-Garakani wrote:
> > Is there a particular reason why Heat.exe is targeted and compiled
> specifically against the x86 architecture?
>
> Because an MSIL .exe runs as a 64-bit process on an x64 system, so it
> couldn't load x86 DLLs. I suspect there's a need for Heat64.
>
> > I may try my hand at compiling the Heat project for 64-bit process
> architectures if that's what it comes down to. Any help before it gets ugly
> would be much appreciated!
> >
>
> Should be pretty straightforward, just get an enlistment.
>
> --
> sig://boB
> http://joyofsetup.com/
>
>
>
> --
>  Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for
> Conference
> attendees to learn about information security's most important issues
> through
> interactions with peers, luminaries and emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Why do I get ICE failures building from a serviceaccount?

[Blair]

For whatever reason on Windows 2008 (I didn't test Vista, XP, 2003, 7, or
2008 R2) the MSI Service is only available from logins that either have
administrative access or are logins that are "interactive". Logins that are
from service accounts that to not have administrative privileges cannot
access the msi service and thus cannot run ICE tests.

I had opened an inquiry inside of MSFT last year about this issue but it was
never resolved (I got a lot of "I would have thought, however). I never got
any other workarounds either.

-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com] 
Sent: Thursday, January 14, 2010 6:21 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Why do I get ICE failures building from a
serviceaccount?

The following string format was not expected by the external UI message
logger: "The Windows Installer Service could not be accessed. This can
occur if you are running Windows in safe mode, or if the Windows
Installer is not correctly installed. Contact your support personnel for
assistance.". 

msiexec service needs to be running for ICE's to be evaluated.

Palbinder Sandher 
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500 
F: +44 (0) 141 945 8501 

http://www.iesve.com 
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456 
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer


-Original Message-
From: Andrew Arnott [mailto:andrewarn...@gmail.com] 
Sent: 14 January 2010 00:06
To: wix-users
Cc: David Christiansen
Subject: Re: [WiX-users] Why do I get ICE failures building from a
serviceaccount?

 When I build my WIX project, it succeeds under user account A when I
log in as that person and build it myself from my Windows desktop.  But
when that same user account is used from a Windows Service (think
automated build
machine) the same build fails with the below errors.
 I've checked the jscript and vbscript engines, and they are registered
under HKLM and not HKCU for that user account.  I don't know what else
to try.  Any ideas?

 Thanks.


http://teamcity.dotnetopenauth.net:82/viewLog.html?buildId=892&tab=build
ResultsDiv&buildTypeId=bt45

 [07:16:41]: Project "build.proj.teamcity.patch.tcprojx" (MSI
target(s)):
(11m:19s)
 [07:27:47]: [Project "build.proj.teamcity.patch.tcprojx" (MSI
target(s)):] Project "DotNetOpenAuth.Installer.wixproj" (default
targets): (14s)
 [07:28:01]: [Project "DotNetOpenAuth.Installer.wixproj" (default
targets):] light.exe error LGHT0217: Error executing ICE action 'ICE01'.
The most common cause of this kind of ICE failure is an incorrectly
registered scripting engine. See
http://wix.sourceforge.net/faq.html#Error217 for details and how to
solve this problem. The following string format was not expected by the
external UI message logger: "The Windows Installer Service could not be
accessed. This can occur if you are running Windows in safe mode, or if
the Windows Installer is not correctly installed. Contact your support
personnel for assistance.".
 [07:28:01]: [Project "DotNetOpenAuth.Installer.wixproj" (default
targets):] light.exe error LGHT0217: Error executing ICE action 'ICE02'.
The most common cause of this kind of ICE failure is an incorrectly
registered scripting engine. See
http://wix.sourceforge.net/faq.html#Error217 for details and how to
solve this problem. The following string format was not expected by the
external UI message logger: "The Windows Installer Service could not be
accessed. This can occur if you are running Windows in safe mode, or if
the Windows Installer is not correctly installed. Contact your support
personnel for assistance.".
 [07:28:01]: [Project "DotNetOpenAuth.Installer.wixproj" (default
targets):] light.exe error LGHT0217: Error executing ICE action 'ICE03'.
The most common cause of this kind of ICE failure is an incorrectly
registered scripting engine. See
http://wix.sourceforge.net/faq.html#Error217 for details and how to
solve this problem. The following string format was not expected by the
external UI message logger: "The Windows Installer Service could not be
accessed. This can occur if you are running Windows in safe mode, or if
the Windows Installer is not correctly installed. Contact your support
personnel for assistance.".
 [07:28:01]: [Project "DotNetOpenAuth.Installer.wixproj" (default
targets):] light.exe error LGHT0217: Error executing ICE action 'ICE04'.
The most common cause of this kind of ICE failure is an incorrectly
registered scripting engine. See
http://wix.sourceforge.net/faq.html#Error217 for details and how to
solve this problem. The following string format was not expected by the
external UI message logger: "The Windows Installer Service could not be
accessed. This can occur if you are running Windows in safe mode, or if
the Windows Installer is not correctly installed. Contact your support
personnel 

[WiX-users] What is the best-practice for updating an HKLM key?

[Joe]

Hi Wix-users,

I am curious about the best-practice way to update a registry key in HKLM. I 
would like to set



If I simply set it from a component with other (HKCU) RegistryValues
and ignore the resulting warning ("warning LGHT1076 : ICE57: Component
'...' has both per-user and per-machine data with an HKCU Registry
KeyPath."), then Windows Installer will remove the key _entirely_ when
I remove the product. Since the key is typically set to something
beforehand, that's not the behavior I want.

(Ideally, the key would be restored to its original value on
uninstallation, but I suspect this would require copying the key to my
own registry entry, then setting a custom action to call reg.exe to
set the key back to the original value when the product is
uninstalled.)

If I pull the RegistryValue tag into its own component and mark it with 
Permanent="yes", then I get ICE38 errors:

  
  
  

error LGHT0204 : ICE38: Component ProgramRegUpdate installs to user profile. 
It's KeyPath registry key must fall under HKCU.

I've read on this list that one way to avoid ICE38 is to create a
dummy registry key and set the keypath to that, but then (a) I'd have
a permanent dummy key hanging around and (b) that defeats the purpose
of the KeyPath -- I would like the _actual_ HKLM key to be checked by
Windows Installer, not the dummy.

I assume I'm either approaching this the wrong way or I haven't
stumbled on the best-practice solution. I'm curious if anyone has any
pointers.

Thanks in advance!


Joe

--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] WiX-users Digest, Vol 44, Issue 50

[Andrew Faust]

Kyle, thanks for the link on ICE. Sebastian was correct, though. I was 
referring to tests to ensure the product was installed or removed correctly. 
Obviously every installer would be different. However, some tasks would be 
common such as checking files, registry keys and shortucts were created or 
deleted. I was hoping there was a toolkit to automate the creation of the shell 
testing code. Perhaps something which takes file lists, registry keys, etc then 
builds the code to run the installer and check the results. 

Coding this manually isn't hard. Just tedious. If I can't find a tool perhaps 
I'll build one.

Thanks,

Andrew Faust

Date: Thu, 14 Jan 2010 07:41:54 +0100
From: "Sebastian Brand \(Instyler Software\)" 
Subject: Re: [WiX-users] Testing Framework
To: "'General discussion for Windows Installer XML toolset.'"

Message-ID: <000701ca94e4$a9631de0$fc2959...@instyler.com>
Content-Type: text/plain;   charset="us-ascii"

The link points to ICE testing. I assume the author is looking for some
testing method that includes the actual installation/repair/remove actions.

I currently use a couple of VMs to test created MSI. To check if the
components get installed correctly I normally have a test program. E.g. if
you want to test that a custom action works, I have an additional program
that tests if the output the custom action creates works.

Still a lot of manual steps though...



--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Use setupbld to chain msi and exe as prerequisites

[Pally Sandher]

Until Burn is feature complete I'd recommend looking at dotnetinstaller
(http://dotnetinstaller.codeplex.com/). Been using it for a while now &
it's quite easy to configure & build in my experience.

Palbinder Sandher 
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500 
F: +44 (0) 141 945 8501 

http://www.iesve.com 
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456 
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer


-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com] 
Sent: 14 January 2010 01:28
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Use setupbld to chain msi and exe as
prerequisites

On 1/13/2010 3:04 PM, Ken Halprin wrote:
> Can I use setupbld to include both msi and exe files as prerequisites 
> before my wix-built msi installer runs?
>

Setupbld doesn't support running .exes.

--
sig://boB
http://joyofsetup.com/



--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for
Conference
attendees to learn about information security's most important issues
through
interactions with peers, luminaries and emerging and established
companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Why do I get ICE failures building from a serviceaccount?

[Pally Sandher]

The following string format was not expected by the external UI message
logger: "The Windows Installer Service could not be accessed. This can
occur if you are running Windows in safe mode, or if the Windows
Installer is not correctly installed. Contact your support personnel for
assistance.". 

msiexec service needs to be running for ICE's to be evaluated.

Palbinder Sandher 
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500 
F: +44 (0) 141 945 8501 

http://www.iesve.com 
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456 
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer


-Original Message-
From: Andrew Arnott [mailto:andrewarn...@gmail.com] 
Sent: 14 January 2010 00:06
To: wix-users
Cc: David Christiansen
Subject: Re: [WiX-users] Why do I get ICE failures building from a
serviceaccount?

 When I build my WIX project, it succeeds under user account A when I
log in as that person and build it myself from my Windows desktop.  But
when that same user account is used from a Windows Service (think
automated build
machine) the same build fails with the below errors.
 I've checked the jscript and vbscript engines, and they are registered
under HKLM and not HKCU for that user account.  I don't know what else
to try.  Any ideas?

 Thanks.


http://teamcity.dotnetopenauth.net:82/viewLog.html?buildId=892&tab=build
ResultsDiv&buildTypeId=bt45

 [07:16:41]: Project "build.proj.teamcity.patch.tcprojx" (MSI
target(s)):
(11m:19s)
 [07:27:47]: [Project "build.proj.teamcity.patch.tcprojx" (MSI
target(s)):] Project "DotNetOpenAuth.Installer.wixproj" (default
targets): (14s)
 [07:28:01]: [Project "DotNetOpenAuth.Installer.wixproj" (default
targets):] light.exe error LGHT0217: Error executing ICE action 'ICE01'.
The most common cause of this kind of ICE failure is an incorrectly
registered scripting engine. See
http://wix.sourceforge.net/faq.html#Error217 for details and how to
solve this problem. The following string format was not expected by the
external UI message logger: "The Windows Installer Service could not be
accessed. This can occur if you are running Windows in safe mode, or if
the Windows Installer is not correctly installed. Contact your support
personnel for assistance.".
 [07:28:01]: [Project "DotNetOpenAuth.Installer.wixproj" (default
targets):] light.exe error LGHT0217: Error executing ICE action 'ICE02'.
The most common cause of this kind of ICE failure is an incorrectly
registered scripting engine. See
http://wix.sourceforge.net/faq.html#Error217 for details and how to
solve this problem. The following string format was not expected by the
external UI message logger: "The Windows Installer Service could not be
accessed. This can occur if you are running Windows in safe mode, or if
the Windows Installer is not correctly installed. Contact your support
personnel for assistance.".
 [07:28:01]: [Project "DotNetOpenAuth.Installer.wixproj" (default
targets):] light.exe error LGHT0217: Error executing ICE action 'ICE03'.
The most common cause of this kind of ICE failure is an incorrectly
registered scripting engine. See
http://wix.sourceforge.net/faq.html#Error217 for details and how to
solve this problem. The following string format was not expected by the
external UI message logger: "The Windows Installer Service could not be
accessed. This can occur if you are running Windows in safe mode, or if
the Windows Installer is not correctly installed. Contact your support
personnel for assistance.".
 [07:28:01]: [Project "DotNetOpenAuth.Installer.wixproj" (default
targets):] light.exe error LGHT0217: Error executing ICE action 'ICE04'.
The most common cause of this kind of ICE failure is an incorrectly
registered scripting engine. See
http://wix.sourceforge.net/faq.html#Error217 for details and how to
solve this problem. The following string format was not expected by the
external UI message logger: "The Windows Installer Service could not be
accessed. This can occur if you are running Windows in safe mode, or if
the Windows Installer is not correctly installed. Contact your support
personnel for assistance.".
 [07:28:01]: [Project "DotNetOpenAuth.Installer.wixproj" (default
targets):] light.exe error LGHT0217: Error executing ICE action 'ICE05'.
The most common cause of this kind of ICE failure is an incorrectly
registered scripting engine. See
http://wix.sourceforge.net/faq.html#Error217 for details and how to
solve this problem. The following string format was not expected by the
external UI message logger: "The Windows Installer Service could not be
accessed. This can occur if you are running Windows in safe mode, or if
the Windows Installer is not correctly installed. Contact your support
personnel for assistance.".
 [07:28:01]: [Project "DotNetOpenAuth.Installer.wixproj" (default
targets):] light.exe error LGHT0217: Error executing ICE action 'ICE06'.
The most common c

Re: [WiX-users] Merge Module for msvcr71.dll

[ricky sundrani]

Supoosing the MSM is some custom msm with one just one component and one
file.
like
..
  

 
  
..

Now if i use the above code then too i can't use it.
Merge Modules are for code re-usability, But using the same merege module
twice within the the same wxs file i.e to install the file (referenced in
the merge module) to two locations is not possible.
Or is there a way to do it?
On Thu, Jan 14, 2010 at 5:47 PM, ricky sundrani wrote:

> The merge module i am using is installing the msvcr71.dll in the directory
> where i am puttin the reference to the merge module.
> Using the above code ,it installed it in Folder1. So maybe i am not using
> the correct msm.
> I'l look into it,
> Thanks
>
>   On Thu, Jan 14, 2010 at 5:16 PM, Pally Sandher 
> wrote:
>
>>
>>  > Id="msvcr71dll"Language="1033"DiskId="1"SourceFile="My_MSM.msm" />
>>
>>
>>  
>>
>>
>> That is all you should Ricky need assuming you're using the VC++ 7 merge
>> modules provided with Visual Studio 2003. Your convoluted directory
>> structure is totally unnecessary as the merge module is going to put the
>> files into the WinSXS area regardless of where you would like it to go.
>> You can't install those merge modules in an arbitrary directory even if
>> you want to.
>>
>> Palbinder Sandher
>> Software Deployment & IT Administrator
>> T: +44 (0) 141 945 8500
>> F: +44 (0) 141 945 8501
>>
>> http://www.iesve.com
>> **Design, Simulate + Innovate with the **
>> Integrated Environmental Solutions Limited. Registered in Scotland No.
>> SC151456
>> Registered Office - Helix Building, West Of Scotland Science Park,
>> Glasgow G20 0SP
>> Email Disclaimer
>>
>> -Original Message-
>> From: Rob Hamflett [mailto:r...@snsys.com]
>> Sent: 14 January 2010 09:29
>> To: wix-users@lists.sourceforge.net
>> Subject: Re: [WiX-users] Merge Module for msvcr71.dll
>>
>> Doesn't the merge module install the file to the Windows system folder?
>> If that's the case then you shouldn't need to install the file anywhere
>> else.
>>
>> Rob
>>
>> On 14/01/2010 09:16, ricky sundrani wrote:
>> > I am trying to use a merge module for msvcr71.dll since its strongly
>> > recommended to use merge models for re-distributing c runtime
>> libraries.
>> > But i want to copy this msvcr71.dll to 2 different folders on
>> installation.
>> > But using the same merge module reference twice would cause the same
>> > file to be included twice in the final msi, which causes conflict in
>> > the File table , since file id is the primary key. (Since same file
>> > would be included twice
>> > )
>> > Here is a sample of the code:
>> >
>> > <
>> > Directory Id="TARGETDIR" Name="SourceDir">
>> >
>> > 
>> >
>> > 
>> >
>> > 
>> >
>> > 
>> >
>> > 
>> >
>> > 
>> >
>> > 
>> >
>> > 
>> >
>> > 
>> >
>> >   
>> >
>> > <
>> > Merge Id="msvcr71dll" Language="1033" DiskId="1"
>> > SourceFile="My_MSM.msm">
>> >
>> > > > Merge>
>> >
>> > > > DirectoryRef>
>> >
>> > <
>> > DirectoryRef Id="Folder2">
>> >
>> > <
>> > Merge Id="msvcr71dllF2" Language="1033" DiskId="1"
>> > SourceFile="My_MSM.msm">
>> >
>> > > > Merge>
>> >
>> > 
>> >
>> > <
>> > Feature Id="ProductFeature1" Title="MergeMod321" Level="1">
>> >
>> > <
>> > MergeRef Id="msvcr71dll"/>
>> >
>> > > > Feature>
>> >
>> > <
>> > Feature Id="ProductFeature2" Title="MergeMod322" Level="1">
>> >
>> > <
>> > MergeRef Id="msvcr71dllodbc"/>
>> >
>> > > > Feature/>
>> > Above code gives obvious error that File/Id is duplicated(which is the
>>
>> > file id in the msm.
>> >
>> >
>> >
>> > Now i have to use the merge module and i cannot even modify the merge
>> > module in anyway and need to copy the file in both the folders.
>> >
>> > Is there a way to do so?
>> >
>> > I saw the CopyFile element but that can be used only under a Component
>>
>> > or File Element.
>> >
>> >
>>
>>
>> 
>> --
>> Throughout its 18-year history, RSA Conference consistently attracts the
>> world's best and brightest in the field, creating opportunities for
>> Conference attendees to learn about information security's most
>> important issues through interactions with peers, luminaries and
>> emerging and established companies.
>> http://p.sf.net/sfu/rsaconf-dev2dev
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
>>
>>
>>
>> --
>> Throughout its 18-year history, RSA Conference consistently attracts the
>> world's best and brightest in the field, creating opportunities for
>> Conference
>> attendees to learn about information security's most important issues
>> through
>> interactions with peers, luminaries and emerging and established
>> companies.
>> http://p.sf.net/sfu/rsaconf-dev2dev
>> ___
>> WiX-users mailing list
>> WiX-users@lists.source

Re: [WiX-users] Merge Module for msvcr71.dll

[ricky sundrani]

The merge module i am using is installing the msvcr71.dll in the directory
where i am puttin the reference to the merge module.
Using the above code ,it installed it in Folder1. So maybe i am not using
the correct msm.
I'l look into it,
Thanks

On Thu, Jan 14, 2010 at 5:16 PM, Pally Sandher wrote:

>
>   Id="msvcr71dll"Language="1033"DiskId="1"SourceFile="My_MSM.msm" />
>
>
>  
>
>
> That is all you should Ricky need assuming you're using the VC++ 7 merge
> modules provided with Visual Studio 2003. Your convoluted directory
> structure is totally unnecessary as the merge module is going to put the
> files into the WinSXS area regardless of where you would like it to go.
> You can't install those merge modules in an arbitrary directory even if
> you want to.
>
> Palbinder Sandher
> Software Deployment & IT Administrator
> T: +44 (0) 141 945 8500
> F: +44 (0) 141 945 8501
>
> http://www.iesve.com
> **Design, Simulate + Innovate with the **
> Integrated Environmental Solutions Limited. Registered in Scotland No.
> SC151456
> Registered Office - Helix Building, West Of Scotland Science Park,
> Glasgow G20 0SP
> Email Disclaimer
>
> -Original Message-
> From: Rob Hamflett [mailto:r...@snsys.com]
> Sent: 14 January 2010 09:29
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Merge Module for msvcr71.dll
>
> Doesn't the merge module install the file to the Windows system folder?
> If that's the case then you shouldn't need to install the file anywhere
> else.
>
> Rob
>
> On 14/01/2010 09:16, ricky sundrani wrote:
> > I am trying to use a merge module for msvcr71.dll since its strongly
> > recommended to use merge models for re-distributing c runtime
> libraries.
> > But i want to copy this msvcr71.dll to 2 different folders on
> installation.
> > But using the same merge module reference twice would cause the same
> > file to be included twice in the final msi, which causes conflict in
> > the File table , since file id is the primary key. (Since same file
> > would be included twice
> > )
> > Here is a sample of the code:
> >
> > <
> > Directory Id="TARGETDIR" Name="SourceDir">
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> >   
> >
> > <
> > Merge Id="msvcr71dll" Language="1033" DiskId="1"
> > SourceFile="My_MSM.msm">
> >
> >  > Merge>
> >
> >  > DirectoryRef>
> >
> > <
> > DirectoryRef Id="Folder2">
> >
> > <
> > Merge Id="msvcr71dllF2" Language="1033" DiskId="1"
> > SourceFile="My_MSM.msm">
> >
> >  > Merge>
> >
> > 
> >
> > <
> > Feature Id="ProductFeature1" Title="MergeMod321" Level="1">
> >
> > <
> > MergeRef Id="msvcr71dll"/>
> >
> >  > Feature>
> >
> > <
> > Feature Id="ProductFeature2" Title="MergeMod322" Level="1">
> >
> > <
> > MergeRef Id="msvcr71dllodbc"/>
> >
> >  > Feature/>
> > Above code gives obvious error that File/Id is duplicated(which is the
>
> > file id in the msm.
> >
> >
> >
> > Now i have to use the merge module and i cannot even modify the merge
> > module in anyway and need to copy the file in both the folders.
> >
> > Is there a way to do so?
> >
> > I saw the CopyFile element but that can be used only under a Component
>
> > or File Element.
> >
> >
>
>
> 
> --
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for
> Conference attendees to learn about information security's most
> important issues through interactions with peers, luminaries and
> emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
>
> --
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for
> Conference
> attendees to learn about information security's most important issues
> through
> interactions with peers, luminaries and emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>



-- 
Best Regards.

Ricky
--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://

Re: [WiX-users] Merge Module for msvcr71.dll

[Pally Sandher]

  


  


That is all you should Ricky need assuming you're using the VC++ 7 merge
modules provided with Visual Studio 2003. Your convoluted directory
structure is totally unnecessary as the merge module is going to put the
files into the WinSXS area regardless of where you would like it to go.
You can't install those merge modules in an arbitrary directory even if
you want to.

Palbinder Sandher 
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500 
F: +44 (0) 141 945 8501 

http://www.iesve.com 
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456 
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer

-Original Message-
From: Rob Hamflett [mailto:r...@snsys.com] 
Sent: 14 January 2010 09:29
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Merge Module for msvcr71.dll

Doesn't the merge module install the file to the Windows system folder?
If that's the case then you shouldn't need to install the file anywhere
else.

Rob

On 14/01/2010 09:16, ricky sundrani wrote:
> I am trying to use a merge module for msvcr71.dll since its strongly 
> recommended to use merge models for re-distributing c runtime
libraries.
> But i want to copy this msvcr71.dll to 2 different folders on
installation.
> But using the same merge module reference twice would cause the same 
> file to be included twice in the final msi, which causes conflict in 
> the File table , since file id is the primary key. (Since same file 
> would be included twice
> )
> Here is a sample of the code:
>
> <
> Directory Id="TARGETDIR" Name="SourceDir">
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
>   
>
> <
> Merge Id="msvcr71dll" Language="1033" DiskId="1" 
> SourceFile="My_MSM.msm">
>
>  Merge>
>
>  DirectoryRef>
>
> <
> DirectoryRef Id="Folder2">
>
> <
> Merge Id="msvcr71dllF2" Language="1033" DiskId="1" 
> SourceFile="My_MSM.msm">
>
>  Merge>
>
> 
>
> <
> Feature Id="ProductFeature1" Title="MergeMod321" Level="1">
>
> <
> MergeRef Id="msvcr71dll"/>
>
>  Feature>
>
> <
> Feature Id="ProductFeature2" Title="MergeMod322" Level="1">
>
> <
> MergeRef Id="msvcr71dllodbc"/>
>
>  Feature/>
> Above code gives obvious error that File/Id is duplicated(which is the

> file id in the msm.
>
>
>
> Now i have to use the merge module and i cannot even modify the merge 
> module in anyway and need to copy the file in both the folders.
>
> Is there a way to do so?
>
> I saw the CopyFile element but that can be used only under a Component

> or File Element.
>
>



--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for
Conference attendees to learn about information security's most
important issues through interactions with peers, luminaries and
emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to handle Registry Redirection throughWIXon64-bit Platform

[Pally Sandher]

Yep, my mistake. Was looking at a package in InstEd! at the time &
forgot about Itanium platform support as it still shows only "AMD64" for
the x64 platform where as Orca has both "AMD64" & "x64" IIRC (haven't
had it installed in a long time so I might be wrong).

Palbinder Sandher 
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500 
F: +44 (0) 141 945 8501 

http://www.iesve.com 
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456 
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer


-Original Message-
From: Jeremy Farrell [mailto:jfarr...@pillardata.com] 
Sent: 14 January 2010 04:23
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to handle Registry Redirection
throughWIXon64-bit Platform

> From: Pally Sandher [mailto:pally.sand...@iesve.com]
> Sent: Wednesday, January 13, 2010 10:49 AM
>
> ...
> An MSI has a platform attribute which must be set to "Intel" for x86 
> packages or "Intel64" for x64 packages (can also use "AMD64" for x64 
> packages but it's deprecated by "Intel64").
> ...

Some confusion here? I believe it's

Intel   - 32-bit x86
Intel64 - Itanium family
AMD64   - 64-bit x86, deprecated
x64 - 64-bit x86



--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for
Conference attendees to learn about information security's most
important issues through interactions with peers, luminaries and
emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] DCOM configuration

[Leo Kushnir]

Hi,

Is it Possible to configure DCOM component security issues?

Thanks,
Leo Kushnir
http://blogs.microsoft.co.il/blogs/leokushnir/


--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Merge Module for msvcr71.dll

[Rob Hamflett]

Doesn't the merge module install the file to the Windows system folder?  If 
that's the case then you 
shouldn't need to install the file anywhere else.

Rob

On 14/01/2010 09:16, ricky sundrani wrote:
> I am trying to use a merge module for msvcr71.dll since its strongly
> recommended to use merge models for re-distributing c runtime libraries.
> But i want to copy this msvcr71.dll to 2 different folders on installation.
> But using the same merge module reference twice would cause the same file to
> be included twice in the final msi, which causes conflict in the File table
> , since file id is the primary key. (Since same file would be included twice
> )
> Here is a sample of the code:
>
> <
> Directory Id="TARGETDIR" Name="SourceDir">
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
>   
>
> <
> Merge Id="msvcr71dll" Language="1033" DiskId="1" SourceFile="My_MSM.msm">
>
>  Merge>
>
>  DirectoryRef>
>
> <
> DirectoryRef Id="Folder2">
>
> <
> Merge Id="msvcr71dllF2" Language="1033" DiskId="1" SourceFile="My_MSM.msm">
>
>  Merge>
>
> 
>
> <
> Feature Id="ProductFeature1" Title="MergeMod321" Level="1">
>
> <
> MergeRef Id="msvcr71dll"/>
>
>  Feature>
>
> <
> Feature Id="ProductFeature2" Title="MergeMod322" Level="1">
>
> <
> MergeRef Id="msvcr71dllodbc"/>
>
>  Feature/>
> Above code gives obvious error that File/Id is duplicated(which is the file
> id in the msm.
>
>
>
> Now i have to use the merge module and i cannot even modify the merge
> module in anyway and need to copy the file in both the folders.
>
> Is there a way to do so?
>
> I saw the CopyFile element but that can be used only under a Component or
> File Element.
>
>


--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Merge Module for msvcr71.dll

[ricky sundrani]

I am trying to use a merge module for msvcr71.dll since its strongly
recommended to use merge models for re-distributing c runtime libraries.
But i want to copy this msvcr71.dll to 2 different folders on installation.
But using the same merge module reference twice would cause the same file to
be included twice in the final msi, which causes conflict in the File table
, since file id is the primary key. (Since same file would be included twice
)
Here is a sample of the code:

<
Directory Id="TARGETDIR" Name="SourceDir">



















 

<
Merge Id="msvcr71dll" Language="1033" DiskId="1" SourceFile="My_MSM.msm">





<
DirectoryRef Id="Folder2">

<
Merge Id="msvcr71dllF2" Language="1033" DiskId="1" SourceFile="My_MSM.msm">





<
Feature Id="ProductFeature1" Title="MergeMod321" Level="1">

<
MergeRef Id="msvcr71dll"/>



<
Feature Id="ProductFeature2" Title="MergeMod322" Level="1">

<
MergeRef Id="msvcr71dllodbc"/>


Above code gives obvious error that File/Id is duplicated(which is the file
id in the msm.



Now i have to use the merge module and i cannot even modify the merge
module in anyway and need to copy the file in both the folders.

Is there a way to do so?

I saw the CopyFile element but that can be used only under a Component or
File Element.


-- 
Best Regards.

Ricky
--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users