date:20080123

[WiX-users] Uninstall fails on IIS

2008-01-23 Thread Dror Cohen

Hi,

I have a package that installs several IIS 6 websites. When I install the 
package everything runs OK. The uninstall fails on the ConfigureIIS action. 
This happens for any new site I add to the package, while the websites that 
were already there from previous versions works fine.

I'm using global CoreXT for the build so it uses version v2.0.5508.0 of WiX.

What can be done to solve this problem?

Here is a log of the ConfigureIIS action on uninstall:

MSI (s) (CC:1C) [17:40:29:055]: Doing action: ConfigureIIs
Action ended 17:40:28: InstallCertificates. Return value 1.
MSI (s) (CC:58) [17:40:29:165]: Invoking remote custom action. DLL: 
C:\WINDOWS\Installer\MSI1B.tmp, Entrypoint: ConfigureIIs
MSI (s) (CC!5C) [17:40:29:455]: PROPERTY CHANGE: Adding 
StartMetabaseTransaction property. Its value is 'ScaConfigureIIs'.
Action start 17:40:29: ConfigureIIs.
MSI (s) (CC!5C) [17:40:29:526]: Doing action: StartMetabaseTransaction
Action start 17:40:29: StartMetabaseTransaction.
MSI (s) (CC!5C) [17:40:29:596]: PROPERTY CHANGE: Adding 
RollbackMetabaseTransaction property. Its value is 'ScaConfigureIIs'.
MSI (s) (CC!5C) [17:40:29:596]: Doing action: RollbackMetabaseTransaction
Action ended 17:40:29: StartMetabaseTransaction. Return value 1.
Action start 17:40:29: RollbackMetabaseTransaction.
MSI (s) (CC!5C) [17:40:29:706]: PROPERTY CHANGE: Adding 
CommitMetabaseTransaction property. Its value is 'ScaConfigureIIs'.
MSI (s) (CC!5C) [17:40:29:706]: Doing action: CommitMetabaseTransaction
Action ended 17:40:29: RollbackMetabaseTransaction. Return value 1.
Action start 17:40:29: CommitMetabaseTransaction.
MSI (s) (CC:58) [17:40:29:906]: Leaked MSIHANDLE (219) of type 790531 for 
thread 3676
MSI (s) (CC:58) [17:40:29:906]: Leaked MSIHANDLE (190) of type 790540 for 
thread 3676
MSI (s) (CC:58) [17:40:29:906]: Leaked MSIHANDLE (189) of type 790540 for 
thread 3676
MSI (s) (CC:58) [17:40:29:906]: Leaked MSIHANDLE (188) of type 790540 for 
thread 3676
MSI (s) (CC:58) [17:40:29:906]: Leaked MSIHANDLE (179) of type 790541 for 
thread 3676
MSI (s) (CC:58) [17:40:29:906]: Note: 1: 2769 2: ConfigureIIs 3: 5
Action ended 17:40:29: CommitMetabaseTransaction. Return value 1.
DEBUG: Error 2769:  Custom Action ConfigureIIs did not close 5 MSIHANDLEs.
The installer has encountered an unexpected error installing this package. This 
may indicate a problem with this package. The error code is 2769. The arguments 
are: ConfigureIIs, 5,
MSI (s) (CC:1C) [17:40:30:057]: Machine policy value 'DisableRollback' is 0
MSI (s) (CC:1C) [17:40:30:057]: Note: 1: 1402 2: 
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts
 3: 2
Action ended 17:40:30: ConfigureIIs. Return value 3.
MSI (s) (CC:1C) [17:40:30:127]: Note: 1: 1402 2: 
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts
 3: 2
MSI (s) (CC:1C) [17:40:30:167]: No System Restore sequence number for this 
installation.
MSI (s) (CC:1C) [17:40:30:167]: Unlocking Server
Action ended 17:40:30: INSTALL. Return value 3.

Thanks,
Dror.

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Strange error regarding IIsWebs table

2008-01-23 Thread Tobias Holm

Hi all,

 

I use WiX to create a website with a MSI-installer.

I run into some problems when deploying it on windows server 2008.

 

There are 3 scenarios:

 

1.   I logon as the Administrator user of the local machine. I click
on the MSI-file.  à Everything installs ok.

2.   I logon as another user called MyAdmin which is a member of the
administrators group.  I click on the file to install. I Get prompted to say
if I trust the application. I click yes. à The installation halts with the
error Failed to Read IIsWebs Table.

3.   I use the MyAdmin account but launch the installation from an
elevated command prompt.  à Everything works ok.

 

I have marked my packages with: InstallPrivileges='elevated

 

I do not use any CustomActions of my own. When I dark my output msi most of
the CA´s created by wix are marked with Execute="deferred" Impersonate="no"

 

What am I missing here?

 

/Tobias

 

 

 

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Trouble with Light in Visual Studio 2008 and Team Build 2008

2008-01-23 Thread Arild Bakken

Hi everyone,

I'm having trouble with Light.exe. I installed the January 11 build (3.0.3711) 
and things work very well except that I can only build the Setup project once 
for every time I start Visual Studio. When I build the first time after I start 
Visual Studio 2008, everything is OK, but all builds after that fail with 
"Light.exe exited with code 1".  If I restart Visual Studio I can build once 
again. I can live with that, cause all I have to do is copy the light.exe 
commandline that Visual Studio shows in the output into a commandprompt and it 
works.

The problem though is that this also happens with Team Build (TFS) when I build 
both release and debug versions of the product. The first (usually Release) 
builds fine, but the second fails. When running Team Build I get additional 
error information (which I don't see when running in Visual Studio):

light.exe : error LGHT0001 : Item has already been added. Key in dictionary: 
'InstallUISequence/PrepareDlg'  Key being added: 'InstallUISequence/PrepareDlg'
Exception Type: System.ArgumentException
Stack Trace:
   at System.Collections.SortedList.Add(Object key, Object value)
   at 
Microsoft.Tools.WindowsInstallerXml.WixActionRowCollection.Add(WixActionRow 
actionRow, Boolean overwrite)
   at Microsoft.Tools.WindowsInstallerXml.Linker.SequenceActions(RowCollection 
actionRows, RowCollection suppressActionRows)
   at Microsoft.Tools.WindowsInstallerXml.Linker.Link(SectionCollection 
sections, ArrayList transforms)
   at Microsoft.Tools.WindowsInstallerXml.Tools.Light.Run(String[] args)
Binder temporary directory located at 'C:\Documents and 
Settings\_tfsservice\Local Settings\Temp\nnj-8nas'.
Validator temporary directory located at 'C:\Documents and 
Settings\_tfsservice\Local Settings\Temp\3b6mv9ua'.

So, it looks like some stuff is "stuck" in memory between builds. It seems that 
Visual Studio 2008 / TFS Build 2008 does not actually spawn a separate process 
for light.exe, but seems to load the assembly into an appdomain - so any static 
stuff would survive successive builds (this is guesswork, but I never see a 
light.exe process during builds so I'm guessing VS loads the assembly and runs 
stuff).

As a test I removed all UI stuff from the wix project (since the error relates 
to InstallUISequence), and now I can build without problems, but of course I 
would like some UI for the installer J

Has anyone else run into this problem? Is there a know fix?


Regards,

Arild
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Visual Studio running detection

2008-01-23 Thread Adrian Alonso

Thanks Bob, but I'm using WIX V2. Do you know if there is a similar CA in V2
too?

Adrian

On Jan 23, 2008 4:25 AM, Bob Arnson <[EMAIL PROTECTED]> wrote:

> Adrian Alonso wrote:
> > Hi! I need to detect if Visual Studio is running to avoid some Custom
> > Actions fail.
> > Do you know if MSI/WIX allows me to detect if a proc is running or,
> > better yet, if it provides some support for detecting if Visual Studio
> > is running specifically?
>
> The CloseApplication custom action does that: See
> http://www.nabble.com/How-to-use-CloseApps-custom-action-td14095635.html.
>
> --
> sig://boB
> http://joyofsetup.com/
>
>
>
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] A Token of My Love

