Re: [WiX-users] filesearch not finding file

2009-07-22 Thread Alexander Shevchuk
Hi Eric, Directory resolution is done during CostFinalize, way after AppSearch. What you need to do is save the value of HostDir in the registry as part of your install. Then, during reinstall/upgrade you can use AppSearch to get saved value from registry and use it for FileSearch. Alex -O

Re: [WiX-users] filesearch not finding file

2009-07-22 Thread Eric Napier
Yes, HostDir is the innermost item in my installation hierarchy. It contains a component and an ini entry (in msi.ini). So if a different msi with this same structure is executed, I'd expect the filesearch to find this file. But it's not. -- Forwarded message -- From: John Ludlow T

Re: [WiX-users] end up with emtpy msi

2009-07-22 Thread Alexander Shevchuk
Make sure you reference all components/groups. Check if your installer installs all files you expect to be installed. Check if any of the components marked as permanent (Permanent attribute is set to "yes"). Remember also that MSI removes only empty folders, so if your application creates some file

Re: [WiX-users] end up with emtpy msi

2009-07-22 Thread jo...@msli.com
I had to learn to pull in the fragments. Thank you very much. I didn't have to create my own cab file. In MyApp.wxs, I added to In MyApp.fragment.wxs, group_MyApp is defined as a and hold all the files. Finally, I had to add to MyApp.wxs

[WiX-users] Question about Create a Shortcut on the Start Menu

2009-07-22 Thread Ryan Dai
Hi, I am checking out wix 3 help doc (How To: Create a Shortcut on the Start Menu). I am wondering why it is necessary to write registry to HKCU if product is installed for all users. Suppose one admin of system installed the product, what will happen if another admin of system uninstall the pro

Re: [WiX-users] Need a Good Working Sample

2009-07-22 Thread Ravi Patt
I am compiling the WiX.wixproj(VS 2008) form the following location on my dev box:- G:\WiX3\wix3.0.5419.0-sources\src\Setup. What is the folder structure that I have to setup to get it compiled correctly? Right now I am getting several of these errors:- G:\WiX3\wix3.0.5419.0-source

Re: [WiX-users] filesearch not finding file

2009-07-22 Thread Alexander Shevchuk
>So instead I'm checking for the presence of this file. If it's there, I want >to fail the install. Not sure how and when HostDir property gets its value. You might want to make it public (all uppercase and Secure set to "yes") if AppSearch happens in the InstallExecuteSequence. Alex -

Re: [WiX-users] filesearch not finding file

2009-07-22 Thread John Ludlow
What sets HostDir? Does HostDir point to a folder containing msi.ini (you can check that from the log)? 2009/7/22 Eric Napier : > Component search is a better choice except that I won't know the old > component guid. > So instead I'm checking for the presence of this file. If it's there, I want >

Re: [WiX-users] end up with emtpy msi

2009-07-22 Thread Alexander Shevchuk
As far as Media element, this can help: http://blogs.technet.com/alexshev/archive/2008/04/04/from-msi-to-wix-part-16 -installable-items-handling-installation-media.aspx I have suspicion that wxs files created by Paraffin contain fragments and in order to include content of fragment to resulting m

Re: [WiX-users] filesearch not finding file

2009-07-22 Thread Eric Napier
Component search is a better choice except that I won't know the old component guid. So instead I'm checking for the presence of this file. If it's there, I want to fail the install. -- Forwarded message -- From: "Wilson, Phil" To: General discussion for Windows Installer XML tool

[WiX-users] end up with emtpy msi

2009-07-22 Thread jo...@msli.com
I am using wix3.0.5419.0 to generate an msi from 2 wxs files (first sets project, second sets files in a tag), but the resulting msi is too small and doesn't work. Incantations to generate msi in my build product directory: Paraffin.exe -dir '.\.' -custom "MyApp" -g -alias '.\' -ext '.WXS' MyApp

