[WiX-users] Multiple Installs without Un-Install?

[Daniel Zak]

Hello,

I created a script to install an SQL Server database. A user needs to be
able to run the script multiple times to install multiple databases.
However, the script requires the user to first un-install the product (which
does not delete the database) before being able to install a new database.

Is there anything I can do to avoid requiring the user to explicitly
un-install the product?

I included an extract of the script as a text file.

Thank you,
Daniel.
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] updating packages

[jeff sacksteder]

I've read this

http://www.tramontana.co.hu/wix/lesson4.php

and I want to make some changes in the 'small updates' category. This
means I make the changes in my MSI, alter the Package ID.

Then what? I want to deploy this as an update with group policy. It's
not clear to me how it will be able to determine the most recent one
if I'm not changing the version number.

Do I just remove the current package, deploy the updated one, and it
will overwrite the existing on based solely on product id?

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] DTF - Using ExtractFiles Method

[Powell, Simon]

Hi,
 
I'm using the ExtractFiles Method to extract files from the Windows 2003
Resource kit msi (rktools.msi). Below is a simple snippet of code used :
 
InstallPackage MsiPackage = new InstallPackage(txtMsi.Text,
DatabaseOpenMode.ReadOnly);
MsiPackage.WorkingDirectory = "c:\\temp";
Regex myReg = new Regex("exe", RegexOptions.IgnoreCase);
string[] filekeys = MsiPackage.FindFiles(myReg);
MsiPackage.ExtractFiles(filekeys);

Some of the files fail to extract return the following
FileNotFoundException :

Could not find file 'c:\temp\Program Files\Windows Resource
Kits\Tools\nlsinfo.exe'.

It's strange, because the file exists in the extracted cab file
(Cabs.winrk.cab), all the files extract correctly to c:\temp if I use
msiexec /a rktools.msi (but this  gives me no control over the files I
extract). Is this a bug or am I doing something wrong? This problem
happens with a number of MSIs including sqlrun.msi of the SQL Server
2005 client tools. 

Your help will be much appreciated.

Regards
Simon Powell


--
This e-mail is confidential and the information contained in it may be 
privileged.  It should not be read, copied or used by anyone other than the 
intended recipient.  If you have received it in error, please contact the 
sender immediately by telephoning +44 (0)20 7623 8000 or by return email, and 
delete the e-mail and do not disclose its contents to any person.  We believe, 
but do not warrant, that this e-mail and any attachments are virus free, but 
you must take full responsibility for virus checking.  Please refer to 
http://www.dresdnerkleinwort.com/disc/email/ and read our e-mail disclaimer 
statement and monitoring policy.

Dresdner Kleinwort is the trading name of the investment banking division of 
Dresdner Bank AG, and operates through Dresdner Bank AG, Dresdner Kleinwort 
Limited, Dresdner Kleinwort Securities Limited and their affiliated or 
associated companies.  Dresdner Bank AG is a company incorporated in Germany 
with limited liability and registered in England (registered no. FC007638, 
place of business 30 Gresham Street, London EC2V 7PG), and is authorised by the 
German Federal Financial Supervisory Authority and by the Financial Services 
Authority ('FSA') and regulated by the FSA for the conduct of designated 
business in the UK.  Dresdner Kleinwort Limited is a company incorporated in 
England (registered no. 551334, registered office 30 Gresham Street, London 
EC2V 7PG), and is authorised and regulated by the FSA.  Dresdner Kleinwort 
Securities Limited is a company incorporated in England (registered no. 
1767419, registered office 30 Gresham Street, London EC2V 7PG), and is 
authorised an
 d regulated by the FSA.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] MessageQueuePermission/Unresolved reference

[Andy Kachelmeier]

Hey everyone,

 

I'm trying to set up permissions to a MSMQ Message queue created with the
following code:

 







 

But when I build the project, I get this error:

 