2008-01-23 Thread 509_philip.gray3

The Dance of Love http://24.0.124.105/


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Get rid of distracting 'run from the network' installation in the root feature

2008-01-23 Thread Christopher Painter

Right, I'm familiar with MenuLocal and MenuAllLocal.   The problem is consider 
this feature tree

  A (root) 
  B Parent A

  MenuLocal and MenuAllLocal is displayed by my selection tree for both 
features.  The annoyance is that B doesn't have any child features so I don't 
know why ( or how to stop ) the control from displaying the ManuAllLocal 
string.The string is correct however in the context of feature A.

  Is this just one of those MSI annoyances?

Bob Arnson <[EMAIL PROTECTED]> wrote:
  Christopher Painter wrote:
> Do you have similar trivia for how to get rid of the annoying `this 
> feature, and all subfeatures, will be installed on local hard drive.` 
> when said feature doesn't have any subfeatures?

That's your choice in localizing UIText strings.

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

-
Looking for last minute shopping deals?  Find them fast with Yahoo! Search.-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Return codes for candle & light

2008-01-23 Thread Nigel . Rochford

Just wondering if anybody knows of a reference somewhere on return codes 
of Wix tools.

Nigel Rochford
Software Development
APC-MGE
Galway

Tel. +353 91 702199-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Custom actions working fine in xp - failing in Vista

2008-01-23 Thread SaiTeja


Hi,

I have created a WIX installer that works perfectly on XP.

But When I try in Vista Business, my custom actions are failing

Below is the custom action





Not
Installed 



I tried with Impersonate="yes" and Impersonate="no". Still it is failing

Any ideas of what might be this issue would be greatly appreciated. 


I want my installer should work on xp,vista,windows server2003 per machine.


please suggest solution for general cases like admin check, registry, COM
objects etc also.

-- 
View this message in context: 
http://www.nabble.com/Custom-actions-working-fine-in-xp---failing-in-Vista-tp15041566p15041566.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Custom actions working fine in xp - failing in Vista

2008-01-23 Thread Johan Appelgren

On Jan 23, 2008 2:20 PM, SaiTeja <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I have created a WIX installer that works perfectly on XP.
>
> But When I try in Vista Business, my custom actions are failing
>
> Below is the custom action
>
>  ExeCommand="UninstallLogonHandler" FileKey="xyz.exe">
> 
>
> 
> Not
> Installed
> 
>
>
> I tried with Impersonate="yes" and Impersonate="no". Still it is failing
>
> Any ideas of what might be this issue would be greatly appreciated.
>
>
> I want my installer should work on xp,vista,windows server2003 per machine.
>
>
> please suggest solution for general cases like admin check, registry, COM
> objects etc also.

What does a log of a failed install say? msiexec /i your.msi /lv* install.log

What does xyz.exe do?

/Johan

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Custom actions working fine in xp - failing in Vista

2008-01-23 Thread SaiTeja

Hi 

Thanks for respones.

Log says:

Action 18:50:25: UninstallLogonHandler. 
Error 1721. There is a problem with this Windows Installer package. A
program required for this install to complete could not be run. Contact your
support personnel or package vendor. Action: UninstallLogonHandler,
location: C:\program files\Client\xyz.exe, command: UninstallLogonHandler 
DEBUG: Error 2888:  Executing the TextStyle view failed
The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2888. The
arguments are: TextStyle, , 

The same custom action( UninstallLogonHandler and File Key: XYZ.exe) is
working fine with XP

Thanks

Johan Appelgren wrote:
> 
> On Jan 23, 2008 2:20 PM, SaiTeja <[EMAIL PROTECTED]> wrote:
>>
>> Hi,
>>
>> I have created a WIX installer that works perfectly on XP.
>>
>> But When I try in Vista Business, my custom actions are failing
>>
>> Below is the custom action
>>
>> > Execute="deferred"
>> ExeCommand="UninstallLogonHandler" FileKey="xyz.exe">
>> 
>>
>> 
>> Not
>> Installed
>> 
>>
>>
>> I tried with Impersonate="yes" and Impersonate="no". Still it is failing
>>
>> Any ideas of what might be this issue would be greatly appreciated.
>>
>>
>> I want my installer should work on xp,vista,windows server2003 per
>> machine.
>>
>>
>> please suggest solution for general cases like admin check, registry, COM
>> objects etc also.
> 
> What does a log of a failed install say? msiexec /i your.msi /lv*
> install.log
> 
> What does xyz.exe do?
> 
> /Johan
> 
> -
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Custom-actions-working-fine-in-xp---failing-in-Vista-tp15041566p15041914.html
Sent from the wix-users mailing list archive at Nabble.com.

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Is there a directory property forCSIDL_COMMON_DOCUMENTS ?

2008-01-23 Thread Scott Palmer

Ah, WiX to the rescue.. thanks for that.

Now, it seems these are just standard properties.. so I don't use them like
Directory Ids, right?
The docs don't seem to have an example of using the WixQueryOsDirs
properties.

I.e. do I use:



or



Thanks,

Scott

On Jan 22, 2008 5:07 PM, Mike Dimmick <[EMAIL PROTECTED]> wrote:

>  If you link with the WixUtilExtension in WiX v3.0, you can use the
> WIX_DIR_COMMON_DOCUMENTS property. See the topic "OSInfo custom actions" in
> WiX.chm.
>
>
>
> --
>
> Mike Dimmick
>
>
>  --
>
> *From:* [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] *On Behalf Of *Scott Palmer
> *Sent:* 22 January 2008 21:32
> *To:* wix-users@lists.sourceforge.net
> *Subject:* [WiX-users] Is there a directory property
> forCSIDL_COMMON_DOCUMENTS ?
>
>
>
> I'm trying to make some changes to play nice on Vista...  Currently our
> product has several folders that it places under Program Files, e.g.:
>
> C:\Program Files\Company\Product\Data_A
>
> C:\Program Files\Company\Product\Data_B
>
> C:\Program Files\Company\Product\Data_C
>
>
>
> The purpose of these folders was to store documents that the user would
> load and possibly modify, as well as saving new doucments that they create..
> such that they are shared for all users of "Product"
>
> In some cases the files in these folders are made available via the
> application UI by choosing them from a combo box.  In other cases they are
> selected with a Open File dialog.
>
>
>
> Vista isn't happy about putting files under the Program Files folder
> though. (Which isn't going to serve the purpose MS thinks it will - but
> whatever.)
>
>
>
> So I was going to relocate all of the file to *CSIDL_COMMON_APPDATA*
> \Company\Product\Data*
>
> It seemed like the right place for the files - and I still think it is the
> right place for *some* of the files, but sadly *CSIDL_COMMON_APPDATA* is a
> hidden folder and so the open file dialogs aren't going to show it and the
> users won't be able to browse to there - if they happen to broswe out of the
> default folder.
>
>
>
> That lead me to think that the right place for some of those data folder
> was under the folder for CSIDL_COMMON_DOCUMENTS .. but I can't see a way to
> install any files there via MSI.
>
>
>
> The some of the data will be machine specifc, so I don't want it to
> "roam".  Most of the data will be shared amoung all users of the
> application, so I want to avoid having things end up in "My Documents".
>
>
>
> What are my options?  Have I overlooked the correct location?
>
>
>
> Thanks,
>
>
>
> Scott
>
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Is there a directory property forCSIDL_COMMON_DOCUMENTS ?