Re: [WiX-users] How to sequence VBScript a in-script custom action

2009-07-22 Thread Jirong Hu
Hi Alex I tried and it worked. Thanks a lot. Not Installed Not Installed -Original Message- From: Al

Re: [WiX-users] Upgrading...

2009-07-22 Thread Alexander Shevchuk
Few options available here and you can find more using search engine of your choice: Neil Sleightholm's blog: - http://neilsleightholm.blogspot.com/2009/01/wix-script-for-major-upgrades.ht ml My take on it: - http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-part-8- major

Re: [WiX-users] Upgrading...

2009-07-22 Thread Chris Lord
Take at look at the WiX tutorial at http://www.tramontana.co.hu/wix/lesson4.php This has some detail on doing upgrades. That should start you on your way. Chris -Original Message- From: John D. Marinuzzi [mailto:nu...@hypack.com] Sent: Wednesday, July 22, 2009 13:12 To: wix-users@lis

Re: [WiX-users] How People Validate Their Installers

2009-07-22 Thread Chris Lord
I run it...plain and simple. I have a dedicated machine with removable drives that I can image to a base setup of Win2000, Win XP, Vista and a Win 7 install will be added in the near future. >From there, I can test a clean install, or I can install a previous version and make sure it gets upgr

Re: [WiX-users] How People Validate Their Installers

2009-07-22 Thread Wilson, Phil
I don't know that they do! How do you automate that a developer says "this file should be installed to that location"? There's no way to automate that unless you have some tool that records it, and that tool is basically WiX. You could have another pretty GUI tool that records what developers sa

Re: [WiX-users] filesearch not finding file

2009-07-22 Thread Wilson, Phil
What's the goal here? Are you looking for that file, or is it just a marker for a previous version of the product? If it was previously installed with an MSI package a component search would be more reliable - it doesn't depend on directory locations, and it works if the user changes the install

Re: [WiX-users] New Major Version. Should I have new Components GUIDs?

2009-07-22 Thread Lord Larry
Bob Arnson wrote: > Pally Sandher wrote: > >> If you want to know what happens if you don't change the GUID's read up >> >> > > MSI supports having multiple products install the same component to > different directories. But it does require even more strict adherence to > all the compo

Re: [WiX-users] strong name for C# custom action project

2009-07-22 Thread Lian Jiang
Thanks Jason. Your input help a lot. -Original Message- From: Jason Ginchereau [mailto:jason...@microsoft.com] Sent: Wednesday, July 22, 2009 9:28 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] strong name for C# custom action project Are you using d

[WiX-users] Upgrading...

2009-07-22 Thread John D. Marinuzzi
Hello, I used WIX to create an installer for our last release of our software. I was using NSIS prior to that, but we had customers who wanted to be to implement installs over a network, so we switched. So, we are at a point where I have to do another release, and I want to be able to 1) Inst

Re: [WiX-users] strong name for C# custom action project

2009-07-22 Thread Jason Ginchereau
Are you using delay-signing? If so is it possible that mycustom.dll was delay-signed without being real-signed. Strong name signing should work fine for mycustom.dll (but not mycustom.CA.dll since that is not a .NET assembly). The tricky thing is you have to make sure the managed assembly gets

[WiX-users] filesearch not finding file

2009-07-22 Thread Eric Napier
I want to fail an installation if a file (msi.ini) is present. My filesearch element doesn't seem to be finding my file. I've confirmed the file is there. If I remove the filesearch element, the directory search finds the directory and fails the install. However, when I include the filesearch eleme

[WiX-users] strong name for C# custom action project

2009-07-22 Thread Lian Jiang
Hi, My msi uses custom action from C# custom action project. As you know, as C# custom action project will generate mycustom.dll and mycustom.CA.dll. The former is managed and the later is unmanaged. In my project, all binaries (including mycustom.dll and mycustom.CA.dll) are signed and the ms

