[WiX-users] WixUI_FeatureTree: disable (lock) target directory selection

2009-10-15 Thread Armin Linder
Hi all,

is it possible to disable the target directory selection GUI elements, 
depending on a condition?

The whole story: a product is delivred in modules (each is one msi) 
which a user can purchase and install in any order. It is essential that 
he always selects the same target directory. The directory is memorized 
via registry, so if he just accespts the defaults everything is fine. 
But he still can choose to select a differet diectory, so after the 
first install I'd like to show the target directory selection (so he 
sees where the data will go), but not let him change the path any more.

Can this be done?

Thanks,

Armin.

--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] WixUI_FeatureTree: disable (lock) target directory selection

2009-10-15 Thread Rob Hamflett
We have something similar where they can choose a location for first install 
but upgrades have to go 
to the same place.  I just disable the UI elements that allow the user to 
choose where to put 
things.  I suspect you can also just not specify feat...@configurabledirectory.

Rob

Armin Linder wrote:
 Hi all,
 
 is it possible to disable the target directory selection GUI elements, 
 depending on a condition?
 
 The whole story: a product is delivred in modules (each is one msi) 
 which a user can purchase and install in any order. It is essential that 
 he always selects the same target directory. The directory is memorized 
 via registry, so if he just accespts the defaults everything is fine. 
 But he still can choose to select a differet diectory, so after the 
 first install I'd like to show the target directory selection (so he 
 sees where the data will go), but not let him change the path any more.
 
 Can this be done?
 
 Thanks,
 
 Armin.
 
 --
 Come build with us! The BlackBerry(R) Developer Conference in SF, CA
 is the only developer event you need to attend this year. Jumpstart your
 developing skills, take BlackBerry mobile applications to market and stay 
 ahead of the curve. Join us from November 9 - 12, 2009. Register now!
 http://p.sf.net/sfu/devconference


--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Compile a project with used, but not specified compile time paramaters...

2009-10-15 Thread Thorsten Schöning
Guten Tag Blair,
am Mittwoch, 14. Oktober 2009 um 22:35 schrieben Sie:

 ?ifndef myvar?
 ?define myvar=abc?
 ?endif?

 ...$(var.myvar)...

 candle ... -dmyvar=123 ...

Thanks again, must have overseen the preprocessor articles. :-)

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning
AM-SoFT IT-Systeme - Hameln | Potsdam | Leipzig
 
Telefon: Potsdam: 0331-743881-0
E-Mail:  tschoen...@am-soft.de
Web: http://www.am-soft.de

AM-SoFT GmbH IT-Systeme, Konsumhof 1-5, 14482 Potsdam
Amtsgericht Potsdam HRB 21278 P, Geschäftsführer: Andreas Muchow


--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Web setup using .msm

2009-10-15 Thread Blair
Who wrote the MSM? Ask them to fix the failing custom action, or at least 
determine why the custom action is failing, or how to determine why the custom 
action is failing.

If the custom action that is failing is attempting self-registration, this 
would be a good opportunity to get rid of that MSM and have what it was doing 
changed to not use self-registration.

-Original Message-
From: cad [mailto:ankit.9...@gmail.com] 
Sent: Wednesday, October 14, 2009 10:14 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Web setup using .msm

Hi Blair,

How do i do this checking in the referred .msm.?

Thanks,



On Wed, Oct 14, 2009 at 8:58 PM, Blair os...@live.com wrote:

 It appears to be a failure in an action coming from your
 HealthCheckMergeModule.msm. You will need to check with the author of that
 MSM in order to diagnose that failure.

 -Original Message-
 From: Asterisk [mailto:ankit.9...@gmail.com]
 Sent: Wednesday, October 14, 2009 12:02 AM
 To: wix-users@lists.sourceforge.net
  Subject: Re: [WiX-users] Web setup using .msm




 Blair-2 wrote:
 
  Not sure, but InstallUtil* is Self-Reg (aka evil). Visual Studio's setup
  projects do several things that make deployment easier that invariably
  cause headaches later on when you have to service/maintain those setups
  (including broken upgrades, orphaned resources, failed removals, etc.).
 
  -Original Message-
  From: Asterisk [mailto:ankit.9...@gmail.com]
  Sent: Tuesday, October 13, 2009 4:26 AM
  To: wix-users@lists.sourceforge.net
  Subject: [WiX-users] Web setup using .msm
 
 
  Hi ,
 
  Please guide me to create a web setup (.msi).
  I have a .msm file created in visual studio merge module which basically
  does all the work.
  1.It creates a virtual directory and deploys the web application.
  2.It creates various performance counters and installs it.
  I want to refer it into a wix based setup(.msi refering to existing.msm)
 
  I have created a a web setup by refering to this existing .msm in VS 2008
  and it works perfect.
  Can anyone help me to create same web setup by refering to the same .msm
  created in vs 2008 as merge module.
 
  When i refer it and create .msi , and run it gives me error Error 1001.
  InstallUtilLib dll: Unknown error while installing the web application.
 
  When i remove my custom actions as part of .msm and refer the same in wix
  web setup. it works fine.
  Can anyone help me put to put these custom actions as a part of .msm?
  Or i have to include these custom actions as a part of wix web setup?
 
 
 
 
  Thanks in advance:)
  --
  View this message in context:
  http://n2.nabble.com/Web-setup-using-msm-tp3815520p3815520.html
  Sent from the wix-users mailing list archive at Nabble.com.
 
 
 
  --
  Come build with us! The BlackBerry(R) Developer Conference in SF, CA
  is the only developer event you need to attend this year. Jumpstart your
  developing skills, take BlackBerry mobile applications to market and stay
  ahead of the curve. Join us from November 9 - 12, 2009. Register now!
  http://p.sf.net/sfu/devconference
  ___
  WiX-users mailing list
  WiX-users@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wix-users
 
 
 
 --
  Come build with us! The BlackBerry(R) Developer Conference in SF, CA
  is the only developer event you need to attend this year. Jumpstart your
  developing skills, take BlackBerry mobile applications to market and stay
  ahead of the curve. Join us from November 9 - 12, 2009. Register now!
  http://p.sf.net/sfu/devconference
  ___
  WiX-users mailing list
  WiX-users@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wix-users
 
 

 In log file i could find that the install sequence is gicing me problem..

 

 MSI (s) (94:50) [11:20:08:552]: Executing op:
 InstallProtectedFiles(AllowUI=1)
 MSI (s) (94:50) [11:20:08:552]: Executing op:
 ActionStart(Name=_51E360DF_F34A_421D_A7AC_67C0A4676F95.commit,,)
 MSI (s) (94:50) [11:20:08:583]: Executing op:

 CustomActionSchedule(Action=_51E360DF_F34A_421D_A7AC_67C0A4676F95.commit,ActionType=3585,Source=BinaryData,Target=ManagedInstall,CustomActionData=/installtype=notransaction
 /action=commit /LogFile= /targetvdir= C:\Program
 Files\Setup\HealthCheck.Core.dll )
 MSI (s) (94:50) [11:20:08:583]: Executing op:
 ActionStart(Name=_5795ED8E_F94E_4E6D_8F5F_0CA4CFB131AD.install,,)
 MSI (s) (94:50) [11:20:08:583]: Executing op:

 CustomActionSchedule(Action=_5795ED8E_F94E_4E6D_8F5F_0CA4CFB131AD.install,ActionType=3073,Source=BinaryData,Target=ManagedInstall,CustomActionData=/installtype=notransaction
 /action=install /LogFile= C:\Program Files\Setup\HealthCheck.Core.dll )
 MSI (s) (94:E0) [11:20:08:599]: Invoking 