2008-01-23 Thread Scott Palmer

Err. of course I meant

 


On Jan 23, 2008 9:31 AM, Scott Palmer <[EMAIL PROTECTED]> wrote:

> Ah, WiX to the rescue.. thanks for that.
>
> Now, it seems these are just standard properties.. so I don't use them
> like Directory Ids, right?
> The docs don't seem to have an example of using the WixQueryOsDirs
> properties.
>
> I.e. do I use:
>
> 
>
> or
>
> 
>
> Thanks,
>
> Scott
>
>   On Jan 22, 2008 5:07 PM, Mike Dimmick <[EMAIL PROTECTED]> wrote:
>
> >  If you link with the WixUtilExtension in WiX v3.0, you can use the
> > WIX_DIR_COMMON_DOCUMENTS property. See the topic "OSInfo custom actions" in
> > WiX.chm.
> >
> >
> >
> > --
> >
> > Mike Dimmick
> >
> >
> >  --
> >
> > *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > ] *On Behalf Of *Scott Palmer
> > *Sent:* 22 January 2008 21:32
> > *To:* wix-users@lists.sourceforge.net
> > *Subject:* [WiX-users] Is there a directory property
> > forCSIDL_COMMON_DOCUMENTS ?
> >
> >
> >
> > I'm trying to make some changes to play nice on Vista...  Currently our
> > product has several folders that it places under Program Files, e.g.:
> >
> > C:\Program Files\Company\Product\Data_A
> >
> > C:\Program Files\Company\Product\Data_B
> >
> > C:\Program Files\Company\Product\Data_C
> >
> >
> >
> > The purpose of these folders was to store documents that the user would
> > load and possibly modify, as well as saving new doucments that they create..
> > such that they are shared for all users of "Product"
> >
> > In some cases the files in these folders are made available via the
> > application UI by choosing them from a combo box.  In other cases they are
> > selected with a Open File dialog.
> >
> >
> >
> > Vista isn't happy about putting files under the Program Files folder
> > though. (Which isn't going to serve the purpose MS thinks it will - but
> > whatever.)
> >
> >
> >
> > So I was going to relocate all of the file to *CSIDL_COMMON_APPDATA *
> > \Company\Product\Data*
> >
> > It seemed like the right place for the files - and I still think it is
> > the right place for *some* of the files, but sadly *CSIDL_COMMON_APPDATA
> > * is a hidden folder and so the open file dialogs aren't going to show
> > it and the users won't be able to browse to there - if they happen to broswe
> > out of the default folder.
> >
> >
> >
> > That lead me to think that the right place for some of those data folder
> > was under the folder for CSIDL_COMMON_DOCUMENTS .. but I can't see a way to
> > install any files there via MSI.
> >
> >
> >
> > The some of the data will be machine specifc, so I don't want it to
> > "roam".  Most of the data will be shared amoung all users of the
> > application, so I want to avoid having things end up in "My Documents".
> >
> >
> >
> > What are my options?  Have I overlooked the correct location?
> >
> >
> >
> > Thanks,
> >
> >
> >
> > Scott
> >
>
>
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Is there a directory property forCSIDL_COMMON_DOCUMENTS ?

2008-01-23 Thread Scott Palmer

Never mind.. got it all sorted.



it is.   I gather Directory Ids are properties of sorts and property
expansion in the directory name doesn't happen.

Sorry for the noise.

On Jan 23, 2008 9:35 AM, Scott Palmer <[EMAIL PROTECTED]> wrote:

> Err. of course I meant
>
>  
>
>
>   On Jan 23, 2008 9:31 AM, Scott Palmer <[EMAIL PROTECTED]> wrote:
>
> > Ah, WiX to the rescue.. thanks for that.
> >
> > Now, it seems these are just standard properties.. so I don't use them
> > like Directory Ids, right?
> > The docs don't seem to have an example of using the WixQueryOsDirs
> > properties.
> >
> > I.e. do I use:
> >
> > 
> >
> > or
> >
> > 
> >
> > Thanks,
> >
> > Scott
> >
> >   On Jan 22, 2008 5:07 PM, Mike Dimmick <[EMAIL PROTECTED]>
> > wrote:
> >
> > >  If you link with the WixUtilExtension in WiX v3.0, you can use the
> > > WIX_DIR_COMMON_DOCUMENTS property. See the topic "OSInfo custom actions" 
> > > in
> > > WiX.chm.
> > >
> > >
> > >
> > > --
> > >
> > > Mike Dimmick
> > >
> > >
> > >  --
> > >
> > > *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > > ] *On Behalf Of *Scott Palmer
> > > *Sent:* 22 January 2008 21:32
> > > *To:* wix-users@lists.sourceforge.net
> > > *Subject:* [WiX-users] Is there a directory property
> > > forCSIDL_COMMON_DOCUMENTS ?
> > >
> > >
> > >
> > > I'm trying to make some changes to play nice on Vista...  Currently
> > > our product has several folders that it places under Program Files,
> > > e.g.:
> > >
> > > C:\Program Files\Company\Product\Data_A
> > >
> > > C:\Program Files\Company\Product\Data_B
> > >
> > > C:\Program Files\Company\Product\Data_C
> > >
> > >
> > >
> > > The purpose of these folders was to store documents that the user
> > > would load and possibly modify, as well as saving new doucments that they
> > > create.. such that they are shared for all users of "Product"
> > >
> > > In some cases the files in these folders are made available via the
> > > application UI by choosing them from a combo box.  In other cases they are
> > > selected with a Open File dialog.
> > >
> > >
> > >
> > > Vista isn't happy about putting files under the Program Files folder
> > > though. (Which isn't going to serve the purpose MS thinks it will - but
> > > whatever.)
> > >
> > >
> > >
> > > So I was going to relocate all of the file to *CSIDL_COMMON_APPDATA *
> > > \Company\Product\Data*
> > >
> > > It seemed like the right place for the files - and I still think it is
> > > the right place for *some* of the files, but sadly *
> > > CSIDL_COMMON_APPDATA* is a hidden folder and so the open file dialogs
> > > aren't going to show it and the users won't be able to browse to there - 
> > > if
> > > they happen to broswe out of the default folder.
> > >
> > >
> > >
> > > That lead me to think that the right place for some of those data
> > > folder was under the folder for CSIDL_COMMON_DOCUMENTS .. but I can't see 
> > > a
> > > way to install any files there via MSI.
> > >
> > >
> > >
> > > The some of the data will be machine specifc, so I don't want it to
> > > "roam".  Most of the data will be shared amoung all users of the
> > > application, so I want to avoid having things end up in "My Documents".
> > >
> > >
> > >
> > > What are my options?  Have I overlooked the correct location?
> > >
> > >
> > >
> > > Thanks,
> > >
> > >
> > >
> > > Scott
> > >
> >
> >
>
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Custom actions working fine in xp - failing in Vista

2008-01-23 Thread Adam Majer

SaiTeja wrote:
> I have created a WIX installer that works perfectly on XP.
> 
> But When I try in Vista Business, my custom actions are failing
> 
> Below is the custom action
> 
>  ExeCommand="UninstallLogonHandler" FileKey="xyz.exe">
> 

Let me quess, the xyz.exe depends on the C runtime? And you are
installing the C runtime in the installer via merge module?

If yes, that is the problem. In Vista the runtime will NOT be accessible
to xyz.exe until *after* the installer completes installation. The only
way to correct this is to either link statically, or distribute the
runtime just as you would in the "copy method". Clearly, the preferred
way is to use the merge module and just statically link the custom action.