Re: [WiX-users] patching - Re: Component GUIDs

2009-07-22 Thread shibo
Bob, 1. GUIDs Sorry, it is my mistake. -ag works. I got error msgs (error LGHT0231) earlier due to my folder structure, installation not default to ProgramFilesFolder. Checked new MSI files, yes, they share the same GUIDs. 2. Patching Just try to find inside details how the difference is calculat

Re: [WiX-users] the doc/examples/wixui/custom directory

2009-07-22 Thread Pally Sandher
The tutorial is a good place to start as there aren't any differences in the UI Elements between v2.0 & v3.0, only the linking method which the WiX 3.0 documentation covers anyway as far as I can remember. Neil Sleightholm has written a very good blog on customising the stock WiX UI's. Find it a

Re: [WiX-users] patching - Re: Component GUIDs

2009-07-22 Thread Bob Arnson
shibo wrote: > 1. auto-generate GUIDs > When using option -ag, I have to manaully change * to a real GUID. > Why? > Is my finding correct? > I don't know. I'd go by the doc. -- sig://boB http://joyofsetup.com/ ---

Re: [WiX-users] Burn, and preventing files being added to a setup

2009-07-22 Thread Bob Arnson
Sean Farrow wrote: > Is there any information on the burn utility as to how itworks and how > it can be uses? > Not yet. > Secondly, I'm creating a setup for a product and need to prevent some > files being added to the setup for the time-being, is there a way of > doing this using a #define o

Re: [WiX-users] the doc/examples/wixui/custom directory

2009-07-22 Thread Bob Arnson
Ole Martin Sørli wrote: > it says to look in the doc/examples/wixui/custom directory, but I can't seem > to find that anywhere... > They never got finished so we removed them but didn't update the help file. Gabor's tutorial discusses some customizations at http://www.tramontana.co.hu/wix/le

[WiX-users] patching - Re: Component GUIDs

2009-07-22 Thread shibo
Bob, More info: 1. auto-generate GUIDs When using option -ag, I have to manaully change * to a real GUID. 2. PatchWizard in WiX 3.0 With different GUIDs of components between two distributions, I can still create a patch and install it properly. The log file shows that file id is used in file com

Re: [WiX-users] Samples errors follow up

2009-07-22 Thread Pally Sandher
When someone volunteers in their own time to write an updated one, yes. Until then, no. Some people don't seem get this whole concept of open source development. Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **D

[WiX-users] Burn, and preventing files being added to a setup

2009-07-22 Thread Sean Farrow
Hi: Is there any information on the burn utility as to how itworks and how it can be uses? Secondly, I'm creating a setup for a product and need to prevent some files being added to the setup for the time-being, is there a way of doing this using a #define or some other similar construct?

Re: [WiX-users] Component GUIDs

2009-07-22 Thread shibo
Bob, No, I have not changed the directories. The commands I run are: heat dir KDS5.0 -gg -o KDS50_1.wxs heat dir KDS5.0 -gg -o KDS50_2.wxs -gg means generating guids now. If this is the right one, shall I use: -ag autogenerate component guids at compile time Thanks, Shibo -- View thi

[WiX-users] the doc/examples/wixui/custom directory

2009-07-22 Thread Ole Martin Sørli
Hi. On this page: http://wix.sourceforge.net/manual-wix2/WixUI_dialog_library.htm under "Customizing dialog sets" it says to look in the doc/examples/wixui/custom directory, but I can't seem to find that anywhere... Am I blind? Kind Regards Ole Martin *

Re: [WiX-users] Problem with a shortcut on Desktop to Shortcuts folder in Star Menu

2009-07-22 Thread Ondrej Zarevucky
Hi, It seems I've found a solution to the problem and the solution may help others trying to do the same thing: I've put the Folder shortcut component under the Shortcuts folder and added tag and used Directory attribute to move the resulting shortcut to the Desktop. Example: