Re: [WiX-users] Generate multiple MSIs from a single wxs source?
I think you'd better off using Fragments and using *Ref elements. Rob Jared Hughes wrote: My group is producing two products: a Runtime and an SDK. Since there is a lot of similarity between the two products (a lot of the same files, reg keys, shortcuts, custom actions, etc) there is a push to get everything unified into a single file that should, in theory, be easy to maintain. Is it possible to do this? I've tried moving a lot of the common components into a separate file which is then included with an ?include? statement, but I get error messages about duplicate symbols for, say, my program files directory or my TARGETDIR directory. Am I overlooking something straightforward here or would it be best to maintain separate files for the Runtime and the SDK? - 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] Generate multiple MSIs from a single wxs source?
I guess my problem is very similar, i.e. includes the one mentioned above... I'm struggling with a forthcoming a product which has three optional components. It is OK to have a single installation containing these as different features. In reality we should obtain packages combining these three components, say a package for component1 and component2, a standalone package for component3, and another msi which contains all of them, each one as a different feature. Currently I have three different main wxs files matching the three packages, a wxi include for defines like ProductID, CompanyName etc., and the three features isolated into three fragments, referred to in different combinations from the main files. (This way the complaints for the duplicate symbols are eliminated.) I'm still unsure whether it is done the recommended way or not. Perhaps it turns out from the following lines, why. My real problem arises when it comes to switching from one kind of installation to another. I would like to see the full installer seamlessly extend e.g. the installed component3 to a full installation. On the other hand, the MSI containing component1 and component2 should extend an installation of component3 to a full installation. There is no 'hierarchy' in the installation (there is no ordering, so I think I should not use updates/upgrades to solve this issue), and I'd like to have a least confusing GUI, without e.g. disabled features, but still based on the wixui lib as far as possible. Having the same package ID confuses the MSI installer, it is clear from the tutorial that this situation should be avoided, but having different package IDs leads to Another version of the product is already installed Can this kind of upgrading/extending be accomplished (I think so), and how? 2007/9/13, Rob Hamflett [EMAIL PROTECTED]: I think you'd better off using Fragments and using *Ref elements. Rob Jared Hughes wrote: My group is producing two products: a Runtime and an SDK. Since there is a lot of similarity between the two products (a lot of the same files, reg keys, shortcuts, custom actions, etc) there is a push to get everything unified into a single file that should, in theory, be easy to maintain. Is it possible to do this? I've tried moving a lot of the common components into a separate file which is then included with an ?include? statement, but I get error messages about duplicate symbols for, say, my program files directory or my TARGETDIR directory. Am I overlooking something straightforward here or would it be best to maintain separate files for the Runtime and the SDK? - 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] save username and password
Hi Salome, to save the value of your Control, you could use a line like the following: RegistryValue Id='UserName' Root='HKLM' Key='Software\MySoftware' Name ='UserName' Action='write' Type='string' Value='[USERNAME]' / For accessing it you'll have to use a registry search with a property: Property Id='UNAME' Admin='no' Hidden='no' Secure='no' RegistrySearch Id='Username_RegSearch' Root='HKLM' Key='Software\MySoftware' Name='UserName' Type='raw' / /Property As far as I rember, the property you read the regvalue into and the property of your control should not be the same, that's why I set the property tu UNAME in this example. Oliver From: salome zk [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 12. September 2007 17:25 To: Mailinglist; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] save username and password How can i access the username that i have saved? and also how can i save it from the PrompCredential Page? Control Id=UserNameValue Type=Edit X=20 Y=72 Width=320 Height=18 Property=USERNAME Text=47 thanks, Mailinglist [EMAIL PROTECTED] wrote: Hi Salome, you can store the username in the registry (but only the username) in a key that is not by default deleted on uninstall. Oliver From: salome zk [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 12. September 2007 14:46 To: Mailinglist; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] save username and password Thanks for you answer, but just one other question, is there a way to just store the username? You see, customers keep losing their username and so once they have unistalled the software the next time they want to install it they can't remeber their username.I wanted to know if there's a way to save the username they enter somwhere and the next time they want to install the software it automatically restores the username in the username box. thanks. Mailinglist [EMAIL PROTECTED] wrote: Hi, even if you use a custom action to encrypt and decrypt the credentials, it would be unsafe to store them, cause they coud be found and decrypted. The data you store can be hacked on (RegistryKeys, File) as well as your code that you use to store/encrypt/decrypt them. If you use tools, they can be extracted from the msi, if you use a stringkey for de/encryption, it can be extracted from the msiââ'¬Â¦ no encryption is safe as long as all secrets are shipped with the data. Oliver - 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 Be a better Globetrotter. Get better travel answers http://us.rd.yahoo.com/evt=48254/*http:/answers.yahoo.com/dir/_ylc=X3oDMTI5MGx2aThyBF9TAzIxMTU1MDAzNTIEX3MDMzk2NTQ1MTAzBHNlYwNCQUJwaWxsYXJfTklfMzYwBHNsawNQcm9kdWN0X3F1ZXN0aW9uX3BhZ2U-?link=listsid=396545469 from someone who knows. Yahoo! Answers - Check it out. Pinpoint customers http://us.rd.yahoo.com/evt=48250/*http:/searchmarketing.yahoo.com/arp/sponsoredsearch_v9.php?o=US2226cmp=Yahooctv=AprNIs=Ys2=EMb=50 who are looking for what you sell. - 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] Generate multiple MSIs from a single wxs source?
Well, I do have the same problem, specially when it comes to votive. The files must be duplicate, to be used in two projects, linking to files in another project is not possible. That leads to much redundant code and a big overhead for maintaining that. In our Solution we have a client and a server installation, which both use the same service and files. The features are already split off to mergemodules to remove as much redundant code as possible, I'm also going to remove the common parts of the gui to a wixlib but the rest stays for own files in both projects. Oliver -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Hamflett Sent: Donnerstag, 13. September 2007 09:22 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Generate multiple MSIs from a single wxs source? I think you'd better off using Fragments and using *Ref elements. Rob Jared Hughes wrote: My group is producing two products: a Runtime and an SDK. Since there is a lot of similarity between the two products (a lot of the same files, reg keys, shortcuts, custom actions, etc) there is a push to get everything unified into a single file that should, in theory, be easy to maintain. Is it possible to do this? I've tried moving a lot of the common components into a separate file which is then included with an ?include? statement, but I get error messages about duplicate symbols for, say, my program files directory or my TARGETDIR directory. Am I overlooking something straightforward here or would it be best to maintain separate files for the Runtime and the SDK? - 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 with Start menu shortcuts in Wix 3.0
I think I have something working in my solution so thought I should create
a complete working samplefirst 3.0 here (in case it can actually help
someone with the same dilemma). It does exactly what I wanted it to -
creates shortcuts in a folder off All Programs pointing to the installed
components.
Please let me know if there is anything unpleasant about this approach.
Thanks.
?xml version=1.0 encoding=utf-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Product Name=Foobar 1.0 Id=257ABFBA-71CC-4C5C-9DEB-398932990DBF
Language=1033 Codepage=1252 Version=1.0.0 Manufacturer=Acme Ltd.
Package Keywords=Installer Description=Acme's Foobar
1.0Installer Comments=Foobar is a registered trademark of Acme Ltd.
Manufacturer=Acme Ltd. InstallerVersion=100 Languages=1033
Compressed=yes SummaryCodepage=1252 /
Media Id=1 Cabinet=Sample.cab EmbedCab=yes DiskPrompt=CD-ROM
#1 /
Property Id=DiskPrompt Value=Acme's Foobar 1.0 Installation [1]
/
Directory Id=TARGETDIR Name=SourceDir
Directory Id=ProgramFilesFolder Name=PFiles
Directory Id=Acme Name=Acme
Directory Id=INSTALLDIR ShortName=Foobar10 Name=Foobar
1.0
Component Id=MainExecutable
Guid=6D4B73E9-D410-465D-BC07-CED8AFD1BC23
RegistryKey Root=HKCU Key=Software\RMS
ConnectPro\Uninstall
RegistryValue Value=0 Type=string KeyPath=yes
/
/RegistryKey
File Id=FoobarEXE ShortName=Foobar10.exe Name=
FoobarAppl10.exe DiskId=1 Source=FoobarAppl10.exe Vital=yes
Shortcut Id=startmenuFoobar10
Directory=ProgramMenuDir ShortName=Foobar10 Name=Foobar 1.0
WorkingDirectory=INSTALLDIR Icon=Foobar10.exe IconIndex=0 /
Shortcut Id=desktopFoobar10
Directory=DesktopFolder ShortName=Foobar10 Name=Foobar 1.0
WorkingDirectory=INSTALLDIR Icon=Foobar10.exe IconIndex=0 /
/File
RemoveFolder Id=ProgramMenuDir On=uninstall /
/Component
Component Id=HelperLibrary
Guid=FBF62A3C-8D14-4A59-B272-66D81F8F41A4
File Id=HelperDLL Name=Helper.dll DiskId=1
Source=Helper.dll Vital=yes /
/Component
Component Id=Manual
Guid=37EDF628-97C8-4FC4-AE6B-3B74EF351FC1
RegistryKey Root=HKCU Key=Software\RMS
ConnectPro\Uninstall
RegistryValue Value=0 Type=string KeyPath=yes
/
/RegistryKey
File Id=Manual Name=Manual.pdf DiskId=1 Source=
Manual.pdf
Shortcut Id=startmenuManual
Directory=ProgramMenuDir ShortName=Manual Name=Instruction Manual /
/File
/Component
/Directory
/Directory
/Directory
Directory Id=ProgramMenuFolder Name=Programs
Directory Id=ProgramMenuDir Name=Foobar 1.0
Component Id=ProgramMenuDirComponent
Guid=1C43BD4D-2BFB-4902-80D9-76EBEC8628D9
RegistryKey Root=HKCU Key=Software\RMS
ConnectPro\Uninstall
RegistryValue
Value={25ADFC0F-BFD4-44A6-91CE-BF653D34BBD0} Type=string KeyPath=yes
/
!-- The value means nothing. Just thought a guid was
an appropriate dummy registry entry --
/RegistryKey
RemoveFolder Id='RemoveProgramMenuDir'
Directory='ProgramMenuDir' On='uninstall' /
/Component
/Directory
/Directory
Directory Id=DesktopFolder Name=Desktop /
/Directory
Feature Id=Complete Level=1
ComponentRef Id=MainExecutable /
ComponentRef Id=HelperLibrary /
ComponentRef Id=Manual /
ComponentRef Id=ProgramMenuDirComponent /
/Feature
Icon Id=Foobar10.exe SourceFile=FoobarAppl10.exe /
/Product
/Wix
-
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] telling WiX to get files from Team Foundation Server
Hi WiX-Team, I am new to WiX and testing it for about a week, because we need to customize the standard Setup of Visual Studio for our webapplication. The problem is that we got a pretty big webapplication (about 3000 files and 200 folders to deploy) and we are using VS 2005 with Team Foundation Server. So here is the problem concerning WiX, I was not able to find any solution in WiX to told it to get every File of the Repository folder (especially new checked-in files), the only thing I found was to write to the wxs the folderstructure and then adding the files, but it is really time consuming to do this and its not really an autobuild. Also heat was not able to create a wxs file for me because it does always exit with a System.ArgumentNullException. If I decompile the setup of Visual Studio with dark it creates me a 2MB wxs file with no real structure at all. So is there a possibility to solve this case, or perhaps is there some kind of workaround or other technology that could help me out, because I do not find a post in the mailing list concerning this problem (or perhaps I was only not able to find it) Regards, Peter Huster - 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] upgrade code in installshield package
I have a previous version of the software installed using installshield and i
do not have any (upgrade) GUIDs associated with the package other than the
one which gets created under
HKLM\Software\Microsoft\Uninstall\{GUID}..How do i make my new WiX 2.0
installer to detect this package? What GUID should i be using inside
Upgrade tag? Any help?
--
View this message in context:
http://www.nabble.com/upgrade-code-in-installshield-package-tf4435209.html#a12653340
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] Frustrating Bootstrapper problem
I have a WIX Msi install almost working fully now. I also have the bootstrapper installing the prerequisites then launching the msi without a hitch this all works great. btw im using the GenerateBootStrapper task for msbuild to generate the bootstrapper, however i have 2 major issues left. the first being, i do not want the user to launch the msi standalone, this is easy, now the MSI is expecting a parameter RUNFROMEXE=1 before it will run. my issue is i cannot get the setup.exe to pass this to the msi when launching it. I have tried msistuff which appears to work, i view the properties of the exe, there are none, i run the msistuff command and check again and my parameters are there, i launch the setup.exe and it doesnt make any difference. Surely someone must be doing something similar and have solved the problem.. thanks in advance -- View this message in context: http://www.nabble.com/Frustrating-Bootstrapper-problem-tf4435226.html#a12653405 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] telling WiX to get files from Team Foundation Server
Are you using TFS TeamBuild? If not, I would certainly suggest you do since it's a very important piece of the TFS system. If you are using TFS, just set the WorkspaceMapping.xml InternalMapping elements in your TeamBuildType to teach TeamBuild how to do the CoreGet. You can also override the BeforeGet and AfterGet targets in your TFSBuild.proj to do things like create ItemsGroups and Copy tasks to teach your build how to bring other build resources into scope for consumption. [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi WiX-Team, I am new to WiX and testing it for about a week, because we need to customize the standard Setup of Visual Studio for our webapplication. The problem is that we got a pretty big webapplication (about 3000 files and 200 folders to deploy) and we are using VS 2005 with Team Foundation Server. So here is the problem concerning WiX, I was not able to find any solution in WiX to told it to get every File of the Repository folder (especially new checked-in files), the only thing I found was to write to the wxs the folderstructure and then adding the files, but it is really time consuming to do this and its not really an autobuild. Also heat was not able to create a wxs file for me because it does always exit with a System.ArgumentNullException. If I decompile the setup of Visual Studio with dark it creates me a 2MB wxs file with no real structure at all. So is there a possibility to solve this case, or perhaps is there some kind of workaround or other technology that could help me out, because I do not find a post in the mailing list concerning this problem (or perhaps I was only not able to find it) Regards, Peter Huster - 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 - Luggage? GPS? Comic books? Check out fitting gifts for grads at Yahoo! Search.- 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] prerequisites .net , sqlce etc
Hi, Where can I find some information of having a WiX project check for prerequisites like .Net2 and SQL Compact Edition and download them from MS and install them if not already on on a users machine. Thanks, Glen. - 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] prerequisites .net , sqlce etc
You can do this by using the GenerateBootStrapper task in MSBuild, it already has a few prerequisites built for you including .Net 2 and SQL CE Documentation is here http://msdn2.microsoft.com/en-us/library/ms164294.aspx Glen Harvy wrote: Hi, Where can I find some information of having a WiX project check for prerequisites like .Net2 and SQL Compact Edition and download them from MS and install them if not already on on a users machine. Thanks, Glen. - 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 -- View this message in context: http://www.nabble.com/prerequisites-.net-%2C-sqlce-etc-tf4435638.html#a12654660 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] Frustrating Bootstrapper problem
conkerjoe wrote: the first being, i do not want the user to launch the msi standalone, this is easy, now the MSI is expecting a parameter RUNFROMEXE=1 before it will run. my issue is i cannot get the setup.exe to pass this to the msi when launching it. Hi, I couldn't find any way to provide RUNFROMEXE from Setup.exe. Besides this RUNFROMEXE=1 could be added to command line of msiexec too. What I would try is to do the prerequesites check within the msi again (and remove RUNFROMEXE). With an appropriate message to use setup.exe instead of msi when the condition fails. See: http://www.wixwiki.com/index.php?title=NetFxExtension hth Dominik -- View this message in context: http://www.nabble.com/Frustrating-Bootstrapper-problem-tf4435226.html#a12654892 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] prerequisites .net , sqlce etc
Glen, Some of the prerequisites you mention (specifically the .NET runtime) are packaged using Microsoft Installer technology themselves. As a result, you cannot automatically install them from within your MSI - all you can do is make your MSI verify that they have been installed. The archives of this mailing list should provide some samples of the syntax you need to use for your tests. As far as actually downloading and installing the prerequisites, you need something known as a bootstrapper or chainer. Searching on those terms will probably give you the information you need. Personally, I have uses NSIS as a bootstrapper with some success. Regards, Richard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Glen Harvy Sent: Thursday, September 13, 2007 9:14 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] prerequisites .net , sqlce etc Hi, Where can I find some information of having a WiX project check for prerequisites like .Net2 and SQL Compact Edition and download them from MS and install them if not already on on a users machine. Thanks, Glen. - 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] telling WiX to get files from Team Foundation Server
Peter, If Heat is exiting with an ArgumentNullException it seems likely that you have caught a bug. I suggest making sure it is added to the tracker (at http://sourceforge.net/tracker/?atid=642714group_id=105970func=browse - I haven't checked to see if there is one entered already). WiX is really not good (at least not yet) in scenarios where there are large numbers of arbitrarily changing files. This is an intentional design decision due to the Microsoft Installer component rules, and the difficulties associated with creating component definitions which are easy to service (apply patches to, etc). IGNORE THE COMPONENT RULES AT YOUR OWN RISK! I thought Rob's blog (http://robmensching.com/blog/) had quite a lot of details behind this decision, and some examples of what could get messed up if the component rules are ignored but it appears I was wrong. Having said that, you may want to read http://robmensching.com/blog/archive/2007/03/09/Windows-Installer-identi fiers-must-be-stable.aspx, and the pages it links to. The best mechanism, but as you have observed not an automated one, is to educate your developers so they know that when they add a file to the solution they also need to add a reference to the WiX source if the file needs to be deployed. Sadly, in many (if not most) large team environments developers don't concern themselves with setup. Sorry I can't help with your immediate problem. Regards, Richard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, September 13, 2007 6:49 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] telling WiX to get files from Team Foundation Server Hi WiX-Team, I am new to WiX and testing it for about a week, because we need to customize the standard Setup of Visual Studio for our webapplication. The problem is that we got a pretty big webapplication (about 3000 files and 200 folders to deploy) and we are using VS 2005 with Team Foundation Server. So here is the problem concerning WiX, I was not able to find any solution in WiX to told it to get every File of the Repository folder (especially new checked-in files), the only thing I found was to write to the wxs the folderstructure and then adding the files, but it is really time consuming to do this and its not really an autobuild. Also heat was not able to create a wxs file for me because it does always exit with a System.ArgumentNullException. If I decompile the setup of Visual Studio with dark it creates me a 2MB wxs file with no real structure at all. So is there a possibility to solve this case, or perhaps is there some kind of workaround or other technology that could help me out, because I do not find a post in the mailing list concerning this problem (or perhaps I was only not able to find it) Regards, Peter Huster - 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] Frustrating Bootstrapper problem
Im sorry i dont quite understand what you are suggesting. If i remove the RUNFROMEXE the user can launch the msi without the exe. which is not what i want. And .Net is not my only prerequisite.. i have over 10 custom prerequisite.. which i have working perfectly. my only issue is modifying the setup.exe generated by GenerateBootStrapper to pass this parameter along with some upgrading parameters to the msiexec call when it launches the msi. Dominik Guder wrote: conkerjoe wrote: the first being, i do not want the user to launch the msi standalone, this is easy, now the MSI is expecting a parameter RUNFROMEXE=1 before it will run. my issue is i cannot get the setup.exe to pass this to the msi when launching it. Hi, I couldn't find any way to provide RUNFROMEXE from Setup.exe. Besides this RUNFROMEXE=1 could be added to command line of msiexec too. What I would try is to do the prerequesites check within the msi again (and remove RUNFROMEXE). With an appropriate message to use setup.exe instead of msi when the condition fails. See: http://www.wixwiki.com/index.php?title=NetFxExtension hth Dominik -- View this message in context: http://www.nabble.com/Frustrating-Bootstrapper-problem-tf4435226.html#a12654902 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] prerequisites .net , sqlce etc
Hi Richard, I appreciate your comments. So far I have always used the Setup Deployment project in VS20005 to create my msi and setup files. I have always configured VS2005 to check and download the prerequisites and they work fine. I need now to become a bit more professional and find that adding dialog boxes etc within the VS2005 IDE daunting and am unable to locate any documentation, tutorials or active assistance in learning how to. For well over a year I have been toying with WiX (Votive actually) but have never reached the end of the task for various reasons. I have also struggled with other installer packages with similar frustrations. As I understand it, I need to create an msi for my application using Wix and then create a setup.exe file which is in effect is a bootstrapper that will check the users computer for prerequisites, download and install them. My applications msi file will be installed by the setup.exe file providing each other prerequisite has succeeded. The prerequisites can be supplied by me, downloaded from me or the vendor's site. I just need to configure the setup.exe file properly and that is done using xml. I believe that I can eventually get WiX working/configured OK - with a little bit of help of course. I have looked in several places and have been unable to find any comprehensive but simplified tutorial on building the setup.exe/bootstrapper file. Terminology is (I have always found) the most confusing when trying to learn. eg what is a msbuild project? I also note that I am not alone! Many web references are people like me screaming out for guidance and a tutorial - I wonder if David Thielen ever worked it out. Thanks for your help. I will need to concentrate on the setup.exe file and get that under my belt before I concentrate on WiX and my msi file. If I still have the wrong end of the stick - please let me know. Cheers. Glen Harvy. On 13/09/2007 11:36 PM, [EMAIL PROTECTED] wrote: Glen, Some of the prerequisites you mention (specifically the .NET runtime) are packaged using Microsoft Installer technology themselves. As a result, you cannot automatically install them from within your MSI -- all you can do is make your MSI verify that they have been installed. The archives of this mailing list should provide some samples of the syntax you need to use for your tests. As far as actually downloading and installing the prerequisites, you need something known as a bootstrapper or chainer. Searching on those terms will probably give you the information you need. Personally, I have uses NSIS as a bootstrapper with some success. Regards, Richard *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *On Behalf Of *Glen Harvy *Sent:* Thursday, September 13, 2007 9:14 AM *To:* wix-users@lists.sourceforge.net *Subject:* [WiX-users] prerequisites .net , sqlce etc Hi, Where can I find some information of having a WiX project check for prerequisites like .Net2 and SQL Compact Edition and download them from MS and install them if not already on on a users machine. Thanks, Glen. - 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] Administrative Installation
Put it on a share and let them browse to the MSI file and run it. Phil Wilson From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of V K Gangwar Sent: Wednesday, September 12, 2007 10:10 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Administrative Installation I made a source image of my .MSI package using msiexec /a option and put in my machine. Can anybody tell me that how on user in same workgroup can install in his machine from this source image? I mean that how a user can install .msi in his machine? What he has to do? regards, Veerendra Luggage? GPS? Comic books? Check out fitting gifts for grads http://us.rd.yahoo.com/evt=48249/*http:/search.yahoo.com/search?fr=oni_ on_mailp=graduation+giftscs=bz at Yahoo! Search. - 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] condition onl component
I'm not sure about the WiX syntax but in MSI terms: if the component condition evaluates to FALSEthe component will NOT be installed. And if it was True in the first time install and then becomes False in the upgrade, that component will be REMOVED - but only if the component has the transitive flag set. Otherwise the condition willö not be re-evaluated. -- Stefan Krueger Microsoft Windows Installer MVP Please post your questions in the newsgroup or vist one of these web sites: Windows Installer FAQ http://www.msifaq.com - http://www.msifaq.de InstallSite - Resources for Setup Developers http://www.installsite.org http://www.installsite.de (GERMAN) Frédéric Viollet [EMAIL PROTECTED] schrieb im Newsbeitrag news:[EMAIL PROTECTED] Stefan Krueger [MVP] a écrit : So you only want to condition the copy (which corresponds to a MoveFile table row I guess) but not the instalaltion of the component. To do this you need to put the copy element in a separate component, because rows in the MoveFile table can't have conditions by themselves, instead they use components as a gate. I tried this out as well. With no success... My problem is really to affect a condition to a component. It seems that whether my condition is full filed or not, the component is upgraded in both cases. This is what my code looks like: Property Id=ENGINECONFISINSTALLED RegistrySearch Id='EngineRegPath' Root='HKLM' Key='SOFTWARE\MyProduct\Engine' Name='InstallDir' Type='directory' DirectorySearch Id='FindEngineIniFilePath' Depth=2 FileSearch Id='FindEngineIniFile' Name=ampm_engine.ini / /DirectorySearch /RegistrySearch /Property Component Id=APM_ENGINE_CONFIG_REF Guid=4C6B380E-4DFE-458C-A29F-8A0C434E7F70 ConditionENGINECONFISINSTALLED/Condition File Id=ampm_engine.ref Name=ampm_engine.ref KeyPath=yes Source=$(var.FACT_DESTDIR)\var\config\ampm_engine.ref CopyFile Id=APM_ENGINE_CONFIG_INI DestinationDirectory=config DestinationName=amengine.ini DestinationLongName=ampm_engine.ini / /File IniFile Id=EnginePort Action=addLine Directory=config Name=ampm_engine.ini Section=NETWORK Key=Port Value=[PORTNUMBER] / /Component I thought that the upper code would allow me to perform the component's tasks only if ENGINECONFISINSTALLED was false (that would be on a first install). What I'm trying to do is condition the whole APM_ENGINE_CONFIG_REF component. But I can't : whatever I put as a condition, the component tasks are executed (on first install AND on upgrade) I must be doing something wrong here, but I can't find out what... Thanks for your help. Fred - 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/ - 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] condition onl component
Ok. This isn't really the behavior I'm looking for. I managed to solve my problem by using Components with empty GUIDs to install and modify the config files. In that way, the component is not managed. Since it cannot be updated or removed, my config files are not overwritten on upgrades any more. And I manage the remove part with RemoveFile elements. Thanks for your help. Fred Stefan Krueger [MVP] a écrit : I'm not sure about the WiX syntax but in MSI terms: if the component condition evaluates to FALSEthe component will NOT be installed. And if it was True in the first time install and then becomes False in the upgrade, that component will be REMOVED - but only if the component has the transitive flag set. Otherwise the condition willö not be re-evaluated. - 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] prerequisites .net , sqlce etc
Glen, I agree, documentation on this is all over the place. Unfortunately like many open source projects any work people do on WiX is almost invariably in their spare time. My understanding is that your understanding is correct. Your MSI should include checks (coded in Wix as as condition elements under the fragment / product - i.e. a launch condition) for the prerequisites just in case someone wants to install your product using an enterprise-wide system management tool like Microsoft's SMS (in which case they are likely to do so using the MSI itself, not a bootstrapper). Your bootstrapper will make the experience for regular users friendlier by ensuring those prerequisites have been met prior to triggering the installation of your MSI. As far as a tutorial for the bootstrapper is concerned the problem is that there are many possible choices for creating one - from rolling your own to using GenerateBootstrapper, and on into one of the process driven installation tools like NSIS or InnoSetup. MSBuild is the build technology behind Visual Studio 2005 (and the .NET 2.0 SDK, IIRC). Think of it as Microsoft's implementation of NAnt and you won't be far wrong. VS 2005 .XXproj files are (if I understand correctly) actually MSBuild scripts. Hope this helps, Regards, Richard From: Glen Harvy [mailto:[EMAIL PROTECTED] Sent: Thursday, September 13, 2007 10:40 AM To: WiX Users Group Subject: Re: [WiX-users] prerequisites .net , sqlce etc Hi Richard, I appreciate your comments. So far I have always used the Setup Deployment project in VS20005 to create my msi and setup files. I have always configured VS2005 to check and download the prerequisites and they work fine. I need now to become a bit more professional and find that adding dialog boxes etc within the VS2005 IDE daunting and am unable to locate any documentation, tutorials or active assistance in learning how to. For well over a year I have been toying with WiX (Votive actually) but have never reached the end of the task for various reasons. I have also struggled with other installer packages with similar frustrations. As I understand it, I need to create an msi for my application using Wix and then create a setup.exe file which is in effect is a bootstrapper that will check the users computer for prerequisites, download and install them. My applications msi file will be installed by the setup.exe file providing each other prerequisite has succeeded. The prerequisites can be supplied by me, downloaded from me or the vendor's site. I just need to configure the setup.exe file properly and that is done using xml. I believe that I can eventually get WiX working/configured OK - with a little bit of help of course. I have looked in several places and have been unable to find any comprehensive but simplified tutorial on building the setup.exe/bootstrapper file. Terminology is (I have always found) the most confusing when trying to learn. eg what is a msbuild project? I also note that I am not alone! Many web references are people like me screaming out for guidance and a tutorial - I wonder if David Thielen ever worked it out. Thanks for your help. I will need to concentrate on the setup.exe file and get that under my belt before I concentrate on WiX and my msi file. If I still have the wrong end of the stick - please let me know. Cheers. Glen Harvy. On 13/09/2007 11:36 PM, [EMAIL PROTECTED] wrote: Glen, Some of the prerequisites you mention (specifically the .NET runtime) are packaged using Microsoft Installer technology themselves. As a result, you cannot automatically install them from within your MSI - all you can do is make your MSI verify that they have been installed. The archives of this mailing list should provide some samples of the syntax you need to use for your tests. As far as actually downloading and installing the prerequisites, you need something known as a bootstrapper or chainer. Searching on those terms will probably give you the information you need. Personally, I have uses NSIS as a bootstrapper with some success. Regards, Richard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Glen Harvy Sent: Thursday, September 13, 2007 9:14 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] prerequisites .net , sqlce etc Hi, Where can I find some information of having a WiX project check for prerequisites like .Net2 and SQL Compact Edition and download them from MS and install them if not already on on a users machine. Thanks, Glen. * C O N F I D E N T I A L I T Y N O T I C E * --- The content of this e-mail is intended solely for the use of the individual or entity to whom it is addressed. If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other
Re: [WiX-users] prerequisites .net , sqlce etc
I would suggest considering http://www.devage.com/Wiki/ViewArticle.aspx?name=dotnetinstallerversion=0 dotNetInstaller . In addition to supporting prerequisite installations of the .NET Framework, it also supports installing other prerequisites such as SQL Express. There is also a GUI to help with creating the bootstrapper configuration. Additionally, the source code is available for download. Hope this helps. Thanks, Matthew Glen Harvy wrote: Hi, Where can I find some information of having a WiX project check for prerequisites like .Net2 and SQL Compact Edition and download them from MS and install them if not already on on a users machine. Thanks, Glen. -- View this message in context: http://www.nabble.com/prerequisites-.net-%2C-sqlce-etc-tf4435638.html#a12659909 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] prerequisites .net , sqlce etc
Actually SMS can push support files like bootstappers out with the msi to the
distribution points and invoke them as part of their package definition. In
fact, SMS doesn't really even require MSI's although MSIs generally behave
nicer.
The scenario you describe is a limitation of GPO since GPO can only invoke
MSI's.
Regardless you are correct, bootstrapper checks should have redundant
LaunchConditions as the user could have invoked the MSI instead of the EXE.
As a note: When using SMS, always distribute the MSI outside of the EXE(
fully ,exposed ) as this is the only way the SMS Advanced Client can be aware
of the packages ProductCode and have access to the MSI for assisting in source
resolution. It should also be noticed that SMS ( atleast the last time I used
it ) only correlates the distribution point to the MSI source if the DP is
considered `local`. It does not do this for remote DP's. I wrote about this
back in 2004 ( bullets 4 and 5 )
http://blog.deploymentengineering.com/2004/12/msi-patching-with-sms.html
[EMAIL PROTECTED] wrote:
v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);}
My understanding is that your understanding is correct. Your MSI should
include checks (coded in Wix as as condition elements under the fragment /
product i.e. a launch condition) for the prerequisites just in case someone
wants to install your product using an enterprise-wide system management tool
like Microsofts SMS (in which case they are likely to do so using the MSI
itself, not a bootstrapper). Your bootstrapper will make the experience for
regular users friendlier by ensuring those prerequisites have been met prior
to triggering the installation of your MSI.
-
Shape Yahoo! in your own image. Join our Network Research Panel today!-
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] prerequisites .net , sqlce etc
Thanks for the clarification Christopher! It was my (apparently inaccurate) understanding that most SMS users preferred using MSI's directly (and managing dependencies themselves) because of the risks associated with a bootstrapper potentially doing something that could not easily be repared and/or removed at a later date. (I'm guessing that is the nicer operation you describe.:-) ) Regards, Richard From: Christopher Painter [mailto:[EMAIL PROTECTED] Sent: Thursday, September 13, 2007 1:50 PM To: Foster, Richard - PAL; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] prerequisites .net , sqlce etc Actually SMS can push support files like bootstappers out with the msi to the distribution points and invoke them as part of their package definition. In fact, SMS doesn't really even require MSI's although MSIs generally behave nicer. [Snip!] * C O N F I D E N T I A L I T Y N O T I C E * --- The content of this e-mail is intended solely for the use of the individual or entity to whom it is addressed. If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited. Quixote Traffic Corporation is neither liable for the contents, nor for the proper, complete and timely transmission of (the information contained in) this communication. If you have received this communication in error, please notify the author by replying to this e-mail immediately and delete the material from any computer. - 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] Install files into MS Office directory
Hi, I would like to install some files into Microsoft Excel startup directory. I decided to use WiX. I created a msi package according to available documentation and it seems well. However, I think that my solution isn't correct. Destination path depends on installed version of MS Office. I can check wheather Microsoft Excel is installed on destination computer. I can read Microsoft Excel version at registry. Now I need to determine destination path according to installed version. Unfortunately, I don't know how to define Property element dynamically. Therefore I created three components. Each component contains the same file(s) as other ones. I think, it isn't correct solution. Could you help me please? http://www.nabble.com/file/p12662778/qc2excel.wxs qc2excel.wxs -- View this message in context: http://www.nabble.com/Install-files-into-MS-Office-directory-tf4438183.html#a12662778 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] Wix3 - Weird error 'FileShare' table collision
Hi, We're using Wix3, and just added some code to try to patch an XML config file which we install. The code wix code for attempting the patch is below: util:XmlFile Id=ModifyDeveloperLog Action=setValue ElementPath=/log4net/[EMAIL PROTECTED]'PerformanceLogAppender']/file/@value File=[#Logging.config] Value=[PROJECT_DIR]\Log\Performance.log/ When linking we get the following error: light.exe : error LGHT0126 : The extension 'Microsoft.Tools.WindowsInstallerXml.Extensions.UtilExtension' contains a defintion for table 'FileShare' that collides with a previously loaded table definition. Please remove one of the conflicting extensions or rename one of the tables to avoid the collision. Thing is that we never explicitly use a FileShare tag in the wix source, so I was wondering if someone knows what's happening here? Thanks in advance, Friedrich Be smarter than spam. See how smart SpamGuard is at giving junk email the boot with the All-new Yahoo! Mail at http://mrd.mail.yahoo.com/try_beta?.intl=ca - 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] Customizing the dialog sequnce with Floating Publish events
HI, I'm trying to see if I can insert a dialog into the WixUI_InstallDir sequence, the docs say you can do Publish Dialog=WelcomeDlg Control=Next Event=NewDialog Value=SpecialDlg1/Publish Publish Dialog=SpecialDlg Control=Back Event=NewDialog Value=WelcomeDlg1/Publish Publish Dialog=SpecialDlg Control=Next Event=NewDialog Value=LicenseAgreementDlg1/Publish Publish Dialog=LicenseAgreementDlg Control=Back Event=NewDialog Value=SpecialDlg1/Publish Publish Dialog=LicenseAgreementDlg Control=Next Event=NewDialog Value=InstallDirDlgLicenseAccepted = 1/Publish But aren't really clear about where that should happen. I tried doing this, but I never see my dialog... Property Id=WIXUI_INSTALLDIR Value=INSTALLDIR / UIRef Id=WixUI_InstallDir / UI Dialog Id=SpecialDlg Width=370 Height=270 Control Id=Special_Txt Type=Text X=5 Y=20 Width=60 Height=18 TabSkip=no Text[DialogFont]Hi there!/Text /Control Control Id=Next Type=PushButton X=236 Y=243 Width=56 Height=17 Default=yes Text=!(loc.WixUINext) / Control Id=Back Type=PushButton X=180 Y=243 Width=56 Height=17 Disabled=yes Text=!(loc.WixUIBack) / /Dialog Publish Dialog=WelcomeDlg Control=Next Event=NewDialog Value=SpecialDlg Order=11/Publish Publish Dialog=SpecialDlg Control=Back Event=NewDialog Value=WelcomeDlg Order=11/Publish Publish Dialog=SpecialDlg Control=Next Event=NewDialog Value=LicenseAgreementDlg Order=11/Publish Publish Dialog=LicenseAgreementDlg Control=Back Event=NewDialog Value=SpecialDlg Order=11/Publish /UI Thanks, -Ian Ian Sullivan Software Development Engineer Microsoft Inc., Windows Live Agents: SDK, Tools, Web Services - 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] install integrated MSHelp2 with WixVSExtensions.dll
We've been exploring WIX a bit and found it's developer friendly compile/link process and the votive wixlib project system to be a fantastic improvement over all other tools we've used. Even with as little documentation as there is on WIX we've been able to get productive quite quickly. However, there is one nagging issue we can't figure out. We are trying to provide integrated help for VS2005 for our developer libraries. The WixVsExtensions.dll looks like it will ultimately do the trick but we just can't figure out how to get it to work right. (Getting an ICE03 error regarding an invalid foreign key if we use the PlugCollectionInto element) Has anyone tried using any of this? Any pointers, suggestions or samples? Steve Maillet - CTO EmbeddedFusion, Ltd. - 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] Installation location in V3
Hi, How can I make installed files go into other than predetermined locations. In V2, I used to write Public property Property Id=SETUPDIR Value=C:\Inetpub\wwwroot / With this property, V3 gave me the following warning, warning LGHT1076 : ICE48: Directory 'SETUPDIR' appears to be hardcoded in the property table to a local drive. even Value=ProgramFilesFolder gave the same warning. Looking for help. Thanks. _ News, entertainment and everything you care about at Live.com. Get it now! http://www.live.com/getstarted.aspx- 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] Something wrong with the component condition
hi all, I has a windows installer package and i want to install the feature sooa when it is on Windows 2008 Server, so i write the component condition like this, but it doesn't work at all and on any operating system the sooa will be installed. Does any one know what's wrong with it. Thanks very much. Feature Id=FeatureSsoa Title=ssoa Level=3 Condition Level=0![CDATA[MsiNTProductType=3 AND VersionNT=600]]/Condition ComponentRef Id=Sss / /Feature -- View this message in context: http://www.nabble.com/Something-wrong-with-the-component-condition-tf4440318.html#a12668955 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
