Re: [WiX-users] Administrative Install and wixui_mondo
They don't handle patching very well either. The Welcome Dialog refers to a Resumed install when running a patch (MSP) and the Progress Dialog is devoid of all text except the ActionText. Exit Dialog could probably do with more specific text to Patching too. Unfortunately the WiX extensions solution is in Visual Studio 2008 format as we're still using Visual Studio 2005, I can't rebuild WixUIExtension.dll to test changes even if I wanted to help update them myself. Palbinder Sandher Software Deployment IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: spsingam [mailto:siva.poobalasin...@gmail.com] Sent: 23 April 2009 06:21 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Administrative Install and wixui_mondo it would be nice to be able to use the msiexec /a and get the Administrative install to work. how would large organisations deploy msi/s if they cannot push it out via group policy. Bob Arnson-6 wrote: Chris Vigelius wrote: Is there any chance to get the behaviour of uisample.msi with Mondo? Not at present: The admin dialogs aren't in WixUI. We have an open feature request on it but it comes up once or twice a year, so it hasn't been high priority. -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] adding a bootstrapper breaks comboboxes on custom UI!
bump,
anyone know how adding a bootstrapper could cause comboboxes to freeze on a
custom ui dialog?
cheers,
barry
barry wrote:
Hi,
I am having a strange problem with my installer.
Basically i have an installer for a c# com office addin. It uses a custom
UI that has a combo box on it.
The combobox sets a public property loglevel which has a default value of
1:
Property Id=LOGLEVEL Value=1 /
my custom UI code is as follows:
UIRef Id=WixUI_Common /
UIRef Id=WixUI_ErrorProgressText /
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=TARGETDIR /
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=UserInputDlg1/Publish
Publish Dialog=UserInputDlg Control=Back Event=NewDialog
Value=WelcomeDlg1/Publish
Publish Dialog=UserInputDlg Control=Next Event=NewDialog
Value=VerifyReadyDlg Order=21/Publish
Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog
Value=UserInputDlg Order=1NOT Installed/Publish
Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog
Value=MaintenanceTypeDlg Order=2Installed/Publish
Publish Dialog=MaintenanceWelcomeDlg Control=Next
Event=NewDialog Value=MaintenanceTypeDlg1/Publish
Publish Dialog=MaintenanceTypeDlg Control=RepairButton
Event=NewDialog Value=VerifyReadyDlg1/Publish
Publish Dialog=MaintenanceTypeDlg Control=RemoveButton
Event=NewDialog Value=VerifyReadyDlg1/Publish
Publish Dialog=MaintenanceTypeDlg Control=Back
Event=NewDialog Value=MaintenanceWelcomeDlg1/Publish
Dialog Id=UserInputDlg Width=370 Height=270
Title=[ProductName] Setup
Control Id=Title Type=Text X=15 Y=6 Width=200
Height=15 Transparent=yes NoPrefix=yes
Text={\WixUI_Font_Title}Installation Configuration /
Control Id=Description Type=Text X=25 Y=23 Width=280
Height=15 Transparent=yes NoPrefix=yes Text=Enter the following
information to configure your installation /
Control Id=BannerBitmap Type=Bitmap X=0 Y=0 Width=370
Height=44 TabSkip=no Text=!(loc.InstallDirDlgBannerBitmap) /
Control Id=BannerLine Type=Line X=0 Y=44 Width=370
Height=0 /
Control Id=LogLevelLabel Type=Text X=30 Y=62 Width=90
Height=13 Text=Logging Level: /
Control Id=LogLevelText Type=ComboBox X=130 Y=60
Width=70 Height=15 Property=LOGLEVEL TabSkip=no ComboList=yes
Sorted=yes
ComboBox Property=LOGLEVEL
ListItem Text=Error Value=0 /
ListItem Text=Info Value=1 /
ListItem Text=Debug Value=2 /
/ComboBox
/Control
!--
Control Id=IsTestingLabel Type=Text X=30 Y=95 Width=90
Height=13 Text=Testing Mode: /
Control Id=IsTestingText Type=ComboBox X=130 Y=93
Width=70 Height=18 Property=ISTESTING TabSkip=no ComboList=yes
Sorted=yes
ComboBox Property=ISTESTING
ListItem Text=Yes Value=1 /
ListItem Text=No Value=0 /
/ComboBox
/Control
--
!--
Control Id=DocsUrlLabel Type=Text X=30 Y=128 Width=90
Height=13 Text=Document Upload URL: /
Control Id=DocsUrlText Type=Edit X=130 Y=126 Width=170
Height=18 Property=DOCSURL Text=47 /
--
Control Id=BottomLine Type=Line X=0 Y=234 Width=370
Height=0 /
Control Id=Next Type=PushButton X=236 Y=243 Width=56
Height=17 Default=yes Text=Next /
Control Id=Back Type=PushButton X=180 Y=243 Width=56
Height=17 Text=Back /
Control Id=Cancel Type=PushButton X=304 Y=243 Width=56
Height=17 Cancel=yes Text=Cancel
Publish Event=SpawnDialog Value=CancelDlg1/Publish
/Control
/Dialog
/UI
This works fine when i build the msi and run it. My combobox works as you
would expect and the public propery is set correctly based on user choice.
http://www.padraiglarkin.com/temp/clicked_msi.jpg click here for
screenshot
The problem is that when I add a bootstrapper to the installation the
combobox becomes locked. I click on the setup.exe. My bootstrapped
components get installed and then the installer runs. When it get to my
custom combobox screen only the default value appears and when you click
to expand the combobox nothing happens.
[WiX-users] Turn off licence in UI
Sorry if this has been asked before, but is there a way not to display the licence agreement when using WixUI? http://www.bbc.co.uk/ This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this. -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Turn off licence in UI
I think this is pretty good for a how to by Neil Sleighthom.. http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html Med vennlig hilsen /Regards Brian 2009/4/23 Mike Scott mike.sc...@bbc.co.uk Sorry if this has been asked before, but is there a way not to display the licence agreement when using WixUI? http://www.bbc.co.uk/ This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this. -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Retriving msiexec command-line options
Retrieving msiexec command-line options Anyone knows how to retrieve the command-line options used to start installer? I understand how to pass/retrieve properties like PROPERTY=PropertyValue via command line but I have no idea how to retrieve options like /quiet /passive etc. Example: msiexec /quiet (I would like to know is the user specified /quiet in the command-line) -- View this message in context: http://n2.nabble.com/Retriving-msiexec-command-line-options-tp2683347p2683347.html Sent from the wix-users mailing list archive at Nabble.com. -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Retriving msiexec command-line options
http://msdn.microsoft.com/en-us/library/aa372096.aspx Palbinder Sandher Software Deployment IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: slmnow [mailto:slm...@hotmail.com] Sent: 23 April 2009 14:55 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Retriving msiexec command-line options Retrieving msiexec command-line options Anyone knows how to retrieve the command-line options used to start installer? I understand how to pass/retrieve properties like PROPERTY=PropertyValue via command line but I have no idea how to retrieve options like /quiet /passive etc. Example: msiexec /quiet (I would like to know is the user specified /quiet in the command-line) -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Turn off licence in UI
Perfect. Except of course I'm using WiX 2. Can anyone point me to a differences between 2 and 3 page? -Original Message- From: Brian Bakkebo [mailto:bbakk...@gmail.com] Sent: 23 April 2009 14:56 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Turn off licence in UI I think this is pretty good for a how to by Neil Sleighthom.. http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html Med vennlig hilsen /Regards Brian http://www.bbc.co.uk/ This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this. -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Retriving msiexec command-line options
thanks, but I specifically need to know when the user supplies the /passive
command-line switch. By default my uninstall is done at UIlevel=3 (or
INSTALLUILEVEL_BASIC) witch is the same as using the /passive switch.
So how can i differentiate between the user doing msiexec /passive /x
{xxx-xxx} vs a normal uninstall. See if it's a normal uninstall I want to
display a Remove User Data message box and if it's a /passive uninstall I
don't want to display anything.
Pally Sandher wrote:
http://msdn.microsoft.com/en-us/library/aa372096.aspx
Palbinder Sandher
Software Deployment IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the Virtual Environment**
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
-Original Message-
From: slmnow [mailto:slm...@hotmail.com]
Sent: 23 April 2009 14:55
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Retriving msiexec command-line options
Retrieving msiexec command-line options
Anyone knows how to retrieve the command-line options used to start
installer? I understand how to pass/retrieve properties like
PROPERTY=PropertyValue via command line but I have no idea how to
retrieve options like /quiet /passive etc.
Example:
msiexec /quiet (I would like to know is the user specified /quiet in the
command-line)
--
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
View this message in context:
http://n2.nabble.com/Retriving-msiexec-command-line-options-tp2683347p2683781.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Reference custom directory
*Bump Sorry for the bump but I'm really interested to know if this is even possible... Thank you. dkijc wrote: Hi everyone! I'm trying to to make a dialog with two options (radio buttons): 1. Fetch thumbnails from the WebServer 2. If not, I want the user to specify a directory where the thumbnails are stored in the disk so we can fetch it from that folder. - The machine usually has a default location where the thumbnails resides, so I want that default directory to be the default location that appears in the field - however the user might have the thumbnail stored on a different location so I want to provide a 'Browse' button for the user to tell our installer where to look for the thumbnails In the end, I want our installer class to know which option the user chose (Web or Local) and if it's web, fetch the thumbnails from the web server but if it's local, get the directory that the user specified (or the default location, if no location was browsed by the user) Is this possible to do? If so I would REALLY appreciate it if you kind guys could shed me some light :) Thanks and god bless! -D -- View this message in context: http://n2.nabble.com/Reference-custom-directory-tp2670501p2683849.html Sent from the wix-users mailing list archive at Nabble.com. -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Turn off licence in UI
Sorry, Can you not upgrade up to wix 3? I think I read you can do it in Wix 2.0 but it is more limited I think in what you can do.. Med vennlig hilsen /Regards Brian 2009/4/23 Mike Scott mike.sc...@bbc.co.uk Perfect. Except of course I'm using WiX 2. Can anyone point me to a differences between 2 and 3 page? -Original Message- From: Brian Bakkebo [mailto:bbakk...@gmail.com] Sent: 23 April 2009 14:56 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Turn off licence in UI I think this is pretty good for a how to by Neil Sleighthom.. http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html Med vennlig hilsen /Regards Brian http://www.bbc.co.uk/ This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this. -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Subversion revision number through a wixproject file using msbuild community tasks
Here's a snippet of what you want to do:
!-- Embed Version target into the build process --
PropertyGroup
Version;
$(CoreBuildDependsOn)
/PropertyGroup
!--Get Subversion Revision here-you must use MSBUILDCommunityTasks:--
Target Name=Version
SvnVersion ToolPath=$(Subversion) LocalPath=..\
Output TaskParameter=Revision PropertyName=Revision/
/SvnVersion
Message Text=Version: $(Revision) Importance=high/
!-- MSBuild 3.5 Syntax --
PropertyGroup
!-- If DefineConstants is not defined --
DefineConstants Condition='$(DefineConstants)' ==
''SubversionRevision=$(Revision)/DefineConstants
!-- If DefineConstants is defined --
DefineConstants Condition='$(DefineConstants)' !=
''$(DefineConstants);SubversionRevision=$(Revision)/DefineConstants
/PropertyGroup
!-- MSBuild 2.0 Syntax --
!-- If DefineConstants is not defined --
CreateProperty Condition='$(DefineConstants)' == ''
Value=SubversionRevision=$(Revision)
Output TaskParameter=Value PropertyName=DefineConstants/
/CreateProperty
!-- If DefineConstants is defined --
CreateProperty Condition='$(DefineConstants)' != ''
Value=$(DefineConstants);SubversionRevision=$(Revision)
Output TaskParameter=Value PropertyName=DefineConstants/
/CreateProperty
/Target
You don't need both the MSBuild 2.0 and 3.5 syntaxes. I use Visual Studio 2008
so I use MSBuild 3.5 syntax. Technically, the !-- If DefineConstants is not
defined -- portions are not necessary because you always define
DefineConstants at the project scope. Here's how I would rewrite your entire
project:
Project DefaultTargets=Build
xmlns=http://schemas.microsoft.com/developer/msbuild/2003;
!--Main Property group--
PropertyGroup
Configuration Condition= '$(Configuration)' == ''Debug/Configuration
Platform Condition= '$(Platform)' == '' x86/Platform
ProductVersion1.0/ProductVersion
ProjectGuid{1bc4cf27-badd-47e0-87a7-9e3ed0c8c50b}/ProjectGuid
SchemaVersion2.0/SchemaVersion
OutputNameWix_TagImport/OutputName
OutputTypePackage/OutputType
WixToolPath..\..\DLL\Wix\/WixToolPath
Subversion..\..\DLL\CollabNet Subversion Client/Subversion
MSBUILDCommunityTasks..\..\DLL\MSBuildCommunityTasks\/MSBUILDCommunityTasks
WixTasksPath$(WixToolPath)\wixtasks.dll/WixTasksPath
WixTargetsPath$(WixToolPath)\Wix.targets/WixTargetsPath
Culturesen-us/Cultures
LinkerBaseInputPaths..\MYAPP\bin\Release/LinkerBaseInputPaths
/PropertyGroup
Import Project=$(WixToolPath)\Wix.targets /
Import Project=$(MSBUILDCommunityTasks)\MSBuild.Community.Tasks.Targets/
!--Include wix files here:--
ItemGroup
WixExtension Include=WixUtilExtension
HintPath$(WixToolPath)\WixUtilExtension.dll/HintPath
/WixExtension
WixExtension Include=WixUIExtension
HintPath$(WixToolPath)\WixUIExtension.dll/HintPath
/WixExtension
/ItemGroup
ItemGroup
Content Include=Config.wxi /
Compile Include=Product.wxs /
Compile Include=WixUI_Minimal_NoLicense.wxs /
Compile Include=Components.wxs /
/ItemGroup
PropertyGroup
Version;
$(CoreBuildDependsOn)
/PropertyGroup
!--Get Subversion Revision here-you must use MSBUILDCommunityTasks:--
Target Name=Version
SvnVersion ToolPath=$(Subversion) LocalPath=..\
Output TaskParameter=Revision PropertyName=Revision/
/SvnVersion
Message Text=Version: $(Revision) Importance=high/
PropertyGroup
DefineConstants$(DefineConstants);SubversionRevision=$(Revision)/DefineConstants
/PropertyGroup
/Target
!--Output based on Release or Debug--
PropertyGroup Condition= '$(Configuration)|$(Platform)' == 'Debug|x86'
OutputPathbin\$(Configuration)\/OutputPath
IntermediateOutputPathobj\$(Configuration)\/IntermediateOutputPath
DefineConstantsDebug;ReleaseDir=..\MYAPP\bin\Release\/DefineConstants
/PropertyGroup
PropertyGroup Condition= '$(Configuration)|$(Platform)' == 'Release|x86'
OutputPathbin\$(Configuration)\/OutputPath
IntermediateOutputPathobj\$(Configuration)\/IntermediateOutputPath
DefineConstantsDebug;ReleaseDir=..\MYAPP\bin\Release\/DefineConstants
/PropertyGroup
/Project
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail
-Original Message-
From: Brian Bakkebo [mailto:bbakk...@gmail.com]
Sent: Wednesday, April 22, 2009 4:27 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Subversion revision number through a
wixproject file using msbuild community tasks
Thanks again for your response EdwinYep, I use the same CollabNet
release for testing. Yep, I expected that also, but I dont see it,
which leads me to believe that there is some kind of pathing/mapping
problem. Also, I am not quite sure on the syntax for DefineConstants
inside the
Re: [WiX-users] Subversion revision number through a wixproject file using msbuild community tasks
Correction:
PropertyGroup
Version;
$(CoreBuildDependsOn)
/PropertyGroup
Should be:
PropertyGroup
CoreBuildDependsOn
Version;
$(CoreBuildDependsOn)
/CoreBuildDependsOn
/PropertyGroup
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail
-Original Message-
From: Castro, Edwin (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Thursday, April 23, 2009 9:08 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Subversion revision number through a
wixproject file using msbuild community tasks
Here's a snippet of what you want to do:
!-- Embed Version target into the build process --
PropertyGroup
Version;
$(CoreBuildDependsOn)
/PropertyGroup
!--Get Subversion Revision here-you must use MSBUILDCommunityTasks:-
-
Target Name=Version
SvnVersion ToolPath=$(Subversion) LocalPath=..\
Output TaskParameter=Revision PropertyName=Revision/
/SvnVersion
Message Text=Version: $(Revision) Importance=high/
!-- MSBuild 3.5 Syntax --
PropertyGroup
!-- If DefineConstants is not defined --
DefineConstants Condition='$(DefineConstants)' ==
''SubversionRevision=$(Revision)/DefineConstants
!-- If DefineConstants is defined --
DefineConstants Condition='$(DefineConstants)' !=
''$(DefineConstants);SubversionRevision=$(Revision)/DefineConstants
/PropertyGroup
!-- MSBuild 2.0 Syntax --
!-- If DefineConstants is not defined --
CreateProperty Condition='$(DefineConstants)' == ''
Value=SubversionRevision=$(Revision)
Output TaskParameter=Value PropertyName=DefineConstants/
/CreateProperty
!-- If DefineConstants is defined --
CreateProperty Condition='$(DefineConstants)' != ''
Value=$(DefineConstants);SubversionRevision=$(Revision)
Output TaskParameter=Value PropertyName=DefineConstants/
/CreateProperty
/Target
You don't need both the MSBuild 2.0 and 3.5 syntaxes. I use Visual
Studio 2008 so I use MSBuild 3.5 syntax. Technically, the !-- If
DefineConstants is not defined -- portions are not necessary because
you always define DefineConstants at the project scope. Here's how I
would rewrite your entire project:
Project DefaultTargets=Build
xmlns=http://schemas.microsoft.com/developer/msbuild/2003;
!--Main Property group--
PropertyGroup
Configuration Condition= '$(Configuration)' ==
''Debug/Configuration
Platform Condition= '$(Platform)' == '' x86/Platform
ProductVersion1.0/ProductVersion
ProjectGuid{1bc4cf27-badd-47e0-87a7-9e3ed0c8c50b}/ProjectGuid
SchemaVersion2.0/SchemaVersion
OutputNameWix_TagImport/OutputName
OutputTypePackage/OutputType
WixToolPath..\..\DLL\Wix\/WixToolPath
Subversion..\..\DLL\CollabNet Subversion Client/Subversion
MSBUILDCommunityTasks..\..\DLL\MSBuildCommunityTasks\/MSBUILDCommuni
tyTasks
WixTasksPath$(WixToolPath)\wixtasks.dll/WixTasksPath
WixTargetsPath$(WixToolPath)\Wix.targets/WixTargetsPath
Culturesen-us/Cultures
LinkerBaseInputPaths..\MYAPP\bin\Release/LinkerBaseInputPaths
/PropertyGroup
Import Project=$(WixToolPath)\Wix.targets /
Import
Project=$(MSBUILDCommunityTasks)\MSBuild.Community.Tasks.Targets/
!--Include wix files here:--
ItemGroup
WixExtension Include=WixUtilExtension
HintPath$(WixToolPath)\WixUtilExtension.dll/HintPath
/WixExtension
WixExtension Include=WixUIExtension
HintPath$(WixToolPath)\WixUIExtension.dll/HintPath
/WixExtension
/ItemGroup
ItemGroup
Content Include=Config.wxi /
Compile Include=Product.wxs /
Compile Include=WixUI_Minimal_NoLicense.wxs /
Compile Include=Components.wxs /
/ItemGroup
PropertyGroup
Version;
$(CoreBuildDependsOn)
/PropertyGroup
!--Get Subversion Revision here-you must use MSBUILDCommunityTasks:-
-
Target Name=Version
SvnVersion ToolPath=$(Subversion) LocalPath=..\
Output TaskParameter=Revision PropertyName=Revision/
/SvnVersion
Message Text=Version: $(Revision) Importance=high/
PropertyGroup
DefineConstants$(DefineConstants);SubversionRevision=$(Revision)/Def
ineConstants
/PropertyGroup
/Target
!--Output based on Release or Debug--
PropertyGroup Condition= '$(Configuration)|$(Platform)' ==
'Debug|x86'
OutputPathbin\$(Configuration)\/OutputPath
IntermediateOutputPathobj\$(Configuration)\/IntermediateOutputPath
DefineConstantsDebug;ReleaseDir=..\MYAPP\bin\Release\/DefineConstant
s
/PropertyGroup
PropertyGroup Condition= '$(Configuration)|$(Platform)' ==
'Release|x86'
OutputPathbin\$(Configuration)\/OutputPath
IntermediateOutputPathobj\$(Configuration)\/IntermediateOutputPath
DefineConstantsDebug;ReleaseDir=..\MYAPP\bin\Release\/DefineConstant
s
/PropertyGroup
[WiX-users] How to disable/bypass FilesInUse dialog
Hello, Is there any easy way (attribute/property to be set) how to disable Files In Use dialog which pops up during the uninstallation process. I simply don't want to bother user with this dialog even if all of installed executables are running. Thanks for your help. Regards, Jan -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Reference custom directory
Hi Pally, Thank you so much for your response! That gives me hope haha. I was actually reading the blog by Neil and had a question. I understand I can get the directory to be set but that's an installation directory. Can I create a custom directory OR can I actually use the INSTALLDIR (or whatever it is called) and when the installation is run can I trick the installer so instead of using the directory for installation folder actually snatch that directory to be stored in a variable within our code so our application knows where to look for the thumbnails? We can fetched the thumbnails over the web just fine but now our application is deployed in the same machine where we fetch the thumbnails so instead of going through a loop with http request we can easily look for thumbnails in the local machine. The reason for asking the path for the folder is because thumbnails are not always stored in the same folder, as that is a preference that a user can set. The problem I was having was when I created a custom dialog (using orca)that asks whether the use wants our application to fetch the thumbnail over the web or just from their local machine. Opening a browse dialog works fine but every time I chose a folder and press 'ok' I'd get '2707' (target not specified). And wasn't sure exactly what was causing the problem. I'm assuming it probably has to do with custom action and was wondering if WiX had a better way of going about it. So my question still remains, is it possible to create a custom ID or variable to store the directory (which is not meant for installation but only purpose is to pass down the directory path into our code). I really hope that made sense... haha thanks, again! 1. The web stuff I'm not sure about. It's likely possible using custom actions as with most things. Someone else may have tried something similar but I don't think pulling arbitrary files off a web server is supported by default in the Windows Installer. 2. Very possible using standard Windows Installer UI controls. Have a look at the InstallDirDlg.wxs in the WiX 3.0 sources which does pretty much what you're trying to here except you'd need to hook it into the radio buttons first. You can even use the BrowseDlg in WiXUI without modification for your browse button. Neil Sleightholm's blog on customizing the WiXUI at http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html should help point you in the right direction. Personally I'd tackle it as 2 separate issues and get the second part working as you'd like it to first, as the web stuff looks like it could take a lot of time to get working right but that's me and I could be wrong. Good luck Palbinder Sandher Software Deployment IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -- View this message in context: http://n2.nabble.com/Reference-custom-directory-tp2670501p2685638.html Sent from the wix-users mailing list archive at Nabble.com. -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to disable/bypass FilesInUse dialog
http://www.installsite.org/pages/en/msifaq/a/1042.htm -Brian Simoneau -Original Message- From: Jan Bilek [mailto:bil...@gmail.com] Sent: Thursday, April 23, 2009 2:58 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] How to disable/bypass FilesInUse dialog Hello, Is there any easy way (attribute/property to be set) how to disable Files In Use dialog which pops up during the uninstallation process. I simply don't want to bother user with this dialog even if all of installed executables are running. Thanks for your help. Regards, Jan -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output
Hi,
In 3.0.4923, I used to get the following output (note how the Interface
element is *outside* of the File element):
Component Id=DisplayFridayListUI.dll
Guid={C4773BDF-6383-423D-BB34-BBB961BFD6DF}
File Id=DisplayFridayListUI.dll
Name=DisplayFridayListUI.dll KeyPath=yes Source=D:\Builds\PRISM
XP\Build 11.50.\Bin\PRISMMsi\DisplayFridayListUI.dll
Class Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}
Context=InprocServer32
Description=DisplayFridayListUI.CDisplayFridayList
Server=DisplayFridayListUI.dll ThreadingModel=apartment Version=1.0
ProgId Id=DisplayFridayListUI.CDisplayFridayList
Description=DisplayFridayListUI.CDisplayFridayList
/ProgId
/Class
/File
Interface Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}
Name=CDisplayFridayList
ProxyStubClassId={00020424---C000-0046}
ProxyStubClassId32={00020424---C000-0046}
/Interface
In 3.0.5217, the heat output is (note how the Interface element is *inside*
the File element):
Component Id=cmp40C4F6ADC9C48FEFA7144101F481848A
Guid={00C04661-3A43-4FD9-B484-0B27EF2BF049}
Class Id={D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}
Context=InprocServer32 Description=VBPropertyBag
ThreadingModel=apartment ForeignServer=msvbvm60.dll /
File Id=filA79D608464525B697087B7D7200AF704
KeyPath=yes Source=SourceDir\DisplayFridayListUI.dll
TypeLib Id={3515D627-3FA0-490F-9330-02A73023E0C0}
Description=DisplayFridayListUI
HelpDirectory=dir667CD14ED201BFF0942A99F02E55F065 Language=0
MajorVersion=1 MinorVersion=0
Class
Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9} Context=InprocServer32
Description=DisplayFridayListUI.CDisplayFridayList
ThreadingModel=apartment Version=1.0 Programmable=yes
ProgId
Id=DisplayFridayListUI.CDisplayFridayList
Description=DisplayFridayListUI.CDisplayFridayList /
/Class
Interface
Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594} Name=CDisplayFridayList
ProxyStubClassId={00020424---C000-0046}
ProxyStubClassId32={00020424---C000-0046} /
/TypeLib
/File
Using the -svb6 doesn't change anything. When using Candle to compile, I
get the following error:
error CNDL0005 : The File element contains an unexpected child element
'Interface'.
This wasn't the case before. Should I file a bug? I'm sure you're starting
to hate my constant emails regarding vb6 and heat :)
--
View this message in context:
http://n2.nabble.com/Heat-3.0.4923-vs-3.0.5217-vb6-dll-output-tp2686239p2686239.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Crystal Reports #45; New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty#45;free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Avoiding ICE30 Errors When Installing Config Files Associated with Policy Assemblies
I have two publisher policy assemblies (i.e. lets say one for version 8.6 and one for version 8.7). Both policy assemblies use the same config file. In order to successfully install these publisher policy files, MSI/fusion requires that the policy assembly and the config policy file are in the same installer component. So this means I need to put the same config file in two different components whihc causes the ICE30 error. Does anybody have suggestions on what the best practice should be in this case? Thanks -- View this message in context: http://n2.nabble.com/Avoiding-ICE30-Errors-When-Installing-Config-Files-Associated-with-Policy-Assemblies-tp2686289p2686289.html Sent from the wix-users mailing list archive at Nabble.com. -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output
Roy,
One question on this however. From the code you sent the Interface /
element is actually under the TypeLib / which is legal. Are you sure that
it is that actual line and not some where else?
Thanks,
Brian Rogers
Intelligence removes complexity. - Me
http://icumove.spaces.live.com
On Thu, Apr 23, 2009 at 2:07 PM, Brian Rogers rogers.br...@gmail.comwrote:
Hey Roy,
Please file a bug.
Thanks,
Brian Rogers
Intelligence removes complexity. - Me
http://icumove.spaces.live.com
On Thu, Apr 23, 2009 at 1:31 PM, Roy Abou Assaly royass...@gmail.comwrote:
Hi,
In 3.0.4923, I used to get the following output (note how the Interface
element is *outside* of the File element):
Component Id=DisplayFridayListUI.dll
Guid={C4773BDF-6383-423D-BB34-BBB961BFD6DF}
File Id=DisplayFridayListUI.dll
Name=DisplayFridayListUI.dll KeyPath=yes Source=D:\Builds\PRISM
XP\Build 11.50.\Bin\PRISMMsi\DisplayFridayListUI.dll
Class Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}
Context=InprocServer32
Description=DisplayFridayListUI.CDisplayFridayList
Server=DisplayFridayListUI.dll ThreadingModel=apartment Version=1.0
ProgId Id=DisplayFridayListUI.CDisplayFridayList
Description=DisplayFridayListUI.CDisplayFridayList
/ProgId
/Class
/File
Interface Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}
Name=CDisplayFridayList
ProxyStubClassId={00020424---C000-0046}
ProxyStubClassId32={00020424---C000-0046}
/Interface
In 3.0.5217, the heat output is (note how the Interface element is
*inside*
the File element):
Component Id=cmp40C4F6ADC9C48FEFA7144101F481848A
Guid={00C04661-3A43-4FD9-B484-0B27EF2BF049}
Class Id={D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}
Context=InprocServer32 Description=VBPropertyBag
ThreadingModel=apartment ForeignServer=msvbvm60.dll /
File Id=filA79D608464525B697087B7D7200AF704
KeyPath=yes Source=SourceDir\DisplayFridayListUI.dll
TypeLib
Id={3515D627-3FA0-490F-9330-02A73023E0C0}
Description=DisplayFridayListUI
HelpDirectory=dir667CD14ED201BFF0942A99F02E55F065 Language=0
MajorVersion=1 MinorVersion=0
Class
Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9} Context=InprocServer32
Description=DisplayFridayListUI.CDisplayFridayList
ThreadingModel=apartment Version=1.0 Programmable=yes
ProgId
Id=DisplayFridayListUI.CDisplayFridayList
Description=DisplayFridayListUI.CDisplayFridayList /
/Class
Interface
Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594} Name=CDisplayFridayList
ProxyStubClassId={00020424---C000-0046}
ProxyStubClassId32={00020424---C000-0046} /
/TypeLib
/File
Using the -svb6 doesn't change anything. When using Candle to compile, I
get the following error:
error CNDL0005 : The File element contains an unexpected child element
'Interface'.
This wasn't the case before. Should I file a bug? I'm sure you're
starting
to hate my constant emails regarding vb6 and heat :)
--
View this message in context:
http://n2.nabble.com/Heat-3.0.4923-vs-3.0.5217-vb6-dll-output-tp2686239p2686239.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Crystal Reports #45; New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty#45;free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Crystal Reports #45; New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty#45;free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output
Hi Brian,
The bug is:
https://sourceforge.net/tracker/?func=detailaid=2779893group_id=105970atid=642714
I've attached a DLL you can use to test with in case you don't have one to
reproduce the issue.
Thanks!
Roy
Brian Rogers wrote:
Hey Roy,
Please file a bug.
Thanks,
Brian Rogers
Intelligence removes complexity. - Me
http://icumove.spaces.live.com
On Thu, Apr 23, 2009 at 1:31 PM, Roy Abou Assaly
royass...@gmail.comwrote:
Hi,
In 3.0.4923, I used to get the following output (note how the Interface
element is *outside* of the File element):
Component Id=DisplayFridayListUI.dll
Guid={C4773BDF-6383-423D-BB34-BBB961BFD6DF}
File Id=DisplayFridayListUI.dll
Name=DisplayFridayListUI.dll KeyPath=yes Source=D:\Builds\PRISM
XP\Build 11.50.\Bin\PRISMMsi\DisplayFridayListUI.dll
Class Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}
Context=InprocServer32
Description=DisplayFridayListUI.CDisplayFridayList
Server=DisplayFridayListUI.dll ThreadingModel=apartment
Version=1.0
ProgId Id=DisplayFridayListUI.CDisplayFridayList
Description=DisplayFridayListUI.CDisplayFridayList
/ProgId
/Class
/File
Interface Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}
Name=CDisplayFridayList
ProxyStubClassId={00020424---C000-0046}
ProxyStubClassId32={00020424---C000-0046}
/Interface
In 3.0.5217, the heat output is (note how the Interface element is
*inside*
the File element):
Component Id=cmp40C4F6ADC9C48FEFA7144101F481848A
Guid={00C04661-3A43-4FD9-B484-0B27EF2BF049}
Class Id={D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}
Context=InprocServer32 Description=VBPropertyBag
ThreadingModel=apartment ForeignServer=msvbvm60.dll /
File Id=filA79D608464525B697087B7D7200AF704
KeyPath=yes Source=SourceDir\DisplayFridayListUI.dll
TypeLib
Id={3515D627-3FA0-490F-9330-02A73023E0C0}
Description=DisplayFridayListUI
HelpDirectory=dir667CD14ED201BFF0942A99F02E55F065 Language=0
MajorVersion=1 MinorVersion=0
Class
Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9} Context=InprocServer32
Description=DisplayFridayListUI.CDisplayFridayList
ThreadingModel=apartment Version=1.0 Programmable=yes
ProgId
Id=DisplayFridayListUI.CDisplayFridayList
Description=DisplayFridayListUI.CDisplayFridayList /
/Class
Interface
Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594} Name=CDisplayFridayList
ProxyStubClassId={00020424---C000-0046}
ProxyStubClassId32={00020424---C000-0046} /
/TypeLib
/File
Using the -svb6 doesn't change anything. When using Candle to compile, I
get the following error:
error CNDL0005 : The File element contains an unexpected child element
'Interface'.
This wasn't the case before. Should I file a bug? I'm sure you're
starting
to hate my constant emails regarding vb6 and heat :)
--
View this message in context:
http://n2.nabble.com/Heat-3.0.4923-vs-3.0.5217-vb6-dll-output-tp2686239p2686239.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Crystal Reports #45; New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty#45;free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Crystal Reports #45; New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty#45;free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
View this message in context:
http://n2.nabble.com/Heat-3.0.4923-vs-3.0.5217-vb6-dll-output-tp2686239p2686605.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Crystal Reports #45; New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty#45;free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output
Roy
The interface element is inside the TypeLib element, I have just
checked my code and this is valid and has been the same for a while, so
the error doesn't really make sense. When you raise a bug is it possible
to include the DLL you are scanning?
Neil
-Original Message-
From: Brian Rogers [mailto:rogers.br...@gmail.com]
Sent: 23 April 2009 22:07
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output
Hey Roy,
Please file a bug.
Thanks,
Brian Rogers
Intelligence removes complexity. - Me
http://icumove.spaces.live.com
On Thu, Apr 23, 2009 at 1:31 PM, Roy Abou Assaly
royass...@gmail.comwrote:
Hi,
In 3.0.4923, I used to get the following output (note how the
Interface
element is *outside* of the File element):
Component Id=DisplayFridayListUI.dll
Guid={C4773BDF-6383-423D-BB34-BBB961BFD6DF}
File Id=DisplayFridayListUI.dll
Name=DisplayFridayListUI.dll KeyPath=yes Source=D:\Builds\PRISM
XP\Build 11.50.\Bin\PRISMMsi\DisplayFridayListUI.dll
Class Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}
Context=InprocServer32
Description=DisplayFridayListUI.CDisplayFridayList
Server=DisplayFridayListUI.dll ThreadingModel=apartment
Version=1.0
ProgId Id=DisplayFridayListUI.CDisplayFridayList
Description=DisplayFridayListUI.CDisplayFridayList
/ProgId
/Class
/File
Interface Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}
Name=CDisplayFridayList
ProxyStubClassId={00020424---C000-0046}
ProxyStubClassId32={00020424---C000-0046}
/Interface
In 3.0.5217, the heat output is (note how the Interface element is
*inside*
the File element):
Component Id=cmp40C4F6ADC9C48FEFA7144101F481848A
Guid={00C04661-3A43-4FD9-B484-0B27EF2BF049}
Class Id={D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}
Context=InprocServer32 Description=VBPropertyBag
ThreadingModel=apartment ForeignServer=msvbvm60.dll /
File Id=filA79D608464525B697087B7D7200AF704
KeyPath=yes Source=SourceDir\DisplayFridayListUI.dll
TypeLib
Id={3515D627-3FA0-490F-9330-02A73023E0C0}
Description=DisplayFridayListUI
HelpDirectory=dir667CD14ED201BFF0942A99F02E55F065 Language=0
MajorVersion=1 MinorVersion=0
Class
Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9} Context=InprocServer32
Description=DisplayFridayListUI.CDisplayFridayList
ThreadingModel=apartment Version=1.0 Programmable=yes
ProgId
Id=DisplayFridayListUI.CDisplayFridayList
Description=DisplayFridayListUI.CDisplayFridayList /
/Class
Interface
Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594} Name=CDisplayFridayList
ProxyStubClassId={00020424---C000-0046}
ProxyStubClassId32={00020424---C000-0046} /
/TypeLib
/File
Using the -svb6 doesn't change anything. When using Candle to
compile, I
get the following error:
error CNDL0005 : The File element contains an unexpected child element
'Interface'.
This wasn't the case before. Should I file a bug? I'm sure you're
starting
to hate my constant emails regarding vb6 and heat :)
--
View this message in context:
http://n2.nabble.com/Heat-3.0.4923-vs-3.0.5217-vb6-dll-output-tp2686239p
2686239.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Crystal Reports #45; New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty#45;free distribution of the report engine for externally
facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Crystal Reports #45; New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty#45;free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Crystal Reports #45; New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty#45;free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
___
WiX-users mailing list
Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output
Running heat and candle against the file you attached to the bug doesn't
generate the error you reported could you give more details of the
command lines you are using?
Neil
-Original Message-
From: Roy Abou Assaly [mailto:royass...@gmail.com]
Sent: 23 April 2009 22:18
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output
Hi Brian,
The bug is:
https://sourceforge.net/tracker/?func=detailaid=2779893group_id=105970
atid=642714
I've attached a DLL you can use to test with in case you don't have one
to
reproduce the issue.
Thanks!
Roy
Brian Rogers wrote:
Hey Roy,
Please file a bug.
Thanks,
Brian Rogers
Intelligence removes complexity. - Me
http://icumove.spaces.live.com
On Thu, Apr 23, 2009 at 1:31 PM, Roy Abou Assaly
royass...@gmail.comwrote:
Hi,
In 3.0.4923, I used to get the following output (note how the
Interface
element is *outside* of the File element):
Component Id=DisplayFridayListUI.dll
Guid={C4773BDF-6383-423D-BB34-BBB961BFD6DF}
File Id=DisplayFridayListUI.dll
Name=DisplayFridayListUI.dll KeyPath=yes Source=D:\Builds\PRISM
XP\Build 11.50.\Bin\PRISMMsi\DisplayFridayListUI.dll
Class Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}
Context=InprocServer32
Description=DisplayFridayListUI.CDisplayFridayList
Server=DisplayFridayListUI.dll ThreadingModel=apartment
Version=1.0
ProgId Id=DisplayFridayListUI.CDisplayFridayList
Description=DisplayFridayListUI.CDisplayFridayList
/ProgId
/Class
/File
Interface Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}
Name=CDisplayFridayList
ProxyStubClassId={00020424---C000-0046}
ProxyStubClassId32={00020424---C000-0046}
/Interface
In 3.0.5217, the heat output is (note how the Interface element is
*inside*
the File element):
Component Id=cmp40C4F6ADC9C48FEFA7144101F481848A
Guid={00C04661-3A43-4FD9-B484-0B27EF2BF049}
Class Id={D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}
Context=InprocServer32 Description=VBPropertyBag
ThreadingModel=apartment ForeignServer=msvbvm60.dll /
File Id=filA79D608464525B697087B7D7200AF704
KeyPath=yes Source=SourceDir\DisplayFridayListUI.dll
TypeLib
Id={3515D627-3FA0-490F-9330-02A73023E0C0}
Description=DisplayFridayListUI
HelpDirectory=dir667CD14ED201BFF0942A99F02E55F065 Language=0
MajorVersion=1 MinorVersion=0
Class
Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9} Context=InprocServer32
Description=DisplayFridayListUI.CDisplayFridayList
ThreadingModel=apartment Version=1.0 Programmable=yes
ProgId
Id=DisplayFridayListUI.CDisplayFridayList
Description=DisplayFridayListUI.CDisplayFridayList /
/Class
Interface
Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594} Name=CDisplayFridayList
ProxyStubClassId={00020424---C000-0046}
ProxyStubClassId32={00020424---C000-0046} /
/TypeLib
/File
Using the -svb6 doesn't change anything. When using Candle to
compile, I
get the following error:
error CNDL0005 : The File element contains an unexpected child
element
'Interface'.
This wasn't the case before. Should I file a bug? I'm sure you're
starting
to hate my constant emails regarding vb6 and heat :)
--
View this message in context:
http://n2.nabble.com/Heat-3.0.4923-vs-3.0.5217-vb6-dll-output-tp2686239p
2686239.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Crystal Reports #45; New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty#45;free distribution of the report engine for externally
facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Crystal Reports #45; New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty#45;free distribution of the report engine for externally
facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
View this message in context:
http://n2.nabble.com/Heat-3.0.4923-vs-3.0.5217-vb6-dll-output-tp2686239p
2686605.html
Sent from the wix-users mailing list archive at Nabble.com.
Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output
Both of you are correct. I have an XSLT that massage the XML that heat
generates in order to ensure certain shortcuts are added and changes a few
other things as well. In the process, the XSLT is not doing its job. I
would cancel the bug as it looks like like it's a data issue on my end.
Sorry for the trouble.
On Thu, Apr 23, 2009 at 5:39 PM, Neil Sleightholm (via Nabble)
ml-user+58265-122838...@n2.nabble.comml-user%2b58265-122838...@n2.nabble.com
wrote:
Running heat and candle against the file you attached to the bug doesn't
generate the error you reported could you give more details of the
command lines you are using?
Neil
-Original Message-
From: Roy Abou Assaly
[mailto:royass...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2686897i=0]
Sent: 23 April 2009 22:18
To:
wix-us...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2686897i=1
Subject: Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output
Hi Brian,
The bug is:
https://sourceforge.net/tracker/?func=detailaid=2779893group_id=105970
atid=642714
I've attached a DLL you can use to test with in case you don't have one
to
reproduce the issue.
Thanks!
Roy
Brian Rogers wrote:
Hey Roy,
Please file a bug.
Thanks,
Brian Rogers
Intelligence removes complexity. - Me
http://icumove.spaces.live.com
On Thu, Apr 23, 2009 at 1:31 PM, Roy Abou Assaly
royass...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2686897i=2wrote:
Hi,
In 3.0.4923, I used to get the following output (note how the
Interface
element is *outside* of the File element):
Component Id=DisplayFridayListUI.dll
Guid={C4773BDF-6383-423D-BB34-BBB961BFD6DF}
File Id=DisplayFridayListUI.dll
Name=DisplayFridayListUI.dll KeyPath=yes Source=D:\Builds\PRISM
XP\Build 11.50.\Bin\PRISMMsi\DisplayFridayListUI.dll
Class Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}
Context=InprocServer32
Description=DisplayFridayListUI.CDisplayFridayList
Server=DisplayFridayListUI.dll ThreadingModel=apartment
Version=1.0
ProgId Id=DisplayFridayListUI.CDisplayFridayList
Description=DisplayFridayListUI.CDisplayFridayList
/ProgId
/Class
/File
Interface Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}
Name=CDisplayFridayList
ProxyStubClassId={00020424---C000-0046}
ProxyStubClassId32={00020424---C000-0046}
/Interface
In 3.0.5217, the heat output is (note how the Interface element is
*inside*
the File element):
Component Id=cmp40C4F6ADC9C48FEFA7144101F481848A
Guid={00C04661-3A43-4FD9-B484-0B27EF2BF049}
Class Id={D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}
Context=InprocServer32 Description=VBPropertyBag
ThreadingModel=apartment ForeignServer=msvbvm60.dll /
File Id=filA79D608464525B697087B7D7200AF704
KeyPath=yes Source=SourceDir\DisplayFridayListUI.dll
TypeLib
Id={3515D627-3FA0-490F-9330-02A73023E0C0}
Description=DisplayFridayListUI
HelpDirectory=dir667CD14ED201BFF0942A99F02E55F065 Language=0
MajorVersion=1 MinorVersion=0
Class
Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9} Context=InprocServer32
Description=DisplayFridayListUI.CDisplayFridayList
ThreadingModel=apartment Version=1.0 Programmable=yes
ProgId
Id=DisplayFridayListUI.CDisplayFridayList
Description=DisplayFridayListUI.CDisplayFridayList /
/Class
Interface
Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594} Name=CDisplayFridayList
ProxyStubClassId={00020424---C000-0046}
ProxyStubClassId32={00020424---C000-0046} /
/TypeLib
/File
Using the -svb6 doesn't change anything. When using Candle to
compile, I
get the following error:
error CNDL0005 : The File element contains an unexpected child
element
'Interface'.
This wasn't the case before. Should I file a bug? I'm sure you're
starting
to hate my constant emails regarding vb6 and heat :)
--
View this message in context:
http://n2.nabble.com/Heat-3.0.4923-vs-3.0.5217-vb6-dll-output-tp2686239p
2686239.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty-free distribution of the report engine for externally
facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
___
WiX-users mailing list
wix-us...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2686897i=3
[WiX-users] Major Upgrade: some files are randomly not installed
Hi All, I run into a stange problem. Forgive me if this question is a bit of long. I try to make it shorter. I need your hlep. We're using WiX version 3.0.4805.0. The problem is: --- I have 3 builds. They have exactly the same feature set. They are just built at different time. So we can say they are almost identical. I ALWAYS use Major Upgrade. That means every time the new build will uninstall the previous build first and then install the new one. Of course, the build server updates the package code, product code, and the product version before making the build. All of these 3 builds have the same upgrade code. I thought these 3 builds can be used to upgrade each other. Namely, any build can upgrade another build without problem. But I found this is not true. Some times, when upgrading from a build to another, some files are not installed during upgrading. Then it caused the application crash. So this is very serious for us.. My question is: --- does anyone get the similar issue? Is this a known issue? Or even a bug in major upgrade(this is the last thing I'd like to say)? Please help. I'd like to clarify something here: --- 1. By installing each build alone without having any previous build, the installation is fine. All files are installed properly. 2. I'm sure Major Upgrade works. Because I keep the same UpgradeCode among these builds. Of course, I change package code, product code and product version each time before making a build. During upgrading, I can even visually see the previous build folder is removed prior the current build installation. 3. During upgrading, sometimes 1 file is missing; sometimes, 3 files are missing. 4. It always happens to one particular file or three files, but not other files. All of these 3 files have their own distinct GUID. And no, these GUIDs are never used by any other files or component. 5. I checked the log file, for successful upgrading, there are some log like this(for failed upgrading, these records can't be found in log file): MSI (s) (C4:54) [17:29:02:497]: Executing op: FileCopy(SourceName=nvhelxcr.dll|Win32Interop.dll,SourceCabKey=Win32Interop.dll,DestName=Win32Interop.dll,Attributes=1536,FileSize=10752,PerTick=32768,,VerifyMedia=1,CheckCRC=0,Version=1.0.3399.27010,Language=0,InstallMode=58982400,,,) MSI (s) (C4:54) [17:29:02:497]: File: C:\Program Files\MyCompany\MyApp\Win32Interop.dll;To be installed;Won't patch;No existing file MSI (s) (C4:54) [17:29:02:497]: Source for file 'Win32Interop.dll' is compressed InstallFiles: File: Win32Interop.dll, Directory: C:\Program Files\MyCompany\MyApp\, Size: 10752 MSI (s) (C4:54) [17:29:02:497]: Note: 1: 2318 2: C:\Program Files\MyCompany\MyApp\Win32Interop.dll MSI (s) (C4:54) [17:29:02:497]: Note: 1: 2360 6. I didn't really change anything when building these builds. They were just built at different time. To make more testing, I made 5 builds. Here are their versions and testing results: 4.0.59, 4.0.64, 4.0.65, 4.0.77, and 4.0.78 4.0 is the version, 59, 64 etc. is the build stamp. I then made the testing. I tried 20 upgrade installation among these 5 builds. Here are the results I got(I also attach a screen shot of this testing matrix, not sure if you can see it or not. But it should be the same as this table below): | 59 | 64 | 65 | 77 | 78 --- 59 | - | OK | OK | OK | OK --- 64 | KO-E2| - | KO-E2| OK | OK --- 65 | KO-E2| OK | - | OK | OK --- 77 | KO-E1| KO-E1| OK | - | OK --- 78 | KO-E1| OK | KO-E1| KO-E1| - --- The build stamp listed in the first row and column. Here is how to read this matrix: 1. For each unit, read the row first and then column. For example, the unit in the 2nd row and 4th column is read as 59-65. It means we need to install build 59 first and then build 65. So this upgrade(from 65 to 59) is OK. 2. - means there is no upgrade 3. OK means the upgrade is good. A good installation should install 37 files. 4. KO-E1 means upgrade is NOT OK, Error Case 1: it only installs 34 files, missing 3 files such as Win32Interop.dll etc. 5. KO-E2 means upgrade is NOT OK, Error Case 2: it only installs 36 files, missing Win32Interop.dll. This problem is really annoying. I tried my best to think about the whole thing, but I couldn't figure it out. I hope that is my problem. But, really, I went through my code again, there is nothing special about these files. As what you can see, the build 78 can be installed on top of 77, but not vice versa. It doesn't make sense. This problem might have happened before in our builds. But no one may have paid any
Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output
Still kind of stuck. I was able to generate the exact xml as Brian did.
Candle compiled fine, but light is complaining. I'm trying to generate a
merge module out of it. Getting this error:
[exec] D:\Builds\PRISM XP\Build 11.51.\Bin\PrismShell.wxs(18) :
error LGHT0130 : The primary key 'reg0387C011F3
F8A22BDFC14B72466D9C9A.C7AC8538_65ED_4C2B_AE16_6291871D0918' is duplicated
in table 'Registry'. Please remove one of the entries or rename a part of
the primary key to avoid the collision.
D:\Builds\PRISM XP\Build 11.51.\Bincandle -v PrismShell.wxs
Microsoft (R) Windows Installer Xml Compiler version 3.0.5217.0
Copyright (C) Microsoft Corporation. All rights reserved.
PrismShell.wxs
D:\Builds\PRISM XP\Build 11.51.\Binlight -v PrismShell.wixobj
Microsoft (R) Windows Installer Xml Linker version 3.0.5217.0
Copyright (C) Microsoft Corporation. All rights reserved.
Updating file information.
Creating cabinet files.
Creating cabinet
'C:\Users\roy\AppData\Local\Temp\jyewbz0r\#MergeModule.CABinet'.
Generating database.
D:\Builds\PRISM XP\Build 11.51.\Bin\PrismShell.wxs(18) : error LGHT0130
: The primary key 'reg0387C011F3F8A22BDFC14B
72466D9C9A.C7AC8538_65ED_4C2B_AE16_6291871D0918' is duplicated in table
'Registry'. Please remove one of the entries or
rename a part of the primary key to avoid the collision.
My merge module looks like this:
?xml version=1.0 encoding=utf-8?
Wix xmlns:wi=http://schemas.microsoft.com/wix/2006/wi;
xmlns=http://schemas.microsoft.com/wix/2006/wi;
Module Id=PrismShell Language=1033 Version=1.0.0.0
Package Id=C7AC8538-65ED-4C2B-AE16-6291871D0918 Description=PRISM
Shell Module Comments=PRISM Shell Merge Module Manufacturer=House of
Commons InstallerVersion=300
/Package
Icon Id=PRISM.ICO SourceFile=PRISM.exe
/Icon
Directory Id=TARGETDIR Name=SourceDir
Directory Id=ProgramFilesFolder Name=Program Files
Directory Id=HOCDir Name=House Of Commons
Directory Id=INSTALLLOCATION Name=PRISM Shell
Component Id=DisplayFridayListUI.dll
Guid={77B6CDD1-B9C6-4497-B7F5-242B9783D6A3}
File Id=DisplayFridayListUI.dll KeyPath=yes
Source=SourceDir\DisplayFridayListUI.dll
TypeLib
Id={3515D627-3FA0-490F-9330-02A73023E0C0}
Description=DisplayFridayListUI HelpDirectory=TARGETDIR Language=0
MajorVersion=1 MinorVersion=0
Class
Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}
Context=InprocServer32
Description=DisplayFridayListUI.CDisplayFridayList
ThreadingModel=apartment Version=1.0 Programmable=yes
ProgId
Id=DisplayFridayListUI.CDisplayFridayList
Description=DisplayFridayListUI.CDisplayFridayList /
/Class
Interface
Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}
Name=CDisplayFridayList
ProxyStubClassId={00020424---C000-0046}
ProxyStubClassId32={00020424---C000-0046} /
/TypeLib
/File
RegistryValue Root=HKCR
Key=CLSID\{9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}\Implemented
Categories\{40FC6ED5-2438-11CF-A3DB-080036F12502} Value= Type=string
Action=write /
RegistryValue Root=HKCR
Key=Interface\{2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}\ProxyStubClsid
Value={00020424---C000-0046} Type=string Action=write
/
RegistryValue Root=HKCR
Key=Interface\{2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}\ProxyStubClsid32
Value={00020424---C000-0046} Type=string Action=write
/
RegistryValue Root=HKCR
Key=Interface\{2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}
Value=_CDisplayFridayList Type=string Action=write /
/Component
/Directory
/Directory
/Directory
Directory Id=ProgramMenuFolder Name=Programs
Directory Id=ProgramMenuDir Name=PRISM
/Directory
/Directory
Directory Id=DesktopFolder SourceName=Desktop
/Directory
/Directory
/Module
/Wix
I then decided to simply remove the following in order to create my merge
module:
Interface Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}
Name=CDisplayFridayList
ProxyStubClassId={00020424---C000-0046}
ProxyStubClassId32={00020424---C000-0046} /
I then check my cleanup XSLT which I used to use to clean up the messy vb6
output, and realized that I used to remove any element with the following
attribute:
000204EF---C000-0046
compare that to:
00020424---C000-0046
Which is slightly off. Me thinks I should also add this to the cleanup xslt
file.
You can copy paste it and try it out. I'm a bit stuck. Perhaps I've been
staring at this for
Re: [WiX-users] Major Upgrade: some files are randomly not installed
Sorry, I forgot to attach the screen shot of the testing matrix. Here it is in the attachment. Hopefully you can see it. Thanks you all. /Brian __ Be smarter than spam. See how smart SpamGuard is at giving junk email the boot with the All-new Yahoo! Mail. Click on Options in Mail and switch to New Mail today or register for free at http://mail.yahoo.ca-- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output
Oh, and one more:
00020420---C000-0046
After that, I was able to build my merge module and link them and create my
MSI which contains 129 vb6 com DLLs and various OCXs. Again, my experience
in this area is weak, but the product seems to install and uninstall without
issues even though I remove those elements that I didn't fully understand.
Roy Abou Assaly wrote:
Still kind of stuck. I was able to generate the exact xml as Brian did.
Candle compiled fine, but light is complaining. I'm trying to generate a
merge module out of it. Getting this error:
[exec] D:\Builds\PRISM XP\Build 11.51.\Bin\PrismShell.wxs(18) :
error LGHT0130 : The primary key 'reg0387C011F3
F8A22BDFC14B72466D9C9A.C7AC8538_65ED_4C2B_AE16_6291871D0918' is duplicated
in table 'Registry'. Please remove one of the entries or rename a part of
the primary key to avoid the collision.
D:\Builds\PRISM XP\Build 11.51.\Bincandle -v PrismShell.wxs
Microsoft (R) Windows Installer Xml Compiler version 3.0.5217.0
Copyright (C) Microsoft Corporation. All rights reserved.
PrismShell.wxs
D:\Builds\PRISM XP\Build 11.51.\Binlight -v PrismShell.wixobj
Microsoft (R) Windows Installer Xml Linker version 3.0.5217.0
Copyright (C) Microsoft Corporation. All rights reserved.
Updating file information.
Creating cabinet files.
Creating cabinet
'C:\Users\roy\AppData\Local\Temp\jyewbz0r\#MergeModule.CABinet'.
Generating database.
D:\Builds\PRISM XP\Build 11.51.\Bin\PrismShell.wxs(18) : error
LGHT0130 : The primary key 'reg0387C011F3F8A22BDFC14B
72466D9C9A.C7AC8538_65ED_4C2B_AE16_6291871D0918' is duplicated in table
'Registry'. Please remove one of the entries or
rename a part of the primary key to avoid the collision.
My merge module looks like this:
?xml version=1.0 encoding=utf-8?
Wix xmlns:wi=http://schemas.microsoft.com/wix/2006/wi;
xmlns=http://schemas.microsoft.com/wix/2006/wi;
Module Id=PrismShell Language=1033 Version=1.0.0.0
Package Id=C7AC8538-65ED-4C2B-AE16-6291871D0918 Description=PRISM
Shell Module Comments=PRISM Shell Merge Module Manufacturer=Acme
InstallerVersion=300
/Package
Icon Id=PRISM.ICO SourceFile=PRISM.exe
/Icon
Directory Id=TARGETDIR Name=SourceDir
Directory Id=ProgramFilesFolder Name=Program Files
Directory Id=HOCDir Name=Acme
Directory Id=INSTALLLOCATION Name=PRISM Shell
Component Id=DisplayFridayListUI.dll
Guid={77B6CDD1-B9C6-4497-B7F5-242B9783D6A3}
File Id=DisplayFridayListUI.dll KeyPath=yes
Source=SourceDir\DisplayFridayListUI.dll
TypeLib
Id={3515D627-3FA0-490F-9330-02A73023E0C0}
Description=DisplayFridayListUI HelpDirectory=TARGETDIR Language=0
MajorVersion=1 MinorVersion=0
Class
Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}
Context=InprocServer32
Description=DisplayFridayListUI.CDisplayFridayList
ThreadingModel=apartment Version=1.0 Programmable=yes
ProgId
Id=DisplayFridayListUI.CDisplayFridayList
Description=DisplayFridayListUI.CDisplayFridayList /
/Class
Interface
Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}
Name=CDisplayFridayList
ProxyStubClassId={00020424---C000-0046}
ProxyStubClassId32={00020424---C000-0046} /
/TypeLib
/File
RegistryValue Root=HKCR
Key=CLSID\{9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}\Implemented
Categories\{40FC6ED5-2438-11CF-A3DB-080036F12502} Value= Type=string
Action=write /
RegistryValue Root=HKCR
Key=Interface\{2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}\ProxyStubClsid
Value={00020424---C000-0046} Type=string
Action=write /
RegistryValue Root=HKCR
Key=Interface\{2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}\ProxyStubClsid32
Value={00020424---C000-0046} Type=string
Action=write /
RegistryValue Root=HKCR
Key=Interface\{2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}
Value=_CDisplayFridayList Type=string Action=write /
/Component
/Directory
/Directory
/Directory
Directory Id=ProgramMenuFolder Name=Programs
Directory Id=ProgramMenuDir Name=PRISM
/Directory
/Directory
Directory Id=DesktopFolder SourceName=Desktop
/Directory
/Directory
/Module
/Wix
I then decided to simply remove the following in order to create my merge
module:
Interface Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}
Name=CDisplayFridayList
ProxyStubClassId={00020424---C000-0046}
[WiX-users] How To Create Successive Patches That Supersede Previous?
I tried looking through the digests on sourceforge but couldn't find a way to search, and didn't see this question answered so I apologize if it's a duplicate. I am trying to create patches for a product that will each be all encompassing of the previous ones, and want anybody at any version to be able to install the latest patch. Following the instructions on the site I can create patches just fine, so I can install 0.3.0.0 then patch from 0.3.0.0 to 0.3.1.0. I created my 0.3.2.0 patch from 0.3.0.0 (to encompass the 0.3.1.0 stuff) and when I apply it it says it cannot as The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. In my PatchFamily tag I have set the version to be the new version in both patches (so 0.3.1.0 and 0.3.2.0), and Supersede=yes for both. Is there something else I'm missing? From my understanding of the documentation the MsiPatchSequence table should have increasing numbers for all my patches and they should supersede each other just fine, but obviously I'm wrong. Any help is appreciated. --Emanuel -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