Unresolved reference to symbol 'User:Everyone' in section
'Product:{3A7A0A26-F579-4158-AACF-CEF6FCEC52D8}'.

 

If I remove the MessageQueuePermission element, it builds and installs fine.
Any ideas??

 

I'm using WiX v3.0.2418.0.

 

Thanks!

Andy

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] configure web.config with XmlConfig

[Zhisheng Huang]

Hi,
 
I am using WIX doing web service setup. During the setup, it needs to update 
the web.config file with correct value. The web.config file is installed in the 
same msi. 
Here is what I am doing.  
 
  
  
  
    
    
    
  
 
However, after running MSI, the attribute values are not updated - looks like 
do nothing. The msi verbose log does says "Action ended 11:39:45: 
SchedXmlConfig. Return value 1." There is no more information. What am I 
missing or doing wrong? 
 
Thanks for help!
Zhisheng


  

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Two questions about new WiX patching

[Tony Juricic]

1) I don't understand how do wixpdb ouputs deal with binary delta
patches? Looking at example commands it appears as if MSI (or binary
files compressed inside MSI cab) are not needed, as if all relevant info
is contained in wixpdb. 

Or is it that torch, while working on the differences between 2 wixpdbs,
expects that MSIs are present in respective locations and decompresses
them to find delta patches?

2) Regarding file sequences, if, for example, I have 200 files to
install and possibly need to patch each and every one of them, am I
supposed to increment media Id by 200? So I would start with say:





Then the next patch would be:





next




and so on?

Thanks for any input!

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] VS 2005 problem with Wix 3.0.4311.0 version

[Jason Ginchereau]

Justin and I talked about this and our best guess is still that something 
didn't get installed properly. If you haven't already, can you try uninstalling 
WiX and installing it again?

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chandra Vuppala
Sent: Thursday, July 17, 2008 10:14 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] VS 2005 problem with Wix 3.0.4311.0 version

These are steps i followed while insatlling wix 1. ProjectAggregator2.msi 2. 
Wix3.0.4311 3. Restated the machene

Now i have opened new project, but it is showing blank in the solution 
explorer, by default it hasopened wxs file.


Thanks &  Regards,
Chandrashekar vuppala
M-9908298419
Oakton Global Technology Services Centre (India)  Results Driven. When Business 
& IT Matters



From: [EMAIL PROTECTED] on behalf of Jason Ginchereau
Sent: Fri 18/07/2008 10:38 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] VS 2005 problem with Wix 3.0.4311.0 version



Oh I think I know what the problem is. You need to also install 
ProjectAggregator2.msi.  That is required for VS2005 integration (but not for 
VS2008).

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chandra Vuppala
Sent: Thursday, July 17, 2008 9:12 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] VS 2005 problem with Wix 3.0.4311.0 version

Hi Jason,

Am using Windows Vista can u tell me what all i need to install and  give me 
the steps for installation to make it work.


From: [EMAIL PROTECTED] on behalf of Jason Ginchereau
Sent: Thu 17/07/2008 9:28 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] VS 2005 problem with Wix 3.0.4311.0 version



There might be some problem with the WiX installation on your system, since 
nobody else is seeing that kind of problem. What OS are you running on? Can you 
try uninstalling and reinstalling WiX? Does the previous week's build work? 
(You probably don't want to use 4311 anyway since that week there was 
regression in the tool command-line processing as called by Votive.)

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chandra Vuppala
Sent: Wednesday, July 16, 2008 9:12 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] VS 2005 problem with Wix 3.0.4311.0 version

Hi Jason,
For existing and new projects.


 I am facing problem with visual studio after installing Wix 3.0.4311.0 version.
 Problem: I am unable to see solution in solution explorer for wix projects but 
I can see c# projects.

 It is also giving access denied error when am building existing wix projects.
 Please help me out.




From: [EMAIL PROTECTED] on behalf of Jason Ginchereau
Sent: Wed 16/07/2008 7:26 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] VS 2005 problem with Wix 3.0.4311.0 version



