Re: [WiX-users] Silent Custom Installation
Hi, Your C code is fundamentally wrong. You need to get target dir from MSI db, and check for free space only on it, for example To get - set MSI property use MSI API calls, like MsiSetProperty() or MsiGetProperty(). For example of implementing the DLL for custom actions, read through this tutorial: http://www.codeproject.com/install/msicustomaction.asp - there you can download sources as well. Keep wix-users list in recipients please. Best regards Albert _ From: Guna S [mailto:[EMAIL PROTECTED] Sent: Friday, October 26, 2007 7:49 AM To: Albert Tuulas Subject: Re: Silent Custom Installation Hi, Please find attached a C prg to find out the disk space. If you dont mind,Could you please modify the same into custom action(C++ DLL). Also the you mention , and if there's not enough of it, change TARGETDIR or INSTALLDIR MSI variables. Could you tell me how to do it. with lotmany thanks, Guna S On 10/25/07, Albert Tuulas [EMAIL PROTECTED] wrote: Rough idea is in my previous email :-) _ From: Guna S [mailto:[EMAIL PROTECTED] Sent: Thursday, October 25, 2007 7:53 AM To: Albert Tuulas Subject: Re: Silent Custom Installation Hi, Thanks for you reply. If you dont mind could you give me the rough idea/code which implements this. thanks inadvance Guna S On 10/24/07, Albert Tuulas [EMAIL PROTECTED] wrote: You can implement it as a custom action (C++ DLL) which checks for reasonable amount of space on system disk, and if there's not enough of it, change TARGETDIR or INSTALLDIR MSI variables. -Original Message- From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ] Sent: Wednesday, October 24, 2007 8:36 AM To: [EMAIL PROTECTED] Subject: Re: Silent Custom Installation Hi, am very new to this installer. My requirement is If space is not available on default loc ie C drive, In case of UI installation user can change the path. No issues. But in case of Silent Installation, because there is no UI, it should select another disk which is available automatically and install there I want both in same file, ie user can go any way. Can you tell me how to implement this. Thanks, Albert Tuulas-3 wrote: I meant something similar to this: Feature Id=Feat1 Title=Feat1 Feature Id=Feat11 Title=Feat11 Level=1 Condition Level=1ADDLOCAL ~= Feat1/Condition /Feature ~= means case-insensitive comparison. Also you can check Check that link: http://msdn2.microsoft.com/en-us/library/aa368012.aspx Substring Operators I've an idea that the ADDLOCAL property can be modified by a custom action: CustomAction Id=CA1 Execute=immediate Property=ADDLOCAL Value=Feat1,Feat11 / And schedule it like that: Custom Action=CA1 Before=CostInitialize![CDATA[Feat1=3]]/Custom To make it running earlier. Although I didn't try any of these by myself, can't tell is it really working. Best regards Albert _ From: Srinivas Tirupati [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 10, 2007 2:42 PM To: Albert Tuulas Subject: RE: [WiX-users] Silent Custom Installation Hi Albert I am very new to this WIX ... I know about this Condition statement in feature tag but I didn't get how we can use this statement for this purpose ?? My purpose here is that the person installing my product should be able to install all the child features by just specifying the parent feature name. Can you briefly explain how I can do this using condition statement in Feature tag ?? Thanks and Regards, Srinivas T From: Albert Tuulas [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 10, 2007 5:00 PM To: Srinivas Tirupati Subject: RE: [WiX-users] Silent Custom Installation I got it, but there's a possibility to set Condition tag inside a feature, and having there attribute (Level=1) marks feature to be installed if condition evaluates to True. Hope it makes sense. _ From: Srinivas Tirupati [mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ] Sent: Tuesday, July 10, 2007 2:25 PM To: Albert Tuulas Subject: RE: [WiX-users] Silent Custom Installation Level=1 for all my features From: Albert Tuulas [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 10, 2007 4:31 PM To: Srinivas Tirupati; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Silent Custom Installation Did you try to play with Condition Level=1 statement inside feature tag? I've got no other ideas :-) _ From: Srinivas Tirupati [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 10, 2007 1:45 PM To: Albert Tuulas; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Silent Custom Installation Yes all features have Level=1 But i found some information from msdn which explains why it didn't install anything :-) (Source :- http://msdn2.microsoft.com/en-us/library/ms144259.aspx) ADDLOCAL Rules: * Feature names
Re: [WiX-users] Wix v3 SQL Error
Christoph Brennecke wrote: Hi, i have created a Wix project in Visual Studio 2005 which, among other things, should create a SQL database, but i'm always getting a compile error with light.exe: Build log: -- Build started: Project: Bit.PowerEconomizer.Setup, Configuration: Debug Any CPU -- C:\Program Files\Windows Installer XML v3\bin\candle.exe -dDebug -dDevEnvDir=C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\\ -dSolutionDir=D:\PowerEconomizer\Bit.PowerEconomizer\ -dSolutionExt=.sln -dSolutionFileName=Bit.PowerEconomizer.sln -dSolutionName=Bit.PowerEconomizer -dSolutionPath=D:\PowerEconomizer\Bit.PowerEconomizer\Bit.PowerEconomizer.sln -out obj\Debug\Bit.PowerEconomizer.Setup.wixobj -ext C:\Program Files\Windows Installer XML v3\bin\WixDifxAppExtension.dll -ext C:\Program Files\Windows Installer XML v3\bin\WixIIsExtension.dll -ext C:\Program Files\Windows Installer XML v3\bin\WixNetFxExtension.dll -ext C:\Program Files\Windows Installer XML v3\bin\WixSqlExtension.dll -ext C:\Program Files\Windows Installer XML v3\bin\WixUIExtension.dll Bit.PowerEconomizer.Setup.wxs C:\Program Files\Windows Installer XML v3\bin\Light.exe -cultures:en-US -ext C:\Program Files\Windows Installer XML v3\bin\WixDifxAppExtension.dll -ext C:\Program Files\Windows Installer XML v3\bin\WixIIsExtension.dll -ext C:\Program Files\Windows Installer XML v3\bin\WixNetFxExtension.dll -ext C:\Program Files\Windows Installer XML v3\bin\WixSqlExtension.dll -ext C:\Program Files\Windows Installer XML v3\bin\WixUIExtension.dll -out D:\PowerEconomizer\Bit.PowerEconomizer\Bit.PowerEconomizer.Setup\bin\Debug\Bit.PowerEconomizer.Setup.msi -v obj\Debug\Bit.PowerEconomizer.Setup.wixobj C:\delivery\Dev\wix\src\ext\sqlextension\wixlib\SqlExtension.wxs(27,0): Error LGHT0094: Unresolved reference to symbol 'Binary:ScaSchedule' in section 'Fragment:'. C:\delivery\Dev\wix\src\ext\sqlextension\wixlib\SqlExtension.wxs(28,0): Error LGHT0094: Unresolved reference to symbol 'Binary:ScaSchedule' in section 'Fragment:'. Done building project Bit.PowerEconomizer.Setup.wixproj -- FAILED. Build FAILED. == Build: 0 succeeded or up-to-date, 1 failed, 0 skipped == I'm using Wix v3.0.2925.0. The SqlDatabase part in my wxs is: Component Id=PowerEconomizerDatabaseComponent Guid=5B2D3457-856F-4505-92F6-87AE0197333B sql:SqlDatabase Id=PowerEconomizerDatabase ConfirmOverwrite=yes CreateOnInstall=yes ContinueOnError=no CreateOnReinstall=no CreateOnUninstall=no Database=PowerEconomizer DropOnInstall=no DropOnReinstall=no DropOnUninstall=yes Instance=SQLEXPRESS Server=localhost sql:SqlFileSpec Id=DatabaseFile Name=PowerEconomizer_mdf Filename=[TARGETDIR]\Data\PowerEconomizer.mdf/ sql:SqlLogFileSpec Id=DatabaseLog Name=PowerEconomizer_ldf Filename=[TARGETDIR]\Data\PowerEconomizer.ldf/ sql:SqlScript Id=PowerEconomizerDatabaseScript BinaryKey=CreateTablesSqlScript ContinueOnError=no ExecuteOnInstall=yes ExecuteOnReinstall=no ExecuteOnUninstall=no RollbackOnInstall=no RollbackOnReinstall=no RollbackOnUninstall=no / /sql:SqlDatabase /Component I tried to get it to work since two days now, but i'm totally stuck. Can anybody help me fixing this? Christoph Brennecke It's a bug in 3.0.2925.0. If you're using WiX v3, I highly recommend getting in a habit of downloading the latest build from http://wix.sourceforge.net/releases regularly (at least, monthly). This bug and a great many more are fixed in a more recent build. We don't update the official release page on SourceForge often (enough) because it is such a painfully manual process. I'll urge Joe (our release guy) to make another push soon. - 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
Re: [WiX-users] uninstall from control pannel does not remove all files
I went through the log file present in the %temp% folder but i am afraid i did not find anything suspicious. i am also putting the part of the log file which i thought could be helpful. Plz advice as an end user amy generally not uninstall the application from the msi .They always tend to uninstallit from control pannel. Part of the log file- Action ended 15:06:14: CostFinalize. Return value 1. MSI (s) (78:60) [15:06:14:918]: Doing action: InstallValidate Action start 15:06:14: InstallValidate. MSI (s) (78:60) [15:06:14:980]: Feature: WaxWebClient; Installed: Absent; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:012]: Feature: Wax; Installed: Local; Request: Absent; Action: Absent MSI (s) (78:60) [15:06:15:027]: Feature: complete; Installed: Local; Request: Absent; Action: Absent MSI (s) (78:60) [15:06:15:043]: Component: InstallConfTool; Installed: Local; Request: Absent; Action: Absent MSI (s) (78:60) [15:06:15:059]: Component: regEntry; Installed: Local; Request: Absent; Action: Absent MSI (s) (78:60) [15:06:15:184]: Component: com; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:200]: Component: SqlComponent; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:215]: Component: Reports; Installed: Local; Request: Absent; Action: Absent MSI (s) (78:60) [15:06:15:215]: Component: Component2; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:231]: Component: Component3; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:231]: Component: Component4; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:247]: Component: Component5; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:247]: Component: Component7; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:262]: Component: Component8; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:262]: Component: Component9; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:278]: Component: Component10; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:278]: Component: Component11; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:294]: Component: Component12; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:294]: Component: Component13; Installed: Null; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:309]: Component: Component14; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:325]: Component: Component15; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:325]: Component: Component16; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:341]: Component: Component17; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:341]: Component: Component18; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:356]: Component: Component19; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:356]: Component: Component20; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:372]: Component: Component21; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:372]: Component: Component22; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:388]: Component: Component23; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:388]: Component: Component24; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:403]: Component: Component25; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:403]: Component: Component26; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:419]: Component: Component27; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:419]: Component: Component28; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:435]: Component: Component29; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:450]: Component: Component30; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:450]: Component: Component31; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:466]: Component: Component32; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:466]: Component: Component33; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:482]: Component: Component34; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:482]: Component: Component35; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:497]: Component: Component36; Installed: Local; Request: Null; Action: Null MSI (s) (78:60) [15:06:15:497]:
Re: [WiX-users] Next official v3 build?
There is no official release schedule for WiX v3. My guess is that we'll be mostly stable by the end of 2008. However, I have to admit I don't see any breaking changes on the horizon and no major features showing up soon. So at this point, every build is just a little bit better than the last. Lots of bug fixing right now (mostly thanks to Peter). However, I do want to get an updated build of WiX v3 on the release share (2925 is really old) and hopefully we can keep that up every third month or so. We just lost our volunteer release manager so our build guy has been filling in... and he's been busy shipping VS 2008 the last month. I'll try to talk him into another official release. smile/ Stefan Kuhr wrote: Hello everyone, I would like to use a version of WiX 3 that supports the new patch creation features as described on Peter Marcu's blog. While I certainly know that I could use a weekly build for that, it would give me much, much more confidence if this feature were available in an official build like the last one, build 2925 as of May 25th 2007. So can anybody tell me if there is a new official build underway in the next few weeks, so it is worth waiting for that? Is there any official release schedule plan for WiX 3 anywhere on the web so I don't have to bother anyone on this list with such a question? 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
[WiX-users] Next official v3 build?
Hello everyone, I would like to use a version of WiX 3 that supports the new patch creation features as described on Peter Marcu's blog. While I certainly know that I could use a weekly build for that, it would give me much, much more confidence if this feature were available in an official build like the last one, build 2925 as of May 25th 2007. So can anybody tell me if there is a new official build underway in the next few weeks, so it is worth waiting for that? Is there any official release schedule plan for WiX 3 anywhere on the web so I don't have to bother anyone on this list with such a question? Thanks, -- Stefan Kuhr -- View this message in context: http://www.nabble.com/Next-official-v3-build--tf4696094.html#a13423576 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] Easy WiX way for a custom action to call multiple utility DLLs?
Rob Mensching-5 wrote: I'm admittedly hardcore about this but IMHO custom actions should be native code DLLs that have as few dependencies as physically possible (certainly should have no dependency on WTL). Statically linking the CRT then use as few DLLs from the system provides the highest probability that the code will work in the most number of environments. Agreed, although I think that Aris was just giving his WTL app as an example of static linking seeming not to work properly, as opposed to actually using WTL within a CA (off the top my head, I can't think when you'd want to do this). It's OT but wrt your WTL prob Aris, might you have missed some other dependency? (Depends.exe v. handy here). Aris Green-2 wrote: Try embedding the other DLL as a custom resource using the .rc file. Extract the DLL first thing when the CA is called. Use delayload linker option or LoadLibrary to call the function in the extracted DLL. I've done this before. Not what I was looking for, but thanks for the tip Aris: I hadn't considered this approach. -- View this message in context: http://www.nabble.com/Easy-WiX-way-for-a-custom-action-to-call-multiple-utility-DLLs--tf4683485.html#a13425076 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] Proposal: Move WiX v3 to CLR 2.0
Today the WiX toolset runs on the .NET Framework 1.1 SP1. The original goal in 2004 was to have the WiX toolset work out of the box on Windows Server 2003 (a very reliable build OS). These days the .NET Framework 2.0 appears to be the framework of choice and I regularly get asked, Why is the WiX toolset still on the 1.1 Framework? I believe that my old answer, The 1.1 Framework is the most prevalent. is probably no longer true and that the 2.0 Framework has taken over. So, I'm wondering if anyone has an real objections to me moving the minimum requirement to run the WiX toolset binaries from .NET Framework 1.1 SP1 to .NET Framework 2.0. I would like to note that a number of tools (Votive, ClickThrough, a couple of the extensions) already require the .NET Framework 2.0 so I'm only really asking about the core toolset. Why is this interesting? Well, I'm told the 2.0 Framework has improved the XML performance. I would like to run some tests to see if that is true but don't want to spend a lot of time investigating that if there is an number of you out there that still need the core toolset to run on the 1.1 Framework. So, I'm looking for people that require the 1.1 SP1 Framework minimum bar to send me your stories. If you already use the 2.0 Framework then just delete this email. Finally, no changes to WiX v2 are being proposed here. the WiX v2 toolset will remain on 1.1 Framework until either of them reach the end of their life. smile/ - 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] Removal of file on uninstall
What file is it? Maybe the windows file protection automatically recovers the file if it is a system file. Best regards, Sebastian Brand Instyler Software - http://www.instyler.com On Oct 25, 2007, at 10:56 PM, Jaguar 36 wrote: Hi, I discovered a weird problem when uninstalling. I had a file in WindowsFolder as well as a file in SystemFolder. Key was set to Permanent=no for both files. On uninstallation, the one in WindowsFolder got removed while the one in SystemFolder did not. I even tried to explicitly remove the file from RemoveFile but it did not work despite the log saying that it did. Thanks for any suggestions! Get your free suite of Windows Live services! Windows Live -- --- 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
Re: [WiX-users] Proposal: Move WiX v3 to CLR 2.0
Personally I'd love to see the build process simplified also. I'm a VS2005/TFS shop... I'd love to be able to throw WiX into TFS and load the PSDK and VS on a build machine and just simply tell it to build the solution without worrying about nant and make bat files and such. Rob Mensching [EMAIL PROTECTED] wrote: Today the WiX toolset runs on the .NET Framework 1.1 SP1. The original goal in 2004 was to have the WiX toolset work out of the box on Windows Server 2003 (a very reliable build OS). These days the .NET Framework 2.0 appears to be the framework of choice and I regularly get asked, Why is the WiX toolset still on the 1.1 Framework? I believe that my old answer, The 1.1 Framework is the most prevalent. is probably no longer true and that the 2.0 Framework has taken over. So, I'm wondering if anyone has an real objections to me moving the minimum requirement to run the WiX toolset binaries from .NET Framework 1.1 SP1 to .NET Framework 2.0. I would like to note that a number of tools (Votive, ClickThrough, a couple of the extensions) already require the .NET Framework 2.0 so I'm only really asking about the core toolset. Why is this interesting? Well, I'm told the 2.0 Framework has improved the XML performance. I would like to run some tests to see if that is true but don't want to spend a lot of time investigating that if there is an number of you out there that still need the core toolset to run on the 1.1 Framework. So, I'm looking for people that require the 1.1 SP1 Framework minimum bar to send me your stories. If you already use the 2.0 Framework then just delete this email. Finally, no changes to WiX v2 are being proposed here. the WiX v2 toolset will remain on 1.1 Framework until either of them reach the end of their life. - 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 __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.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] Removal of file on uninstall
Hi Sebastian, They are .sys files , but I did not set them to be system files in the property. Thanks! CC: wix-users@lists.sourceforge.net From: [EMAIL PROTECTED] Subject: Re: [WiX-users] Removal of file on uninstall Date: Fri, 26 Oct 2007 13:13:09 +0200 To: [EMAIL PROTECTED] What file is it? Maybe the windows file protection automatically recovers the file if it is a system file. Best regards, Sebastian Brand Instyler Software - http://www.instyler.com On Oct 25, 2007, at 10:56 PM, Jaguar 36 wrote: Hi, I discovered a weird problem when uninstalling. I had a file in WindowsFolder as well as a file in SystemFolder. Key was set to Permanent=no for both files. On uninstallation, the one in WindowsFolder got removed while the one in SystemFolder did not. I even tried to explicitly remove the file from RemoveFile but it did not work despite the log saying that it did. Thanks for any suggestions! Get your free suite of Windows Live services! Windows Live --- --- --- 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 _ Manage multiple email accounts with Windows Live Mail! http://www.get.live.com/wl/all- 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] What's the right way to use InstallExecuteSequence from a fragment?
Hello, This may be a misunderstanding of how WiX is supposed to work. Basically... I have a Fragment file, InstallExecuteSequence.wxs, that contains only an InstallExecuteSequence node: InstallExecuteSequence Custom Action=SetProp1 Sequence=10/ /InstallExecuteSequence My problem is that this sequence doesn't by default get included within anything I build. E.g.: candle InstallExecuteSequence.wxs candle SequenceTest.wxs (= generated by Votive, with an appropriate CustomAction Id=SetProp1 ... node). light -out test.msi InstallExecuteSequence.wixobj SequenceTest.wixobj + look at test.msi in orca = InstallExecuteSequence table doesn't contain the SetProp1 CA. The workaround is easy enough: stick a dummy CustomAction inside InstallExecuteSequence.wxs and a matching CustomActionRef in SequenceTest.wxs, but does anyone know the proper way to get InstallExecuteSequence.wixobj linked into test.msi, or am I missing something..? thanks for any help, Karim -- View this message in context: http://www.nabble.com/What%27s-the-right-way-to-use-InstallExecuteSequence-from-a-fragment--tf4698457.html#a13431009 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] What's the right way to use InstallExecuteSequence from a fragment?
If it is related to some UI things, an adequate UiRef element could help you to include it clearly. 2007/10/26, Karim MacDonald [EMAIL PROTECTED]: Hello, This may be a misunderstanding of how WiX is supposed to work. Basically... I have a Fragment file, InstallExecuteSequence.wxs, that contains only an InstallExecuteSequence node: InstallExecuteSequence Custom Action=SetProp1 Sequence=10/ /InstallExecuteSequence My problem is that this sequence doesn't by default get included within anything I build. E.g.: candle InstallExecuteSequence.wxs candle SequenceTest.wxs (= generated by Votive, with an appropriate CustomAction Id=SetProp1 ... node). light -out test.msi InstallExecuteSequence.wixobj SequenceTest.wixobj + look at test.msi in orca = InstallExecuteSequence table doesn't contain the SetProp1 CA. The workaround is easy enough: stick a dummy CustomAction inside InstallExecuteSequence.wxs and a matching CustomActionRef in SequenceTest.wxs, but does anyone know the proper way to get InstallExecuteSequence.wixobj linked into test.msi, or am I missing something..? thanks for any help, Karim -- View this message in context: http://www.nabble.com/What%27s-the-right-way-to-use-InstallExecuteSequence-from-a-fragment--tf4698457.html#a13431009 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 - 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] MMC Snapin
I added the xmlns, but what's the name of the extension itself? The documentation does not mention that. Thanks! -Original Message- From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Thursday, October 25, 2007 19:57 To: Levon Levonian Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] MMC Snapin There is an extension in WiX v3 that handles much of the authoring work for you. Levon Levonian wrote: Hi All, Is there a (easy) way to deploy an MMC Snap-in? - 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] Controls not displaying w/ bkgrd bitmaps-workaround
Is this a know issue that when you set a background bitmap on the dialog, controls like push buttons, radio and check boxes don't show up until you hover over with the mouse? Also in this case it shows the controls like check boxes with the standard gray color, setting the transparent property doesn't help in this case either. I am having this issue with both WiX 2.0 and 3.0. Is there a workaround this? Is there someway I can set the background color or something to get around this issue? Or has someone ever done a hack into the windows installer itself for resolving UI issues? Thanks, Jacob - 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] Controls not displaying w/ bkgrd bitmaps-workaround
This is a known behavior of the Windows Installer (which means WiX version matters very little). There are discussions in the archive about various ways to work around the issue, none of which are perfect. I think the closest to perfect is to create an External UI handler (which is a boatload of work). Sajo Jacob wrote: Is this a know issue that when you set a background bitmap on the dialog, controls like push buttons, radio and check boxes don't show up until you hover over with the mouse? Also in this case it shows the controls like check boxes with the standard gray color, setting the transparent property doesn't help in this case either. I am having this issue with both WiX 2.0 and 3.0. Is there a workaround this? Is there someway I can set the background color or something to get around this issue? Or has someone ever done a hack into the windows installer itself for resolving UI issues? Thanks, Jacob - 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
Re: [WiX-users] Problems with copy file
Even with all this I'm not really sure what I need to do to make this work. I have multiple wix files that need to know PATH/temp. But the user only enters PATH. Not sure how I'm going to make a Dir element out of PATH. -Mike -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sent: Saturday, October 20, 2007 8:29 AM To: WiX Users Subject: Re: [WiX-users] Problems with copy file In article [EMAIL PROTECTED], Jeremy Farrell [EMAIL PROTECTED] writes: In article [EMAIL PROTECTED], Jeremy Farrell [EMAIL PROTECTED] writes: Then, assuming the documentation's correct, it needs to be set to a property which contains the required path as the doc says. In DestinationProperty=PATH which works, you've set it to the name of the property called PATH which contains a pathname. You need to create a property which contains a string giving the required path, and give the name of that property to DestinationProperty. Its not a property he needs to create, its a row in the Directory table (primary keys in the directory table are also mirrored as properties containing the resolved path, but just creating a property is not sufficient). That means the WiX help file is as wrong as it could be about this then, despite being clear and explicit - and how come DestinationProperty=PATH works? Are you sure you aren't thinking of DestinationDirectory rather than DestinationProperty? Windows Installer uses a property to identify the destination. Every entry in the Directory table gets a property to go with it. So by defining an entry in the Directory table you also get a property. You could just use a property separate from the Directory table as well. But either way you can't specy DestinationProperty or DestinationDirectory as formatted text that will resolve to the desired path. -- 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 - 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] MMC Snapin
OK, I got the extension name, but: None of the WiX v3 packages contains WixMMCExtension, I only found it in v2, but v3 does not load v2 extensions (Error The extension 'C:\Program Files\Windows Installer XML v3\bin\WixMMCExtension.dll' could not be loaded.candle.exe) Anybody has a working example for Snap-in deployment? Thanks! -Original Message- From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Thursday, October 25, 2007 19:57 To: Levon Levonian Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] MMC Snapin There is an extension in WiX v3 that handles much of the authoring work for you. Levon Levonian wrote: Hi All, Is there a (easy) way to deploy an MMC Snap-in? ** READER BEWARE: Unencrypted, unsigned Internet e-mail is inherently insecure. Internet messages may be corrupted, incomplete, misdirected or may incorrectly identify the sender. Therefore, nothing in this message or attachments may be considered legally binding. THIS MESSAGE IS ONLY INTENDED FOR THE USE OF THE INDIVIDUAL OR ENTITY TO WHICH IT IS ADDRESSED AND MAY BE PRIVILEGED. If you are not the intended recipient or their authorized agent, you may not forward or copy this information and must delete or destroy all copies of this message and attachments received. If you have received this communication in error, please notify Matrikon Inc. by telephone at (780) 448-1010. ** - 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] Problem in WixVariable for WixUIUpIco and WixUINewIco variables
I am using the following the in my wix project to display the custom banner and dialog bmps as well as the the icons and the License file. Everything works fine, except the .ico files. None of the .ico files show up in the UI when I build it and run the installer. The .ico files are right size. I have tried placing these files in WiX binaries folder (where candle/light sits) as well as in the location where all other .wxs files and bmps are, but no cigar. Am I missing anything? Do I need to put these files in some other location? Also, I have tried use hard coded path to these .ico files, but it does not work. Note that the bmps and the license show up fine. Any suggestions? Thanks UIRef Id=WixUI_Mondo/ UIRef Id=WixUI_ErrorProgressText / WixVariable Id=WixUILicenseRtf Value=License.rtf/ WixVariable Id=WixUIDialogBmp Value=dlgbmp.bmp/ WixVariable Id=WixUIBannerBmp Value=bannrbmp.bmp/ WixVariable Id=WixUIExclamationIco Value=exclamic.ico/ WixVariable Id=WixUIInfoIco Value=info.ico/ WixVariable Id=WixUINewIco Value=new.ico/ WixVariable Id=WixUIUpIco Value=Up.ico/ _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ - 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
