Re: [WiX-users] bootstrapperApplicationData' attribute is not declared.
Sorry for misunderstanding. Actually I have one solution project created. It has existing project where output path is set with some properties. Now I need to refer those properties, therefore I achieve these properties by adding project as reference of bootstrapper application project. Thus I create whole input path of msi. In above case, it gives compilation error. But if I create one another bootstrapper project in different solution ,where I take msi input path as hard coded string,then project compiled successfully. I am not sure about cause of different behavior for above cases. I don't think just adding project as reference should cause this error. with regards, KD -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/bootstrapperApplicationData-attribute-is-not-declared-tp7595444p7596009.html Sent from the wix-users mailing list archive at Nabble.com. -- Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] detected dependencies
Does the wix support detected dependencies like in setup project visual studio 2010? And how to implement it? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/detected-dependencies-tp7596011.html Sent from the wix-users mailing list archive at Nabble.com. -- Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Context Menu for edit control to paste the data
I have an edit control being used in one of the wizard. Is there aprovision to display a context menu to paste the data onto the edit control ? Currently it works fine with 'Ctrl+V' but need to show up a context menu as well with paste option. Thanks, Veeresh -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Context-Menu-for-edit-control-to-paste-the-data-tp7596012.html Sent from the wix-users mailing list archive at Nabble.com. -- Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] bootstrapperApplicationData' attribute is not declared.
So if you have a Visual Studio Solution file, and each project that you want to reference has been added to that VS Solution file, then you add the reference to your project and use the variables as documented here: http://wixtoolset.org/documentation/manual/v3/votive/votive_project_references.html Personally I avoid that approach for several reasons. My main reason is that I want to be able to build my projects on the command line using MSBuild commands, (in addition to building my projects within VS IDE) VS Project References are only resolve when the VS IDE is using the Solution file. There are several other approaches to defining the your source paths. with some infor here: http://wixtoolset.org/documentation/manual/v3/howtos/general/specifying_source_files.html The approach I use most of the time is: 1) I define an environment variable to root of all of my projects (to harvest MSI, etc.) 2) In the bootstrapper project file (I unload it and edit it directly), I modify the LinkerAdditionalOptions to include: -b $(EnvVariableName to root of all projects)\Project\bin\$(Configuration) In the bootstrapper the MsiPackage/@SourceFile=(local or platform)\Project.msi (For projects that do not have multiple locales or platforms, just specify the package name.) There are other approaches that make use of binding or preprocessor variables. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/bootstrapperApplicationData-attribute-is-not-declared-tp7595444p7596016.html Sent from the wix-users mailing list archive at Nabble.com. -- Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] bootstrapperApplicationData' attribute is not declared.
Votive references work just fine from a build using MSBuild on the command line. I test this scenario dozens of times a day. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Phill Hogland [mailto:phogl...@rimage.com] Sent: Monday, July 21, 2014 8:33 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] bootstrapperApplicationData' attribute is not declared. So if you have a Visual Studio Solution file, and each project that you want to reference has been added to that VS Solution file, then you add the reference to your project and use the variables as documented here: http://wixtoolset.org/documentation/manual/v3/votive/votive_project_references.html Personally I avoid that approach for several reasons. My main reason is that I want to be able to build my projects on the command line using MSBuild commands, (in addition to building my projects within VS IDE) VS Project References are only resolve when the VS IDE is using the Solution file. There are several other approaches to defining the your source paths. with some infor here: http://wixtoolset.org/documentation/manual/v3/howtos/general/specifying_source_files.html The approach I use most of the time is: 1) I define an environment variable to root of all of my projects (to harvest MSI, etc.) 2) In the bootstrapper project file (I unload it and edit it directly), I modify the LinkerAdditionalOptions to include: -b $(EnvVariableName to root of all projects)\Project\bin\$(Configuration) In the bootstrapper the MsiPackage/@SourceFile=(local or platform)\Project.msi (For projects that do not have multiple locales or platforms, just specify the package name.) There are other approaches that make use of binding or preprocessor variables. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/bootstrapperApplicationData-attribute-is-not-declared-tp7595444p7596016.html Sent from the wix-users mailing list archive at Nabble.com. -- Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] bootstrapperApplicationData' attribute is not declared.
Thanks for the correction. I will have to review where I got the erroneous idea from. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/bootstrapperApplicationData-attribute-is-not-declared-tp7595444p7596020.html Sent from the wix-users mailing list archive at Nabble.com. -- Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] wix 3.9.720 update removed packages observation
I had a bundle with multiple msi packages installed on a test system (built with installed wix 3.9.702 on build system). I installed the wix 3.9.720 on build system this morning, an only rebuilt the bundle. When I moved it to the test system, which had the prior version of this product installed, built with 3.9.702, it installed successfully and in the process removed all of the packages. The new updated bundle is listed in ARP with no packages installed. I have verbose logs of bundles and msi packages, but am still looking for a reason. since I do not plan to deploy this build, and wait until a future build to completely test the update scenario, this observation may not matter. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/wix-3-9-720-update-removed-packages-observation-tp7596021.html Sent from the wix-users mailing list archive at Nabble.com. -- Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Shared components problem
Thanks Jacob/Rob I'm not using Burn, mostly for historical reasons but the UI is beyond StdBA and I don't currently have time to do a Custom BA. DLLs aren't COM / don't require reg settings. Think I will have to just do something along the lines suggested by Rob and accept there are known issues (with workarounds). It is highly unlikely there will be more than a handful of customers installing both products. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Shared-components-problem-tp7595964p7596023.html Sent from the wix-users mailing list archive at Nabble.com. -- Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] reinstall major upgrade removes files yet installed
For the longest time I have had a wix msi and bundle that I could
upgrade or downgrade without having to uninstall first, before
installing the version I want to test.
Now it seems if a previous install exists, the bundle (or msi) will
remove the files from the previous install, and mark the program
installed in ARP. In this state, I have to uninstall and then reinstall
in order to get the files and mark the program installed in ARP.
If I install on a system without the program, everything installs as
expected.
This behavior change seems to coenside with my building the program with
dynamic linking (vs. static linking), which called for the inclusion of
Microsoft Redistributables.
It is very handy for a user to just install without having to un-install
first, so i would like to keep that experience.
Bellow find my msi and bundle wxs files.
---
MyProgram.wxs (msi)
---
?xml version=1.0 encoding=UTF-8?
?include $(var.wxi_variables) ?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:bal=http://schemas.microsoft.com/wix/BalExtension;
xmlns:util=http://schemas.microsoft.com/wix/UtilExtension;
Product
Id=*
Language=1033
Manufacturer=$(var.MyCompanyName)
Name=$(var.MyInstallerName)
UpgradeCode={$(var.Guid_Upgrade)}
Version=$(var.Version)
!-- Main packed declaration --
Package
Comments=$(var.MyCompanyNameShort) - $(var.MyProductName)
$(var.Version) Installation
Compressed=yes
Description=$(var.MyDescription)
InstallerVersion=301
/
!-- How data is packed inside the msi --
!--
Media Id=1 Cabinet=contents.capab EmbedCab=yes /
--
MediaTemplate EmbedCab=yes/
!-- Directory Structure --
Directory Id=TARGETDIR Name=SourceDir
Merge Id=VCRedist Language=0 DiskId=1
src=$(env.CommonProgramFiles(x86))\Merge Modules
\Microsoft_VC100_CRT_x86.msm/
Directory Id=ProgramFilesFolder Name=Pfiles
Directory Id=MYPRODUCTSDIR
Name=$(var.MyCompanyNameShort) ShortName=livl8li5
Directory Id=INSTALLDIR Name=$(var.MyProductName)
$(var.Version) ShortName=rclggtos
/Directory
/Directory
/Directory
/Directory
!-- Install the Visual C++ Redistributable with your installer
--
Feature Id=VCRedist Title=Visual C++ Runtime
AllowAdvertise=no Display=hidden Level=1
MergeRef Id=VCRedist/
/Feature
!-- Files --
Feature Id='Complete' Level='1'
!-- Pulls in fragment file created by heat.exe or Paraffin3.1
--
ComponentGroupRef Id='group_ProductFiles'/
!-- Pulls in fragment file to creat Shortcut Program File
Icons File association --
ComponentRef Id=ProgramFileShortcuts /
ComponentRef Id=DesktopShortcuts /
ComponentRef Id=FileAssociations /
/Feature
!-- Add Remove Programs metadata --
Property Id=ARPHELPLINK Value=$(var.HelpUrl) /
Property Id=ARPURLINFOABOUT Value=$(var.AboutUrl) /
Icon Id='Compass.ico' SourceFile=$(var.ProdIcon)/
Property Id=ARPPRODUCTICON Value='Compass.ico' /
!-- Using the Wix UI library --
Property Id=WIXUI_INSTALLDIRINSTALLDIR/Property
!-- Icons for the installer --
WixVariable Id='WixUIBannerBmp' Value='$(var.InstallBanner)' /
WixVariable Id='WixUIDialogBmp' Value='$(var.InstallDialog)' /
WixVariable Id=WixUILicenseRtf Value=$(var.EULArtf) /
!-- Allow per user or per machine --
WixVariable Id=WixUISupportPerUser Value=1 /
Property Id=ApplicationFolderName
Value=$(var.MyCompanyNameShort)\$(var.MyProductName) $(var.Version) /
Property Id=WixAppFolder2 Value=WixPerMachineFolder /
Property Id=WixAppFolder Value=WixPerMachineFolder /
UIRef Id=WixUI_MyInstallDir /
UIRef Id=WixUI_ErrorProgressText /
!-- Major Update --
MajorUpgrade
AllowDowngrades=yes
Schedule=afterInstallValidate /
!-- Always allow Upgrades and Downgrades --
Upgrade Id={$(var.Guid_Upgrade)}
UpgradeVersion
Minimum=$(var.Version)
OnlyDetect=yes
Property=NEWERVERSIONDETECTED
/
UpgradeVersion
Minimum=0.0.0
Maximum=$(var.Version)
IncludeMinimum=no
IncludeMaximum=no
Property=OLDERVERSIONBEINGUPGRADED
/
/Upgrade
/Product
/Wix
-
MyProgram.bundle.wxs (burn bundle)
--
?xml version=1.0 encoding=UTF-8?
?include $(var.wxi_variables) ?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:bal=http://schemas.microsoft.com/wix/BalExtension;
Re: [WiX-users] reinstall major upgrade removes files yet installed
Posting links to logs of the downgrade (both the uninstall and the install
logs) would help deduce the actual problem. The bundle logs detect and planning
sections of the logs would be the first place to look.
-Original Message-
From: jo...@msli.com [mailto:jo...@msli.com]
Sent: Monday, July 21, 2014 6:09 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: [WiX-users] reinstall major upgrade removes files yet installed
For the longest time I have had a wix msi and bundle that I could upgrade or
downgrade without having to uninstall first, before installing the version I
want to test.
Now it seems if a previous install exists, the bundle (or msi) will remove the
files from the previous install, and mark the program installed in ARP. In
this state, I have to uninstall and then reinstall in order to get the files
and mark the program installed in ARP.
If I install on a system without the program, everything installs as expected.
This behavior change seems to coenside with my building the program with
dynamic linking (vs. static linking), which called for the inclusion of
Microsoft Redistributables.
It is very handy for a user to just install without having to un-install first,
so i would like to keep that experience.
Bellow find my msi and bundle wxs files.
---
MyProgram.wxs (msi)
---
?xml version=1.0 encoding=UTF-8?
?include $(var.wxi_variables) ?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:bal=http://schemas.microsoft.com/wix/BalExtension;
xmlns:util=http://schemas.microsoft.com/wix/UtilExtension;
Product
Id=*
Language=1033
Manufacturer=$(var.MyCompanyName)
Name=$(var.MyInstallerName)
UpgradeCode={$(var.Guid_Upgrade)}
Version=$(var.Version)
!-- Main packed declaration --
Package
Comments=$(var.MyCompanyNameShort) - $(var.MyProductName)
$(var.Version) Installation
Compressed=yes
Description=$(var.MyDescription)
InstallerVersion=301
/
!-- How data is packed inside the msi --
!--
Media Id=1 Cabinet=contents.capab EmbedCab=yes /
--
MediaTemplate EmbedCab=yes/
!-- Directory Structure --
Directory Id=TARGETDIR Name=SourceDir
Merge Id=VCRedist Language=0 DiskId=1
src=$(env.CommonProgramFiles(x86))\Merge Modules
\Microsoft_VC100_CRT_x86.msm/
Directory Id=ProgramFilesFolder Name=Pfiles
Directory Id=MYPRODUCTSDIR
Name=$(var.MyCompanyNameShort) ShortName=livl8li5
Directory Id=INSTALLDIR Name=$(var.MyProductName)
$(var.Version) ShortName=rclggtos
/Directory
/Directory
/Directory
/Directory
!-- Install the Visual C++ Redistributable with your installer
--
Feature Id=VCRedist Title=Visual C++ Runtime
AllowAdvertise=no Display=hidden Level=1
MergeRef Id=VCRedist/
/Feature
!-- Files --
Feature Id='Complete' Level='1'
!-- Pulls in fragment file created by heat.exe or Paraffin3.1
--
ComponentGroupRef Id='group_ProductFiles'/
!-- Pulls in fragment file to creat Shortcut Program File Icons
File association --
ComponentRef Id=ProgramFileShortcuts /
ComponentRef Id=DesktopShortcuts /
ComponentRef Id=FileAssociations /
/Feature
!-- Add Remove Programs metadata --
Property Id=ARPHELPLINK Value=$(var.HelpUrl) /
Property Id=ARPURLINFOABOUT Value=$(var.AboutUrl) /
Icon Id='Compass.ico' SourceFile=$(var.ProdIcon)/
Property Id=ARPPRODUCTICON Value='Compass.ico' /
!-- Using the Wix UI library --
Property Id=WIXUI_INSTALLDIRINSTALLDIR/Property
!-- Icons for the installer --
WixVariable Id='WixUIBannerBmp' Value='$(var.InstallBanner)' /
WixVariable Id='WixUIDialogBmp' Value='$(var.InstallDialog)' /
WixVariable Id=WixUILicenseRtf Value=$(var.EULArtf) /
!-- Allow per user or per machine --
WixVariable Id=WixUISupportPerUser Value=1 /
Property Id=ApplicationFolderName
Value=$(var.MyCompanyNameShort)\$(var.MyProductName) $(var.Version) /
Property Id=WixAppFolder2 Value=WixPerMachineFolder /
Property Id=WixAppFolder Value=WixPerMachineFolder /
UIRef Id=WixUI_MyInstallDir /
UIRef Id=WixUI_ErrorProgressText /
!-- Major Update --
MajorUpgrade
AllowDowngrades=yes
Schedule=afterInstallValidate /
!-- Always allow Upgrades and Downgrades --
Upgrade Id={$(var.Guid_Upgrade)}
UpgradeVersion
Minimum=$(var.Version)
OnlyDetect=yes
Property=NEWERVERSIONDETECTED
/
UpgradeVersion
Minimum=0.0.0
Maximum=$(var.Version)
IncludeMinimum=no