Is this a problem only with existing wix projects you previously created with 
an older build of wix, or do you also also have the problem with newly-created 
wix projects?

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chandra Vuppala
Sent: Wednesday, July 16, 2008 3:35 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] VS 2005 problem with Wix 3.0.4311.0 version

 Hi,
 I am facing problem with visual studio after installing Wix 3.0.4311.0 version.
 Problem: I am unable to see solution in solution explorer for wix projects but 
I can see c# projects.

 It is also giving access denied error when am building existing wix projects.
 Please help me out.


Thanks &  Regards,
Chandrashekar vuppala
M-9908298419
Oakton Global Technology Services Centre (India)  Results Driven. When Business 
& IT Matters



-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge 
Build the coolest Linux based applications with Moblin SDK & win great prizes 
Grand prize is a trip for two to an Open Source event anywhere in the world 
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



IMPORTANT
1.  This email and any attachments are confidential.  Any unauthorised 
dissemination or other use of these materials is prohibited.  If received in 
error, please contact us and delete all copies.
2.  Before opening or using attachments, check them for viruses and 
defects.  Our liability is limited to resupplying any affected attachments.
3.  Protecting your privacy is important to us.  Our privacy statement and 
further information is available at www.oak

Re: [WiX-users] prevent an old package from installing not working

[Lucius Fleuchaus]

Thanks for the lower case char in the upgrade GUID.  I can still fix this (I 
believe candle just upper cases it for you). There was one over sight in the 
way I was testing (that I did know but had forgotten).  I was only changing the 
forth portion of the version stamp, which installer engine ignores.

Thanks for all responses!
-Lucius

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alexander 
Shevchuk
Sent: Monday, July 21, 2008 10:32 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] prevent an old package from installing not working

Hi Lucius,

Is it too late in the game to fix __UPGRADEGUID__?  All GUIDs must be upper 
cased in MSI and your upgrade code is not following this rule.  Other than that 
I can't see what can be wrong with your code (I assume that your project is 
using same upgrade code for all versions).  Try a small test project to see if 
upgrade guid is the problem here.

Regards,
Alex Shevchuk


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lucius Fleuchaus
Sent: Monday, July 21, 2008 10:07 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] prevent an old package from installing not working

That would not work since it would also prevent upgrading to newer versions, 
which I like allow by having installer uninstall automatically the older 
version.


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Karthik Krishnan
Sent: Monday, July 21, 2008 8:41 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] prevent an old package from installing not working

Your [EMAIL PROTECTED] is set to "*" meaning that it is autogenerated every 
time.
If you set this to a static value, perhaps passed it in as a var the same
way you do the UpgradeCode, Windows Installer should throw an error saying
that another version of the same product is installed. Is this what you are
trying to do?

K

On Sat, Jul 19, 2008 at 1:41 PM, Lucius Fleuchaus <[EMAIL PROTECTED]>
wrote:

> I am following the instructions given at
> http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-part-8-major-upgrade.aspxand
> http://msdn.microsoft.com/en-us/library/aa370840(VS.85).aspxto
>  prevent an old package from installing.  Below is the WIX file with the
> yellow highlight the additional steps I added.  However, it does not work.
>  It still installs resulting in a second entry in Add/Remove programs.  Can
> someone see what is wrong?  I am using WIX v3.0.3907.0.  Thanks.



>
>Id="*"













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










(VersionNT >= 501 AND ServicePackLevel>=2) OR (VersionNT >= 502 AND 
ServicePackLevel>=1) OR (VersionNT>502)





Installed OR NETFRAMEWORK30












































  

  
  








NEWPRODUCTFOUND



NOT 
REMOVE="ALL"




NEWPRODUCTFOUND






-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.source

Re: [WiX-users] prevent an old package from installing not working

[Alexander Shevchuk]

Hi Lucius,