Re: [WiX-users] failed install, error is Failed to open XML file

2009-10-15 Thread Chris Jokinen
Ok, I found this old posting on the same issue I am having. 
http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg22390.html
It would look like I need to switch from XmlFile to XmlConfig to do what I need 
to do. I see the example that Brian posted was

util:XmlConfig Id=AddElementText
File=[SOMEEXISTINGFILE]
Action=create
ElementPath=/someElement
Node=value
Value=NEW TEXT
On=install
Sequence=1 /

My question is do I need to delete the file first or can I use a create action 
directly?

-Original Message-
From: Chris Jokinen [mailto:chr...@directron.us] 
Sent: Wednesday, October 14, 2009 5:15 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: [WiX-users] failed install, error is Failed to open XML file

This extract is from my msi log file.

 

MSI (s) (6C:D8) [16:49:36:281]: Executing op: 
CustomActionSchedule(Action=ExecXmlFile,ActionType=3073,Source=BinaryData,Target=ExecXmlFile,CustomActionData=1€0€\RollCall.exe.config€3€0€/configuration/applicationSettings/RollCall.Properties.Settings/setti...@key='project']/value/€value€test)

MSI (s) (6C:B8) [16:49:36:281]: Invoking remote custom action. DLL: 
C:\WINDOWS\Installer\MSIF10.tmp, Entrypoint: ExecXmlFile

ExecXmlFile:  Found Wow64 API, but unable to link to 
Wow64DisableWow64FsRedirection function in kernel32.dll

ExecXmlFile:  Found Wow64 API, but unable to link to 
Wow64RevertWow64FsRedirection function in kernel32.dll

ExecXmlFile:  Error 0x8007006e: failed to load XML file: \RollCall.exe.config

MSI (s) (6C!28) [16:49:36:312]: Product: setup -- Error 25531. Failed to open 
XML file \RollCall.exe.config, system error: -2147024786

 

It looks to have an issue with Wow64…any guidance on this error?

 

Thanks

--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] failed install, error is Failed to open XML file

2009-10-15 Thread Blair
XmlConfig, just like XmlFile, depend on the XML file already existing when the 
action runs. The syntax between the two actions is slightly different, and the 
capabilities are slightly different, but I'm not sure what you are referring to 
when you say do I need to delete the file first or can I use a create action 
directly.

If the element you want to modify already exists, you can simply change the 
element by creating its value (or the value of its attribute, depending on 
what you are trying to do). I'm assuming that you were asking about the 
perceived need to delete the value/element/attribute first (instead of file?).

-Original Message-
From: Chris Jokinen [mailto:chr...@directron.us] 
Sent: Thursday, October 15, 2009 7:58 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] failed install, error is Failed to open XML file

Ok, I found this old posting on the same issue I am having. 
http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg22390.html
It would look like I need to switch from XmlFile to XmlConfig to do what I need 
to do. I see the example that Brian posted was

util:XmlConfig Id=AddElementText
File=[SOMEEXISTINGFILE]
Action=create
ElementPath=/someElement
Node=value
Value=NEW TEXT
On=install
Sequence=1 /

My question is do I need to delete the file first or can I use a create action 
directly?

-Original Message-
From: Chris Jokinen [mailto:chr...@directron.us] 
Sent: Wednesday, October 14, 2009 5:15 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: [WiX-users] failed install, error is Failed to open XML file

This extract is from my msi log file.

 

MSI (s) (6C:D8) [16:49:36:281]: Executing op: 
CustomActionSchedule(Action=ExecXmlFile,ActionType=3073,Source=BinaryData,Target=ExecXmlFile,CustomActionData=1€0€\RollCall.exe.config€3€0€/configuration/applicationSettings/RollCall.Properties.Settings/setti...@key='project']/value/€value€test)

MSI (s) (6C:B8) [16:49:36:281]: Invoking remote custom action. DLL: 
C:\WINDOWS\Installer\MSIF10.tmp, Entrypoint: ExecXmlFile

ExecXmlFile:  Found Wow64 API, but unable to link to 
Wow64DisableWow64FsRedirection function in kernel32.dll

ExecXmlFile:  Found Wow64 API, but unable to link to 
Wow64RevertWow64FsRedirection function in kernel32.dll

ExecXmlFile:  Error 0x8007006e: failed to load XML file: \RollCall.exe.config