Pre-Vista OSes acted differently with respect to SxS DLLs hence your
action worked.

- Adam

-- 
Mail Etiquette
==
* Quote properly or not at all. Top posters, this applies to you!
* When replying to posts on mailing lists, only address the mailing list
  unless poster explicitly requested you include them in CC

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Conditional website locator

2008-01-23 Thread Richard Cannock

Hi.


i am writing a (my first) wix script that needs to conditional create a
virtual directory within an existing website.


I have currently defined the web service locator as:

 



  

  



 

Which i believe that will install a vdir called quote within a website
that's all IP unassigned, listening on port80.

 

However, this logical website exists with Different IP address, port
combos in our different development environments.

 

Is there an easy way to do this web service locator with a ?

 

Cheers

 

Rich


This e-mail is private and confidential and is protected by copyright. It may 
also be privileged or otherwise protected by other legal rules.  Access by or 
disclosure to anyone other than the intended recipient for any reason other 
than the business purpose for which the message is intended, is unauthorised. 
If you receive it in error, notify us, delete it and do not make use of or copy 
it.

Internet communications are not secure and therefore Assureweb Limited do not 
accept legal responsibility for the contents of this message. Any views or 
opinions presented are solely those of the author and do not necessarily 
represent those of Assureweb Limited unless otherwise specifically stated.-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Copy external files into destination folder

2008-01-23 Thread Richard Wilde

Hi

 

I have a folder called resellers that contains an unknown amount of files
that need to be copied to the destination directory/Templates from the msi
installer. 

 

Basically the reseller folder will contain a logo and X amount of templates.

 

MSI.EXE
  à FOLDER called Reseller

è Logo

è X amount of templates

 

I do not really want to create an installer for each reseller which has a
defined amount of files, rather create one installer which is flexible.

 

What is the best approach to do this? 

 

Many thanks

Richard

 

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Bootstrapper and MsiInstallProduct

2008-01-23 Thread Wilson, Phil

MsiEnableLog (~0, . ) doesn't work. Something like MsiEnableLog 
(INSTALLLOGMODE_VERBOSE,..) does.  What are you coding in? If C++, there 
are header files etc.

Phil Wilson

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Krause, Henning
Sent: Tuesday, January 22, 2008 11:36 PM
To: Paul McCloskey
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Bootstrapper and MsiInstallProduct

Hello,

I'm currently testing this by calling c:\winodows\system32\calc.exe...
to minimize side-effects.

And I wait for the other process to finish.

Kind regards,
Henning

