Re: [WiX-users] Does Pyro (or Torch) ignore 4-th version number?
It just goes to show how easy it is to commit gross component rules violations even after months of reading articles and blogs on component rules! However, it seems that I have also misunderstood the purpose of MSIENFORCEUPGRADECOMPONENTRULES property. I was under the impression that it would add to verbose log. I mean, if MSI *knows* that there is component violation, it would be of great help if it could add a sentence to the log saying at least something along the lines of: There is component rules violation of some sort! After reading all that I could find on MSIENFORCEUPGRADECOMPONENTRULES property I can't say that I am 100% sure about what is it that it really does? How can the consequences of having this property defined or not be seen on some practical example? I was certainly none the wiser in this specific case since verbose logs were identical with or without it, for all that I could see. It *seems* that a small update patch may be applied by MSI in some cases even if there was a component rule violation and this property prevents it. -Original Message- From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Saturday, August 02, 2008 1:10 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Does Pyro (or Torch) ignore 4-th version number? Tony Juricic wrote: but reading the install.log I cannot find anything a bit more explicit about this violation. It is certainly not saying something like you changed the name of your root installation folder and you shouldn't :) Sorry, it's not that polite.g The Windows Installer Components topic summarizes the magic of component rules with two bullets: In brief, these rules are: * Each component must be stored in a single folder. * No file, registry entry, shortcut, or other resources should ever be shipped as a member of more than one component. This applies across products, product versions, and companies. So changing the directory violates 50 percent of the component rules.g -- 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=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Upgrade with new Microsoft libraries
On a project which has been upgraded from Visual Studio 2005 to 2008 running an upgrade on the MSI package not work correctly. The reason for this is that the project is dependent on the Microsoft CRT libraries. Previously the library was included in the install as follows: Merge Id=msvcrt Language=1033 SourceFile=$(env.ProgramFiles)\\Common Files\\Merge Modules\\Microsoft_VC80_CRT_x86.msm DiskId=1 / Merge Id=msvcrt_policy Language=1033 SourceFile=$(env.ProgramFiles)\\Common Files\\Merge Modules\\policy_8_0_Microsoft_VC80_CRT_x86.msm DiskId=1 / Now this has been replaced with: Merge Id=msvcrt Language=1033 SourceFile=$(env.ProgramFiles)\\Common Files\\Merge Modules\\Microsoft_VC90_CRT_x86.msm DiskId=1 / Merge Id=msvcrt_policy Language=1033 SourceFile=$(env.ProgramFiles)\\Common Files\\Merge Modules\\policy_9_0_Microsoft_VC90_CRT_x86.msm DiskId=1 / The only change here being that the referenced merge modules have changed. Attempting to upgrade the package using the REINSTALLMODE=vomus REINSTALL=ALL switch succeeds but the new MS libraries are not installed. I believe this is because the components in the new merge modules were not previously present so no action is taken. Can anyone shed any light on this and suggest a way that I can author the install so that the upgrade will work. Thanks Chris Walford NOTICE: This email message and all attachments transmitted with it are intended solely for the use of the addressees and may contain confidential information. If you have received this message in error, please notify the sender immediately by email reply and please delete this message from your computer and destroy any copies. PassGo Technologies Ltd is incorporated in England and Wales (registered number 04222450) with its registered address at Horton Manor, Horton Cross, Ilminster, Somerset TA19 9PY. PassGo Technologies Ltd is now part of the Quest Software Group of Companies. - 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=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WebSites in ComboBox dynamically
Hello Alexei and All, I'm new to Wix. I'm trying to make a installer for website - something similar to what visual studio IDE provides. I've tried using the two scripts mentioned in the posts here to populate the combo box with the websites available on a machine as well as set the port of the in the WebAddress element using the script given here. But my installation is failing with the error message ConfigureIIs: Error 0x8007000d: invalid port provided for web site: ConfigureIIs: Error 0x8007000d: failed to read IIsWebSite table Error 26002. Failed to read IIsWebSite table. (-2147024883 ) I don't know where I'm going wrong. Please guide me as to how do i set the website port correctly. The following are the files i'm using Test.wxs: ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; xmlns:iis=http://schemas.microsoft.com/wix/IIsExtension; xmlns:ui=http://schemas.microsoft.com/wix/WixUIExtension; Product Id=7b523f47-ef58-4d3c-8ca1-fea6be516471 Name=My Product Language=1033 Version=1.0.0.0 Manufacturer=Personal Co UpgradeCode=0a8c10df-fe3e-4aec-8954-50b9ecdb0a41 Package InstallerVersion=100 Compressed=yes / Icon Id=icon.ico SourceFile=tray.ico/ Property Id=ProductIcon Value=icon.ico / Condition Message=Only an Administrator can install this application Privileged /Condition Condition Message=Windows Server 2003 is required VersionNT = 502 /Condition PropertyRef Id=NETFRAMEWORK20/ Condition Message=The .NET Framework 2.0 or higher must be installed Installed OR NETFRAMEWORK20 /Condition PropertyRef Id=IISMAJORVERSION/ Condition Message=IIS version 5 or higher must be installed Installed OR (IISMAJORVERSION = #5) /Condition Media Id=1 Cabinet=WebAppWixProject.cab EmbedCab=yes / Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFilesFolder Directory Id=PersonalCo Name=Personal Co. Directory Id=INSTALLLOCATION Name=TestApplication Component Id=TestComponent DiskId=1 Guid=80b0ee2a-a102-46ec-a456-33a23eb0588e File Id=Error.aspx Name=Error.aspx Source=Error.aspx / File Id=Login.aspx Name=Login.aspx Source=Login.aspx / iis:WebVirtualDir Id=MyWebApp Alias=TestApplication Directory=INSTALLLOCATION WebSite=DefaultWebSite iis:WebApplication Id=TestWebApplication Name=TestApplication / /iis:WebVirtualDir /Component /Directory /Directory /Directory /Directory iis:WebSite Id='DefaultWebSite' Description='[WebsiteCombo]' Directory='INSTALLLOCATION' iis:WebAddress Id=AllUnassigned Port=[WebsiteComboIP] IP=[WebsiteComboIA] / /iis:WebSite Feature Id=ProductFeature Title=registeR4Health - Provider Application Level=1 ComponentRef Id=TestComponent / /Feature UIRef Id=WixUI_Common / UI Property Id=DefaultUIFont Value=WixUI_Font_Normal / TextStyle Id=WixUI_Font_Normal FaceName=Tahoma Size=8 / TextStyle Id=WixUI_Font_Bigger FaceName=Tahoma Size=12 / TextStyle Id=WixUI_Font_Title FaceName=Tahoma Size=9 Bold=yes / Property Id=WIXUI_INSTALLDIR Value=INSTALLLOCATION / Property Id=PIDTemplate Value=--- / Property Id=ARPNOMODIFY Value=1 / DialogRef Id=BrowseDlg / DialogRef Id=DiskCostDlg / DialogRef Id=ErrorDlg / DialogRef Id=FatalError / DialogRef Id=FilesInUse / DialogRef Id=MsiRMFilesInUse / DialogRef Id=PrepareDlg / DialogRef Id=ProgressDlg / DialogRef Id=ResumeDlg / DialogRef Id=UserExit / Publish Dialog=ExitDialog Control=Finish Event=EndDialog Value=Return Order=9991/Publish Publish Dialog=WelcomeDlg Control=Next Event=NewDialog Value=LicenseAgreementDlg1/Publish Publish Dialog=LicenseAgreementDlg Control=Back Event=NewDialog Value=WelcomeDlg1/Publish Publish Dialog=LicenseAgreementDlg Control=Next Event=DoAction Value=GetIISSites Order=1LicenseAccepted = 1/Publish Publish Dialog=LicenseAgreementDlg Control=Next Event=NewDialog Value=LicenseKeyDlg Order=2LicenseAccepted = 1/Publish Publish Dialog=LicenseKeyDlg Control=Back Event=NewDialog Value=LicenseAgreementDlg1/Publish Publish Dialog=LicenseKeyDlg Control=Next Event=ValidateProductID Value=[PIDKEY] Order=11/Publish Publish Dialog=LicenseKeyDlg Control=Next Event=DoAction Value=ConfigureIISSite Order=21/Publish Publish Dialog=LicenseKeyDlg Control=Next Event=NewDialog Value=InstallDirDlg Order=3ProductID/Publish Publish Dialog=InstallDirDlg Control=Back Event=NewDialog Value=LicenseKeyDlg1/Publish Publish Dialog=InstallDirDlg Control=Next Event=SetTargetPath Value=[WIXUI_INSTALLDIR] Order=11/Publish Publish Dialog=InstallDirDlg Control=Next Event=NewDialog
Re: [WiX-users] Call a .NET dll file in wix using custom
But still I have a problem when I try to run a html file, although
DLfetcher is registered in gac, issue is as follows:
DLFetcher Component is not registered[object error]
Html file:
html
body
script language=javascript
try
{
ob1 = new ActiveXObject(DLFetcher.RetreiveDL);
alert(ob1);
if(ob1!=null)
{
username=ob1.GetUserName();
//alert(Windows : +username);
var IsUserValid=ob1.IsUserExist(username);
if(IsUserValid)
{
alert(UserName is available );
var arDL=ob1.GetDLforUserAsString(baijuv);
if(arDL.length==0)
{
alert(Invalid User);
}
else
{
alert(arDL);
}
}
else
{
alert(User is not avaliable in the Domain Control to
connect to Active Directory);
}
}
}
catch(e)
{
alert(DLFetcher component is not registered +e);
}
/script
/body
/html
Can you please suggest me further, what changes can I do in wix so that
the dlfetcher component gets registered.
But when I try to run a batch file as follows:
c:
cd C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
regasm D:\DLFetcher_July10\DLFetcher.dll
gacutil /i D:\DLFetcher_July10\DLFetcher.dll
pause
the registry is happening in gac, as well as when I try to run my html
file, no issues are coming... So can you please suggest me a way to do
this procedure in wix...
Thanks in advance
Regards,
Poornima.S
--
Glad to help. Unless you have an exceptionally good reason you should
*always* have exactly one file per component.
Neil
From: Poornima S [EMAIL PROTECTED]
Sent: Monday, August 04, 2008 10:59 PM
To: Neil Enns
Subject: RE: [WiX-users] Call a .NET dll file in wix using custom
Thanks Neil, its working fine now, I created a separate component and
under that I created my file element its working fine Thanks a
lot :)
Regards
Poornima.S
Aztecsoft Limited
-Original Message-
From: Neil Enns [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 05, 2008 10:30 AM
To: Poornima S; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Call a .NET dll file in wix using custom
A live.com search for 0x80131043 yielded many results, including this
one at Aaron's blog:
http://blogs.msdn.com/astebner/archive/2004/11/10/255346.aspx, and this
specific comment from him in the comment section:
The error code you are getting is 0x80131043. According to the chart
at the top of this blog post, it means Modules which are not in the
manifest were streamed in. This most likely means that your assembly
component contains other files that are not a part of this assembly.
You will need to double check your WXS file and make sure that you are
only installing one assembly per component (unless the assembly consists
of multiple files and is a multi-module assembly).
Neil
-Original Message-
From: Poornima S
Sent: Tuesday, August 05, 2008 10:24 AM
To: 'wix-users@lists.sourceforge.net'
Cc: '[EMAIL PROTECTED]'
Subject: Re: [WiX-users] Call a .NET dll file in wix using custom
I tried to register DLL in the GAC, by adding Assembly=.net to my
File element, as below:
File KeyPath=yes Id=InstallDlfetcher
Name=DLFetcher.dll
DiskId=1
Source=D:\DLFetcher_July10\DLFetcher.dll Assembly=.net
/File
But I am getting an error when I try to run my installer as follows:
An error occurred during the installation of assembly
'DLFetcher,version=1.1.0.0,
culture=neutral,publickeyToken=402B9D8975482830'. Please refer to
Help and support for more information. HRESULT:0x80131043.
Please can you further help me out in solving this issue.
Regards
Poornima.S
Aztecsoft Limited
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Monday, August 04, 2008 8:32 PM
To: wix-users@lists.sourceforge.net
Subject: WiX-users Digest, Vol 27, Issue 8
Send WiX-users mailing list submissions to
wix-users@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/wix-users
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than Re: Contents of WiX-users digest...
Today's Topics:
1. FW: Re: ServiceInstall account problem (Daniel Rieck)
2. updating with a different account? (Mattias ?slund)
3. Call a .NET dll file in wix using custom action (Poornima S)
4.
Re: [WiX-users] Upgrade with new Microsoft libraries
This is only the beginning of your pains. My recommendation is to switch to a major upgrade. http://msdn.microsoft.com/en-us/library/aa369786(VS.85).aspx http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-par t-8-major-upgrade.aspx cheers dB. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Walford Sent: Wednesday, August 06, 2008 5:46 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Upgrade with new Microsoft libraries On a project which has been upgraded from Visual Studio 2005 to 2008 running an upgrade on the MSI package not work correctly. The reason for this is that the project is dependent on the Microsoft CRT libraries. Previously the library was included in the install as follows: Merge Id=msvcrt Language=1033 SourceFile=$(env.ProgramFiles)\\Common Files\\Merge Modules\\Microsoft_VC80_CRT_x86.msm DiskId=1 / Merge Id=msvcrt_policy Language=1033 SourceFile=$(env.ProgramFiles)\\Common Files\\Merge Modules\\policy_8_0_Microsoft_VC80_CRT_x86.msm DiskId=1 / Now this has been replaced with: Merge Id=msvcrt Language=1033 SourceFile=$(env.ProgramFiles)\\Common Files\\Merge Modules\\Microsoft_VC90_CRT_x86.msm DiskId=1 / Merge Id=msvcrt_policy Language=1033 SourceFile=$(env.ProgramFiles)\\Common Files\\Merge Modules\\policy_9_0_Microsoft_VC90_CRT_x86.msm DiskId=1 / The only change here being that the referenced merge modules have changed. Attempting to upgrade the package using the REINSTALLMODE=vomus REINSTALL=ALL switch succeeds but the new MS libraries are not installed. I believe this is because the components in the new merge modules were not previously present so no action is taken. Can anyone shed any light on this and suggest a way that I can author the install so that the upgrade will work. Thanks Chris Walford NOTICE: This email message and all attachments transmitted with it are intended solely for the use of the addressees and may contain confidential information. If you have received this message in error, please notify the sender immediately by email reply and please delete this message from your computer and destroy any copies. PassGo Technologies Ltd is incorporated in England and Wales (registered number 04222450) with its registered address at Horton Manor, Horton Cross, Ilminster, Somerset TA19 9PY. PassGo Technologies Ltd is now part of the Quest Software Group of Companies. - 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=100url=/ ___ 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=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WindowsFolder variable is not getting picked up
Hi, I have the following Property element within my WiX source file: Property Id='INSTALLUTIL_PATH' Value='[WindowsFolder]\Microsoft.NET\Framework\v2.0.50727\InstallUtil.exe'/ Its parent is the Product element for the feature installed. For some reason, the MSI gets built without error, but the installer barfs, with logs showing that the [WindowsFolder] string was never resolved into the folder. Am I doing something wrong with the syntax? Thanks -greg - 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=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Heat - Controling Component Generation
Hi,
I have two questions about the functionality of Heat.exe.
First, is there a to get heat.exe to generate 64-bit components? Right now it
is giving me something like:
Component Id=somefile Guid={4B211B5B-4419-4E72-A3AA-D34FAF443625}
File Id=K somefile Name=somefile KeyPath=yes Source=C:\somefile /
/Component
And I would like something like:
Component Id=somefile Guid={4B211B5B-4419-4E72-A3AA-D34FAF443625}
Win64=yes
File Id=K somefile Name=somefile KeyPath=yes Source=C:\somefile /
/Component
And secondly, is there any way for it to output relative directory paths?
Right now I am solving these problems with some regex on the resulting wxs
file, but wondering if there is a better way.
Thanks!
Ahearn
This e-mail message and any files transmitted with it are for the sole use of
the intended recipient(s) and may contain confidential and privileged
information. Any unauthorized review, use, disclosure or distribution is
prohibited. If you are not the intended recipient, please contact the sender
by reply e-mail and destroy all copies of the original message. Please note
that any views or opinions presented in this e-mail are solely those of the
author and do not necessarily represent those of The Company. Finally, the
recipient should check this e-mail and any attachments for the presence of
viruses. The Company accepts no liability for any damage caused by any virus
transmitted by this e-mail.
-
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=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WindowsFolder variable is not getting picked up
WiX Property element creates a record in the Property table (http://msdn.microsoft.com/en-us/library/aa370908(VS.85).aspx). As you can see, the type of the Value column in this table is Text (not Formatted). Also, Remarks section has the following: Note that you cannot use the Property table to set a property to the value of another property. The installer does nothing to the text string entered in the Value column before setting the property in the Property column. If FirstProperty is entered into the Property column and [SecondProperty] in the Value column, the value of FirstProperty is set to the text string [SecondProperty] and not to the value of the SecondProperty property. This is necessary to prevent creating circular references in the Property table. Instead, you can set one property to another by using a Custom Action Type 51. I have samples on all types (including Type 51) in here: http://blogs.technet.com/alexshev/archive/2008/02/21/from-msi-to-wix-part-5-custom-actions.aspx Regards, Alex Shevchuk -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greg Silin Sent: Wednesday, August 06, 2008 8:44 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] WindowsFolder variable is not getting picked up Hi, I have the following Property element within my WiX source file: Property Id='INSTALLUTIL_PATH' Value='[WindowsFolder]\Microsoft.NET\Framework\v2.0.50727\InstallUtil.exe'/ Its parent is the Product element for the feature installed. For some reason, the MSI gets built without error, but the installer barfs, with logs showing that the [WindowsFolder] string was never resolved into the folder. Am I doing something wrong with the syntax? Thanks -greg - 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=100url=/ ___ 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=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WindowsFolder variable is not getting picked up
I don't believe the Property element supports formatted strings, if you are using WiX v4 try using the SetProperty element. Otherwise you will need to do it with a custom action. Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greg Silin Sent: 06 August 2008 16:44 To: wix-users@lists.sourceforge.net Subject: [WiX-users] WindowsFolder variable is not getting picked up Hi, I have the following Property element within my WiX source file: Property Id='INSTALLUTIL_PATH' Value='[WindowsFolder]\Microsoft.NET\Framework\v2.0.50727\InstallUtil.ex e'/ Its parent is the Product element for the feature installed. For some reason, the MSI gets built without error, but the installer barfs, with logs showing that the [WindowsFolder] string was never resolved into the folder. Am I doing something wrong with the syntax? Thanks -greg - 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=100url=/ ___ 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=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat - Controling Component Generation
I use the regex search and replace too. Which harvester are you using? I
can take a look to see how hard it would be to add support for that, but as
far as I know, these things are not currently possible, and no one is
working on heat other than myself.
Chris
On Wed, Aug 6, 2008 at 12:01 PM, Ahearn Stevens [EMAIL PROTECTED] wrote:
Hi,
I have two questions about the functionality of Heat.exe.
First, is there a to get heat.exe to generate 64-bit components? Right now
it is giving me something like:
Component Id=somefile Guid={4B211B5B-4419-4E72-A3AA-D34FAF443625}
File Id=K somefile Name=somefile KeyPath=yes Source=C:\somefile
/
/Component
And I would like something like:
Component Id=somefile Guid={4B211B5B-4419-4E72-A3AA-D34FAF443625}
Win64=yes
File Id=K somefile Name=somefile KeyPath=yes Source=C:\somefile
/
/Component
And secondly, is there any way for it to output relative directory paths?
Right now I am solving these problems with some regex on the resulting wxs
file, but wondering if there is a better way.
Thanks!
Ahearn
This e-mail message and any files transmitted with it are for the sole use
of the intended recipient(s) and may contain confidential and privileged
information. Any unauthorized review, use, disclosure or distribution is
prohibited. If you are not the intended recipient, please contact the
sender by reply e-mail and destroy all copies of the original message.
Please note that any views or opinions presented in this e-mail are solely
those of the author and do not necessarily represent those of The Company.
Finally, the recipient should check this e-mail and any attachments for the
presence of viruses. The Company accepts no liability for any damage caused
by any virus transmitted by this e-mail.
-
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=100url=/
___
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=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WindowsFolder variable is not getting picked up
Wix v4? Did I miss something? On Wed, Aug 6, 2008 at 12:07 PM, Neil Sleightholm [EMAIL PROTECTED]wrote: I don't believe the Property element supports formatted strings, if you are using WiX v4 try using the SetProperty element. Otherwise you will need to do it with a custom action. Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greg Silin Sent: 06 August 2008 16:44 To: wix-users@lists.sourceforge.net Subject: [WiX-users] WindowsFolder variable is not getting picked up Hi, I have the following Property element within my WiX source file: Property Id='INSTALLUTIL_PATH' Value='[WindowsFolder]\Microsoft.NET\Framework\v2.0.50727\InstallUtil.ex e'/ Its parent is the Product element for the feature installed. For some reason, the MSI gets built without error, but the installer barfs, with logs showing that the [WindowsFolder] string was never resolved into the folder. Am I doing something wrong with the syntax? Thanks -greg - 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=100url=/ ___ 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=100url=/ ___ 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=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Upgrade with new Microsoft libraries
You've probably broken the component rules be deleting components and replacing them with others. This will result in the advertised feature behavior and updates not being done. If you take a log of the install I think you'd see SELMGR errors. A major upgrade would be the cure, as was suggested. Phil Wilson -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Walford Sent: Wednesday, August 06, 2008 2:46 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Upgrade with new Microsoft libraries On a project which has been upgraded from Visual Studio 2005 to 2008 running an upgrade on the MSI package not work correctly. The reason for this is that the project is dependent on the Microsoft CRT libraries. Previously the library was included in the install as follows: Merge Id=msvcrt Language=1033 SourceFile=$(env.ProgramFiles)\\Common Files\\Merge Modules\\Microsoft_VC80_CRT_x86.msm DiskId=1 / Merge Id=msvcrt_policy Language=1033 SourceFile=$(env.ProgramFiles)\\Common Files\\Merge Modules\\policy_8_0_Microsoft_VC80_CRT_x86.msm DiskId=1 / Now this has been replaced with: Merge Id=msvcrt Language=1033 SourceFile=$(env.ProgramFiles)\\Common Files\\Merge Modules\\Microsoft_VC90_CRT_x86.msm DiskId=1 / Merge Id=msvcrt_policy Language=1033 SourceFile=$(env.ProgramFiles)\\Common Files\\Merge Modules\\policy_9_0_Microsoft_VC90_CRT_x86.msm DiskId=1 / The only change here being that the referenced merge modules have changed. Attempting to upgrade the package using the REINSTALLMODE=vomus REINSTALL=ALL switch succeeds but the new MS libraries are not installed. I believe this is because the components in the new merge modules were not previously present so no action is taken. Can anyone shed any light on this and suggest a way that I can author the install so that the upgrade will work. Thanks Chris Walford NOTICE: This email message and all attachments transmitted with it are intended solely for the use of the addressees and may contain confidential information. If you have received this message in error, please notify the sender immediately by email reply and please delete this message from your computer and destroy any copies. PassGo Technologies Ltd is incorporated in England and Wales (registered number 04222450) with its registered address at Horton Manor, Horton Cross, Ilminster, Somerset TA19 9PY. PassGo Technologies Ltd is now part of the Quest Software Group of Companies. - 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=100url=/ ___ 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=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WindowsFolder variable is not getting picked up
Yes that's the version that just knows what we want to do and writes the code for us! As I'm sure you all guessed it meant v3. Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Karper Sent: 06 August 2008 18:24 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WindowsFolder variable is not getting picked up Wix v4? Did I miss something? On Wed, Aug 6, 2008 at 12:07 PM, Neil Sleightholm [EMAIL PROTECTED]wrote: I don't believe the Property element supports formatted strings, if you are using WiX v4 try using the SetProperty element. Otherwise you will need to do it with a custom action. Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greg Silin Sent: 06 August 2008 16:44 To: wix-users@lists.sourceforge.net Subject: [WiX-users] WindowsFolder variable is not getting picked up Hi, I have the following Property element within my WiX source file: Property Id='INSTALLUTIL_PATH' Value='[WindowsFolder]\Microsoft.NET\Framework\v2.0.50727\InstallUtil.ex e'/ Its parent is the Product element for the feature installed. For some reason, the MSI gets built without error, but the installer barfs, with logs showing that the [WindowsFolder] string was never resolved into the folder. Am I doing something wrong with the syntax? Thanks -greg - 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=100url=/ ___ 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=100url=/ ___ 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=100url=/ ___ 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=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat - Controling Component Generation
I am using the directory harvester.
Thanks Chris.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher
Karper
Sent: Wednesday, August 06, 2008 11:24 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Heat - Controling Component Generation
I use the regex search and replace too. Which harvester are you using? I
can take a look to see how hard it would be to add support for that, but as
far as I know, these things are not currently possible, and no one is
working on heat other than myself.
Chris
On Wed, Aug 6, 2008 at 12:01 PM, Ahearn Stevens [EMAIL PROTECTED] wrote:
Hi,
I have two questions about the functionality of Heat.exe.
First, is there a to get heat.exe to generate 64-bit components? Right now
it is giving me something like:
Component Id=somefile Guid={4B211B5B-4419-4E72-A3AA-D34FAF443625}
File Id=K somefile Name=somefile KeyPath=yes Source=C:\somefile
/
/Component
And I would like something like:
Component Id=somefile Guid={4B211B5B-4419-4E72-A3AA-D34FAF443625}
Win64=yes
File Id=K somefile Name=somefile KeyPath=yes Source=C:\somefile
/
/Component
And secondly, is there any way for it to output relative directory paths?
Right now I am solving these problems with some regex on the resulting wxs
file, but wondering if there is a better way.
Thanks!
Ahearn
This e-mail message and any files transmitted with it are for the sole use
of the intended recipient(s) and may contain confidential and privileged
information. Any unauthorized review, use, disclosure or distribution is
prohibited. If you are not the intended recipient, please contact the
sender by reply e-mail and destroy all copies of the original message.
Please note that any views or opinions presented in this e-mail are solely
those of the author and do not necessarily represent those of The Company.
Finally, the recipient should check this e-mail and any attachments for the
presence of viruses. The Company accepts no liability for any damage caused
by any virus transmitted by this e-mail.
-
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=100url=/
___
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=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
This e-mail message and any files transmitted with it are for the sole use of
the intended recipient(s) and may contain confidential and privileged
information. Any unauthorized review, use, disclosure or distribution is
prohibited. If you are not the intended recipient, please contact the sender
by reply e-mail and destroy all copies of the original message. Please note
that any views or opinions presented in this e-mail are solely those of the
author and do not necessarily represent those of The Company. Finally, the
recipient should check this e-mail and any attachments for the presence of
viruses. The Company accepts no liability for any damage caused by any virus
transmitted by this e-mail.
-
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=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Custom Actions
I'm creating an installer that executes an embedded vbscript on install an a vbscript on uninstall. Why does it want to run both scripts on the install. And this gives me an error on the install: Custom Action=Custom4 Before=RemoveFilesNot Installed /Custom Custom4 is the vbscript that removes a shortcut, but it wants to run on the install. Any help would be great thanks. - 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=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom Actions
Custom4 runs during the install because your condition is Not Installed. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jonathan Moore Sent: Wednesday, August 06, 2008 2:34 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Custom Actions I'm creating an installer that executes an embedded vbscript on install an a vbscript on uninstall. Why does it want to run both scripts on the install. And this gives me an error on the install: Custom Action=Custom4 Before=RemoveFilesNot Installed /Custom Custom4 is the vbscript that removes a shortcut, but it wants to run on the install. Any help would be great thanks. - 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=100url=/ ___ 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=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How to preserve INI file during major upgrade
I have a WiX installer which includes merge modules for the Visual Studio 2005 CRT. I'm moving the project to Visual Studio 2008, and now the merge modules are different (for example, Microsoft_VC90_CRT_x86.msm instead of Microsoft_VC80_CRT_x86.msm). I would like to distribute this change as a major upgrade, for one, to avoid running msiexec at the command line with options (for a minor upgrade) and two, as I understand it, replacing files (from the merge modules -- i.e. delete the *8* files and install the *9* files into C:\Windows\WinSxS) requires a major upgrade. How do I preserve an INI file that was installed by the first installer, and which be deleted by the uninstall which happens when the major upgrade runs? - 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=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to preserve INI file during major upgrade
Where is your RemoveExistingProducts action scheduled? Ref: http://msdn.microsoft.com/en-us/library/aa371197(VS.85).aspx From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Jim Flood [EMAIL PROTECTED] Sent: Wednesday, August 06, 2008 4:26 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] How to preserve INI file during major upgrade I have a WiX installer which includes merge modules for the Visual Studio 2005 CRT. I'm moving the project to Visual Studio 2008, and now the merge modules are different (for example, Microsoft_VC90_CRT_x86.msm instead of Microsoft_VC80_CRT_x86.msm). I would like to distribute this change as a major upgrade, for one, to avoid running msiexec at the command line with options (for a minor upgrade) and two, as I understand it, replacing files (from the merge modules -- i.e. delete the *8* files and install the *9* files into C:\Windows\WinSxS) requires a major upgrade. How do I preserve an INI file that was installed by the first installer, and which be deleted by the uninstall which happens when the major upgrade runs? - 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=100url=/ ___ 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=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WindowsFolder variable is not getting picked up
Must be a typo... that's a WiX v3 feature. smile/ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Karper Sent: Wednesday, August 06, 2008 10:24 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WindowsFolder variable is not getting picked up Wix v4? Did I miss something? On Wed, Aug 6, 2008 at 12:07 PM, Neil Sleightholm [EMAIL PROTECTED]wrote: I don't believe the Property element supports formatted strings, if you are using WiX v4 try using the SetProperty element. Otherwise you will need to do it with a custom action. Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greg Silin Sent: 06 August 2008 16:44 To: wix-users@lists.sourceforge.net Subject: [WiX-users] WindowsFolder variable is not getting picked up Hi, I have the following Property element within my WiX source file: Property Id='INSTALLUTIL_PATH' Value='[WindowsFolder]\Microsoft.NET\Framework\v2.0.50727\InstallUtil.ex e'/ Its parent is the Product element for the feature installed. For some reason, the MSI gets built without error, but the installer barfs, with logs showing that the [WindowsFolder] string was never resolved into the folder. Am I doing something wrong with the syntax? Thanks -greg - 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=100url=/ ___ 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=100url=/ ___ 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=100url=/ ___ 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=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Does Pyro (or Torch) ignore 4-th version number?
Just to make my life easier, now that I corrected the mistake and double-checked that I haven't committed component violation again, I am back to having exactly the same problem. Pyro doesn't find anything to put in a patch cab and running verbose log doesn't reveal anything. Even a nice tool like WiLogUtl doesn't see any error or reveals anything unusual. My patch application is a complete success as I can verify in ARP that product version has changed! However, none of the changed binary files were updated, despite my changing the fourth version number in both exes and dlls. I guess this was to be expected since msp's cab was empty as reported by Pyro. At this point I am inclined to mistrust delta patching capabilities of the tools and am back to the question in the title. I am open to all suggestions on what else to try and what may have gone wrong :( In the meantime, I will try old style patching with PatchWiz.dll. - 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=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] New wix binary delta patching doesn't work
I can confirm this now that I produced two MSIs that don't have any component rules problems. Some history of this problem can be found in posts titled 'Does Pyro (or Torch) ignore 4-th version number?'. I have 2 MSIs and 2 corresponding binary wixout files. Using new patching with wixout input produced a msp file which applied transformation to the original database (i.e. I could see that product version was changed in ARP after patch application) but none of the binary files were changed. In particular all updated exes and dlls had new and larger version numbers and should have been patched too. Using old-style patching, meaning: -MSIs were decompressed using administrative install -PatchCreation WiX element was used in Patch.wxs -MsiMsp.exe was used to produce msp from pcp. applied patch both to the database and to the installed binary files. I could verify that all exe and dll version numbers were upped despite *erroneous* warnings in the log produced by msimsp.exe like: INFO Comparing Files: C:\wixpatchbin\Build2081\admin\...\some.exe C:\wixpatchbin\Build2082\admin\.. some.exe... INFO Comparing bytes... WARNING: File versions for target file: C:\wixpatchbin\Build2081\admin\...\soome.exe and upgrade file: C:\wixpatchbin\Build2082\admin\...\some.exe are same, while the files itself are different. INFO Different content... INFO File Key: SOME.EXE is modified These warnings come from the wrong assumption that everything related to Windows installer should respect only 3 upper version numbers according to an explanation given by Stefan Krueger when I asked about it on InstallSite forum. I can file this as a bug, unless there are suggestions on other things to try. From my perspective Torch and Pyro are not yet in the shape to be reliable tools for binary patching. - 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=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] New wix binary delta patching doesn't work
Tony Juricic wrote: I have 2 MSIs and 2 corresponding binary wixout files. Using new patching with wixout input produced a msp file which applied transformation to the original database (i.e. I could see that product version was changed in ARP after patch application) but none of the binary files were changed. In particular all updated exes and dlls had new and larger version numbers and should have been patched too. So does it work if you: 1. Use full-file patches? 2. Use delta patches but change the build (third) version number? -- 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=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom Actions
Jonathan Moore wrote: Custom4 is the vbscript that removes a shortcut You shouldn't use VBScript custom actions. http://blogs.msdn.com/robmen/archive/2004/05/20/136530.aspxMSI automatically removes shortcuts it installs but if you need to clean up extra files, use the RemoveFile element. Custom actions aren't necessary for that. -- 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=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Font not correct when uninstall from control panel
The font used in the basic UI can be set using the DefaultUIFont property: http://msdn.microsoft.com/en-us/library/aa368266(VS.85).aspx -- View this message in context: http://www.nabble.com/Font-not-correct-when-uninstall-from-control-panel-tp18088307p18864176.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=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