MSI (s) (6C!28) [16:49:36:312]: Product: setup -- Error 25531. Failed to open 
XML file \RollCall.exe.config, system error: -2147024786

 

It looks to have an issue with Wow64…any guidance on this error?

 

Thanks

--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] light.exe failed randomly when running ICEs.

2009-10-15 Thread Blair
Not sure. The semi-pseudocode would look like the following, however:

[assembly: AssemblyDefaultWixExtension(typeof(MyConcurrencyExtension))]
class MyConcurrencyExtension : WixExtension
{
private ValidatorExtension myValidation;

public override ValidatorExtension ValidatorExtension
{
get
{
if (null == myValidation)
{
myValidation = new MyValidatorExt();
}
return myValidation;
}
}
}
class MyValidatorExt : ValidatorExtension
{
private Mutex msiMutex;

public override void InitializeValidator()
{
base.InitializeValidator();
msiMutex = acquire-mutex();
}

public override void FinalizeValidator()
{
release-mutex(msiMutex);
base.FinalizeValidator();
}
}

Heath has blogged about using the public well known MSI mutex (in other
contexts) which should also help prevent build errors caused by WUS or other
background operations accessing MSI during your builds. In a previous
project (before having a better idea what was really happening) I used a
private semaphore and discovered that the number of concurrent validation
sessions had to be exactly one, and then managed to have a background
installation operation (a corporate patch push of some sort) happen during a
build which lead me to believe the best synchronization object would be the
MSI mutex.

You could use the above extension with both light and smoke. It will hold
the mutex the minimal amount of time necessary, which will allow maximal use
of the concurrency you have built into your build system while still
preventing the errors you were seeing.

-Original Message-
From: Kevin Gu [mailto:k...@microsoft.com] 
Sent: Wednesday, October 14, 2009 9:18 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] light.exe failed randomly when running ICEs.

Hi Blair,

   Thanks for your information. 

   Is there any example of writing a ValidatorExtension?


Thanks,
Kevin GU | SDE | CSAT China | 8621-61518167


-Original Message-
From: Blair [mailto:os...@live.com] 
Sent: Thursday, October 15, 2009 12:33 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] light.exe failed randomly when running ICEs.

ICE validations run the Windows Installer transaction engine (which is a
singleton), but it doesn't seem to check for the public mutex first. The
error messages returned as a result often don't make sense, however.

The best fix is to add a validation extension that acquires the installation
mutex when starting validation and releasing it when it ends. The next best
fix is to either ensure that only one copy of light runs at a time (you can
create multiple cabs on multiple threads to regain most of the performance
impact lost by making light a singleton) or suppress validation in light and
run smoke as a singleton. If you run smoke, pass it both the MSI and the
wixpdb together to get the same/best output (pointing to your source code
where possible).

-Original Message-
From: Kevin Gu [mailto:k...@microsoft.com] 
Sent: Wednesday, October 14, 2009 9:16 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] light.exe failed randomly when running ICEs.

Hi,

   I've got this kind of error when building concurrently using 4 threads.

Error executing ICE action 'ICE38'. 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: Error 1711.An error occurred while writing installation
information to disk. Check to make sure enough disk space is available, and
click Retry, or Cancel to end the install..

   This error occurs randomly. It seems that ICE validations are not stable
when running on multiple instances of MSIs. Any idea about how to fix this
issue?


Thanks,
Kevin GU | SDE | CSAT China | 8621-61518167


--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 

Re: [WiX-users] failed install, error is Failed to open XML file

2009-10-15 Thread Chris Jokinen
The installer copies two files; an exe and a config (the xml file) into the 
same directory (finally got that to work!). The next thing I need to do is 
update the xml config file with the 3 command line parameters being supplied 
during a silent install. Currently I am just testing 1 parameter with a command 
line like this...

Msiexec /i setup.msi /qn /l*v c:\install.log PROJECT=test

The goal here is to update the programs xml based config file 
(RollCall.exe.config) with the value of the parameter PROJECT

I changed my wix file to use...
Component Id=RollCall.exe.config Guid=3b367d78-64a2-4eb5-bf8d-3aa5ada56735

File Id=RollCallexeconfig Source=C:\Documents and Settings\chrisj\My 
Documents\Visual Studio 2005\Projects\Roll Call\Roll 
Call\bin\Release\RollCall.exe.config DiskId=1 KeyPath=yes /

util:XmlConfig Id=AddProjectText
File=[INSTALLLOCATION]\RollCall.exe.config

ElementPath=/configuration/applicationSettings/RollCall.Properties.Settings/setting[...@key='project'[\]]/value
Value=[PROJECT]
On=install
Sequence=1 /
/Component

My original concern is that since my file already had a tag with a name of 
project and that I would need to delete it and then recreate it. I came to this 
conclusion do to the XmlFile action having only; create and delete 
actions...and nothing like an update action. 

From reading your response I see I am missing the usage of create as you have 
stated below. I will change my XmlConfig to include the action create and 
test again.

I feel I am getting close... =)

-- Chris

-Original Message-
From: Blair [mailto:os...@live.com] 
Sent: Thursday, October 15, 2009 11:14 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] failed install, error is Failed to open XML file

XmlConfig, just like XmlFile, depend on the XML file already existing when the 
action runs. The syntax between the two actions is slightly different, and the 
capabilities are slightly different, but I'm not sure what you are referring to 
when you say do I need to delete the file first or can I use a create action 
directly.

If the element you want to modify already exists, you can simply change the 
element by creating its value (or the value of its attribute, depending on 
what you are trying to do). I'm assuming that you were asking about the 
perceived need to delete the value/element/attribute first (instead of file?).

-Original Message-
From: Chris Jokinen [mailto:chr...@directron.us] 
Sent: Thursday, October 15, 2009 7:58 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] failed install, error is Failed to open XML file

Ok, I found this old posting on the same issue I am having. 
http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg22390.html
It would look like I need to switch from XmlFile to XmlConfig to do what I need 
to do. I see the example that Brian posted was