> -Original Message-
> From: Paul McCloskey [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 22, 2008 10:41 PM
> To: Krause, Henning; Ben Greenberg
> Cc: wix-users@lists.sourceforge.net
> Subject: RE: [WiX-users] Bootstrapper and MsiInstallProduct
>
> Are you waiting for the perquisite executables to completely finish
> installing before trying to call MsiInstallProduct? There can be only
> one executing MSI at a time.
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Krause,
> Henning
> Sent: Tuesday, January 22, 2008 4:36 PM
> To: Ben Greenberg
> Cc: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Bootstrapper and MsiInstallProduct
>
> Hello,
>
> I already call MsiEnableLog(~0, logfile, 3);
>
> But no log is created. The method fails instantly.
>
> Kind regards,
> Henning
>
> > -Original Message-
> > From: Ben Greenberg [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, January 22, 2008 10:23 PM
> > To: Krause, Henning
> > Cc: wix-users@lists.sourceforge.net
> > Subject: Re: [WiX-users] Bootstrapper and MsiInstallProduct
> >
> > Perhaps you can try shelling out and running msiexec.exe with
logging
> > enabled.  Even if it still doesn't work, you may have a more
> > descriptive
> > error message.
> >
> > bg
> >
> >
> > Krause, Henning wrote:
> > > Hello,
> > >
> > > I'm writing a setup-bootstrapper which installs some required
> > software
> > > before the actual MSI is executed. The MSI is installed via
> > > MsiInstallProduct.
> > >
> > > This works just fine if no external process is called prior to the
> > call
> > > to MsiInstallProduct.
> > >
> > > But if I launch any executable prior to the call,
MsiInstallProduct
> > > fails with E_FAIL (0x80004005).
> > >
> > > I've googled for this combination but found nothing.
> > >
> > > Anyone got a clue?
> > >
> > > Kind regards,
> > > Henning
> > >
> > >
> -
> > 
> > > This SF.net email is sponsored by: Microsoft
> > > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
> > > ___
> > > WiX-users mailing list
> > > WiX-users@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/wix-users
> > >
>
>
>
---
> -
> -
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Bootstrapper and MsiInstallProduct

2008-01-23 Thread Krause, Henning

Hi,

actually it's a .NET Bootstrapper.

I'm calling MsiEnableLog and MsiInstallProduct via Interop. And it works
like charm if I don't execute another executable from the process.

Kind regards,
Henning

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:wix-users-
> [EMAIL PROTECTED] On Behalf Of Wilson, Phil
> Sent: Wednesday, January 23, 2008 8:03 PM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Bootstrapper and MsiInstallProduct
> 
> MsiEnableLog (~0, . ) doesn't work. Something like MsiEnableLog
> (INSTALLLOGMODE_VERBOSE,..) does.  What are you coding in? If C++,
> there are header files etc.
> 
> Phil Wilson
> 
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:wix-users-
> [EMAIL PROTECTED] On Behalf Of Krause, Henning
> Sent: Tuesday, January 22, 2008 11:36 PM
> To: Paul McCloskey
> Cc: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Bootstrapper and MsiInstallProduct
> 
> Hello,
> 
> I'm currently testing this by calling c:\winodows\system32\calc.exe...
> to minimize side-effects.
> 
> And I wait for the other process to finish.
> 
> Kind regards,
> Henning
> 
> > -Original Message-
> > From: Paul McCloskey [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, January 22, 2008 10:41 PM
> > To: Krause, Henning; Ben Greenberg
> > Cc: wix-users@lists.sourceforge.net
> > Subject: RE: [WiX-users] Bootstrapper and MsiInstallProduct
> >
> > Are you waiting for the perquisite executables to completely finish
> > installing before trying to call MsiInstallProduct? There can be
only
> > one executing MSI at a time.
> >
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of
Krause,
> > Henning
> > Sent: Tuesday, January 22, 2008 4:36 PM
> > To: Ben Greenberg
> > Cc: wix-users@lists.sourceforge.net
> > Subject: Re: [WiX-users] Bootstrapper and MsiInstallProduct
> >
> > Hello,
> >
> > I already call MsiEnableLog(~0, logfile, 3);
> >
> > But no log is created. The method fails instantly.
> >
> > Kind regards,
> > Henning
> >
> > > -Original Message-
> > > From: Ben Greenberg [mailto:[EMAIL PROTECTED]
> > > Sent: Tuesday, January 22, 2008 10:23 PM
> > > To: Krause, Henning
> > > Cc: wix-users@lists.sourceforge.net
> > > Subject: Re: [WiX-users] Bootstrapper and MsiInstallProduct
> > >
> > > Perhaps you can try shelling out and running msiexec.exe with
> logging
> > > enabled.  Even if it still doesn't work, you may have a more
> > > descriptive
> > > error message.
> > >
> > > bg
> > >
> > >
> > > Krause, Henning wrote:
> > > > Hello,
> > > >
> > > > I'm writing a setup-bootstrapper which installs some required
> > > software
> > > > before the actual MSI is executed. The MSI is installed via
> > > > MsiInstallProduct.
> > > >
> > > > This works just fine if no external process is called prior to
> the
> > > call
> > > > to MsiInstallProduct.
> > > >
> > > > But if I launch any executable prior to the call,
> MsiInstallProduct
> > > > fails with E_FAIL (0x80004005).
> > > >
> > > > I've googled for this combination but found nothing.
> > > >
> > > > Anyone got a clue?
> > > >
> > > > Kind regards,
> > > > Henning
> > > >
> > > >
> >
-
> > > 
> > > > This SF.net email is sponsored by: Microsoft
> > > > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > > > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
> > > > ___
> > > > WiX-users mailing list
> > > > WiX-users@lists.sourceforge.net
> > > > https://lists.sourceforge.net/lists/listinfo/wix-users
> > > >
> >
> >
> >
>
---
> > -
> > -
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
> > ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> 
>
---
> --
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 
> 
>
---
> --
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users

-
Thi

Re: [WiX-users] Bootstrapper and MsiInstallProduct

2008-01-23 Thread Wilson, Phil

Ah, ok, you said that MsiEnableLog didn't work - I thought that was still an 
issue.  So your current problem is that calling MsiEnableLog, then processing 
some executable like calc.exe, and then calling MsiInstallProduct doesn't work? 
Is that the order you're doing it?

Phil Wilson


-Original Message-
From: Krause, Henning [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 23, 2008 11:41 AM
To: Wilson, Phil; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Bootstrapper and MsiInstallProduct

Hi,

actually it's a .NET Bootstrapper.

I'm calling MsiEnableLog and MsiInstallProduct via Interop. And it works
like charm if I don't execute another executable from the process.

Kind regards,
Henning

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:wix-users-
> [EMAIL PROTECTED] On Behalf Of Wilson, Phil
> Sent: Wednesday, January 23, 2008 8:03 PM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Bootstrapper and MsiInstallProduct
>
> MsiEnableLog (~0, . ) doesn't work. Something like MsiEnableLog
> (INSTALLLOGMODE_VERBOSE,..) does.  What are you coding in? If C++,
> there are header files etc.
>
> Phil Wilson
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:wix-users-
> [EMAIL PROTECTED] On Behalf Of Krause, Henning
> Sent: Tuesday, January 22, 2008 11:36 PM
> To: Paul McCloskey
> Cc: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Bootstrapper and MsiInstallProduct
>
> Hello,
>
> I'm currently testing this by calling c:\winodows\system32\calc.exe...
> to minimize side-effects.
>
> And I wait for the other process to finish.
>
> Kind regards,
> Henning
>
> > -Original Message-
> > From: Paul McCloskey [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, January 22, 2008 10:41 PM
> > To: Krause, Henning; Ben Greenberg
> > Cc: wix-users@lists.sourceforge.net
> > Subject: RE: [WiX-users] Bootstrapper and MsiInstallProduct
> >
> > Are you waiting for the perquisite executables to completely finish
> > installing before trying to call MsiInstallProduct? There can be
only
> > one executing MSI at a time.
> >
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of
Krause,
> > Henning
> > Sent: Tuesday, January 22, 2008 4:36 PM
> > To: Ben Greenberg
> > Cc: wix-users@lists.sourceforge.net
> > Subject: Re: [WiX-users] Bootstrapper and MsiInstallProduct
> >
> > Hello,
> >
> > I already call MsiEnableLog(~0, logfile, 3);
> >
> > But no log is created. The method fails instantly.
> >
> > Kind regards,
> > Henning
> >
> > > -Original Message-
> > > From: Ben Greenberg [mailto:[EMAIL PROTECTED]
> > > Sent: Tuesday, January 22, 2008 10:23 PM
> > > To: Krause, Henning
> > > Cc: wix-users@lists.sourceforge.net
> > > Subject: Re: [WiX-users] Bootstrapper and MsiInstallProduct
> > >
> > > Perhaps you can try shelling out and running msiexec.exe with
> logging
> > > enabled.  Even if it still doesn't work, you may have a more
> > > descriptive
> > > error message.
> > >
> > > bg
> > >
> > >
> > > Krause, Henning wrote:
> > > > Hello,
> > > >
> > > > I'm writing a setup-bootstrapper which installs some required
> > > software
> > > > before the actual MSI is executed. The MSI is installed via
> > > > MsiInstallProduct.
> > > >
> > > > This works just fine if no external process is called prior to
> the
> > > call
> > > > to MsiInstallProduct.
> > > >
> > > > But if I launch any executable prior to the call,
> MsiInstallProduct
> > > > fails with E_FAIL (0x80004005).
> > > >
> > > > I've googled for this combination but found nothing.
> > > >
> > > > Anyone got a clue?
> > > >
> > > > Kind regards,
> > > > Henning
> > > >
> > > >
> >
-
> > > 
> > > > This SF.net email is sponsored by: Microsoft
> > > > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > > > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
> > > > ___
> > > > WiX-users mailing list
> > > > WiX-users@lists.sourceforge.net
> > > > https://lists.sourceforge.net/lists/listinfo/wix-users
> > > >
> >
> >
> >
>
---
> > -
> > -
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
> > ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
---
> --
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/list

Re: [WiX-users] Bootstrapper and MsiInstallProduct

2008-01-23 Thread Krause, Henning

Hi Wilson,

the order is this:

1. Call calc.exe
2. Call MsiEnableLog
3. Call MsiInstallProduct.

MsiInstallProduct then returns E_FAIL.

Kind regards,
Henning

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:wix-users-
> [EMAIL PROTECTED] On Behalf Of Wilson, Phil
> Sent: Wednesday, January 23, 2008 9:01 PM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Bootstrapper and MsiInstallProduct
> 
> Ah, ok, you said that MsiEnableLog didn't work - I thought that was
> still an issue.  So your current problem is that calling MsiEnableLog,
> then processing some executable like calc.exe, and then calling
> MsiInstallProduct doesn't work? Is that the order you're doing it?
> 
> Phil Wilson
> 
> 
> -Original Message-
> From: Krause, Henning [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 23, 2008 11:41 AM
> To: Wilson, Phil; wix-users@lists.sourceforge.net
> Subject: RE: [WiX-users] Bootstrapper and MsiInstallProduct
> 
> Hi,
> 
> actually it's a .NET Bootstrapper.
> 
> I'm calling MsiEnableLog and MsiInstallProduct via Interop. And it
> works
> like charm if I don't execute another executable from the process.
> 
> Kind regards,
> Henning
> 
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:wix-users-
> > [EMAIL PROTECTED] On Behalf Of Wilson, Phil
> > Sent: Wednesday, January 23, 2008 8:03 PM
> > To: wix-users@lists.sourceforge.net
> > Subject: Re: [WiX-users] Bootstrapper and MsiInstallProduct
> >
> > MsiEnableLog (~0, . ) doesn't work. Something like MsiEnableLog
> > (INSTALLLOGMODE_VERBOSE,..) does.  What are you coding in? If
> C++,
> > there are header files etc.
> >
> > Phil Wilson
> >
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:wix-users-
> > [EMAIL PROTECTED] On Behalf Of Krause, Henning
> > Sent: Tuesday, January 22, 2008 11:36 PM
> > To: Paul McCloskey
> > Cc: wix-users@lists.sourceforge.net
> > Subject: Re: [WiX-users] Bootstrapper and MsiInstallProduct
> >
> > Hello,
> >
> > I'm currently testing this by calling
> c:\winodows\system32\calc.exe...
> > to minimize side-effects.
> >
> > And I wait for the other process to finish.
> >
> > Kind regards,
> > Henning
> >
> > > -Original Message-
> > > From: Paul McCloskey [mailto:[EMAIL PROTECTED]
> > > Sent: Tuesday, January 22, 2008 10:41 PM
> > > To: Krause, Henning; Ben Greenberg
> > > Cc: wix-users@lists.sourceforge.net
> > > Subject: RE: [WiX-users] Bootstrapper and MsiInstallProduct
> > >
> > > Are you waiting for the perquisite executables to completely
finish
> > > installing before trying to call MsiInstallProduct? There can be
> only
> > > one executing MSI at a time.
> > >
> > > -Original Message-
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED] On Behalf Of
> Krause,
> > > Henning
> > > Sent: Tuesday, January 22, 2008 4:36 PM
> > > To: Ben Greenberg
> > > Cc: wix-users@lists.sourceforge.net
> > > Subject: Re: [WiX-users] Bootstrapper and MsiInstallProduct
> > >
> > > Hello,
> > >
> > > I already call MsiEnableLog(~0, logfile, 3);
> > >
> > > But no log is created. The method fails instantly.
> > >
> > > Kind regards,
> > > Henning
> > >
> > > > -Original Message-
> > > > From: Ben Greenberg [mailto:[EMAIL PROTECTED]
> > > > Sent: Tuesday, January 22, 2008 10:23 PM
> > > > To: Krause, Henning
> > > > Cc: wix-users@lists.sourceforge.net
> > > > Subject: Re: [WiX-users] Bootstrapper and MsiInstallProduct
> > > >
> > > > Perhaps you can try shelling out and running msiexec.exe with
> > logging
> > > > enabled.  Even if it still doesn't work, you may have a more
> > > > descriptive
> > > > error message.
> > > >
> > > > bg
> > > >
> > > >
> > > > Krause, Henning wrote:
> > > > > Hello,
> > > > >
> > > > > I'm writing a setup-bootstrapper which installs some required
> > > > software
> > > > > before the actual MSI is executed. The MSI is installed via
> > > > > MsiInstallProduct.
> > > > >
> > > > > This works just fine if no external process is called prior to
> > the
> > > > call
> > > > > to MsiInstallProduct.
> > > > >
> > > > > But if I launch any executable prior to the call,
> > MsiInstallProduct
> > > > > fails with E_FAIL (0x80004005).
> > > > >
> > > > > I've googled for this combination but found nothing.
> > > > >
> > > > > Anyone got a clue?
> > > > >
> > > > > Kind regards,
> > > > > Henning
> > > > >
> > > > >
> > >
> -
> > > > 
> > > > > This SF.net email is sponsored by: Microsoft
> > > > > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > > > > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
> > > > > ___
> > > > > WiX-users mailing list
> > > > > WiX-users@lists.sourceforge.net
> > > > > https://lists.sourceforge.net/lists/listinfo/wix-users
> > > > >
> > >
> > >
> > >
> >
>
---
> > > -
> > > -
> > > This SF

Re: [WiX-users] Trouble with Light in Visual Studio 2008 and Team Build2008

2008-01-23 Thread Mike Dimmick

This is a change in the MSBuild actions in very recent builds of WiX.
Instead of creating a new process it now loads the assembly in-process.

 

It looks like light.exe can't actually handle that - that various static
variables aren't being cleared down between sessions.

 

Unfortunately to revert requires changing the base class of
Microsoft.Tools.WindowsInstallerXml.Build.Tasks.Light (in
src\WixTasks\Light.cs) back to ToolTask, rather than WixToolTask, then
rebuilding.

 

You can probably get round it by creating a new AppDomain for each run
rather than reusing AppDomains. (A new AppDomain has its own copy of static
variables.)

 

I suggest logging a bug at http://sourceforge.net/tracker/?group_id=105970
 &atid=642714.

 

-- 

Mike Dimmick

 

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Arild Bakken
Sent: 23 January 2008 10:37
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Trouble with Light in Visual Studio 2008 and Team
Build2008

 

Hi everyone,

 

I'm having trouble with Light.exe. I installed the January 11 build
(3.0.3711) and things work very well except that I can only build the Setup
project once for every time I start Visual Studio. When I build the first
time after I start Visual Studio 2008, everything is OK, but all builds
after that fail with "Light.exe exited with code 1".  If I restart Visual
Studio I can build once again. I can live with that, cause all I have to do
is copy the light.exe commandline that Visual Studio shows in the output
into a commandprompt and it works.

 

The problem though is that this also happens with Team Build (TFS) when I
build both release and debug versions of the product. The first (usually
Release) builds fine, but the second fails. When running Team Build I get
additional error information (which I don't see when running in Visual
Studio):

 

light.exe : error LGHT0001 : Item has already been added. Key in dictionary:
'InstallUISequence/PrepareDlg'  Key being added:
'InstallUISequence/PrepareDlg'

Exception Type: System.ArgumentException

Stack Trace:

   at System.Collections.SortedList.Add(Object key, Object value)

   at
Microsoft.Tools.WindowsInstallerXml.WixActionRowCollection.Add(WixActionRow
actionRow, Boolean overwrite)

   at
Microsoft.Tools.WindowsInstallerXml.Linker.SequenceActions(RowCollection
actionRows, RowCollection suppressActionRows)

   at Microsoft.Tools.WindowsInstallerXml.Linker.Link(SectionCollection
sections, ArrayList transforms)

   at Microsoft.Tools.WindowsInstallerXml.Tools.Light.Run(String[] args)

Binder temporary directory located at 'C:\Documents and
Settings\_tfsservice\Local Settings\Temp\nnj-8nas'.

Validator temporary directory located at 'C:\Documents and
Settings\_tfsservice\Local Settings\Temp\3b6mv9ua'.

 

So, it looks like some stuff is "stuck" in memory between builds. It seems
that Visual Studio 2008 / TFS Build 2008 does not actually spawn a separate
process for light.exe, but seems to load the assembly into an appdomain - so
any static stuff would survive successive builds (this is guesswork, but I
never see a light.exe process during builds so I'm guessing VS loads the
assembly and runs stuff).

 

As a test I removed all UI stuff from the wix project (since the error
relates to InstallUISequence), and now I can build without problems, but of
course I would like some UI for the installer :-)

 

Has anyone else run into this problem? Is there a know fix?

 

 

Regards,

 

Arild

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] WiX install fails - VS Std Ed or higher required

2008-01-23 Thread David White

I am trying to install from Wix-3.0.2925.0.msi on Vista Ultimate with
UAC turned off. Why am I getting this message:

  "Votive, the WiX project and editor package for Visual Studio,
  cannot be installed because Visual Studio Standard Edition
  or higher is not installed."

This is despite the fact that I have Visual Studio Team System 2008
Development Edition installed.

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] re install question

2008-01-23 Thread hina1703


I have created a installer which installs a dll & a wicc file without any UI.
But if I make any changes to the installer & try to install on top of it, it
gives a message that "another version of the product is already installed".
Is there any way to uninstall it automatically & install again instead of
popping that message or just reinstall on top of it?


-- 
View this message in context: 
http://www.nabble.com/reinstall-question-tp15052047p15052047.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] 32-bit and 64-bit MSIs bundled in single EXE

2008-01-23 Thread Kevin Richardson

Hi there,

For several products, I have distinct 32-bit and 64-bit MSIs, as you'd  
expect.

I'd like a single download that contained both, and would install the  
correct MSI, depending on the system architecture. For this to work,  
the executable would have to be compiled as 32-bit.

Is it "OK" to bundle both MSIs into a single, 32-bit, bootstrapper  
executable?

Of course, I'd need to add logic to the executable to install the  
correct architecture's package, but my question is about whether the  
correct processes will be called. Will Windows (and the MSI APIs) "do  
the right thing" depending on the platform specified in each MSI?

Thanks,

-kevin

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Installing 2 files w/same filename from diff features breaks ICE30?

2008-01-23 Thread Chris Weiss

I've got two versions of an assembly installed based on whether the
user is on a Terminal Services machine or not. The files are
associated with two different mutually-exclusive features that are set
to not install by default. One feature is installed if it's a
TS-supported box, the other for all other instances.

The trouble is, when I go to compile, I get the following:
Error 16 ICE30: The target file 'qd66ikg8.dll|Interop.BIPRNDRVLib.dll'
is installed in '[SystemFolder]\' by two different components on an
LFN system: 'Interop.BIPRNDRVLibNT.dll' and
'Interop.BIPRNDRVLibTS.dll'. This breaks component reference
counting.
C:\srv-perforce\p4_all\ELN\Main\CM\Symyx.Notebook.Application.Installer\Symyx.Notebook.Application.Installer.wxs
156 1 Symyx.Notebook.Application.Installer
Error 17 ICE30: The target file 'qd66ikg8.dll|Interop.BIPRNDRVLib.dll'
is installed in '[SystemFolder]\' by two different components on an
LFN system: 'Interop.BIPRNDRVLibNT.dll' and
'Interop.BIPRNDRVLibTS.dll'. This breaks component reference
counting.
C:\srv-perforce\p4_all\ELN\Main\CM\Symyx.Notebook.Application.Installer\Symyx.Notebook.Application.Installer.wxs
135 1 Symyx.Notebook.Application.Installer

Is there any way to avoid this error? Because this assembly is called
all over, it's no small chunk of work to update the references.

The component definitions look like:

--
-Chris

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Help with ICE38 and KeyPath installing to a folder on the Desktop

2008-01-23 Thread Paul McLaughlin


Greetings.  Please excuse my noobness, but I am new to WiX and all things MSI.  
I'm guessing this is a trivial issue:
 
I've read the WiX tutorial and am trying to deviate just a bit, by creating a 
directory on the Desktop and copy a file in there and then also create a 
shortcut to that file on the Desktop.  After that works, I want to do that to 
the LocalAppDataFolder.
 
Here is my test.wxs file:
 

http://schemas.microsoft.com/wix/2006/wi";>
  




 

  

 
  

  

  



  
  

  

 

  



 
 
Here is what light.exe outputs:
 
Microsoft (R) Windows Installer Xml Linker version 3.0.2925.0
Copyright (C) Microsoft Corporation 2003. All rights reserved.
 
test.wxs(18) : error LGHT0204 : ICE38: Component idTestProgram installs to user 
profile.
It must use a registry key under HKCU as its KeyPath, not a file.
 
 
 
I tried learning what KeyPath means, but I can't find anything that really 
talks about it in the WiX help file.  Many topics refer to it, but I can't find 
what ICE38 is and why I need a registry key, and I still don't know what a 
KeyPath means.
 
Thank you so much for your help!
 
_
Shed those extra pounds with MSN and The Biggest Loser!
http://biggestloser.msn.com/-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Bootstrapper and MsiInstallProduct

2008-01-23 Thread Richard

In article <[EMAIL PROTECTED]>,
"Krause, Henning" <[EMAIL PROTECTED]>  writes:

> the order is this:
> 
> 1. Call calc.exe
> 2. Call MsiEnableLog
> 3. Call MsiInstallProduct.
> 
> MsiInstallProduct then returns E_FAIL.

MSI functions don't return HRESULTs, so it doesn't return E_FAIL.

How are you calling MSI functions through interop?  i.e. custom
p/invoke, some wrapper library, what?
-- 
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download

Legalize Adulthood! 

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Return codes for candle & light

2008-01-23 Thread Bob Arnson


[EMAIL PROTECTED] wrote:
Just wondering if anybody knows of a reference somewhere on return 
codes of Wix tools.


0 on success, otherwise the error number shown in the last error message.

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

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Get rid of distracting 'run from the network' installation in the root feature

2008-01-23 Thread Bob Arnson

Christopher Painter wrote:
> Right, I'm familiar with MenuLocal and MenuAllLocal.   The problem is 
> consider this feature tree
>  
> A (root)
> B Parent A
> MenuLocal and MenuAllLocal is displayed by my selection tree for both 
> features.  The annoyance is that B doesn't have any child features so 
> I don't know why ( or how to stop ) the control from displaying the 
> ManuAllLocal string.The string is correct however in the context 
> of feature A.
>  
> Is this just one of those MSI annoyances?

Yes, that's the SelectionTree control.

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

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] re install question

2008-01-23 Thread Bob Arnson

hina1703 wrote:
> I have created a installer which installs a dll & a wicc file without any UI.
> But if I make any changes to the installer & try to install on top of it, it
> gives a message that "another version of the product is already installed".
> Is there any way to uninstall it automatically & install again instead of
> popping that message or just reinstall on top of it?
>   

Use a major upgrade. See http://www.tramontana.co.hu/wix/lesson4.php for 
details.

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

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Visual Studio running detection

2008-01-23 Thread Bob Arnson

Adrian Alonso wrote:
> Thanks Bob, but I'm using WIX V2. Do you know if there is a similar CA 
> in V2 too?

No, that CA is a new feature in v3.

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

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] 32-bit and 64-bit MSIs bundled in single EXE

2008-01-23 Thread Bob Arnson

Kevin Richardson wrote:
> Is it "OK" to bundle both MSIs into a single, 32-bit, bootstrapper  
> executable?
>
> Of course, I'd need to add logic to the executable to install the  
> correct architecture's package, but my question is about whether the  
> correct processes will be called. Will Windows (and the MSI APIs) "do  
> the right thing" depending on the platform specified in each MSI?
>   

Yes, just detect the platform and kick off the appropriate package. MSI 
is 64-bit and 32-bit on x64 OSes.

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

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] WiX install fails - VS Std Ed or higher required

2008-01-23 Thread Bob Arnson

David White wrote:
> I am trying to install from Wix-3.0.2925.0.msi on Vista Ultimate with
> UAC turned off. Why am I getting this message:
>
>   "Votive, the WiX project and editor package for Visual Studio,
>   cannot be installed because Visual Studio Standard Edition
>   or higher is not installed."
>
> This is despite the fact that I have Visual Studio Team System 2008
> Development Edition installed.
>   

That version of WiX is eight months old and doesn't support VS2008. Use 
3.0.3704.0 from http://wix.sourceforge.net/releases/ instead.

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

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Installing 2 files w/same filename from diff features breaks ICE30?

2008-01-23 Thread Bob Arnson

Chris Weiss wrote:
> I've got two versions of an assembly installed based on whether the
> user is on a Terminal Services machine or not. The files are
> associated with two different mutually-exclusive features that are set
> to not install by default. One feature is installed if it's a
> TS-supported box, the other for all other instances.
>   

Use conditions on both components; that turns ICE30 into a warning 
instead of an error. ICE30 doesn't peek into feature conditions and even 
if it did, there are so many ways of turning on features, it couldn't 
realistically check them all.

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

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Help with ICE38 and KeyPath installing to a folder on the Desktop

2008-01-23 Thread Bob Arnson


Paul McLaughlin wrote:


test.wxs(18) : error LGHT0204 : ICE38: Component idTestProgram 
installs to user profile.


It must use a registry key under HKCU as its KeyPath, not a file.

 

 

 

I tried learning what KeyPath means, but I can't find anything that 
really talks about it in the WiX help file.  Many topics refer to it, 
but I can't find what ICE38 is and why I need a registry key, and I 
still don't know what a KeyPath means.




WiX doesn't do much on documenting MSI concepts; for those, you 
want/need the MSI SDK. KeyPath is a column in the Component table: 
http://msdn2.microsoft.com/en-us/library/aa368007(VS.85).aspx.


See 
http://robmensching.com/blog/archive/2007/04/27/How-to-create-an-uninstall-shortcut-and-pass-all-the.aspx 
for the oddities of ICEs and resources installed into the user profile.


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

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Installing 2 files w/same filename from diff features breaks ICE30?

2008-01-23 Thread Chris Weiss

On Jan 23, 2008 7:49 PM, Bob Arnson <[EMAIL PROTECTED]> wrote:
> Chris Weiss wrote:
> > I've got two versions of an assembly installed based on whether the
> > user is on a Terminal Services machine or not. The files are
> > associated with two different mutually-exclusive features that are set
> > to not install by default. One feature is installed if it's a
> > TS-supported box, the other for all other instances.
> >
>
> Use conditions on both components; that turns ICE30 into a warning
> instead of an error. ICE30 doesn't peek into feature conditions and even
> if it did, there are so many ways of turning on features, it couldn't
> realistically check them all.
>

Ahh - thanks!. What's the syntax for attaching a condition directly to
a component?

-- 
-Chris

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Flag Setting

2008-01-23 Thread SaiTeja


Hi,

Like in install shield, is Wix has Release Flags? If yes can any one tell me
how to do in wix

Note:
For example, if you are creating a trial version of your product and do not
want to include all the features in the build, you can flag features and
then specify those flagged features under the product configuration or the
release.
-- 
View this message in context: 
http://www.nabble.com/Flag-Setting-tp15058668p15058668.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] MSI not removed files under allusers-application data

2008-01-23 Thread SaiTeja


Hi,

I added one component(xyz.exe) property Permanent="yes"

When I uninstall the client, xyz.exe is still there under INSTALLDIR.
I think this becuase of property permanent=yes.

Also when I uninstall the client, the files under C:\Documents and
Settings\All Users\Application Data\Test Machine are not removed.  (I
believe the correct behavior is to remove all files there except for a
couple of log files.)

I created same MSI through InstallShield, after uninstalling it is created
.tmp("2008-01-23T06%3a50%3a39%2e577Zxyz.exe.tmp") under INSTALLDIR and it
removed all files from C:\Documents and Settings\All Users\Application
Data\Test Machine except for a couple of log files.

Can any one give ideas?
-- 
View this message in context: 
http://www.nabble.com/MSI-not-removed-files-under-allusers-application-data-tp15058673p15058673.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] 32-bit and 64-bit MSIs bundled in single EXE

2008-01-23 Thread Kevin Richardson

Thanks, Bob.

It looks like the current bootstrapper calls msiexec.exe, rather than  
using the APIs. I inherited the code and it looks like it was done  
that way to make it convenient to pass command line arguments, among  
other things.

If I continue to call the executable, I assume that I'll need to  
choose the correct msiexec.exe (system32 for 64-bit on x64, syswow64  
for 32-bit on x64, system32 on 32-bit), or can x64's system32\msiexec  
install 32-bit MSIs?

-kevin

On Jan 23, 2008, at 7:46 PM, Bob Arnson wrote:

> Kevin Richardson wrote:
>> Is it "OK" to bundle both MSIs into a single, 32-bit, bootstrapper   
>> executable?
>>
>> Of course, I'd need to add logic to the executable to install the   
>> correct architecture's package, but my question is about whether  
>> the  correct processes will be called. Will Windows (and the MSI  
>> APIs) "do  the right thing" depending on the platform specified in  
>> each MSI?
>>
>
> Yes, just detect the platform and kick off the appropriate package.  
> MSI is 64-bit and 32-bit on x64 OSes.
>
> -- 
> sig://boB
> http://joyofsetup.com/
>
>

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Trouble with Light in Visual Studio 2008 and Team Build2008

2008-01-23 Thread Arild Bakken

Mike,

Thanks for the info! I actually found a bug registered January 22nd that looks 
to be the same issue ([ 1877424 ] LGHT0001: Duplicate Key added) although a 
different key. That bug report states that the 3.0.3526 release does not have 
this problem so I downgraded to that release and now it works perfectly. I 
tried to compile the sourcecode of 3.0.3711 in order to fix the error according 
to your suggestion, but there was just too much that needed to be changed in 
the build configuration in order to build on my Vista x64 computer with only VS 
2008 installed (I didn't want to install VS 2005 as well) so I decided to save 
some time and downgrade Wix instead.


Regards,

Arild

From: Mike Dimmick [mailto:[EMAIL PROTECTED]
Sent: 23. januar 2008 21:37
To: Arild Bakken; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Trouble with Light in Visual Studio 2008 and Team 
Build2008

This is a change in the MSBuild actions in very recent builds of WiX. Instead 
of creating a new process it now loads the assembly in-process.

It looks like light.exe can't actually handle that - that various static 
variables aren't being cleared down between sessions.

Unfortunately to revert requires changing the base class of 
Microsoft.Tools.WindowsInstallerXml.Build.Tasks.Light (in 
src\WixTasks\Light.cs) back to ToolTask, rather than WixToolTask, then 
rebuilding.

You can probably get round it by creating a new AppDomain for each run rather 
than reusing AppDomains. (A new AppDomain has its own copy of static variables.)

I suggest logging a bug at 
http://sourceforge.net/tracker/?group_id=105970&atid=642714.

--
Mike Dimmick


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Arild Bakken
Sent: 23 January 2008 10:37
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Trouble with Light in Visual Studio 2008 and Team Build2008

Hi everyone,

I'm having trouble with Light.exe. I installed the January 11 build (3.0.3711) 
and things work very well except that I can only build the Setup project once 
for every time I start Visual Studio. When I build the first time after I start 
Visual Studio 2008, everything is OK, but all builds after that fail with 
"Light.exe exited with code 1".  If I restart Visual Studio I can build once 
again. I can live with that, cause all I have to do is copy the light.exe 
commandline that Visual Studio shows in the output into a commandprompt and it 
works.

The problem though is that this also happens with Team Build (TFS) when I build 
both release and debug versions of the product. The first (usually Release) 
builds fine, but the second fails. When running Team Build I get additional 
error information (which I don't see when running in Visual Studio):

light.exe : error LGHT0001 : Item has already been added. Key in dictionary: 
'InstallUISequence/PrepareDlg'  Key being added: 'InstallUISequence/PrepareDlg'
Exception Type: System.ArgumentException
Stack Trace:
   at System.Collections.SortedList.Add(Object key, Object value)
   at 
Microsoft.Tools.WindowsInstallerXml.WixActionRowCollection.Add(WixActionRow 
actionRow, Boolean overwrite)
   at Microsoft.Tools.WindowsInstallerXml.Linker.SequenceActions(RowCollection 
actionRows, RowCollection suppressActionRows)
   at Microsoft.Tools.WindowsInstallerXml.Linker.Link(SectionCollection 
sections, ArrayList transforms)
   at Microsoft.Tools.WindowsInstallerXml.Tools.Light.Run(String[] args)
Binder temporary directory located at 'C:\Documents and 
Settings\_tfsservice\Local Settings\Temp\nnj-8nas'.
Validator temporary directory located at 'C:\Documents and 
Settings\_tfsservice\Local Settings\Temp\3b6mv9ua'.

So, it looks like some stuff is "stuck" in memory between builds. It seems that 
Visual Studio 2008 / TFS Build 2008 does not actually spawn a separate process 
for light.exe, but seems to load the assembly into an appdomain - so any static 
stuff would survive successive builds (this is guesswork, but I never see a 
light.exe process during builds so I'm guessing VS loads the assembly and runs 
stuff).

As a test I removed all UI stuff from the wix project (since the error relates 
to InstallUISequence), and now I can build without problems, but of course I 
would like some UI for the installer J

Has anyone else run into this problem? Is there a know fix?


Regards,

Arild
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

40 matches

Mail list logo