Is it too late in the game to fix __UPGRADEGUID__?  All GUIDs must be upper 
cased in MSI and your upgrade code is not following this rule.  Other than that 
I can't see what can be wrong with your code (I assume that your project is 
using same upgrade code for all versions).  Try a small test project to see if 
upgrade guid is the problem here.

Regards,
Alex Shevchuk


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lucius Fleuchaus
Sent: Monday, July 21, 2008 10:07 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] prevent an old package from installing not working

That would not work since it would also prevent upgrading to newer versions, 
which I like allow by having installer uninstall automatically the older 
version.


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Karthik Krishnan
Sent: Monday, July 21, 2008 8:41 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] prevent an old package from installing not working

Your [EMAIL PROTECTED] is set to "*" meaning that it is autogenerated every 
time.
If you set this to a static value, perhaps passed it in as a var the same
way you do the UpgradeCode, Windows Installer should throw an error saying
that another version of the same product is installed. Is this what you are
trying to do?

K

On Sat, Jul 19, 2008 at 1:41 PM, Lucius Fleuchaus <[EMAIL PROTECTED]>
wrote:

> I am following the instructions given at
> http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-part-8-major-upgrade.aspxand
> http://msdn.microsoft.com/en-us/library/aa370840(VS.85).aspxto
>  prevent an old package from installing.  Below is the WIX file with the
> yellow highlight the additional steps I added.  However, it does not work.
>  It still installs resulting in a second entry in Add/Remove programs.  Can
> someone see what is wrong?  I am using WIX v3.0.3907.0.  Thanks.



>
>Id="*"













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










(VersionNT >= 501 AND ServicePackLevel>=2) OR (VersionNT >= 502 AND 
ServicePackLevel>=1) OR (VersionNT>502)





Installed OR NETFRAMEWORK30












































  

  
  








NEWPRODUCTFOUND



NOT 
REMOVE="ALL"




NEWPRODUCTFOUND






-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] prevent an old package from installing not working

[Lucius Fleuchaus]

That would not work since it would also prevent upgrading to newer versions, 
which I like allow by having installer uninstall automatically the older 
version.


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Karthik Krishnan
Sent: Monday, July 21, 2008 8:41 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] prevent an old package from installing not working

Your [EMAIL PROTECTED] is set to "*" meaning that it is autogenerated every 
time.
If you set this to a static value, perhaps passed it in as a var the same
way you do the UpgradeCode, Windows Installer should throw an error saying
that another version of the same product is installed. Is this what you are
trying to do?

K

On Sat, Jul 19, 2008 at 1:41 PM, Lucius Fleuchaus <[EMAIL PROTECTED]>
wrote:

> I am following the instructions given at
> http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-part-8-major-upgrade.aspxand
> http://msdn.microsoft.com/en-us/library/aa370840(VS.85).aspxto
>  prevent an old package from installing.  Below is the WIX file with the
> yellow highlight the additional steps I added.  However, it does not work.
>  It still installs resulting in a second entry in Add/Remove programs.  Can
> someone see what is wrong?  I am using WIX v3.0.3907.0.  Thanks.



>
>Id="*"













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










(VersionNT >= 501 AND ServicePackLevel>=2) OR (VersionNT >= 502 AND 
ServicePackLevel>=1) OR (VersionNT>502)





Installed OR NETFRAMEWORK30












































  

  
  








NEWPRODUCTFOUND



NOT 
REMOVE="ALL"




NEWPRODUCTFOUND






-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Localization filename change

[Ilya Slobodin]

Neil,

Nothing fundamental, the idea is great and I hope the next step will 
be the MsBuild task for language transforms.

My opposition is based on general considerations on how the new builds 
of applications should work. I think that the new build is good when I 
do not need to tweak my scripts until I need the new functions in that 
build. What's why I call this a break of compatibility.

Best regards,
Ilya Slobodin


- Original Message - 
From: "Neil Enns" <[EMAIL PROTECTED]>
To: "General discussion for Windows Installer XML toolset." 