util:XmlConfig Id=AddElementText
File=[SOMEEXISTINGFILE]
Action=create
ElementPath=/someElement
Node=value
Value=NEW TEXT
On=install
Sequence=1 /

My question is do I need to delete the file first or can I use a create action 
directly?

-Original Message-
From: Chris Jokinen [mailto:chr...@directron.us] 
Sent: Wednesday, October 14, 2009 5:15 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: [WiX-users] failed install, error is Failed to open XML file

This extract is from my msi log file.

 

MSI (s) (6C:D8) [16:49:36:281]: Executing op: 
CustomActionSchedule(Action=ExecXmlFile,ActionType=3073,Source=BinaryData,Target=ExecXmlFile,CustomActionData=1€0€\RollCall.exe.config€3€0€/configuration/applicationSettings/RollCall.Properties.Settings/setti...@key='project']/value/€value€test)

MSI (s) (6C:B8) [16:49:36:281]: Invoking remote custom action. DLL: 
C:\WINDOWS\Installer\MSIF10.tmp, Entrypoint: ExecXmlFile

ExecXmlFile:  Found Wow64 API, but unable to link to 
Wow64DisableWow64FsRedirection function in kernel32.dll

ExecXmlFile:  Found Wow64 API, but unable to link to 
Wow64RevertWow64FsRedirection function in kernel32.dll

ExecXmlFile:  Error 0x8007006e: failed to load XML file: \RollCall.exe.config

MSI (s) (6C!28) [16:49:36:312]: Product: setup -- Error 25531. Failed to open 
XML file \RollCall.exe.config, system error: -2147024786

 

It looks to have an issue with Wow64…any guidance on this error?

 

Thanks

--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference

Re: [WiX-users] failed install, error is Failed to open XML file

2009-10-15 Thread Blair
Just an aside:

For the File attribute of the util:XmlConfig element, instead of 
[INSTALLLOCATION]\RollCall.exe.config you could use [#RollCallexeconfig]. 
That would protect you against changes in the directory name and even 
filename of the file you are updating, especially since you are always altering 
that file every time you replace it and at no other time (so 
[#RollCallexeconfig] will always be defined when you need it), as a consequence 
of keeping the XmlConfig tag inside the same component that writes the config 
file.

One rule to make code more maintainable is to reduce the repetition of the same 
information over and over again. One way to do that is to reference code 
instead of recreating it all the time.

-Original Message-
From: Chris Jokinen [mailto:chr...@directron.us] 
Sent: Thursday, October 15, 2009 9:37 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] failed install, error is Failed to open XML file

The installer copies two files; an exe and a config (the xml file) into the 
same directory (finally got that to work!). The next thing I need to do is 
update the xml config file with the 3 command line parameters being supplied 
during a silent install. Currently I am just testing 1 parameter with a command 
line like this...

Msiexec /i setup.msi /qn /l*v c:\install.log PROJECT=test

The goal here is to update the programs xml based config file 
(RollCall.exe.config) with the value of the parameter PROJECT

I changed my wix file to use...
Component Id=RollCall.exe.config Guid=3b367d78-64a2-4eb5-bf8d-3aa5ada56735

File Id=RollCallexeconfig Source=C:\Documents and Settings\chrisj\My 
Documents\Visual Studio 2005\Projects\Roll Call\Roll 
Call\bin\Release\RollCall.exe.config DiskId=1 KeyPath=yes /

util:XmlConfig Id=AddProjectText
File=[INSTALLLOCATION]\RollCall.exe.config

ElementPath=/configuration/applicationSettings/RollCall.Properties.Settings/setting[...@key='project'[\]]/value
Value=[PROJECT]
On=install
Sequence=1 /
/Component

My original concern is that since my file already had a tag with a name of 
project and that I would need to delete it and then recreate it. I came to this 
conclusion do to the XmlFile action having only; create and delete 
actions...and nothing like an update action. 

From reading your response I see I am missing the usage of create as you have 
stated below. I will change my XmlConfig to include the action create and 
test again.

I feel I am getting close... =)

-- Chris

-Original Message-
From: Blair [mailto:os...@live.com] 
Sent: Thursday, October 15, 2009 11:14 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] failed install, error is Failed to open XML file

XmlConfig, just like XmlFile, depend on the XML file already existing when the 
action runs. The syntax between the two actions is slightly different, and the 
capabilities are slightly different, but I'm not sure what you are referring to 
when you say do I need to delete the file first or can I use a create action 
directly.

If the element you want to modify already exists, you can simply change the 
element by creating its value (or the value of its attribute, depending on 
what you are trying to do). I'm assuming that you were asking about the 
perceived need to delete the value/element/attribute first (instead of file?).

-Original Message-
From: Chris Jokinen [mailto:chr...@directron.us] 
Sent: Thursday, October 15, 2009 7:58 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] failed install, error is Failed to open XML file

Ok, I found this old posting on the same issue I am having. 
http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg22390.html
It would look like I need to switch from XmlFile to XmlConfig to do what I need 
to do. I see the example that Brian posted was

util:XmlConfig Id=AddElementText
File=[SOMEEXISTINGFILE]
Action=create
ElementPath=/someElement
Node=value
Value=NEW TEXT
On=install
Sequence=1 /

My question is do I need to delete the file first or can I use a create action 
directly?

-Original Message-
From: Chris Jokinen [mailto:chr...@directron.us] 
Sent: Wednesday, October 14, 2009 5:15 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: [WiX-users] failed install, error is Failed to open XML file

This extract is from my msi log file.

 

MSI (s) (6C:D8) [16:49:36:281]: Executing op: 
CustomActionSchedule(Action=ExecXmlFile,ActionType=3073,Source=BinaryData,Target=ExecXmlFile,CustomActionData=1€0€\RollCall.exe.config€3€0€/configuration/applicationSettings/RollCall.Properties.Settings/setti...@key='project']/value/€value€test)

MSI (s) (6C:B8) [16:49:36:281]: Invoking remote custom action. DLL: 

