Re: [WiX-users] Patch build with GAC update
I'm afraid I have only ever done this as a major upgrade, I don't think it should matter. But would I have to change the version number for the major upgrd? All we have is a minor change to one of the assemblies and this assembly could be used to host a strongly typed remoting object. if I change the version I will have to update the client configuratio with the latest version number, that is the reason we dont change the assembly version, we make sure the changes we do is compatible with the old version. did you mean an upgrade which re-installs whole system? -- View this message in context: http://www.nabble.com/Patch-build-with-GAC-update-tp17880093p17960954.html Sent from the wix-users mailing list archive at Nabble.com. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] self-registering
I'm trying to package a legacy program that registers some third-party ocx and dlls. I see that the consensus is that I should be handling this with a registry component. However, this application's 'installer' just copies stuff into a folder off the root of c:\ and runs a 'register.bat' to regsvr32 /s each necessary item. In this case, is there really any downside to making the files self-register? For me the real problems with self-registration came when my components had dependencies on C++ runtimes, that were not available at the point at which I was trying to run the self-registration. Regards, John - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MSBuild inside Wix development
May be I am not getting.. Please guide me .. Given below is my situation.. - We have completed MSBuild based batch files to complete the number of task to build developer assemblies, Build biztalk assemblies, Deploying Biztalk assemblies inside the Biztalk server. - Now we want to package all these MSBuild based stuff into Wix package to acheive the same functionality inside the Wix. - I am assuming Inside the Wix I can call the Cmd.. BuildDevAssmblies.bat . something like this so that it will call the batch file so that all the MSBuild functionality acheived inside the Wix. - When I am trying to call the Custom Action Command prompt inside the Wix it is not working.. - Am I missing something very obivous.. ?? Is my approach is correct ?? Can I get more guidance to complete my task. Thanks in advance. Cheers Raj On Wed, Jun 18, 2008 at 8:34 AM, Chris Mumford [EMAIL PROTECTED] wrote: You don't want to call MSBuild *from* WiX. Instead you want to mave MSBuild call WiX. Attached is my MSBuild project file that calls candle.exe and light.exe to build an MSI file. You can see that I have the path to the WiX bin folder hard-coded (and my machine is x64). So as an improvement you could use the MSBuild Community Tasks (http://msbuildtasks.tigris.org/) to read the registry (via RegistryRead) to dynamically determine the install location of WiX. Hope this helps. -Chris On Tue, Jun 17, 2008 at 1:08 AM, Krishnan Senthilraj [EMAIL PROTECTED] wrote: Hi, I am new to Wix and MSBuild area. I have one fundamental quention. I completed all the building of my application in MSBuild. Now I am writing Wix construction. I was under impressing we can call the MSBuild project inside Wix. I am trying examples for this. But unfortunately I didn't get that. So I would like to confirm with this group that *Is it possible and workable solution to call the MSBuild project inside the Wix?* If answer is yes then please give some links/direction to acheive the same. Cheers Senthilraj - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MSBuild inside Wix development
Thank you very much Chris, that helped a lot. I have been successfully using MSBuild to build the installers, but your solution is cleaner. Best regards, Mello -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Mumford Sent: quarta-feira, 18 de junho de 2008 00:05 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] MSBuild inside Wix development You don't want to call MSBuild *from* WiX. Instead you want to mave MSBuild call WiX. Attached is my MSBuild project file that calls candle.exe and light.exe to build an MSI file. You can see that I have the path to the WiX bin folder hard-coded (and my machine is x64). So as an improvement you could use the MSBuild Community Tasks (http://msbuildtasks.tigris.org/) to read the registry (via RegistryRead) to dynamically determine the install location of WiX. Hope this helps. -Chris On Tue, Jun 17, 2008 at 1:08 AM, Krishnan Senthilraj [EMAIL PROTECTED] wrote: Hi, I am new to Wix and MSBuild area. I have one fundamental quention. I completed all the building of my application in MSBuild. Now I am writing Wix construction. I was under impressing we can call the MSBuild project inside Wix. I am trying examples for this. But unfortunately I didn't get that. So I would like to confirm with this group that *Is it possible and workable solution to call the MSBuild project inside the Wix?* If answer is yes then please give some links/direction to acheive the same. Cheers Senthilraj -- --- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Preservation of .net settings?
Thanks for the quick reply. This does exactly what I wanted. After testing it
out, I have another question. After the upgrade, the old settings file is still
there. How do I remove the folder and the settings file for the last version?
Also, is it possible to remove the settings folder in the user's $APPDATA%
folder on an uninstall, but not when doing an upgrade?
Thanks,
Ryan
Date: Wed, 18 Jun 2008 12:39:54 +1000 From: [EMAIL PROTECTED] To:
wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Preservation of
.net settings? The Settings class has an Upgrade method that grabs the
previous settings. Make sure you add your own setting SettingsUpdateRequired
that is defaultly set to true, otherwise this will overwrite your settings
each time you start your program. static class Program { /// summary
/// The main entry point for the application. /// /summary [STAThread]
static void Main() { Application.EnableVisualStyles();
Application.SetCompatibleTextRenderingDefault(false); // Get the settings
from a previous version if we can if
(Properties.Settings.Default.SettingsUpdateRequired) {
Properties.Settings.Default.Upgrade();
Properties.Settings.Default.SettingsUpdateRequired = false; }
Application.Run(new MainForm()); } } Regards, Ross. -Original
Message- From: [EMAIL PROTECTED]
ourceforge.net [mailto:[EMAIL PROTECTED] On Behalf Of Ryan Dunn Sent:
Wednesday, 18 June 2008 11:35 AM To: wix-users@lists.sourceforge.net Subject:
[WiX-users] Preservation of .net settings? I have a WiX project used to
install a .net app. The app makes use of the Properties of .net to store
settings. These settings go in %APPDATA%\Path\to\dir\version\user.config
After I rev the version (either through a small patch, minor upgrade, major
upgrade), how do I pull in these settings to be used by the new app? I'm not
sure if this should be handled by the installer or my program. Within the .net
app, I only access these settings through the Properties.* namespace, not by
the path, so I'm unsure how to handle this issue. Thanks, Ryan
_ The other
season of giving begins 6/24/08. Check out the i'm Talkathon.
http://www.imtalkathon.com?source=TXT_EML_WLH_SeasonOfGiving
-
Check out the new SourceForge.net Marketplace. It's the best place to buy or
sell services for just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___ WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
Check out the new SourceForge.net Marketplace. It's the best place to buy or
sell services for just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___ WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
_
Need to know now? Get instant answers with Windows Live Messenger.
http://www.windowslive.com/messenger/connect_your_way.html?ocid=TXT_TAGLM_WL_Refresh_messenger_062008
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] CreateFolder and CopyFile elements
Hi, I have stored in a property a path where I need to create a folder and afterwards copy in it some files. I've played a bit with the CreateFolder element, but I don't know how to parse the information stored in my property to correctly create the directory. I've also tried to use the CopyFile element, but I've been unable to move the file copied in the INSTALLOCATION to my desired new location stored in the property. That's a code snippet of what I try, but seems that I couldn't specify the Delete attribute if the FileId is defined : Component... File Id=TestFile Name=test.txt Source=test.txt Vital='yes' DiskId='1' / CopyFile Id=copyFile FileId=TestFile Delete=yes DestinationProperty=[COPY_FOLDER]/ ... /Component How could this be achieved? There are some samples? Another problem is that my installer have to copy a bunch of files to diferent folders (not all to the INSTALLLOCATION path), and I'm not sure how to achieve this. The better way would be defining diferent modules or fragments in diferent wix files? Or it would exist a better option? Thanks in advance. -- Regards, *Natxo Mateos* [EMAIL PROTECTED] *Asuni CAD* - _www.asuni.es http://www.asuni.es_ - 93 319 6868 - 91 541 6439 *Especialistas en el desarrollo de aplicaciones a medida sobre AutoCAD* - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installation on Vista
Hi Bob,
Thank your for pointing this out and helping me to clarify things.
Cheers Volker
Bob Arnson wrote:
Volker Enderlein wrote:
this way). The installer is started without elevation and defaults to an
per-user installation. Later the user/admin can change the preselection
in the GUI to an per-machine installation. And if he presses the install
button Vista UAC prompts for elevation.
All I do is set the ALLUSERS Property for a per-user installation to
{} and for a per-machine installation to 1. When running without GUI
it defaults to 2.
Vista always starts packages without elevation. Unless you use
Package/@InstallPrivileges=limited or Package/@InstallScope=perUser
MSI will prompt for elevation when the user clicks the final Install
button that kicks off the installation. That's regardless of the
ALLUSERS value.
--
Volker Enderlein
Tel: +49 (0)371 53119651 Institut für Mechatronik
Fax: +49 (0)371 53119699 Reichenhainer Strasse 88
email: [EMAIL PROTECTED] D-09126 Chemnitz
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] upgrade shortcut
Hi, I am doing a major upgrade and the Start Menu/Programs/OldEntry folder is not removed. I would like to keep the OldEntry, but now, both OldEntry and NewEntry exist in the Programs folder. Any ideas as to why is the delete shortcuts action inhibited? Best regards, Calin PS. The intention is to have the upgrade process keep the old entries and paths. The new upgrade should use new names where applicable. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Patch build with GAC update
I wasn't suggesting you had to do a major update only that that was all I had done. Have you tried enabling the logs during the install to see what it says when it tried to install the file? Neil Neil Sleightholm X2 Systems Limited [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] From: [EMAIL PROTECTED] on behalf of wixuser1105 Sent: Wed 18/06/2008 08:05 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Patch build with GAC update I'm afraid I have only ever done this as a major upgrade, I don't think it should matter. But would I have to change the version number for the major upgrd? All we have is a minor change to one of the assemblies and this assembly could be used to host a strongly typed remoting object. if I change the version I will have to update the client configuratio with the latest version number, that is the reason we dont change the assembly version, we make sure the changes we do is compatible with the old version. did you mean an upgrade which re-installs whole system? -- View this message in context: http://www.nabble.com/Patch-build-with-GAC-update-tp17880093p17960954.html Sent from the wix-users mailing list archive at Nabble.com. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WiX and Support Information in Add or Remove Programs panel
Hi all,
If I set version number like this:
Product Name=XXX 7.5.6.001' Id='{BB52FB21-F007-40ef-A73E-6717AE770446}'
Language='1033' Codepage='1252' Version='*7.5.6.001*' Manufacturer='XXX,
Inc.'
UpgradeCode='ebb5dec0-edce-4531-9d2b-668c8a7e0ba7'
after installation process in support information I see version without
leading zeroes - *7.5.6.1*
Can somebody explain how to leave leading zeroes?
--
Thanks,
Max
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX and Support Information in Add or Remove Programs panel
You can't, assembly version numbers are stored as numbers by the OS, so leading
zeros are stripped.
Neil
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Maxim Vyazovsky
Sent: Wednesday, June 18, 2008 8:31 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] WiX and Support Information in Add or Remove Programs
panel
Hi all,
If I set version number like this:
Product Name=XXX 7.5.6.001' Id='{BB52FB21-F007-40ef-A73E-6717AE770446}'
Language='1033' Codepage='1252' Version='*7.5.6.001*' Manufacturer='XXX,
Inc.'
UpgradeCode='ebb5dec0-edce-4531-9d2b-668c8a7e0ba7'
after installation process in support information I see version without
leading zeroes - *7.5.6.1*
Can somebody explain how to leave leading zeroes?
--
Thanks,
Max
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX and Support Information in Add or Remove Programs panel
hm,
http://i.piccy.kiev.ua/i2/45/c7/aea71120584104c1c6b99d3ba93e.jpeg
what about this?
On Wed, Jun 18, 2008 at 7:01 PM, Neil Enns [EMAIL PROTECTED] wrote:
You can't, assembly version numbers are stored as numbers by the OS, so
leading zeros are stripped.
Neil
-Original Message-
From: [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] On Behalf Of Maxim Vyazovsky
Sent: Wednesday, June 18, 2008 8:31 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] WiX and Support Information in Add or Remove
Programs panel
Hi all,
If I set version number like this:
Product Name=XXX 7.5.6.001 http://7.5.6.1/'
Id='{BB52FB21-F007-40ef-A73E-6717AE770446}'
Language='1033' Codepage='1252' Version='*7.5.6.001 http://7.5.6.1/*'
Manufacturer='XXX,
Inc.'
UpgradeCode='ebb5dec0-edce-4531-9d2b-668c8a7e0ba7'
after installation process in support information I see version without
leading zeroes - *7.5.6.1*
Can somebody explain how to leave leading zeroes?
--
Thanks,
Max
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Thanks,
Max
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX and Support Information in Add or Remove Programs panel
No idea how they did that. The second one isn't even a valid Windows file
version number. It must be a text string that comes from somewhere else,
although the Windows Installer property reference doesn't list any properties
for the version number.
Neil
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Maxim Vyazovsky
Sent: Wednesday, June 18, 2008 9:13 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiX and Support Information in Add or Remove
Programs panel
hm,
http://i.piccy.kiev.ua/i2/45/c7/aea71120584104c1c6b99d3ba93e.jpeg
what about this?
On Wed, Jun 18, 2008 at 7:01 PM, Neil Enns [EMAIL PROTECTED] wrote:
You can't, assembly version numbers are stored as numbers by the OS, so
leading zeros are stripped.
Neil
-Original Message-
From: [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] On Behalf Of Maxim Vyazovsky
Sent: Wednesday, June 18, 2008 8:31 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] WiX and Support Information in Add or Remove
Programs panel
Hi all,
If I set version number like this:
Product Name=XXX 7.5.6.001 http://7.5.6.1/'
Id='{BB52FB21-F007-40ef-A73E-6717AE770446}'
Language='1033' Codepage='1252' Version='*7.5.6.001 http://7.5.6.1/*'
Manufacturer='XXX,
Inc.'
UpgradeCode='ebb5dec0-edce-4531-9d2b-668c8a7e0ba7'
after installation process in support information I see version without
leading zeroes - *7.5.6.1*
Can somebody explain how to leave leading zeroes?
--
Thanks,
Max
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Thanks,
Max
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX and Support Information in Add or Remove Programs panel
question of the century :)
the same situation with Orca, it has version 3.1.3790., and all zeroes
are shown in the support info.
i decompiled Orca with dark.exe and can see that:
Product Id={85F4CBCB-9BBC-4B50-A7D8-E1106771498D} Language=1033
Manufacturer=Microsoft Corporation Name=Orca
UpgradeCode={1AA03E10-2B19-11D2-B2EA-006097C99860} Version=*3.1.3790.
*
so, if somebody knows the solution, please share it ;)
On Wed, Jun 18, 2008 at 7:22 PM, Neil Enns [EMAIL PROTECTED] wrote:
No idea how they did that. The second one isn't even a valid Windows file
version number. It must be a text string that comes from somewhere else,
although the Windows Installer property reference doesn't list any
properties for the version number.
Neil
-Original Message-
From: [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] On Behalf Of Maxim Vyazovsky
Sent: Wednesday, June 18, 2008 9:13 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiX and Support Information in Add or Remove
Programs panel
hm,
http://i.piccy.kiev.ua/i2/45/c7/aea71120584104c1c6b99d3ba93e.jpeg
what about this?
On Wed, Jun 18, 2008 at 7:01 PM, Neil Enns [EMAIL PROTECTED]
wrote:
You can't, assembly version numbers are stored as numbers by the OS, so
leading zeros are stripped.
Neil
-Original Message-
From: [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] On Behalf Of Maxim Vyazovsky
Sent: Wednesday, June 18, 2008 8:31 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] WiX and Support Information in Add or Remove
Programs panel
Hi all,
If I set version number like this:
Product Name=XXX 7.5.6.001 http://7.5.6.1/ http://7.5.6.1/'
Id='{BB52FB21-F007-40ef-A73E-6717AE770446}'
Language='1033' Codepage='1252' Version='*7.5.6.001 http://7.5.6.1/
http://7.5.6.1/*'
Manufacturer='XXX,
Inc.'
UpgradeCode='ebb5dec0-edce-4531-9d2b-668c8a7e0ba7'
after installation process in support information I see version without
leading zeroes - *7.5.6.1*
Can somebody explain how to leave leading zeroes?
--
Thanks,
Max
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Thanks,
Max
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Thanks,
Max
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Question on Merge Modules
I have a program I need to install that won't work without the VC 9.0 redistributable package. Can I simply add the necessary merge modules and be done? Or is there more involved? - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Question on Merge Modules
Here's the info on how to do it from the new How To topic I wrote on this very topic that should show up in the next weekly WiX build: How To: Install the Visual C++ Redistributable with your installer If your application depends on the Visual C++ runtimes you can include them as part of your installer to simplify the installation experience for your end users. This how to describes including the Visual C++ runtime merge modules into your installer and explains the expected ICE warnings you will see. Step 1: Obtain the correct Visual C++ runtime merge modules The Visual C++ runtime merge modules are installed with Visual Studio and are located in \Program Files\Common Files\Merge Modules. The Visual C++ 8.0 runtime file is Microsoft_VC80_CRT_x86.msm. This same MSM is used for the Visual C++ 8.0 SP1 runtime, however it is updated in place by the Visual Studio 2005 SP1 installer. The Visual Studio 9.0 runtime file is Microsoft_VC90_CRT_x86.msm. There is generally no need to include the policy MSMs as part of the installation. Step 2: Include the merge module in your installer To include the merge module in your installer use the Merge and MergeRef elements. The following example illustrates how these elements are used. DirectoryRef Id=TARGETDIR Merge Id=VCRedist SourceFile=MySourceFiles\Microsoft_VC80_CRT_x86.msm DiskId=1 Language=0/ /DirectoryRef Feature Id=VCRedist Title=Visual C++ 8.0 Runtime AllowAdvertise=no Display=hidden Level=1 MergeRef Id=VCRedist/ /Feature The Merge element ensures the merge module is included in the final Windows Installer package. A unique id is assigned using the Id attribute. The SourceFile attribute points to the location of the merge module on your machine. The DiskId attribute should match the DiskId specified in your project's Media element. The Language attribute should always be 0. The MergeRef element is used within a Feature element to actually install the merge module. In the example above a feature specific to the runtime is created and marked as hidden to prevent it from displaying in any UI your installer may use. The MergeRef refers to the merge module by its unique id. A note about ICE warnings Including the Visual C++ Runtime merge module in your installer will result in the following ICE warnings: light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.762.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.100.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.101.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.103.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.104.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.193.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): reg_downlevel_manifest.8.0.50727.100.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): reg_downlevel_manifest.8.0.50727.101.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): reg_downlevel_manifest.8.0.50727.103.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): reg_downlevel_manifest.8.0.50727.104.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): reg_downlevel_manifest.8.0.50727.193.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): reg_downlevel_manifest.8.0.50727.762.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE25: Possible dependency failure as
Re: [WiX-users] Question on Merge Modules
Fixed a small wrapping issue below that made the code sample hard to read. Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Enns Sent: Wednesday, June 18, 2008 9:57 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Question on Merge Modules Here's the info on how to do it from the new How To topic I wrote on this very topic that should show up in the next weekly WiX build: How To: Install the Visual C++ Redistributable with your installer If your application depends on the Visual C++ runtimes you can include them as part of your installer to simplify the installation experience for your end users. This how to describes including the Visual C++ runtime merge modules into your installer and explains the expected ICE warnings you will see. Step 1: Obtain the correct Visual C++ runtime merge modules The Visual C++ runtime merge modules are installed with Visual Studio and are located in \Program Files\Common Files\Merge Modules. The Visual C++ 8.0 runtime file is Microsoft_VC80_CRT_x86.msm. This same MSM is used for the Visual C++ 8.0 SP1 runtime, however it is updated in place by the Visual Studio 2005 SP1 installer. The Visual Studio 9.0 runtime file is Microsoft_VC90_CRT_x86.msm. There is generally no need to include the policy MSMs as part of the installation. Step 2: Include the merge module in your installer To include the merge module in your installer use the Merge and MergeRef elements. The following example illustrates how these elements are used. DirectoryRef Id=TARGETDIR Merge Id=VCRedist SourceFile=MySourceFiles\Microsoft_VC80_CRT_x86.msm DiskId=1 Language=0/ /DirectoryRef Feature Id=VCRedist Title=Visual C++ 8.0 Runtime AllowAdvertise=no Display=hidden Level=1 MergeRef Id=VCRedist/ /Feature The Merge element ensures the merge module is included in the final Windows Installer package. A unique id is assigned using the Id attribute. The SourceFile attribute points to the location of the merge module on your machine. The DiskId attribute should match the DiskId specified in your project's Media element. The Language attribute should always be 0. The MergeRef element is used within a Feature element to actually install the merge module. In the example above a feature specific to the runtime is created and marked as hidden to prevent it from displaying in any UI your installer may use. The MergeRef refers to the merge module by its unique id. A note about ICE warnings Including the Visual C++ Runtime merge module in your installer will result in the following ICE warnings: light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.762.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.100.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.101.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.103.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.104.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.193.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): reg_downlevel_manifest.8.0.50727.100.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): reg_downlevel_manifest.8.0.50727.101.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): reg_downlevel_manifest.8.0.50727.103.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): reg_downlevel_manifest.8.0.50727.104.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s):
Re: [WiX-users] WiX and Support Information in Add orRemove Programs panel
Interesting! I am porting InstallShield project to Wix and I see that IS
keeps leading 0s.
-Original Message-
From: Neil Enns [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 18, 2008 12:23 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiX and Support Information in Add orRemove
Programs panel
No idea how they did that. The second one isn't even a valid Windows
file version number. It must be a text string that comes from somewhere
else, although the Windows Installer property reference doesn't list any
properties for the version number.
Neil
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Maxim
Vyazovsky
Sent: Wednesday, June 18, 2008 9:13 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiX and Support Information in Add or Remove
Programs panel
hm,
http://i.piccy.kiev.ua/i2/45/c7/aea71120584104c1c6b99d3ba93e.jpeg
what about this?
On Wed, Jun 18, 2008 at 7:01 PM, Neil Enns [EMAIL PROTECTED]
wrote:
You can't, assembly version numbers are stored as numbers by the OS,
so
leading zeros are stripped.
Neil
-Original Message-
From: [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] On Behalf Of Maxim Vyazovsky
Sent: Wednesday, June 18, 2008 8:31 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] WiX and Support Information in Add or Remove
Programs panel
Hi all,
If I set version number like this:
Product Name=XXX 7.5.6.001 http://7.5.6.1/'
Id='{BB52FB21-F007-40ef-A73E-6717AE770446}'
Language='1033' Codepage='1252' Version='*7.5.6.001
http://7.5.6.1/*'
Manufacturer='XXX,
Inc.'
UpgradeCode='ebb5dec0-edce-4531-9d2b-668c8a7e0ba7'
after installation process in support information I see version
without
leading zeroes - *7.5.6.1*
Can somebody explain how to leave leading zeroes?
--
Thanks,
Max
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Thanks,
Max
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Question on Merge Modules
Thanks Neil. Good information! On Wed, Jun 18, 2008 at 1:00 PM, Neil Enns [EMAIL PROTECTED] wrote: Fixed a small wrapping issue below that made the code sample hard to read. Neil -Original Message- From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] On Behalf Of Neil Enns Sent: Wednesday, June 18, 2008 9:57 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Question on Merge Modules Here's the info on how to do it from the new How To topic I wrote on this very topic that should show up in the next weekly WiX build: How To: Install the Visual C++ Redistributable with your installer If your application depends on the Visual C++ runtimes you can include them as part of your installer to simplify the installation experience for your end users. This how to describes including the Visual C++ runtime merge modules into your installer and explains the expected ICE warnings you will see. Step 1: Obtain the correct Visual C++ runtime merge modules The Visual C++ runtime merge modules are installed with Visual Studio and are located in \Program Files\Common Files\Merge Modules. The Visual C++ 8.0 runtime file is Microsoft_VC80_CRT_x86.msm. This same MSM is used for the Visual C++ 8.0 SP1 runtime, however it is updated in place by the Visual Studio 2005 SP1 installer. The Visual Studio 9.0 runtime file is Microsoft_VC90_CRT_x86.msm. There is generally no need to include the policy MSMs as part of the installation. Step 2: Include the merge module in your installer To include the merge module in your installer use the Merge and MergeRef elements. The following example illustrates how these elements are used. DirectoryRef Id=TARGETDIR Merge Id=VCRedist SourceFile=MySourceFiles\Microsoft_VC80_CRT_x86.msm DiskId=1 Language=0/ /DirectoryRef Feature Id=VCRedist Title=Visual C++ 8.0 Runtime AllowAdvertise=no Display=hidden Level=1 MergeRef Id=VCRedist/ /Feature The Merge element ensures the merge module is included in the final Windows Installer package. A unique id is assigned using the Id attribute. The SourceFile attribute points to the location of the merge module on your machine. The DiskId attribute should match the DiskId specified in your project's Media element. The Language attribute should always be 0. The MergeRef element is used within a Feature element to actually install the merge module. In the example above a feature specific to the runtime is created and marked as hidden to prevent it from displaying in any UI your installer may use. The MergeRef refers to the merge module by its unique id. A note about ICE warnings Including the Visual C++ Runtime merge module in your installer will result in the following ICE warnings: light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.762.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.100.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.101.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.103.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.104.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.193.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): reg_downlevel_manifest.8.0.50727.100.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): reg_downlevel_manifest.8.0.50727.101.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): reg_downlevel_manifest.8.0.50727.103.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): reg_downlevel_manifest.8.0.50727.104.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): warning LGHT1076:
Re: [WiX-users] WiX and Support Information in Add or Remove Programs panel
Thank you Alex,
dark doesn't insert asterisks in the version.
it's incorrect formatting, i wanted simply highlight version with bold in my
email client, but here
http://www.nabble.com/WiX-and-Support-Information-in-%22Add-or-Remove-Programs%22-panel-td17985802.htmli
see version between stars.
so do not pay attention on these asterisks.
On Wed, Jun 18, 2008 at 8:11 PM, Alexander Shevchuk
[EMAIL PROTECTED] wrote:
Well, according to *the source*:
- Version data type (
http://msdn.microsoft.com/en-us/library/aa372488(VS.85).aspx):
The Version data type is a text string containing a valid version string.
A version string has the format:
x.x.x.x
where x is a digit.
- ProductVersion property (
http://msdn.microsoft.com/en-us/library/aa370859(VS.85).aspx):
The value of the ProductVersion property is the version of the product in
string format.
The format of the string is as follows:
major.minor.build
Note that Windows Installer uses only the first three fields of the product
version. If you include a fourth field in your product version, the
installer ignores the fourth field.
Because MSDN does not say anything about stars in the version string, the
question really is - why dark.exe puts them in the Version attribute?
Alex
-Original Message-
From: [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] On Behalf Of Maxim Vyazovsky
Sent: Wednesday, June 18, 2008 9:29 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiX and Support Information in Add or Remove
Programs panel
question of the century :)
the same situation with Orca, it has version 3.1.3790., and all zeroes
are shown in the support info.
i decompiled Orca with dark.exe and can see that:
Product Id={85F4CBCB-9BBC-4B50-A7D8-E1106771498D} Language=1033
Manufacturer=Microsoft Corporation Name=Orca
UpgradeCode={1AA03E10-2B19-11D2-B2EA-006097C99860}
Version=*3.1.3790.
*
so, if somebody knows the solution, please share it ;)
On Wed, Jun 18, 2008 at 7:22 PM, Neil Enns [EMAIL PROTECTED]
wrote:
No idea how they did that. The second one isn't even a valid Windows file
version number. It must be a text string that comes from somewhere else,
although the Windows Installer property reference doesn't list any
properties for the version number.
Neil
-Original Message-
From: [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] On Behalf Of Maxim Vyazovsky
Sent: Wednesday, June 18, 2008 9:13 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiX and Support Information in Add or Remove
Programs panel
hm,
http://i.piccy.kiev.ua/i2/45/c7/aea71120584104c1c6b99d3ba93e.jpeg
what about this?
On Wed, Jun 18, 2008 at 7:01 PM, Neil Enns [EMAIL PROTECTED]
wrote:
You can't, assembly version numbers are stored as numbers by the OS, so
leading zeros are stripped.
Neil
-Original Message-
From: [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] On Behalf Of Maxim Vyazovsky
Sent: Wednesday, June 18, 2008 8:31 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] WiX and Support Information in Add or Remove
Programs panel
Hi all,
If I set version number like this:
Product Name=XXX 7.5.6.001 http://7.5.6.1/ http://7.5.6.1/
http://7.5.6.1/'
Id='{BB52FB21-F007-40ef-A73E-6717AE770446}'
Language='1033' Codepage='1252' Version='*7.5.6.001http://7.5.6.1/
http://7.5.6.1/
http://7.5.6.1/*'
Manufacturer='XXX,
Inc.'
UpgradeCode='ebb5dec0-edce-4531-9d2b-668c8a7e0ba7'
after installation process in support information I see version without
leading zeroes - *7.5.6.1*
Can somebody explain how to leave leading zeroes?
--
Thanks,
Max
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Thanks,
Max
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
Re: [WiX-users] WiX and Support Information in Add or Remove Programs panel
I see what you mean. I just did a quick test with product version set to 001.000.000.. When I opened msi with Orca, ProductVersion is set to 1.0.0.0. If I manually change the product version back to what I have in the WiX file than I can see all zeros in the ARP. So, it seems like it is WiX's problem. It changes ProductVersion by removing leading zeros. Alex -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Maxim Vyazovsky Sent: Wednesday, June 18, 2008 10:36 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX and Support Information in Add or Remove Programs panel Thank you Alex, dark doesn't insert asterisks in the version. it's incorrect formatting, i wanted simply highlight version with bold in my email client, but here http://www.nabble.com/WiX-and-Support-Information-in-%22Add-or-Remove-Programs%22-panel-td17985802.htmli see version between stars. so do not pay attention on these asterisks. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] file sequencing
Hello, I am facing a strange issue here and any help to figure out what is happening will be greatly appreciated. We released our product SP1 (build 6.0.6278.) and then started work on SP2 build after few builds I noticed the file sequencing has changed in the File table. Tracing back to old builds the number of files and sequence till SP2 build 6.0.6316 was exactly same as that released SP1 build, but the filesequence suddenly changed in build 6.0.6317, though the number of files were same in this build. Looking at our source code there has not been any change in the wix scripts ( no new files, removal of files, re-org or anything ) that could have affected the file ordering in File table. We are using Wix to build the MSIs (candle and light versions is 2.0.4409.0 ) Is there any reason why this sudden change of file ordering might have happened and any work around for this? (We did not either change the wix toolset between these builds.) Looking at the wix code base looks like the rows are created and maintained using ICollection typed object (for e.g. FileMediaInformationCollection) and I suspect either sorting mechanism in wix or .net implementation can affect this change in behavior (or I could be missing something here). As a result of this when we create a patch with delta between SP1 and SP2 it gives error 1334 during patch application. We faced this issue earlier and it was because we had mistakenly added files in existing mergemodule and in the same media; adding files to separate merge modules and on different media had restored the file sequencing. But this time we have not added any file to the MSI. Using patch group can preserve the file sequence but I read on this group that patch groups does not help for file sequencing in case we are using merge modules and we in this case I am using merge modules here. Any pointers to solve this or explaining how file sequencing works ( or if you can point to the code) would be greatly appreciated. Thanks, Sandip - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Patch build with GAC update
The way this works is that file version can be used to do an in-place update of the assembly in the GAC. An assembly's file version defaults to its .NET assembly version, but you can add an AssemblyFileVersion to give the assembly a file version that's different from the assembly version. The file version does not affect binding clients. The resulting MSI file will have a FileVersion row in the MsiAssemblyName table. I assume you'll need to make your new file version higher than your current assembly version (=file version) to replace your GAC assembly. Phil Wilson -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of wixuser1105 Sent: Wednesday, June 18, 2008 12:06 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Patch build with GAC update I'm afraid I have only ever done this as a major upgrade, I don't think it should matter. But would I have to change the version number for the major upgrd? All we have is a minor change to one of the assemblies and this assembly could be used to host a strongly typed remoting object. if I change the version I will have to update the client configuratio with the latest version number, that is the reason we dont change the assembly version, we make sure the changes we do is compatible with the old version. did you mean an upgrade which re-installs whole system? -- View this message in context: http://www.nabble.com/Patch-build-with-GAC-update-tp17880093p17960954.html Sent from the wix-users mailing list archive at Nabble.com. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Can't install Wix in VS 2008
I'm just trying out WiX and still have a lot to learn about Visual Studio so I may have made a stupid mistake here. I can't get WiX to appear under Visual Studio 2008 standard. I have Visual Studio 2005 and 2008 installed. It seems to work fine for 2005. When I did the initial install I was never prompted for options, it just installed the software. When I run the installer a second time and click the change button I do not see and VS 2008 options. I do see 2 VS 2005 entries. Is there something I need to do to get the installer to see 2008? Jon - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Patch build with GAC update
Just to add to what Phil Wilson wrote: The resulting MSI file will have a FileVersion row in the MsiAssemblyName table. Unless I am mistaken this will only be true if you use the -fv option to light. Neil Neil Sleightholm X2 Systems Limited [EMAIL PROTECTED] - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] file sequencing
Thanks Heath, but unfortunately wix 3.0 Patch does not seem to support patching files from MSMs ( http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg12785.html ) and going to wixlibs from MSM now means a complete overhaul of setup. I am pretty sure something has changed on our build system or in Wix code and debugging the light may give some idea.. Thanks and Regards, Sandip From: Heath Stewart Sent: Wednesday, June 18, 2008 1:17 PM To: Sandip Shahane; WiX-users@lists.sourceforge.net Cc: Anandha Ganesan Subject: RE: file sequencing I recommend using the new patching built into WiX v3. See the documentation for the Patch element. There’s also some examples of building a patch using this new infrastructure in wix.chm. In this case, maintaining file sequences doesn’t matter. Heath Stewart Deployment Technology Group, Microsoft http://blogs.msdn.com/heaths From: Sandip Shahane Sent: Wednesday, June 18, 2008 12:13 PM To: WiX-users@lists.sourceforge.net Cc: Heath Stewart; Anandha Ganesan Subject: file sequencing Hello, I am facing a strange issue here and any help to figure out what is happening will be greatly appreciated. We released our product SP1 (build 6.0.6278.) and then started work on SP2 build after few builds I noticed the file sequencing has changed in the File table. Tracing back to old builds the number of files and sequence till SP2 build 6.0.6316 was exactly same as that released SP1 build, but the filesequence suddenly changed in build 6.0.6317, though the number of files were same in this build. Looking at our source code there has not been any change in the wix scripts ( no new files, removal of files, re-org or anything ) that could have affected the file ordering in File table. We are using Wix to build the MSIs (candle and light versions is 2.0.4409.0 ) Is there any reason why this sudden change of file ordering might have happened and any work around for this? (We did not either change the wix toolset between these builds.) Looking at the wix code base looks like the rows are created and maintained using ICollection typed object (for e.g. FileMediaInformationCollection) and I suspect either sorting mechanism in wix or .net implementation can affect this change in behavior (or I could be missing something here). As a result of this when we create a patch with delta between SP1 and SP2 it gives error 1334 during patch application. We faced this issue earlier and it was because we had mistakenly added files in existing mergemodule and in the same media; adding files to separate merge modules and on different media had restored the file sequencing. But this time we have not added any file to the MSI. Using patch group can preserve the file sequence but I read on this group that patch groups does not help for file sequencing in case we are using merge modules and we in this case I am using merge modules here. Any pointers to solve this or explaining how file sequencing works ( or if you can point to the code) would be greatly appreciated. Thanks, Sandip - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] file sequencing
What version of the WiX toolset are you using? There are reports that changing the .NET Framework version changes the sort order in WiX v2. WiX v3 is not affected by this problem because the sorting algorithm was changed. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sandip Shahane Sent: Wednesday, June 18, 2008 16:00 To: Heath Stewart; WiX-users@lists.sourceforge.net Cc: Anandha Ganesan Subject: Re: [WiX-users] file sequencing Thanks Heath, but unfortunately wix 3.0 Patch does not seem to support patching files from MSMs ( http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg12785.html ) and going to wixlibs from MSM now means a complete overhaul of setup. I am pretty sure something has changed on our build system or in Wix code and debugging the light may give some idea.. Thanks and Regards, Sandip From: Heath Stewart Sent: Wednesday, June 18, 2008 1:17 PM To: Sandip Shahane; WiX-users@lists.sourceforge.net Cc: Anandha Ganesan Subject: RE: file sequencing I recommend using the new patching built into WiX v3. See the documentation for the Patch element. There’s also some examples of building a patch using this new infrastructure in wix.chm. In this case, maintaining file sequences doesn’t matter. Heath Stewart Deployment Technology Group, Microsoft http://blogs.msdn.com/heaths From: Sandip Shahane Sent: Wednesday, June 18, 2008 12:13 PM To: WiX-users@lists.sourceforge.net Cc: Heath Stewart; Anandha Ganesan Subject: file sequencing Hello, I am facing a strange issue here and any help to figure out what is happening will be greatly appreciated. We released our product SP1 (build 6.0.6278.) and then started work on SP2 build after few builds I noticed the file sequencing has changed in the File table. Tracing back to old builds the number of files and sequence till SP2 build 6.0.6316 was exactly same as that released SP1 build, but the filesequence suddenly changed in build 6.0.6317, though the number of files were same in this build. Looking at our source code there has not been any change in the wix scripts ( no new files, removal of files, re-org or anything ) that could have affected the file ordering in File table. We are using Wix to build the MSIs (candle and light versions is 2.0.4409.0 ) Is there any reason why this sudden change of file ordering might have happened and any work around for this? (We did not either change the wix toolset between these builds.) Looking at the wix code base looks like the rows are created and maintained using ICollection typed object (for e.g. FileMediaInformationCollection) and I suspect either sorting mechanism in wix or .net implementation can affect this change in behavior (or I could be missing something here). As a result of this when we create a patch with delta between SP1 and SP2 it gives error 1334 during patch application. We faced this issue earlier and it was because we had mistakenly added files in existing mergemodule and in the same media; adding files to separate merge modules and on different media had restored the file sequencing. But this time we have not added any file to the MSI. Using patch group can preserve the file sequence but I read on this group that patch groups does not help for file sequencing in case we are using merge modules and we in this case I am using merge modules here. Any pointers to solve this or explaining how file sequencing works ( or if you can point to the code) would be greatly appreciated. Thanks, Sandip - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX and Support Information in Add or Remove Programs panel
Yes, the version gets normalized down to numbers without extra zeroes. There are bugs in the Fusion processing of version where they incorrectly treat versions as strings and it was found that removing insignificant zeroes from a version string would avoid them. At least, that's what my memory is telling me. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alexander Shevchuk Sent: Wednesday, June 18, 2008 11:05 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX and Support Information in Add or Remove Programs panel I see what you mean. I just did a quick test with product version set to 001.000.000.. When I opened msi with Orca, ProductVersion is set to 1.0.0.0. If I manually change the product version back to what I have in the WiX file than I can see all zeros in the ARP. So, it seems like it is WiX's problem. It changes ProductVersion by removing leading zeros. Alex -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Maxim Vyazovsky Sent: Wednesday, June 18, 2008 10:36 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX and Support Information in Add or Remove Programs panel Thank you Alex, dark doesn't insert asterisks in the version. it's incorrect formatting, i wanted simply highlight version with bold in my email client, but here http://www.nabble.com/WiX-and-Support-Information-in-%22Add-or-Remove-Programs%22-panel-td17985802.htmli see version between stars. so do not pay attention on these asterisks. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] self-registering
MSI SDK has a list of reasons why SelfReg is evil. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of jeff sacksteder Sent: Tuesday, June 17, 2008 18:02 To: wix-users@lists.sourceforge.net Subject: [WiX-users] self-registering I'm trying to package a legacy program that registers some third-party ocx and dlls. I see that the consensus is that I should be handling this with a registry component. However, this application's 'installer' just copies stuff into a folder off the root of c:\ and runs a 'register.bat' to regsvr32 /s each necessary item. In this case, is there really any downside to making the files self-register? - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX and Support Information in Add or Remove Programs panel
Alexander Shevchuk wrote: So, it seems like it is WiX's problem. It changes ProductVersion by removing leading zeros. Please file a bug. The compiler core uses the Version class to validate version information; it parses the string down to their component integers, which loses the leading zeros. -- sig://boB http://joyofsetup.com/ - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Question about Control element
Amy Rosewater wrote: Schema validation failed with the following error: The element 'Control' in namespace 'http://schemas.microsoft.com/wix/2006/wi' has invalid child element 'Text' in namespace 'http://schemas.microsoft.com/wix/2006/wi'. List of possible elements expected: 'Condition Publish Subscribe'. in iVantageUI.wxs I'm pretty sure that it's a limitation in XSD schemas but please enter a bug so someone verifies that. -- sig://boB http://joyofsetup.com/ - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] upgrade shortcut
Calin Iaru wrote: I am doing a major upgrade and the Start Menu/Programs/OldEntry folder is not removed. I would like to keep the OldEntry, but now, both OldEntry and NewEntry exist in the Programs folder. Any ideas as to why is the delete shortcuts action inhibited? Check a verbose log around the RemoveShortcuts action invocations. -- sig://boB http://joyofsetup.com/ - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] BUG: Group cannot be added to component.
Adrian Lewis wrote: Not knowingly... Okay my extension has packaged the wixlib as an embedded resource (and the wixlib has the custom action binding - not forgetting the -bf switch to get it included in the build) is there somewhere else in the extension where I'm supposed to inform WiX that I need it? Yes. You need to add a reference to something that causes the fragment containing the custom action to be linked in. For example, the firewall compiler extension has the following: this.Core.CreateWixSimpleReferenceRow(sourceLineNumbers, CustomAction, WixSchedFirewallExceptionsInstall); this.Core.CreateWixSimpleReferenceRow(sourceLineNumbers, CustomAction, WixSchedFirewallExceptionsUninstall); The linker sees a reference to the custom action and uses the .wixlib as a source for it. -- sig://boB http://joyofsetup.com/ - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX and Support Information in Add or Remove Programs panel
Rob, This Fusion processing related to putting assemblies in GAC? What we are seeing is that the value of ProductVersion property is getting normalized, not assembly version. Alex -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: Wednesday, June 18, 2008 5:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX and Support Information in Add or Remove Programs panel Yes, the version gets normalized down to numbers without extra zeroes. There are bugs in the Fusion processing of version where they incorrectly treat versions as strings and it was found that removing insignificant zeroes from a version string would avoid them. At least, that's what my memory is telling me. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alexander Shevchuk Sent: Wednesday, June 18, 2008 11:05 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX and Support Information in Add or Remove Programs panel I see what you mean. I just did a quick test with product version set to 001.000.000.. When I opened msi with Orca, ProductVersion is set to 1.0.0.0. If I manually change the product version back to what I have in the WiX file than I can see all zeros in the ARP. So, it seems like it is WiX's problem. It changes ProductVersion by removing leading zeros. Alex -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Maxim Vyazovsky Sent: Wednesday, June 18, 2008 10:36 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX and Support Information in Add or Remove Programs panel Thank you Alex, dark doesn't insert asterisks in the version. it's incorrect formatting, i wanted simply highlight version with bold in my email client, but here http://www.nabble.com/WiX-and-Support-Information-in-%22Add-or-Remove-Programs%22-panel-td17985802.htmli see version between stars. so do not pay attention on these asterisks. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How to execute powershell scripts
Hi, I have a powershell script which will be added into the MSI package. I want to execute the script after installation completed automatically. How can I do it? Thanks a lot for your help in advance. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MSBuild inside Wix development
Well in part because these have evolved for a while and I've been using them for at least three years - possibly before wix.targets became part of the product? And in part because I had no idea they were there :-/ I'm really glad you pointed this out, but it got me wondering (again) how I missed this??? Apparently this is part of Visual Studio 2008 and/or .Net 3.5. Man it sure would be nice to have this at least referenced in WiX.chm or the web site or did I just miss it? Well anyhow, thanks for pointing this out. On Tue, Jun 17, 2008 at 10:08 PM, Neil Enns [EMAIL PROTECTED] wrote: Chris, I'm curious, why do you use this approach instead of the shipping wix.targets build process that comes with WiX? Neil From: [EMAIL PROTECTED] [ [EMAIL PROTECTED] On Behalf Of Chris Mumford [ [EMAIL PROTECTED] Sent: Tuesday, June 17, 2008 8:04 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] MSBuild inside Wix development You don't want to call MSBuild *from* WiX. Instead you want to mave MSBuild call WiX. Attached is my MSBuild project file that calls candle.exe and light.exe to build an MSI file. You can see that I have the path to the WiX bin folder hard-coded (and my machine is x64). So as an improvement you could use the MSBuild Community Tasks (http://msbuildtasks.tigris.org/) to read the registry (via RegistryRead) to dynamically determine the install location of WiX. Hope this helps. -Chris On Tue, Jun 17, 2008 at 1:08 AM, Krishnan Senthilraj [EMAIL PROTECTED] wrote: Hi, I am new to Wix and MSBuild area. I have one fundamental quention. I completed all the building of my application in MSBuild. Now I am writing Wix construction. I was under impressing we can call the MSBuild project inside Wix. I am trying examples for this. But unfortunately I didn't get that. So I would like to confirm with this group that *Is it possible and workable solution to call the MSBuild project inside the Wix?* If answer is yes then please give some links/direction to acheive the same. Cheers Senthilraj - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Patch build with GAC update
Hi Neil, Thanks for the response..
Yes, the log says..
MSI (c) (0C:28) [13:45:05:326]: PROPERTY CHANGE: Adding INSTALLLEVEL
property. Its value is '1'.
MSI (c) (0C:28) [13:45:05:326]: skipping installation of assembly component:
{646909B9-8B31-4429-9556-82AE57B3F4EE} since the assembly already exists
Action ended 13:45:05: CostFinalize. Return value 1.
MSI (c) (0C:28) [13:45:05:342]: Doing action: ExecuteAction
--
View this message in context:
http://www.nabble.com/Patch-build-with-GAC-update-tp17880093p17997633.html
Sent from the wix-users mailing list archive at Nabble.com.
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MSBuild inside Wix development
You can use it stand-alone, but it's also part of the Votive stuff that's significantly reworked in WiX v3. Assuming you installed WiX v3 on a machine that has VS on it you should be able to do File New Project... and then pick WiX from the left nodes and create a new WiX project. This is in the WiX.chm file :) When you run the chm click on Using WiX in Visual Studio in the first page that shows up. There's 6 topics on it. Neil From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Chris Mumford [EMAIL PROTECTED] Sent: Wednesday, June 18, 2008 9:52 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] MSBuild inside Wix development Well in part because these have evolved for a while and I've been using them for at least three years - possibly before wix.targets became part of the product? And in part because I had no idea they were there :-/ I'm really glad you pointed this out, but it got me wondering (again) how I missed this??? Apparently this is part of Visual Studio 2008 and/or .Net 3.5. Man it sure would be nice to have this at least referenced in WiX.chm or the web site or did I just miss it? Well anyhow, thanks for pointing this out. On Tue, Jun 17, 2008 at 10:08 PM, Neil Enns [EMAIL PROTECTED] wrote: Chris, I'm curious, why do you use this approach instead of the shipping wix.targets build process that comes with WiX? Neil From: [EMAIL PROTECTED] [ [EMAIL PROTECTED] On Behalf Of Chris Mumford [ [EMAIL PROTECTED] Sent: Tuesday, June 17, 2008 8:04 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] MSBuild inside Wix development You don't want to call MSBuild *from* WiX. Instead you want to mave MSBuild call WiX. Attached is my MSBuild project file that calls candle.exe and light.exe to build an MSI file. You can see that I have the path to the WiX bin folder hard-coded (and my machine is x64). So as an improvement you could use the MSBuild Community Tasks (http://msbuildtasks.tigris.org/) to read the registry (via RegistryRead) to dynamically determine the install location of WiX. Hope this helps. -Chris On Tue, Jun 17, 2008 at 1:08 AM, Krishnan Senthilraj [EMAIL PROTECTED] wrote: Hi, I am new to Wix and MSBuild area. I have one fundamental quention. I completed all the building of my application in MSBuild. Now I am writing Wix construction. I was under impressing we can call the MSBuild project inside Wix. I am trying examples for this. But unfortunately I didn't get that. So I would like to confirm with this group that *Is it possible and workable solution to call the MSBuild project inside the Wix?* If answer is yes then please give some links/direction to acheive the same. Cheers Senthilraj - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