Sent: Monday, July 21, 2008 8:07 PM
Subject: Re: [WiX-users] Localization filename change


> Ilya,
>
> Thanks for the additional insight into how your builds work. A 
> follow-up question: is there something fundamental in the new 
> localization work that doesn't integrate into your builds, or is the 
> issue that the change to either a suffix or directory will require 
> tweaks to your existing build process to integrate properly? For 
> what it's worth, when I integrated this build of WiX into my own 
> team we had to make a few build process tweaks as well.
>
> Neil
>
> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Ilya 
> Slobodin
> Sent: Monday, July 21, 2008 8:30 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Localization filename change
>
> Hi Neil,
>
> We use at least two builds of WiX at the same time. Newer builds on
> the development computers and older and well-tested on the 
> production
> server. And we upgrade the server only when we need to use some new
> functions. Before each upgrade we have to make sure that all our
> setups are not broken.
>
> For our environment, the output into subdirectories is better than
> culture suffix but this still is not as flexible as It could be.
>
> Is it possible to replace the proposed
>
> $(TargetDir)\CultureName\$(TargetName)$(TargetExt).
>
> with
>
> $(TargetDir)\$(CultureSuffix)\$(TargetName)$(TargetExt)
>
> where CultureSuffix is overridable and is empty by default when 
> single
> culture is used?
>
> Or, even better, put
> $(TargetDir)\$(CultureSuffix)\$(TargetName)$(TargetExt) into the
> overridable property, say TargetDirLocalized.
>
> Best regards,
> Ilya Slobodin
>
> - Original Message -
> From: "Neil Enns" <[EMAIL PROTECTED]>
> To: "General discussion for Windows Installer XML toolset."
> 
> Sent: Monday, July 21, 2008 6:18 PM
> Subject: Re: [WiX-users] Localization filename change
>
>
>> Ilya,
>>
>> If we changed things so the localized output went into
>> subdirectories, rather than modified the name of the MSI, would 
>> htat
>> work for your situation?
>> Neil
>>
>> 
>> From: [EMAIL PROTECTED]
>> [EMAIL PROTECTED] On Behalf Of Ilya 
>> Slobodin
>> [EMAIL PROTECTED]
>> Sent: Monday, July 21, 2008 1:59 AM
>> To: General discussion for Windows Installer XML toolset.
>> Subject: Re: [WiX-users] Localization filename change
>
>
>
> -
> This SF.Net email is sponsored by the Moblin Your Move Developer's 
> challenge
> Build the coolest Linux based applications with Moblin SDK & win 
> great prizes
> Grand prize is a trip for two to an Open Source event anywhere in 
> the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> -
> This SF.Net email is sponsored by the Moblin Your Move Developer's 
> challenge
> Build the coolest Linux based applications with Moblin SDK & win 
> great prizes
> Grand prize is a trip for two to an Open Source event anywhere in 
> the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 



-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Localization filename change

[Neil Enns]

Ilya,

Thanks for the additional insight into how your builds work. A follow-up 
question: is there something fundamental in the new localization work that 
doesn't integrate into your builds, or is the issue that the change to either a 
suffix or directory will require tweaks to your existing build process to 
integrate properly? For what it's worth, when I integrated this build of WiX 
into my own team we had to make a few build process tweaks as well.

Neil

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ilya Slobodin
Sent: Monday, July 21, 2008 8:30 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Localization filename change

Hi Neil,

We use at least two builds of WiX at the same time. Newer builds on
the development computers and older and well-tested on the production
server. And we upgrade the server only when we need to use some new
functions. Before each upgrade we have to make sure that all our
setups are not broken.

For our environment, the output into subdirectories is better than
culture suffix but this still is not as flexible as It could be.

Is it possible to replace the proposed

$(TargetDir)\CultureName\$(TargetName)$(TargetExt).

with

$(TargetDir)\$(CultureSuffix)\$(TargetName)$(TargetExt)

where CultureSuffix is overridable and is empty by default when single
culture is used?

Or, even better, put
$(TargetDir)\$(CultureSuffix)\$(TargetName)$(TargetExt) into the
overridable property, say TargetDirLocalized.

Best regards,
Ilya Slobodin

- Original Message -
From: "Neil Enns" <[EMAIL PROTECTED]>
To: "General discussion for Windows Installer XML toolset."

Sent: Monday, July 21, 2008 6:18 PM
Subject: Re: [WiX-users] Localization filename change


> Ilya,
>
> If we changed things so the localized output went into
> subdirectories, rather than modified the name of the MSI, would htat
> work for your situation?
> Neil
>
> 
> From: [EMAIL PROTECTED]
> [EMAIL PROTECTED] On Behalf Of Ilya Slobodin
> [EMAIL PROTECTED]
> Sent: Monday, July 21, 2008 1:59 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Localization filename change



-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] prevent an old package from installing not working

[Karthik Krishnan]

Your [EMAIL PROTECTED] is set to "*" meaning that it is autogenerated every 
time.
If you set this to a static value, perhaps passed it in as a var the same
way you do the UpgradeCode, Windows Installer should throw an error saying
that another version of the same product is installed. Is this what you are
trying to do?

K

On Sat, Jul 19, 2008 at 1:41 PM, Lucius Fleuchaus <[EMAIL PROTECTED]>
wrote:

> I am following the instructions given at
> http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-part-8-major-upgrade.aspxand
> http://msdn.microsoft.com/en-us/library/aa370840(VS.85).aspxto
>  prevent an old package from installing.  Below is the WIX file with the
> yellow highlight the additional steps I added.  However, it does not work.
>  It still installs resulting in a second entry in Add/Remove programs.  Can
> someone see what is wrong?  I am using WIX v3.0.3907.0.  Thanks.



>
>Id="*"
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Localization filename change

[Ilya Slobodin]

Hi Neil,

We use at least two builds of WiX at the same time. Newer builds on 
the development computers and older and well-tested on the production 
server. And we upgrade the server only when we need to use some new 
functions. Before each upgrade we have to make sure that all our 
setups are not broken.

For our environment, the output into subdirectories is better than 
culture suffix but this still is not as flexible as It could be.

Is it possible to replace the proposed

$(TargetDir)\CultureName\$(TargetName)$(TargetExt).

with

$(TargetDir)\$(CultureSuffix)\$(TargetName)$(TargetExt)

where CultureSuffix is overridable and is empty by default when single 
culture is used?

Or, even better, put 
$(TargetDir)\$(CultureSuffix)\$(TargetName)$(TargetExt) into the 
overridable property, say TargetDirLocalized.

Best regards,
Ilya Slobodin

- Original Message - 
From: "Neil Enns" <[EMAIL PROTECTED]>
To: "General discussion for Windows Installer XML toolset." 

Sent: Monday, July 21, 2008 6:18 PM
Subject: Re: [WiX-users] Localization filename change


> Ilya,
>
> If we changed things so the localized output went into 
> subdirectories, rather than modified the name of the MSI, would htat 
> work for your situation?
> Neil
>
> 
> From: [EMAIL PROTECTED] 
> [EMAIL PROTECTED] On Behalf Of Ilya Slobodin 
> [EMAIL PROTECTED]
> Sent: Monday, July 21, 2008 1:59 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Localization filename change



-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] ConfigureUsers Custom Action scheduling

[Dana Gutride]

Hi all:

We've encountered a problem where ConfigureUsers causes an uninstall to fail
if a domain user is used on install and they are not logged in to the domain
on uninstall.  I found this bug on the issue already:
https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1894167&group_id=105970.
We are already persisting the username/domain in the registry for use on
uninstall and upgrade so that solution doesn't help me.

Why can't we just schedule ConfigureUsers to NOT REMOVE so it doesn't ever
run on uninstall?  Is there anything it needs to do on uninstall that
requires it?  I am setting a user on a WebAppPool, a service, message queues
and some directory and registry permissions, too and when testing this
theory, the uninstall was fine.

Dana
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Localization filename change

[Neil Enns]

Thanks for the feedback Dominik. You're correct, there's no way to do count 
tests against items in an itemgroup using MSBuild.

One option I'm exploring is to modify the WiXAssignCultures task to supply that 
information.

Neil


From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Dominik Guder [EMAIL 
PROTECTED]
Sent: Monday, July 21, 2008 12:23 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Localization filename change




Neil Enns wrote:
>
> While Rob wasn't part of the change, I was :)
>
> I'm looking for feedback on how to best approach tweaking this. One option
> that's been suggested is to not rename the MSI file, and to instead put
> them into subdirectories. So on a build you'd have
> $(TargetDir)\CultureName\$(TargetName)$(TargetExt).
>
> Would that work better for people? For those of you that commented on the
> original issue at the tracker below, do your projects have multiple
> languages in them? Or do you just have a single language in the project?
>
> Neil
>
>

Hi Neil,

I think there is no single way to do fit in all circumstances.
Adding the culture makes sense, if you really use it to provide msi files
for multiple cultures. Also the directory would help.
But in case of a single culture there should be a way to handle this without
culture in filename.
I took a short look and I couldn't find a masbuild way to determine if a
itemgroup contains only one
item. So maybe the culture dialog/light should be extendend to use another
property like "single culture" or "create *.culture.msi" to handle this
issue.

Regards Dominik
--
View this message in context: 
http://www.nabble.com/Localization-filename-change-tp18527119p18563392.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Localization filename change

[Neil Enns]

Ilya,

If we changed things so the localized output went into subdirectories, rather 
than modified the name of the MSI, would htat work for your situation?
Neil


From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Ilya Slobodin [EMAIL 
PROTECTED]
Sent: Monday, July 21, 2008 1:59 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Localization filename change

Hi Bob, Rob, Neil and others,

Sorry for being so emotional, I really appreciate your work for the
WiX project.

>From my point of view the best approach is overridability, and
backward compatibility when possible. So, I fully agree with Dominik's
position.

Our projects have multiple languages that are build into different
subdirectories by custom scripts. That's why I was pleased to see the
new multi-language-build feature and then I was slightly dissapointed
that I cannot override the output name and fit into my existing
environment. Anyway, such minor inconsitencies are usual for a growing
project.

Best regards,
Ilya Slobodin



-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Reg: WixLib

[Natarajan, Thangaraj (MLITS)]

Hi All,

 I want to know how to create Wixlib Files and also how to reference it
in Visual Studio?

Thanks,
Thangaraj Natarajan
Associate Consultant.GWMT (CAI)
=
Merrill Lynch India Tech Service Pvt Ltd.,
GWMT (CAI) Framework Technologies



This message w/attachments (message) may be privileged, confidential or 
proprietary, and if you are not an intended recipient, please notify the 
sender, do not use or share it and delete it. Unless specifically indicated, 
this message is not an offer to sell or a solicitation of any investment 
products or other financial product or service, an official confirmation of any 
transaction, or an official statement of Merrill Lynch. Subject to applicable 
law, Merrill Lynch may monitor, review and retain e-communications (EC) 
traveling through its networks/systems. The laws of the country of each 
sender/recipient may impact the handling of EC, and EC may be archived, 
supervised and produced in countries other than the country in which you are 
located. This message cannot be guaranteed to be secure or error-free. This 
message is subject to terms available at the following link: 
http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you 
consent to the foregoing.

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Localization filename change

[Ilya Slobodin]

Hi Bob, Rob, Neil and others,

Sorry for being so emotional, I really appreciate your work for the 
WiX project.

>From my point of view the best approach is overridability, and 
backward compatibility when possible. So, I fully agree with Dominik's 
position.

Our projects have multiple languages that are build into different 
subdirectories by custom scripts. That's why I was pleased to see the 
new multi-language-build feature and then I was slightly dissapointed 
that I cannot override the output name and fit into my existing 
environment. Anyway, such minor inconsitencies are usual for a growing 
project.

Best regards,
Ilya Slobodin 



-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Merge Module Help

[Neil Sleightholm]

James
 
I haven't been following this thread in detail but I read the "wixlib" bit and 
thought I might be able to help. I have been doing quite a lot with them 
recently and have found them to be an excellent replacement of merge modules 
(assuming the consumer is using WiX). Let me know if you need more details on 
how to create and use them - I am hoping to document this soon for the WiX help 
file.
 
Neil
 
Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED]  
 



From: [EMAIL PROTECTED] on behalf of James Minnis
Sent: Sat 19/07/2008 21:11
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Merge Module Help



Based on what people said in earlier messages, I'm migrating to using a
wixlib with a fragment generated by Heat.  A lack of samples or useful
documentation had left me doing trial and error to figure how.

If you think that there is a better method, please let me know what it is.
:)

-Jamey

[EMAIL PROTECTED]

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:wix-users-
> [EMAIL PROTECTED] On Behalf Of Bob Arnson
> Sent: Saturday, July 19, 2008 10:22 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Merge Module Help
>
> James Minnis wrote:
> > Right now, I'm generating a merge module
>
> Do you have a specific need for a merge module? (i.e., are you sharing
> it with others so they can create installers?) If not, avoid merge
> modules. They needlessly complicate things, as you're finding out with #1.
>
> > 1) I want to create shortcuts to several of the files in the merge
> module.
> > I'm doing this currently in a start menu shortcuts component in the main
> > installer.  However, I cannot figure out how to reference the
> directories in
> > the merge module in the main project (I get an empty string when I try
> to
> > reference them like I do the directories in the main installer project).
> > How do I reference the directories?  Or is there a better way to do
> this?
> >
>
> You can't. Merge modules are supposed to be self-contained, so if you
> want shortcuts, define them in the merge module. Or don't use merge
> modules.
>
> > 2) The components in the merge module are generated with GUIDs.  If I
> > regenerate the merge module WXS file using Heat (e.g. if I add files),
> those
> > GUIDs change.  How will this affect patches?  Will the patch recognize
> the
> > files as being the same, or will it consider all of the files changed
> and
> > overwrite everything?  Will I need to add files manually to the merge
> module
> > WXS file to make patching work correctly?
> >
>
> You won't be able to patch. The WiX approach is to use stable GUIDs
> (heat's -ag switch). But with 7000 files, that's going to cause some
> long pauses during costing.
>
> --
> sig://boB
> http://joyofsetup.com/
>
>
>
> -
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Localization filename change

[Dominik Guder]

Neil Enns wrote:
> 
> While Rob wasn't part of the change, I was :)
> 
> I'm looking for feedback on how to best approach tweaking this. One option
> that's been suggested is to not rename the MSI file, and to instead put
> them into subdirectories. So on a build you'd have
> $(TargetDir)\CultureName\$(TargetName)$(TargetExt).
> 
> Would that work better for people? For those of you that commented on the
> original issue at the tracker below, do your projects have multiple
> languages in them? Or do you just have a single language in the project?
> 
> Neil
> 
> 

Hi Neil,

I think there is no single way to do fit in all circumstances.
Adding the culture makes sense, if you really use it to provide msi files
for multiple cultures. Also the directory would help. 
But in case of a single culture there should be a way to handle this without
culture in filename.
I took a short look and I couldn't find a masbuild way to determine if a
itemgroup contains only one 
item. So maybe the culture dialog/light should be extendend to use another
property like "single culture" or "create *.culture.msi" to handle this
issue.

Regards Dominik
-- 
View this message in context: 
http://www.nabble.com/Localization-filename-change-tp18527119p18563392.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users