[WiX-users] Creating a component group using mallow
Is there a way to create a component group using mallow? -- View this message in context: http://www.nabble.com/Creating-a-component-group-using-mallow-tp14575919p14575919.html Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Automatically creating a shortcut after the FileSet has been written
The only possibility to create a shortcut for a file, as far as I know, is to use the Shortcut -element within the FileSet. This works fine. But I am having a fully automated process to build an msi file using tallow to create the FileSet. Now I want to create a shortcut for a certain file in this FileSet, but do not want to do that by hand, but automatically. Therefore I would like to know if anybody knows how to create a shortcut for a certain file after the fileset has already been created? Maybe using a CustomAction is an option? Any help is highly appreciated, thanks. -- View this message in context: http://www.nabble.com/Automatically-creating-a-shortcut-after-the-FileSet-has-been-written-tp14576701p14576701.html Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Wix 3.0 : website and virtual directory created with Wix are not removed on uninstall
In my installation, I give the user the ability to create a virtual
directory (under an existing website) or to create a new website, giving
the name, port number, IP and header value.
All works just fine, but when I'm uninstalling, the virtual dir or the
website, if created, are not removed and are shown in IIS (we support
IIS 5 and 6).
This is the code snippet:
Directory Id=TARGETDIR Name=SourceDir
Directory Id=ProgramMenuFolder
Directory Id=MenuDir Name=MY_NAME
.
.
.
/Directory
/Directory
Component Id=VIR_DIR Guid={29181CC3---81E3-
2C2148D1CD92} KeyPath=yes
iis:WebVirtualDir Id=R1VirtualDir Directory=USER_WEB_DIR
Alias=[VIRTUALDIR] WebSite=WebSite DirProperties=ReadAndExecute
iis:WebApplication Id=WebApplication Name=MY_NAME
/
/iis:WebVirtualDir
Condition IISINSTALL = 1/Condition
/Component
Component Id=NEW_WEB_SITE Guid={1012DBD5---8B7C-
BD355D8BA27E} KeyPath=yes
iis:WebSite Id=NewWebSite Description=[NEW_WEBSITE]
Directory=USER_WEB_DIR
DirProperties=ReadAndExecute
ConfigureIfExists=no StartOnInstall=yes
iis:WebAddress Id=NewWebAddress
IP=[NEW_WEBSITE_IP]
Port=[NEW_WEBSITE_PORT]
Header=[NEW_WEBSITE_HEADER]/
/iis:WebSite
Condition IISINSTALL = 1/Condition
/Component
/Directory
iis:WebSite Id=WebSite Description=[WEBSITE]
iis:WebAddress Id=WebAddress IP=[WEBSITE_IP]
Port=[WEBSITE_PORT] Header=[WEBSITE_HEADER]/
/iis:WebSite
iis:WebDirProperties Id=ReadAndExecute Read=yes Write=no
Script=yes Execute=yes AnonymousAccess=yes /
The VIR_DIR component is installed under WebSite (which is an
unremoveable component, so it won't be damaged by uninstall).
The NEW_WEB_SITE component is a new site.
The user installs either VIR_DIR or NEW_WEB_SITE, but not both.
Each component belongs to its own feature, with no other components (I
know that's ugly, but it was due to technical constraints).
The MSI log of the uninstall shows that the components are detected as
Installed:Local, with Action: Absent, but yet are not removed.
Is that a known bug, or am I doing something wrong?
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Shared Files
Hi, I'm fairly new to wix, and I want to create a msi-file to distribute my .net application. My app consists of several components, which require certain assemblies. These assemblies are required in the same folder as the application (I don't want to place them in the GAC right now). So I have an assembly containing common interface defintions. This assembly has to be installed to several directories, obviously in each components directory. How should I layout my wix-config to achive this? I didn't find an obvious way to include a file only once in the MSI and install it to serveral locations ... signature.asc Description: OpenPGP digital signature - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] FileShare - Question
Hi there, I probably have a quite simple question: How can I set the sharing of my C-drive and name it as Root? I tried something like this but it creates the Root-folder: Directory Id=TARGETDIR Name=SourceDir Directory Id=INSTALLDIR Directory Id=MyRoot Name=Root Component Id=FirstFileShare Guid=6f051579-2950-42e3-9381-2f538ae1de12 CreateFolder/ util:User Id=MyUser Name=user Password=password PasswordNeverExpires=yes RemoveOnUninstall=yes UpdateIfExists=yes CreateUser=yes/ util:FileShare Id =ShareRoot Name=Root util:FileSharePermission GenericAll=yes User=MyUser Read=yes/ /util:FileShare /Component /Directory /Directory /Directory Thank's in advance, Chris - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix layout
Dominik Guder wrote:
this looks suitable for me. I'll give it a try.
After a bunch of more important tasks I was able to come back to this task.
I first tried the diff solution which worked as expected and I ended with a
nant solution which removes the diff dependency. I would like to share this
here for all others who might need it.
Since wix throws an error on missing files in buildarea, only a one way
check is needed to check if all files from buildarea are present in
administrative install location (below installer dir).
In addition some files could be excluded from the check if needed.
Regards Dominik
?xml version=1.0 encoding=utf-8 ?
project name=check installer default=check-installed-files basedir=.
xmlns=http://nant.sf.net/release/0.85-rc3/nant.xsd;
description
/description
property name=buildarea.dir value=C:\path\to\buildarea /
property name=msitarget.dir value=_installer /
property name=msi.file value=ProductName.msi /
target name=extract-msi description=extract
delete dir=${msitarget.dir} /
exec program=msiexec.exe verbose=true
arg value=/a /
arg value=${msi.file} /
arg
value=TARGETDIR=${path::get-full-path(msitarget.dir)} /
arg line=/qn INSTALL=ALL /
/exec
/target
target name=check-installed-files description=check
property name=check.dir
value=${path::combine(msitarget.dir, 'Program
Files\ProductName')} /
property name=missingfiles value=false /
fileset id=files.deployed basedir=${buildarea.dir}
include name=** /
exclude name=**\SomeFileToExclude.dll /
/fileset
foreach item=File property=filename
in
items refid=files.deployed /
/in
do
property name=filepath
value=${string::replace(filename,
buildarea.dir + '\', '')} /
if test=${not
file::exists(path::combine(check.dir, filepath))}
echo message=File '${filepath}' is
missing in installer
level=Error /
property name=missingfiles
value=true /
/if
/do
/foreach
if test=${missingfiles}
echo message=Directories used: /
echo message=Source files in
'${path::get-full-path(buildarea.dir)}' /
echo message=Msi files in '${path::get-full-path(check.dir)}' /
fail message=One or more files are missing in installer. /
/if
/target
/project
--
View this message in context:
http://www.nabble.com/Wix-layout-tp12592040p14581722.html
Sent from the wix-users mailing list archive at Nabble.com.
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using XmlFile in a merge module
Here's a sample that demonstrates the problem: ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; xmlns:sql=http://schemas.microsoft.com/wix/SqlExtension; xmlns:iis=http://schemas.microsoft.com/wix/IIsExtension; xmlns:util=http://schemas.microsoft.com/wix/UtilExtension; Module Guid=02f45038-587d-4cc0-af41-0380cf378c2c Id=TestMergeModule Language=1033 Version=1.0.0.0 Package Id=02f45038-587d-4cc0-af41-0380cf378c2d InstallerVersion=200 Manufacturer=Test Company Compressed=yes / Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFilesFolder Directory Id=MANUFACTURERFOLDER Name=Test Company Directory Id=INSTALLLOCATION Name=Test Product Directory Id=TESTPATH Name=Test Path Component Id=WebConfigComponent Guid=02440d26-f08c-4b28-b037-8303314ff4dd File Id=WebCONFIG Name=Web.config ReadOnly=no Source=$(var.SourceDir)Web.config/ util:XmlFile Id=ModifyValue Action=setValue ElementPath=/configuration/ValueConfiguration File=[TESTPATH]web.config Value=Value/ CreateFolder/ /Component /Directory /Directory /Directory /Directory /Directory /Module /Wix If I remove the util:XmlFile line, the merge module will correctly copy web.config. With that line, I get failure to configure XML files error, and web.config has not been copied. Is there anything I can do here? csellers wrote: I currently have an MSI Wix project that (among other things) copies an xml file and makes modifications to it using util:XmlFile. I am in the process of converting this project to a merge module (MSM), but when I include the merge module in another install, I get an error saying there was a failure while configuring XML files. I then noticed that I get this error before the xml file had been copied (which would explain the error). I did not have this problem when I was building an msi file. Looking at the log file, the failure is in SchedXmlFile, which is occurring before any files have been copied. If I remove the XmlFile commands, the install runs without any problems. Is there a reason why this is happening in the merge module when it didn't in the msi? Is there anyway to control when SchedXmlFile runs? -- View this message in context: http://www.nabble.com/Using-XmlFile-in-a-merge-module-tp14519897p14582035.html Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Wix 3.0.3621.0
What is the status of the above WIX install with VS.NET 2008 RTM ? Is Votive still installed with this release ? Votive does not show up as a VS.NET 2008 RTM add-in. Philip - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Problem Starting service on XP
I am trying to install and start a service but its coming back with. Error msg: Verify that you have sufficient priveleges to start system services. I am running the msi file as an administrator. I can install / start the service manually but not via wix, has anyone seen this before and do they have sample code? Much appreciated. Graham Code: Component Id='ServiceExeComponent' Guid='6ca52ece-6346-4bbf-ae10-248cc3ab74c4' SharedDllRefCount='no' KeyPath='no' NeverOverwrite='no' Permanent='no' Transitive='no' Win64='no' Location='either' File Id='ServiceExeFile' Name='Call Manager Service.exe' DiskId='1' Source='Call Manager Service.exe' ReadOnly='no' KeyPath='yes' Vital='yes' Hidden='no' System='no' Checksum='no' / ServiceInstall Id='CMServiceInstall' DisplayName='Call Manager Service' Name='Call Manager Service' ErrorControl='normal' Start='auto' Type='ownProcess' Vital='yes' Interactive=no / ServiceControl Id='CMServiceControl' Name='Call Manager Service' Start='install' Stop='both' Remove='uninstall' Wait='yes' / /Component - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Problem Starting service on XP
The error message you receive implies that the service was installed but failed to start. Once getting this error (before canceling the installation or anything else), if you go to Windows Service Manager, can you start the service manually, right there in that minute? I use Wix to install and start many services with my installation. I've learned that I get errors like these only when there's a real error not related to Wix. I was never able to manually start something Wix couldn't... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Graham Vickrage Sent: Wednesday, January 02, 2008 8:42 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Problem Starting service on XP I am trying to install and start a service but its coming back with. Error msg: Verify that you have sufficient priveleges to start system services. I am running the msi file as an administrator. I can install / start the service manually but not via wix, has anyone seen this before and do they have sample code? Much appreciated. Graham Code: Component Id='ServiceExeComponent' Guid='6ca52ece-6346-4bbf-ae10-248cc3ab74c4' SharedDllRefCount='no' KeyPath='no' NeverOverwrite='no' Permanent='no' Transitive='no' Win64='no' Location='either' File Id='ServiceExeFile' Name='Call Manager Service.exe' DiskId='1' Source='Call Manager Service.exe' ReadOnly='no' KeyPath='yes' Vital='yes' Hidden='no' System='no' Checksum='no' / ServiceInstall Id='CMServiceInstall' DisplayName='Call Manager Service' Name='Call Manager Service' ErrorControl='normal' Start='auto' Type='ownProcess' Vital='yes' Interactive=no / ServiceControl Id='CMServiceControl' Name='Call Manager Service' Start='install' Stop='both' Remove='uninstall' Wait='yes' / /Component - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Substitution for Fragments in MMs?
I'm trying to create a merge module with the file list as a separate
file so that programmers can edit it while still exposing as little of
the installer as possible. I'd planned to use a Fragment, but
discovered that Fragments are no longer supported (why?). If this were
not a merge module, I could easily use FeatureRef to include the
chunks of files. I'd rather not have dozens of ComponentRef entries,
as then either myself or the engineering group has to update the main
file each time there's a new addition to the file roster (which is
what I'm trying to avoid in the first place). If I use an include, the
file contents wont be brought into the correct location (inside the
Module node), right?
The Fragment structure looks like this currently:
Fragment
Directory Id=TARGETDIR Name=SourceDir
Component Id=AddRoles.sql
Guid={E384FA8D-1EC9-49ED-9D6C-241439A2E873}
File Id=AddRoles.sql Name=AddRoles.sql
KeyPath=yes Source=$(var.db_script_src_dir)\AddRoles.sql /
/Component
...
/Directory
/Fragment
How
I'm new to this whole WiX thing, so please forgive me if I'm missing
the obvious.
--
-Chris
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] FileShare - Question
Set the ROOTDRIVE property to C:\ and Move your component under the TARGETDIR DirectoryId tag. I am not sure why you would want your setup package to share the root. That seems a little dangerous and counterintuitive. //aj On Jan 2, 2008 8:14 AM, Chris [EMAIL PROTECTED] wrote: Hi there, I probably have a quite simple question: How can I set the sharing of my C-drive and name it as Root? I tried something like this but it creates the Root-folder: Directory Id=TARGETDIR Name=SourceDir Directory Id=INSTALLDIR Directory Id=MyRoot Name=Root Component Id=FirstFileShare Guid=6f051579-2950-42e3-9381-2f538ae1de12 CreateFolder/ util:User Id=MyUser Name=user Password=password PasswordNeverExpires=yes RemoveOnUninstall=yes UpdateIfExists=yes CreateUser=yes/ util:FileShare Id =ShareRoot Name=Root util:FileSharePermission GenericAll=yes User=MyUser Read=yes/ /util:FileShare /Component /Directory /Directory /Directory Thank's in advance, Chris - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] www.travel-bargains.com.ar
Please see this site in Subject - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Problem Starting service on XP
If it can be started ok after the install then the issue could be dependencies. If it's dependent on an assembly in the GAC or (on Vista) the C++ CRT support being installed from a merge module these won't be available at StartServices time. Phil Wilson -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Graham Vickrage Sent: Wednesday, January 02, 2008 10:42 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Problem Starting service on XP I am trying to install and start a service but its coming back with. Error msg: Verify that you have sufficient priveleges to start system services. I am running the msi file as an administrator. I can install / start the service manually but not via wix, has anyone seen this before and do they have sample code? Much appreciated. Graham Code: Component Id='ServiceExeComponent' Guid='6ca52ece-6346-4bbf-ae10-248cc3ab74c4' SharedDllRefCount='no' KeyPath='no' NeverOverwrite='no' Permanent='no' Transitive='no' Win64='no' Location='either' File Id='ServiceExeFile' Name='Call Manager Service.exe' DiskId='1' Source='Call Manager Service.exe' ReadOnly='no' KeyPath='yes' Vital='yes' Hidden='no' System='no' Checksum='no' / ServiceInstall Id='CMServiceInstall' DisplayName='Call Manager Service' Name='Call Manager Service' ErrorControl='normal' Start='auto' Type='ownProcess' Vital='yes' Interactive=no / ServiceControl Id='CMServiceControl' Name='Call Manager Service' Start='install' Stop='both' Remove='uninstall' Wait='yes' / /Component - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Problem Starting service on XP
I've also worked on projects where the developers used environment variables across the system and in the service. This also can cause a race condition as the SCM doesn't recognize environment changes. The poster mentioned install/start manually. Certainly try install MSI start manually. If this works you probably have a race conditionion. If it doesn't work, you probably have configuration / installation data problems. Wilson, Phil [EMAIL PROTECTED] wrote: If it can be started ok after the install then the issue could be dependencies. If it's dependent on an assembly in the GAC or (on Vista) the C++ CRT support being installed from a merge module these won't be available at StartServices time. Phil Wilson -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Graham Vickrage Sent: Wednesday, January 02, 2008 10:42 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Problem Starting service on XP I am trying to install and start a service but its coming back with. Error msg: Verify that you have sufficient priveleges to start system services. I am running the msi file as an administrator. I can install / start the service manually but not via wix, has anyone seen this before and do they have sample code? Much appreciated. Graham Code: SharedDllRefCount='no' KeyPath='no' NeverOverwrite='no' Permanent='no' Transitive='no' Win64='no' Location='either' Source='Call Manager Service.exe' ReadOnly='no' KeyPath='yes' Vital='yes' Hidden='no' System='no' Checksum='no' / ErrorControl='normal' Start='auto' Type='ownProcess' Vital='yes' Interactive=no / Start='install' Stop='both' Remove='uninstall' Wait='yes' / - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Never miss a thing. Make Yahoo your homepage.- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Problem Starting service on XP
Make sure you are using the service name in the ServiceControl table and not the display name. The two are not necessarily the same and you must use the service name when controlling services in Windows Installer. -- The Direct3D Graphics Pipeline -- DirectX 9 draft available for download http://www.xmission.com/~legalize/book/download/index.html Legalize Adulthood! http://blogs.xmission.com/legalize/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Two questions on SelectionTree and Features.
I have two questions. I am using the SelectionTree control to allow customization. When I click on the top level of the tree it has the following entries: Will be installed on local hard drive Entire feature will be installed on local hard drive - Will be installed to run from the network Entire feature will be installed to run from the network - Feature will be installed when required - Entire feature will be unavailable. Our team does not want to support network installs or when required installs. Is there a way to remove these from the list? My second question: Is there a way to automatically set a feature to be installed based on other features without using SetInstallLevel? Brad Thompson. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Two questions on SelectionTree and Features.
Brad,
First question:
Set the attributes when you are defining your feature and components.
Example:
Feature Id=MyFeature Title=My Feature Title *AllowAdvertise=no
InstallDefault=local* Level=1
Component Id=MyComponent Guid={----0123456789EF}
*Location=local*
Second question:
There is no elegant solution unfortunately. You could use a custom dialog
that does not employ the SelectionTree control, such as checkboxes, or a
custom action that hooks your feature selection dialogs and watches for
event triggers of the SelectionTree control. Windows Installer UI is
limited at best and leaves a lot to be desired.
Regards,
//aj
On Jan 2, 2008 1:50 PM, Brad Thompson (WEBSTORE) [EMAIL PROTECTED]
wrote:
I have two questions. I am using the SelectionTree control to allow
customization. When I click on the top level of the tree it has the
following entries:
Will be installed on local hard drive
Entire feature will be installed on local hard drive
-
Will be installed to run from the network
Entire feature will be installed to run from the network
-
Feature will be installed when required
-
Entire feature will be unavailable.
Our team does not want to support network installs or when required
installs. Is there a way to remove these from the list?
*My second question:*
Is there a way to automatically set a feature to be installed based on
other features without using SetInstallLevel?
Brad Thompson.
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] SQL Elements are not recognized in Visual Studio?
I Installed Votive 3.0 and I started testing out a project in Visual Studio. When I tried to build the project it did not recognize SQLDatabase and User as valid tags. I checked the help file to make sure I had the proper version and it shows the definition for both. Have I missed some versionsetting in VS or is there something else I need to do? -- View this message in context: http://www.nabble.com/SQL-Elements-are-not-recognized-in-Visual-Studio--tp14587359p14587359.html Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] ICE60 and DefaultLanguage
I am packaging third party DLLs in my .msi file. These DLLs do not contain a Language entry in their resource bundle. When I validate the MSI I get an ICE60 warning for each of these DLLs: The file component name is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column. If I manually add the value 1033 to the Language column for each of these entries I no longer get the validation warning. I have added a DefaultLanguage=1033 attribute to the File/ element for each of these libraries, but this value seems to be ignored. I still get empty Language column values for these files. What am I doing wrong? Ted - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How to create help file shortcut icon?
When we created help file shortcuts in the start menu using
InstallShield, we had to manually set the icon to
System32\WinHlp32.exe. If I try to do this with WiX, it complains that
the extension of icon 'xyz' for shortcut 'abc' does not match the
extension of the Key File for component 'foo.chm'.
How does one go about getting a nice help icon in the start menu?
My code looks more or less like this:
Component Id=APPHELP.chm
Guid={91CD65F1-FAA3-42FD-9E1A-DDED9FA65CAC}
File Id=APPHELP.chm Name=APPHELP.chm KeyPath=yes
Source=..\APPHELP.chm /
RemoveFolder Id=NewShortcut1 Directory=newfolder1
On=uninstall /
Shortcut Id=NewShortcut1 Directory=newfolder1
Name=Application Help ShortName=APPHELP Icon=helpicon
IconIndex=1 Show=normal Advertise=yes /
/Component
...
Icon Id=helpicon SourceFile=$(env.windir)\system32\winhlp32.exe /
Thanks!
--
-Chris
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to create help file shortcut icon?
What you specify in the Icon elements gets incorporated in your .msi as a
binary at build time, so it should be something you have control over, not
attempting to use a system executable.
The warning message is described in the documentation for the Icon table,
where it states:
Icon files that are associated with shortcuts must be in the EXE binary
format and must be named such that their extension matches the extension of
the target. The shortcut will not work if this rule is not followed. For
example, if a shortcut is to point to a resource having the key file
Red.bar, then the icon file must also have the extension .bar. Multiple
icons can be stuffed into the same icon file as long as all of the target
files have the same extension.
The Id attribute is used for the icon file's name when it is extracted onto
the system. So you should use something like:
Icon Id=helpicon.chm SourceFile=myhelpicon.dll /
When they say the EXE binary format they actually mean a Portable Executable
file - a resource-only DLL is acceptable. It does not actually have to be
executable.
--
Mike Dimmick
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chris Weiss
Sent: 03 January 2008 00:06
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to create help file shortcut icon?
When we created help file shortcuts in the start menu using
InstallShield, we had to manually set the icon to
System32\WinHlp32.exe. If I try to do this with WiX, it complains that
the extension of icon 'xyz' for shortcut 'abc' does not match the
extension of the Key File for component 'foo.chm'.
How does one go about getting a nice help icon in the start menu?
My code looks more or less like this:
Component Id=APPHELP.chm
Guid={91CD65F1-FAA3-42FD-9E1A-DDED9FA65CAC}
File Id=APPHELP.chm Name=APPHELP.chm KeyPath=yes
Source=..\APPHELP.chm /
RemoveFolder Id=NewShortcut1 Directory=newfolder1
On=uninstall /
Shortcut Id=NewShortcut1 Directory=newfolder1
Name=Application Help ShortName=APPHELP Icon=helpicon
IconIndex=1 Show=normal Advertise=yes /
/Component
...
Icon Id=helpicon SourceFile=$(env.windir)\system32\winhlp32.exe /
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ICE60 and DefaultLanguage
I can't do better than refer to the documentation for ICE60 at http://msdn2.microsoft.com/en-us/library/aa369003.aspx. Failure to fix a warning reported by ICE60 generally leads to a file being needlessly reinstalled when a product repair is done. This happens because the file to be installed in the repair and the existing file on disk have the same version (they are the same file) but different languages. The file table lists the language as null, but the file itself has a language value in the resource. Based on the file versioning rules, the installer favors the file to be installed, so it is recopied needlessly. I believe the installer is using the Translation key in the VarFileInfo of the resources to get the list of languages from the already-installed version. WiX - specifically, light - is supposed to get the language information at build time, unless you have specified the -sf or -sh switches. I would not advise using these switches as they suppress ALL the version information collection, throwing you into the chaos of unversioned files (where last-installed wins). Why does Windows Installer want you to duplicate all this information in the database, when it's already in the files? To prevent it having to obtain the file (potentially a CAB download from the Internet, for HTTP MSIs) just to discover that it wasn't needed. -- Mike Dimmick -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ted Berg Sent: 02 January 2008 23:27 To: wix-users@lists.sourceforge.net Subject: [WiX-users] ICE60 and DefaultLanguage I am packaging third party DLLs in my .msi file. These DLLs do not contain a Language entry in their resource bundle. When I validate the MSI I get an ICE60 warning for each of these DLLs: The file component name is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column. If I manually add the value 1033 to the Language column for each of these entries I no longer get the validation warning. I have added a DefaultLanguage=1033 attribute to the File/ element for each of these libraries, but this value seems to be ignored. I still get empty Language column values for these files. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] SQL Elements are not recognized in Visual Studio?
Did you add the references to your extensions in your WiX project? ...and, did you add the schemas to the wxs file? i.e. Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; xmlns:util=http://schemas.microsoft.com/wix/UtilExtension; xmlns:sql=http://schemas.microsoft.com/wix/SqlExtension; xmlns:ui=http://schemas.microsoft.com/wix/UIExtension; Regards, //aj On Jan 2, 2008 3:03 PM, JCWrs [EMAIL PROTECTED] wrote: I Installed Votive 3.0 and I started testing out a project in Visual Studio. When I tried to build the project it did not recognize SQLDatabase and User as valid tags. I checked the help file to make sure I had the proper version and it shows the definition for both. Have I missed some versionsetting in VS or is there something else I need to do? -- View this message in context: http://www.nabble.com/SQL-Elements-are-not-recognized-in-Visual-Studio--tp14587359p14587359.html Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix3: File/@Name as part of @Source
Alexander Biryukov wrote: Bob, while it feature is NEW, you can improve it without damage of bracking changes. The breaking change would be that Name currently defaults to Id. If you cannot improve this feature withot Feature request, i will create it. Please do. Otherwise it's likely to get lost in e-mail. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Latest build - specifically MSMQ extension
Henning Eiben wrote: Hmm, but as far as I can see only the source-version contains the msmq-extension, the binary version does not contain those binaries. It was probably a casualty of the conversion to MSBuild. Please enter a bug. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using XmlFile in a merge module
csellers wrote: We are using Wix build 3.0.2925.0 Please try the latest weekly release. The version you're using is over six months old. And please include the exact error message from a verbose log, to get the details the CA logs. Looking at this, you would think SchedXmlFile would occur after InstallFiles, but it doesn't seem to work this way. SchedXmlFile is an immediate custom action; it runs while the installation script is being generated. It tells MSI to run other CAs when the script is executed (which is when the files are actually installed). -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Substitution for Fragments in MMs?
Chris Weiss wrote: the installer as possible. I'd planned to use a Fragment, but discovered that Fragments are no longer supported (why?). Fragments are still supported. What's no longer supported is FragmentRef. Take a look at using ComponentGroup/ComponentGroupRef instead. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Crystal Reports Merge Module Installation Woes
Szentpali Janos wrote: Merge modules are generally now considered bad practice... If this is true than what is the point of the whole MSI system? I mean if I have a 3rd party component (x.dll) that 4th party and 5th party are using too, how does the system decide that the x.dll component installed by the 4th party's installer and the x.dll component installed by the 5th party's installer are the same and how does it make sure that upon un-install it is only un-installed if both (all) products are un-installed and that it IS un-installed if both (all) products are un-installed? I'm thinking of a common file placed under say %COMMONPROGRAMFILES%\3rd Party\x.dll.. MSI manages that at the component level; merge modules are an authoring construct, not an installation construct. Because patches target products, not components, however, most redistributables are shipped as MSI packages, not merge modules. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Dark - NullReferenceException due to rows in the AppSearch table
Frank Eden wrote: I run dark against my MSI, and I get an exception. Ive tracked it down a bit, and I find that if I delete particular ros in the AppSearch table, I can get dark to work. Please find an attached MSI that demonstrates the problem. Its 4Mg - Sorry its so big!! Your attachment didn't come through. Please enter a bug and try attaching the MSI. (I'm not sure what the size limits on attachments are in the SF bug system, though; it might be too big.) -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix 3.0.3621.0
Philip Lippard wrote: What is the status of the above WIX install with VS.NET 2008 RTM ? Is Votive still installed with this release ? Yes. What features are shown if you click Advanced? -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Shared Files
Henning Eiben wrote: I didn't find an obvious way to include a file only once in the MSI and install it to serveral locations ... Generally you don't. Instead, you can use WiX's support for smart cabbing so that only a single copy of the file is included in your MSI package regardless of how many times it's installed. See http://robmensching.com/blog/archive/2007/06/01/quotSmart-cabbingquot-added-to-WiX-toolset.aspx for details. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
