Re: [WiX-users] Advertised feature install starting
I've got some machines that after a minor upgrade, unprivileged users unexpectedly get MSI launching a dialog saying that the feature you are trying to use is on a network resource that is unavailable. Administrators do not see the message. The installer was run as Administrator. I assume it is because some features have been installed as Advertised rather than Local. In my installer however, I have marked all my features with AllowAdvertise=no, so It's probably an automatic repair. Check the System event log to see which component MSI thinks is broken. Bob, Thanks for the pointer. It's an HKCU registry key that would have been created for the user who installed the application, but obviously not the user who is running. Is this the default behaviour for a key in HKCU even if the feature is not advertised? In this case, it doesn't matter if the settings are not available for the current user, and I would prefer MSI just to ignore these keys. Also, is this the expected behaviour? I thought that a copy of the MSI was stored away in c:\Windows\Installer, so why is the system not able to use that one rather than looking for the original .msi file that the bootstrapper dropped into the temp directory. Regards, John - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Upgrading
hmmm What about a component search, if it finds the product it fills the keypath?? Ive read this but am unsure on how to execute this my self thanks Bob Arnson-6 wrote: Craig0ss wrote: I need my MSI to check for an existing install of the software ie. 5.2.1, now it does this fine, however i also need it to check for the existing directory and then pass that information to a variable that the installer then sets the installer to install to. Basically i need the upgrade to install to the directory that the previous installation resides in? Write the directory to the registry so the upgraded version can find it using RegistrySearch. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ 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/Upgrading-tf4751110.html#a13605528 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Custom actions per component?
Hi, I wanted to know if it is possible to make a custom action run only if a certain component is installed and how to do it. Also, is there a way to put custom actions in a fragment? Thanks, Dror. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom actions as executables
In article [EMAIL PROTECTED], Dror Cohen [EMAIL PROTECTED] writes: I want my MSI to run in a custom action an executable that I want to add in= to the package but not stay on the user's machine. This executable might al= so be dependent on files (DLLs) that will be installed on the machine. What= is the easiest way to achieve that? Use a type 2 custom action. -- 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: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom actions per component?
In article [EMAIL PROTECTED], Dror Cohen [EMAIL PROTECTED] writes: I wanted to know if it is possible to make a custom action run only if a ce= rtain component is installed and how to do it. Use a condition that is true when the component is set to be installed. http://msdn2.microsoft.com/en-us/library/aa368012.aspx -- 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: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Just found SetupBld
I have been having issues with getting a bootstrapper working for some time now. i just recently found the program setupbld, and it looks like it might solve my problems. Here is what i aim to achieve the user runs setup.exe. it would detect and prerequisits and install them, then launch the msi but passing the update parameters if it already exists. curretly my setup.exe installs the prereqs but i have to do a major upgrade everytime. which is causing us major amounts of work with hacking things to make the update go smoothly. this isnt pleasent for us or the end user. will setupbld let me do this. if not is there a known bootstrapper that can achieve this for me. Back to installshield if not :( not something i would relish -- View this message in context: http://www.nabble.com/Just-found-SetupBld-tf4759258.html#a13610281 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Subclassing WIX dialogs
Folks: It appears the standard methodology for making changes in dialogs is to copy the dialog into your own .wxs file, and anything that referred to it (like a UI sequence) also has to be copied and modified. Are there any plans (maybe in Wix v3?) to include an ability to do some sort of limited 'dialog subclassing'? where perhaps you could just add a control? For example, maybe something like: Dialog Id=MyDialog Width=370 Height=270 InheritFrom=OrigDialog Control Id=CDKeyLabel Type=Text X=45 Y=147 Width=50 Height=10 TabSkip=no InsertAfter=SOMECONTROL TextCD amp;Key:/Text /Control /Dialog Lewis. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Building a patch in Visual Studio
Is it possible to build a patch inside VS2005? All I've been able to generate is a useless MSI. Thanks, Mike - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstalling WinSxS in Vista
On Nov 5, 2007 9:33 PM, Bob Arnson [EMAIL PROTECTED] wrote: Geoff Finger wrote: I've run into an issue with Vista where the side by side assemblies installed to WinSxS do not get removed when the uninstaller is run. Known issue and I'm not aware of a workaround. And yes it sucks. Well good to know that it's still a current issue and not something wrong on my end. Thanks! - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Building a patch in Visual Studio
Not possible using the Setup Deployment project. You can however build patches out of the MSI's it produces using wix v3's admin image patching features. Generate an admin image of your baseline and upgrade msi's. Call torch with -ax and the msi's in the admin layouts. Then follow the wix patch building process from there. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Schuett, Michael Sent: Tuesday, November 06, 2007 10:08 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Building a patch in Visual Studio Is it possible to build a patch inside VS2005? All I've been able to generate is a useless MSI. Thanks, Mike - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Chaining a redist package into an MSI
Hello, My issue is that I try to build an MSI, and it has a third party redist package inside it. This redist package has to be installed as part of my MSI installation. I believe this can be done by creating a custom action to execute this package. The problem is that this redist package is actually another MSI that was compiled into a .exe, and I have no idea what kind of problems this can bring up. So, the questions are: Is this a supported scenario? Do I have to do something special or just create a simple custom action that runs the redist .exe? Will there be any issues uninstalling my MSI (and will it uninstall the redist bits as well)? Thanks in advance for your insight, Karesz -- Mostly Harmless - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Chaining a redist package into an MSI
If you run it then it will probably unpack into a folder with a GUID for a name. If you keep Windows Explorer open on C:\ you will see the new folder appear as a child of the root. Generally these folders are removed again when the setup exits cleanly so the key is to terminate with extreme prejudice using Task Manager. Then you can rummage through the contents, picking out MSIs and other goodies. This is how I extracted sqlncli.msi from SQLEXPR.EXE so now I don't have to deploy all of SQL Express just to get SQL Native Client support. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Karesz Kecskemeti Sent: Wednesday, 7 November 2007 9:07 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Chaining a redist package into an MSI Hello, My issue is that I try to build an MSI, and it has a third party redist package inside it. This redist package has to be installed as part of my MSI installation. I believe this can be done by creating a custom action to execute this package. The problem is that this redist package is actually another MSI that was compiled into a .exe, and I have no idea what kind of problems this can bring up. So, the questions are: Is this a supported scenario? Do I have to do something special or just create a simple custom action that runs the redist .exe? Will there be any issues uninstalling my MSI (and will it uninstall the redist bits as well)? Thanks in advance for your insight, Karesz -- Mostly Harmless No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.503 / Virus Database: 269.15.23/1113 - Release Date: 6/11/2007 10:04 AM - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] install integrated MSHelp2 with WixVSExtensions.dll
Steve Not sure if you're still working on this, but I've recently been struggling with the same issues in WiX v3, and have finally got the help integration working. On the LGHT0204 errors (sequencing errors), I had to do the following InstallExecuteSequence InstallFinalize Sequence=7800 / /InstallExecuteSequence As per https://sourceforge.net/tracker/?func=detailatid=642714aid=1588180gro up_id=105970 Also referenced there is the Foreign Key issue. WiX v3 currently has an 'explicit' foreign key between HelpPlugIn and HelpNamespace, whereas the Merge Modules only assume a 'logical' foreign key. Check the differences between the resulting MSI and the Merge Modules in the _Validation table entries for the HelpPlugIn table (Orca is probably the easiest tool to use). Interestingly, these ICE checks seem to be done on the MSI after it has been created on disk, i.e. the FK errors don't actually stop the MSI creation. If you open the MSI with Orca and run the validation you'll see the same issues appear. If you use Orca to modify the entries in the _Validation table, to match those of the Merge Modules, the errors will no longer appear. The ICE82 warnings referring to ProgramFilesFolder.364... will still appear, but can apparently be ignored. As can the ICE03 warnings relating to string overflows. I'm only new to both building MSIs and using Help2, so I'm far from an authority on either, just wanted to pass on the little that I had learned along the way. Some other notes: I have a WiX node that looks like Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; xmlns:vs=http://schemas.microsoft.com/wix/VSExtension; And the HelpFile node vs:HelpFile Id=someHxSFile Name=nameAsPerHxtUrl / As indicated, the Name attribute must match the Url attribute in the HelpTOCNode of the HxT file, if not the Table of Contents does not deploy properly (the help will correctly appear in the dexplore Index tab though). I got this wrong initially, novice mistake I'm assuming, and it took me a LONG time to find what was wrong. The MSDN help for HxReg.exe eventually tipped me off to what I'd done wrong. Then the HelpCollection node looks like vs:HelpCollection Id=someHxC Description=some description Name=company.title.1033 vs:HelpFileRef Id=someHxSFile / vs:PlugCollectionInto Attributes=someHxA TableOfContents=someHxT TargetCollection=MS_VSIPCC_v80 TargetTableOfContents=FL_vsipcc_hxt_86880.3643236F_FC70_11D3_A5 36_0090278A1BB8/ /vs:HelpCollection HelpCollection Name is using format as per recommendation in http://msdn2.microsoft.com/en-us/library/bb164959(VS.80).aspx The Attributes attribute is optional, you may not need it depending on how you've authored the help content. I'm assuming than an MST file, in conjunction with MSITRAN.EXE, could be used to correct the ICE03 errors as a post build step (to correct the _Validation table), but I haven't tried yet. http://www.creativedocs.net/blog/archives/32-Patching-the-MSI-file-for-V ista-compliance.html gave me the idea for this. Whilst it would obviously be nice to get an Error and Warning free compile done, it appears there is at least a workaround until the WiX team can get to the issue. Hope this helps Regards Shannon Lewis Systems Architect Runge Limited Value through Planning Ph: (+61 7) 3100 7274 Fax: (+61 7) 3100 7297 www.runge.com http://www.runge.com/ LEGAL NOTICE The information contained in this e-mail, and any attachments to it, are for the use of the intended recipient and are confidential. If you are not the intended recipient, you must not use, commercialise, disclose, read, forward, copy or retain any of the information. If you have received this e-mail in error, please delete it and notify the sender by return e-mail or telephone on +61 7 3100 7200. Runge Limited (ABN 17 010 672 321) does not warrant that any attachments are free from viruses or any other defects. You assume all liability for any loss, damage, or other consequences, which may arise from opening or using the attachments. Unless otherwise expressly stated by an authorized representative of Runge Ltd, any views, opinions and other information expressed in this message and any attachments are solely those of the sender and do not constitute formal views or opinions of our firm. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net
[WiX-users] File Reference Syntax
Once again I am struggling badly with wix. I have a file File Id=File_ClientExe Name=StrawberryFields.exe Source=$(var.ClientRoot)$(var.ClientExeName) Checksum=no ReadOnly=yes that I want to use as the target of a verb ProgId Id=StrawberryFields.sbf Description=!(loc.SampleDescStr2) Extension Id=sbf ContentType=application/sbf Verb Id='open' Command='Open' TargetFile='[!File_ClientExe]' Argument='%1' / /Extension /ProgId What is wrong with my use of File_ClientExe? Error 25 Unresolved reference to symbol 'File:[#File_ClientExe]' in section 'Fragment:'. D:\Home\Development\StrawberryFields\InstallationKit\StrawberryFieldsInstaller\Client.wxs 24 1 StrawberryFieldsInstaller I have tried the usual sequence of '[!File_ClientExe]' '[#File_ClientExe]' '[File_ClientExe]' '!File_ClientExe' etc - which never works Can someone please point me to the complete language syntax and scope rules BTW in the documentation for Wix - it describes using Wix as a mind set change - where your installer should be written in parallel with your development. I would say that the same goes for documentation. I am afraid that to date the last couple of weeks of using Wix has been the most depressing and frustrating experience in a quarter of a century of coding. The years of effort that have gone into this thing which should be a poster child is totally let down by inadequate documentation, lack of examples etc. So as a word of advice - Stop all development now and work on the documentation. If all the words that have been typed into this forum had been typed into a wiki the job would have been done long ago. As it is the same people are repeating the same answers to the same questions to the point that they cant be bothered providing answers that people can understand. Once you have an up to date and complete language definition and a full set of examples - then by all means respond to queries with Its in the Wix 3 chm - but at the moment I've looked - and I cant find it - and if I can find it I can't understand it. Sorry about the venting. Now can someone tell me how to refer to a file by its id -- View this message in context: http://www.nabble.com/File-Reference-Syntax-tf4762398.html#a13620533 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Advertised feature install starting
John Hall wrote: It's an HKCU registry key that would have been created for the user who installed the application, but obviously not the user who is running. Is this the default behaviour for a key in HKCU even if the feature is not advertised? Yes, for an advertised shortcut. Also, is this the expected behaviour? I thought that a copy of the MSI was stored away in c:\Windows\Installer, so why is the system not able to use that one rather than looking for the original .msi file that the bootstrapper dropped into the temp directory. It does but something's requiring source. You can set the MSI logging policy to get a verbose log when the repair is triggered. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom actions as executables
Dror Cohen wrote: I want my MSI to run in a custom action an executable that I want to add into the package but not stay on the user's machine. This executable might also be dependent on files (DLLs) that will be installed on the machine. What is the easiest way to achieve that? MSI doesn't have support for an embedded CA that relies on installed DLLs. Either live with the file staying behind or remove the dependencies. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Chaining a redist package into an MSI
Karesz Kecskemeti wrote: My issue is that I try to build an MSI, and it has a third party redist package inside it. This redist package has to be installed as part of my MSI installation. I believe this can be done by creating a custom action to execute this package. The problem is that this redist package is actually another MSI that was compiled into a .exe, and I have no idea what kind of problems this can bring up. MSI doesn't support installing multiple MSI packages in one transaction. You need to use a bootstrapper. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Upgrading
Craig0ss wrote: What about a component search, if it finds the product it fills the keypath?? Should work. I've never tried it. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Subclassing WIX dialogs
Lewis G. Pringle, Jr. wrote: Are there any plans (maybe in Wix v3?) to include an ability to do some sort of limited 'dialog subclassing'? where perhaps you could just add a control? It's not supported now; it might be possible, similar to how WiX v3 implements floating Publish elements that let you define control events outside the dialog. Feel free to file a feature request. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] upgrade and 3 field version numbers
Hi, I ran in some issue with upgrades, and when I checked the logs, I found that the version numbers were 4 fields ( 1.0.0.1 ). MSDN tells me that it will ignore the 4th part, so I have changed my version to 1.0.1, which works. The problem is I show my product version (in about box) based on my .net assembly version, which has 4 fields, but for MSI, I use 3 fields, so Add/remove shows 3 fields. I would like to know why MSI doesn't support 4 field versions. Any best practices for versioning? Thanks, Nitin - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