[WiX-users] Any way to control the # of service start attempts on ServiceControl?

2009-10-15 Thread Dave Kolb
Is there any way to control the # of service start attempts on
ServiceControl or elsewhere in the .msi file? MSI seems to try 7 times to
start my service before declaring an install failure. The service is not
starting due to no fault of wix or MSI and so I am not asking about that. I
just want to try to start the service once not 7 times before declaring a
failure. Thanks, Dave

--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] votive2008 help

2009-10-15 Thread Corey Partridge
Hi, I am trying to compile this project on my local VS2008 but I keep
getting the following errors:

 

Error  1  The Language parameter is not supported by
the VsTemplatePaths task. Verify the parameter exists on the task, and
it is a settable public instance property.  votive2008

Error  2  The VsTemplatePaths task could not be
initialized with its input parameters.   votive2008

 

Can anyone shed some light on this?

I assume it has something to do with votive.common.targets, but not
sure.

 

I am trying to recompile the entire project on my machine.

 

Corey

 

 

Corey Partridge

Senior Software Engineer

Skipjack Financial Services

The Payment Solutions Experts

480 Parkland Drive - Suite 201

Halifax, Nova Scotia B3S 1P9

t: 902.431.9977 ext 3208   

f: 902.484.6370

 




Notice of Confidentiality: 

The information transmitted is intended only for the person or entity to which 
it is addressed and may contain confidential and/or privileged material. Any 
review, re-transmission, dissemination or other use of, or taking of any action 
in reliance upon, this information by persons or entities other than the 
intended recipient is prohibited. If you received this in error, please contact 
the sender immediately by return electronic transmission and then immediately 
delete this transmission, including all attachments, without copying, 
distributing or disclosing same.

--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] failed install, error is Failed to open XML file

2009-10-15 Thread Chris Jokinen
I'm at a loss...

I have this currently

Component Id=RollCall.exe.config Guid=3b367d78-64a2-4eb5-bf8d-3aa5ada56735
File Id=RollCallexeconfig Source=C:\Documents and 
Settings\chrisj\My Documents\Visual Studio 2005\Projects\Roll Call\Roll 
Call\bin\Release\RollCall.exe.config DiskId=1 KeyPath=yes /
util:XmlConfig Id=ChangeProject
File=[#RollCallexeconfig]
Action=create
On=install

ElementPath=/configuration/applicationSettings/RollCall.Properties.Settings/setting[...@key='project'[\]]/value
Value=[PROJECT]
Sequence=1 /
  /Component

And it will install, but it does not update the file with the passed value (as 
listed earlier). If I add the Node attribute to the above code with a value of 
value the install fails with the wow64 error in the log. If I set node to 
element it will install the files with a can not locate element error.

I do see in the log that the command line argument is seen.

Ideas?

-Original Message-
From: Blair [mailto:os...@live.com] 
Sent: Thursday, October 15, 2009 11:56 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] failed install, error is Failed to open XML file

Just an aside:

For the File attribute of the util:XmlConfig element, instead of 
[INSTALLLOCATION]\RollCall.exe.config you could use [#RollCallexeconfig]. 
That would protect you against changes in the directory name and even 
filename of the file you are updating, especially since you are always altering 
that file every time you replace it and at no other time (so 
[#RollCallexeconfig] will always be defined when you need it), as a consequence 
of keeping the XmlConfig tag inside the same component that writes the config 
file.

One rule to make code more maintainable is to reduce the repetition of the same 
information over and over again. One way to do that is to reference code 
instead of recreating it all the time.

-Original Message-
From: Chris Jokinen [mailto:chr...@directron.us] 
Sent: Thursday, October 15, 2009 9:37 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] failed install, error is Failed to open XML file

The installer copies two files; an exe and a config (the xml file) into the 
same directory (finally got that to work!). The next thing I need to do is 
update the xml config file with the 3 command line parameters being supplied 
during a silent install. Currently I am just testing 1 parameter with a command 
line like this...

Msiexec /i setup.msi /qn /l*v c:\install.log PROJECT=test

The goal here is to update the programs xml based config file 
(RollCall.exe.config) with the value of the parameter PROJECT

I changed my wix file to use...
Component Id=RollCall.exe.config Guid=3b367d78-64a2-4eb5-bf8d-3aa5ada56735

File Id=RollCallexeconfig Source=C:\Documents and Settings\chrisj\My 
Documents\Visual Studio 2005\Projects\Roll Call\Roll 
Call\bin\Release\RollCall.exe.config DiskId=1 KeyPath=yes /

util:XmlConfig Id=AddProjectText
File=[INSTALLLOCATION]\RollCall.exe.config

ElementPath=/configuration/applicationSettings/RollCall.Properties.Settings/setting[...@key='project'[\]]/value
Value=[PROJECT]
On=install
Sequence=1 /
/Component

My original concern is that since my file already had a tag with a name of 
project and that I would need to delete it and then recreate it. I came to this 
conclusion do to the XmlFile action having only; create and delete 
actions...and nothing like an update action. 

From reading your response I see I am missing the usage of create as you have 
stated below. I will change my XmlConfig to include the action create and 
test again.

I feel I am getting close... =)

-- Chris

-Original Message-
From: Blair [mailto:os...@live.com] 
Sent: Thursday, October 15, 2009 11:14 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] failed install, error is Failed to open XML file

XmlConfig, just like XmlFile, depend on the XML file already existing when the 
action runs. The syntax between the two actions is slightly different, and the 
capabilities are slightly different, but I'm not sure what you are referring to 
when you say do I need to delete the file first or can I use a create action 
directly.

If the element you want to modify already exists, you can simply change the 
element by creating its value (or the value of its attribute, depending on 
what you are trying to do). I'm assuming that you were asking about the 
perceived need to delete the value/element/attribute first (instead of file?).

-Original Message-
From: Chris Jokinen [mailto:chr...@directron.us] 
Sent: Thursday, October 15, 2009 7:58 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] failed install, error is Failed to open XML file

Re: [WiX-users] failed install, error is Failed to open XML file

2009-10-15 Thread Chris Jokinen
Got it


I can't believe I have been chasing my tail this whole time I had
ElementPath=/configuration/applicationSettings/RollCall.Properties.Settings/setting[...@key='project'[\]]/value

And it needed to be
ElementPath=/configuration/applicationSettings/RollCall.Properties.Settings/setting[...@name='project'[\]]/value


Bah!


Well thanks for the helpnow on to the next step!

Chris

-Original Message-
From: Chris Jokinen [mailto:chr...@directron.us] 
Sent: Thursday, October 15, 2009 2:48 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] failed install, error is Failed to open XML file

I'm at a loss...

I have this currently

Component Id=RollCall.exe.config Guid=3b367d78-64a2-4eb5-bf8d-3aa5ada56735
File Id=RollCallexeconfig Source=C:\Documents and 
Settings\chrisj\My Documents\Visual Studio 2005\Projects\Roll Call\Roll 
Call\bin\Release\RollCall.exe.config DiskId=1 KeyPath=yes /
util:XmlConfig Id=ChangeProject
File=[#RollCallexeconfig]
Action=create
On=install

ElementPath=/configuration/applicationSettings/RollCall.Properties.Settings/setting[...@key='project'[\]]/value
Value=[PROJECT]
Sequence=1 /
  /Component

And it will install, but it does not update the file with the passed value (as 
listed earlier). If I add the Node attribute to the above code with a value of 
value the install fails with the wow64 error in the log. If I set node to 
element it will install the files with a can not locate element error.

I do see in the log that the command line argument is seen.

Ideas?

-Original Message-
From: Blair [mailto:os...@live.com] 
Sent: Thursday, October 15, 2009 11:56 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] failed install, error is Failed to open XML file

Just an aside:

For the File attribute of the util:XmlConfig element, instead of 
[INSTALLLOCATION]\RollCall.exe.config you could use [#RollCallexeconfig]. 
That would protect you against changes in the directory name and even 
filename of the file you are updating, especially since you are always altering 
that file every time you replace it and at no other time (so 
[#RollCallexeconfig] will always be defined when you need it), as a consequence 
of keeping the XmlConfig tag inside the same component that writes the config 
file.

One rule to make code more maintainable is to reduce the repetition of the same 
information over and over again. One way to do that is to reference code 
instead of recreating it all the time.

-Original Message-
From: Chris Jokinen [mailto:chr...@directron.us] 
Sent: Thursday, October 15, 2009 9:37 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] failed install, error is Failed to open XML file

The installer copies two files; an exe and a config (the xml file) into the 
same directory (finally got that to work!). The next thing I need to do is 
update the xml config file with the 3 command line parameters being supplied 
during a silent install. Currently I am just testing 1 parameter with a command 
line like this...

Msiexec /i setup.msi /qn /l*v c:\install.log PROJECT=test

The goal here is to update the programs xml based config file 
(RollCall.exe.config) with the value of the parameter PROJECT

I changed my wix file to use...
Component Id=RollCall.exe.config Guid=3b367d78-64a2-4eb5-bf8d-3aa5ada56735

File Id=RollCallexeconfig Source=C:\Documents and Settings\chrisj\My 
Documents\Visual Studio 2005\Projects\Roll Call\Roll 
Call\bin\Release\RollCall.exe.config DiskId=1 KeyPath=yes /

util:XmlConfig Id=AddProjectText
File=[INSTALLLOCATION]\RollCall.exe.config

ElementPath=/configuration/applicationSettings/RollCall.Properties.Settings/setting[...@key='project'[\]]/value
Value=[PROJECT]
On=install
Sequence=1 /
/Component

My original concern is that since my file already had a tag with a name of 
project and that I would need to delete it and then recreate it. I came to this 
conclusion do to the XmlFile action having only; create and delete 
actions...and nothing like an update action. 

From reading your response I see I am missing the usage of create as you have 
stated below. I will change my XmlConfig to include the action create and 
test again.

I feel I am getting close... =)

-- Chris

-Original Message-
From: Blair [mailto:os...@live.com] 
Sent: Thursday, October 15, 2009 11:14 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] failed install, error is Failed to open XML file

XmlConfig, just like XmlFile, depend on the XML file already existing when the 
action runs. The syntax between the two actions is slightly different, and the 
capabilities are slightly different, but I'm not sure what you are referring to 

[WiX-users] When to change Product/@Id (ProductCode)? - two editions of the same product.

2009-10-15 Thread Sascha Beaumont
Hi All,

This isn't so much a WiX specific question, but more of a Windows
Installer one... however those on the list seem to have a pretty good
understanding of all the rules we should be following so I'm hoping
someone can point me in the right direction.

Currently for our main product I'm using two Product/@Id with each
release - one for x86 and one for x64. However I'm using the *same*
Product/@Id and Upgrade/@Id for the 6 different languages we ship.

Question 1 - Looking at ProductCode Property [
http://msdn.microsoft.com/en-us/library/aa370854(VS.85).aspx ] I see a
requirement that the ProductCode must differ for different versions,
and languages. I'm just wondering why a different code for a different
language if I don't permit them to be installed side-by-side? The
packages are identical, we are just using Lingobit Localizer to
replace the resources in a pre-WiX build step and using a different
.wxl for the WiX build.

Question 2 - Looking at Changing the Product Code [
http://msdn.microsoft.com/en-us/library/aa367850(VS.85).aspx ] I see
that adding new features is permitted without changing the product
code. However as the feature is only requested by a small portion of
our customer base... we're wanting to ship two versions of the same
MSI, one with the additional feature (which almost doubles the
download size) and one without. Should I be changing the product code
here or not?

Effectively in Question 2 my aim is to distribute two editions of the
same product, prevent them being installed simultaneously, and permit
the user to upgrade from the Standard to the Enterprise release.
We always release major upgrades and so separating things into two
distinct product lines is a feasible one - I'm just trying to figure
out if I do so (different product codes, upgrade codes, etc) can I
prevent the user from installing one over the other just by using the
upgrade table? Or will I need some complicated CA's?

Sascha

--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] When to change Product/@Id (ProductCode)? - two editions of the same product.

2009-10-15 Thread Dave Kolb
I understand Product/@Id is an XPath fragment but where is such syntax
used in conjunction with wix? I could find no such usage in any wix or
project files that I am using. Just trying to understand what you are
talking about. Thanks, Dave

snip

Currently for our main product I'm using two Product/@Id with each
release - one for x86 and one for x64. However I'm using the *same*
Product/@Id and Upgrade/@Id for the 6 different languages we ship.

snip


--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] When to change Product/@Id (ProductCode)? - two editions of the same product.

2009-10-15 Thread Sascha Beaumont
Hi Dave,

http://wix.sourceforge.net/manual-wix3/wix_xsd_product.htm

The Id attribute of the Product element... It's the third line in
every single one of my WiX projects :)

?xml version=1.0 encoding=utf-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
  Product Id=$(var.Property_ProductCode) 


Sascha

On Fri, Oct 16, 2009 at 2:38 PM, Dave Kolb d...@dotnetcodeslingers.com wrote:
 I understand Product/@Id is an XPath fragment but where is such syntax
 used in conjunction with wix? I could find no such usage in any wix or
 project files that I am using. Just trying to understand what you are
 talking about. Thanks, Dave

 snip

 Currently for our main product I'm using two Product/@Id with each
 release - one for x86 and one for x64. However I'm using the *same*
 Product/@Id and Upgrade/@Id for the 6 different languages we ship.

 snip


 --
 Come build with us! The BlackBerry(R) Developer Conference in SF, CA
 is the only developer event you need to attend this year. Jumpstart your
 developing skills, take BlackBerry mobile applications to market and stay
 ahead of the curve. Join us from November 9 - 12, 2009. Register now!
 http://p.sf.net/sfu/devconference
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] When to change Product/@Id (ProductCode)? - two editions of the same product.

2009-10-15 Thread Dave Kolb
Hi Sascha, I also do that same exact thing since I use the same .wxs file
for x64 and x86 and define unique product codes for each but was wondering
where exactly you were using/seeing that xpath syntax fragment of
Product/@Id which is different than the 3rd line of what you just listed
which is the syntax I would expect in an .xls file. - Dave

-Original Message-
From: Sascha Beaumont [mailto:sascha.beaum...@gmail.com] 
Sent: Thursday, October 15, 2009 11:56 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] When to change Product/@Id (ProductCode)? - two
editions of the same product.

Hi Dave,

http://wix.sourceforge.net/manual-wix3/wix_xsd_product.htm

The Id attribute of the Product element... It's the third line in
every single one of my WiX projects :)

?xml version=1.0 encoding=utf-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
  Product Id=$(var.Property_ProductCode) 


Sascha

On Fri, Oct 16, 2009 at 2:38 PM, Dave Kolb d...@dotnetcodeslingers.com
wrote:
 I understand Product/@Id is an XPath fragment but where is such syntax
 used in conjunction with wix? I could find no such usage in any wix or
 project files that I am using. Just trying to understand what you are
 talking about. Thanks, Dave

 snip

 Currently for our main product I'm using two Product/@Id with each
 release - one for x86 and one for x64. However I'm using the *same*
 Product/@Id and Upgrade/@Id for the 6 different languages we ship.

 snip




--
 Come build with us! The BlackBerry(R) Developer Conference in SF, CA
 is the only developer event you need to attend this year. Jumpstart your
 developing skills, take BlackBerry mobile applications to market and stay
 ahead of the curve. Join us from November 9 - 12, 2009. Register now!
 http://p.sf.net/sfu/devconference
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users



--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] When to change Product/@Id (ProductCode)? - two editions of the same product.

2009-10-15 Thread Sascha Beaumont
Hi Dave,

I'm not using the fragment *in* my WiX sources, I'm using it for
clarification in referring *to* my WiX sources... does that make
sense?

Sascha


On Fri, Oct 16, 2009 at 3:17 PM, Dave Kolb d...@dotnetcodeslingers.com wrote:
 Hi Sascha, I also do that same exact thing since I use the same .wxs file
 for x64 and x86 and define unique product codes for each but was wondering
 where exactly you were using/seeing that xpath syntax fragment of
 Product/@Id which is different than the 3rd line of what you just listed
 which is the syntax I would expect in an .xls file. - Dave

 -Original Message-
 From: Sascha Beaumont [mailto:sascha.beaum...@gmail.com]
 Sent: Thursday, October 15, 2009 11:56 PM
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] When to change Product/@Id (ProductCode)? - two
 editions of the same product.

 Hi Dave,

 http://wix.sourceforge.net/manual-wix3/wix_xsd_product.htm

 The Id attribute of the Product element... It's the third line in
 every single one of my WiX projects :)

 ?xml version=1.0 encoding=utf-8?
 Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
  Product Id=$(var.Property_ProductCode) 


 Sascha

 On Fri, Oct 16, 2009 at 2:38 PM, Dave Kolb d...@dotnetcodeslingers.com
 wrote:
 I understand Product/@Id is an XPath fragment but where is such syntax
 used in conjunction with wix? I could find no such usage in any wix or
 project files that I am using. Just trying to understand what you are
 talking about. Thanks, Dave

 snip

 Currently for our main product I'm using two Product/@Id with each
 release - one for x86 and one for x64. However I'm using the *same*
 Product/@Id and Upgrade/@Id for the 6 different languages we ship.

 snip



 
 --
 Come build with us! The BlackBerry(R) Developer Conference in SF, CA
 is the only developer event you need to attend this year. Jumpstart your
 developing skills, take BlackBerry mobile applications to market and stay
 ahead of the curve. Join us from November 9 - 12, 2009. Register now!
 http://p.sf.net/sfu/devconference
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


 
 --
 Come build with us! The BlackBerry(R) Developer Conference in SF, CA
 is the only developer event you need to attend this year. Jumpstart your
 developing skills, take BlackBerry mobile applications to market and stay
 ahead of the curve. Join us from November 9 - 12, 2009. Register now!
 http://p.sf.net/sfu/devconference
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


 --
 Come build with us! The BlackBerry(R) Developer Conference in SF, CA
 is the only developer event you need to attend this year. Jumpstart your
 developing skills, take BlackBerry mobile applications to market and stay
 ahead of the curve. Join us from November 9 - 12, 2009. Register now!
 http://p.sf.net/sfu/devconference
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] When to change Product/@Id (ProductCode)? - two editions of the same product.

2009-10-15 Thread Dave Kolb
Yes thanks! I had seen a couple such references before and did not realize
you all were talking like an xpath compiler J Kind of like talking like a
pirate. Arrgh! Sorry I can't help with your actual question.Dave

 

-Original Message-
From: Sascha Beaumont [mailto:sascha.beaum...@gmail.com] 
Sent: Friday, October 16, 2009 12:55 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] When to change Product/@Id (ProductCode)? - two
editions of the same product.

 

Hi Dave,

 

I'm not using the fragment *in* my WiX sources, I'm using it for

clarification in referring *to* my WiX sources... does that make

sense?

 

Sascha

--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Web setup using .msm

2009-10-15 Thread cad
Hi Blair,

I did a smoke test (using smoke.exe) on the .msm(containing custom actions)
I got this result.

It results into following error.


error SMOK0204 : ICE03: Table: Error Column: Error Missing specifications in
_Validation Table (or Old Database)
error SMOK0204 : ICE03: Table: Error Column: Message Missing specifications
in _Validation Table (or Old Database)

and resulting .msm (without custom actions)

passes this test.

Can you help me how can i fix this issue in .msm or any pointers how to
locate the problem.
I am the one who is creating the .msm using VS Merge Module and want to use
the same in web based wix set up.

Thanks for reply.


On Thu, Oct 15, 2009 at 7:38 PM, Blair os...@live.com wrote:

 Who wrote the MSM? Ask them to fix the failing custom action, or at least
 determine why the custom action is failing, or how to determine why the
 custom action is failing.

 If the custom action that is failing is attempting self-registration, this
 would be a good opportunity to get rid of that MSM and have what it was
 doing changed to not use self-registration.

 -Original Message-
 From: cad [mailto:ankit.9...@gmail.com]
 Sent: Wednesday, October 14, 2009 10:14 PM
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Web setup using .msm

 Hi Blair,

 How do i do this checking in the referred .msm.?

 Thanks,



 On Wed, Oct 14, 2009 at 8:58 PM, Blair os...@live.com wrote:

  It appears to be a failure in an action coming from your
  HealthCheckMergeModule.msm. You will need to check with the author of
 that
  MSM in order to diagnose that failure.
 
  -Original Message-
  From: Asterisk [mailto:ankit.9...@gmail.com]
  Sent: Wednesday, October 14, 2009 12:02 AM
  To: wix-users@lists.sourceforge.net
   Subject: Re: [WiX-users] Web setup using .msm
 
 
 
 
  Blair-2 wrote:
  
   Not sure, but InstallUtil* is Self-Reg (aka evil). Visual Studio's
 setup
   projects do several things that make deployment easier that
 invariably
   cause headaches later on when you have to service/maintain those setups
   (including broken upgrades, orphaned resources, failed removals, etc.).
  
   -Original Message-
   From: Asterisk [mailto:ankit.9...@gmail.com]
   Sent: Tuesday, October 13, 2009 4:26 AM
   To: wix-users@lists.sourceforge.net
   Subject: [WiX-users] Web setup using .msm
  
  
   Hi ,
  
   Please guide me to create a web setup (.msi).
   I have a .msm file created in visual studio merge module which
 basically
   does all the work.
   1.It creates a virtual directory and deploys the web application.
   2.It creates various performance counters and installs it.
   I want to refer it into a wix based setup(.msi refering to
 existing.msm)
  
   I have created a a web setup by refering to this existing .msm in VS
 2008
   and it works perfect.
   Can anyone help me to create same web setup by refering to the same
 .msm
   created in vs 2008 as merge module.
  
   When i refer it and create .msi , and run it gives me error Error
 1001.
   InstallUtilLib dll: Unknown error while installing the web
 application.
  
   When i remove my custom actions as part of .msm and refer the same in
 wix
   web setup. it works fine.
   Can anyone help me put to put these custom actions as a part of .msm?
   Or i have to include these custom actions as a part of wix web setup?
  
  
  
  
   Thanks in advance:)
   --
   View this message in context:
   http://n2.nabble.com/Web-setup-using-msm-tp3815520p3815520.html
   Sent from the wix-users mailing list archive at Nabble.com.
  
  
 
 
   --
   Come build with us! The BlackBerry(R) Developer Conference in SF, CA
   is the only developer event you need to attend this year. Jumpstart
 your
   developing skills, take BlackBerry mobile applications to market and
 stay
   ahead of the curve. Join us from November 9 - 12, 2009. Register now!
   http://p.sf.net/sfu/devconference
   ___
   WiX-users mailing list
   WiX-users@lists.sourceforge.net
   https://lists.sourceforge.net/lists/listinfo/wix-users
  
  
  
 
 --
   Come build with us! The BlackBerry(R) Developer Conference in SF, CA
   is the only developer event you need to attend this year. Jumpstart
 your
   developing skills, take BlackBerry mobile applications to market and
 stay
   ahead of the curve. Join us from November 9 - 12, 2009. Register now!
   http://p.sf.net/sfu/devconference
   ___
   WiX-users mailing list
   WiX-users@lists.sourceforge.net
   https://lists.sourceforge.net/lists/listinfo/wix-users
  
  
 
  In log file i could find that the install sequence is gicing me problem..
 
  
 
  MSI (s) (94:50) [11:20:08:552]: Executing op:
  InstallProtectedFiles(AllowUI=1)
  MSI (s) (94:50) [11:20:08:552]: