[WiX-users] help! How do I launch a file upon install ?
Hello folks.. I've looked at http://wixtoolset.org/documentation/manual/v3/howtos/ui_and_localization/run_program_after_install.html to see the proper way to launch an exe that I'm installing after the user clicks the finish button. I've used the minimal gui, but added it as a reference by right-clicking the references in the wix project in visual studio, so I don't have a UI UIRef Id=WixUI_Minimal / /UI element in my wxs file. So where do I add this code ? Publish Dialog=ExitDialog Control=Finish Event=DoAction Value=LaunchApplicationWIXUI_EXITDIALOGOPTIONALCHECKBOX = 1 and NOT Installed/Publish The tutorial suggest I add it anywhere in the UI element, but as I've added the UI element as a reference through visual studio, I don't have it in my wxs file! Would really appreciate someone's help on this as I've been stuck here for quite some time, and I'm very new to wix ! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/help-How-do-I-launch-a-file-upon-install-tp7588736.html Sent from the wix-users mailing list archive at Nabble.com. -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Shortcut not being deleted
Separate shortcut from the component. like this: https://github.com/krab/vacuum-im-wix-installer/blob/master/Product.wxs#L20 https://github.com/krab/vacuum-im-wix-installer/blob/master/Files.wxs#L54 2013/9/4 Natalie Carr natalie.c...@measuresoft.com Hi I have this code for a shortcut. This setup is an add on for my main product so the code adds a shortcut to the shortcuts already installed on the target machine. On uninstall however the add on shortcut is never removed, can anyone see what I am doing wrong? Component Id=PIDShortcut Guid=696E79B3-D417-4352-9CEE-378DEECD9295 Directory=ProgramMenuDir Shortcut Id=PIDShortcut Directory=ProgramMenuDir Name=PID Controller Icon=pid_cf.exe IconIndex=0 Target=[BIN]pid_cf.exe Icon Id=pid_cf.exe SourceFile=E:\Products\Measuresoft_SCADA\Processors\PID_Controller\Sources\ PID_CF\res\pid_cf.ico/ ShortcutProperty Key=System.AppUserModel.ExcludeFromShowInNewInstall Value=1/ /Shortcut RemoveFolder Id='ProgramMenuDir' On='uninstall'/ RegistryValue Root='HKCU' Key='Software\ShortcutProperty\[PRODUCTNAME]' Type='string' Value='1' KeyPath='yes' Name='PIDShortcut'/ /Component Thanks -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Search and Read properties of ComPlusApplication
Hi, During patch install is there a way for msp to search and read properties of ComPlusApplication similar to how we use RegistrySearch element in wix? I need to read identity and Password properties of an existing complus application during the patch install so that I can pass them back when com+ application is re-installed. Thanks, Swaroop This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which it is addressed and may contain information which is privileged, confidential or prohibited from disclosure or unauthorised use. You are hereby notified that any use, any form of reproduction, dissemination, copying, disclosure, modification, distribution and/or publication of this e-mail message or its attachments other than by it's intended recipient is strictly prohibited by the sender. If you have received this email in error, please notify the system manager by email at ad...@ifdspercana.com Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, this email has been scanned for the presence of viruses. The recipient should also check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email __ IFDS Percana Group Limited, no. 307152, is registered in Ireland at 16 Joyce Way, Park West Business Park, Dublin 12, Ireland. Directors: Eugene Larmon, Patrick Concannon, William Slattery, Paul O'Neil (UK), Simon Hudson-Lund (UK) and Stephen Parkinson (UK) IFDS Percana International Managed Services Limited, no. 368022, is regulated by the Central Bank of Ireland. Registered in Ireland at 16 Joyce Way, Park West Business Park, Dublin 12, Ireland. IFDS Percana International Managed Services Limited is a wholly owned subsidiary of IFDS Percana Group Limited and provides support services to the life and pensions industry. Directors: Eugene Larmon, Patrick Concannon, Stephen Parkinson (UK) and Paul O'Neil (UK). www.ifdspercana.com __ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com __ -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Launching Bootstrapper executable should only show the internal MSI interface.
Dear All, Launching Bootstrapper executable should only show the internal MSI interface. Not to show any of the Bootstrapper UI. Is this Possible? Any one please help me on this? Thanks in Advance. Anil -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Shortcut not being deleted
Hi, Thank you, done exactly the same and it still is not deleting :( -Original Message- From: Alexey Ivanov [mailto:alexey.iva...@gmail.com] Sent: 04 September 2013 10:50 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Shortcut not being deleted Separate shortcut from the component. like this: https://github.com/krab/vacuum-im-wix-installer/blob/master/Product.wxs#L20 https://github.com/krab/vacuum-im-wix-installer/blob/master/Files.wxs#L54 2013/9/4 Natalie Carr natalie.c...@measuresoft.com Hi I have this code for a shortcut. This setup is an add on for my main product so the code adds a shortcut to the shortcuts already installed on the target machine. On uninstall however the add on shortcut is never removed, can anyone see what I am doing wrong? Component Id=PIDShortcut Guid=696E79B3-D417-4352-9CEE-378DEECD9295 Directory=ProgramMenuDir Shortcut Id=PIDShortcut Directory=ProgramMenuDir Name=PID Controller Icon=pid_cf.exe IconIndex=0 Target=[BIN]pid_cf.exe Icon Id=pid_cf.exe SourceFile=E:\Products\Measuresoft_SCADA\Processors\PID_Controller\So urces\ PID_CF\res\pid_cf.ico/ ShortcutProperty Key=System.AppUserModel.ExcludeFromShowInNewInstall Value=1/ /Shortcut RemoveFolder Id='ProgramMenuDir' On='uninstall'/ RegistryValue Root='HKCU' Key='Software\ShortcutProperty\[PRODUCTNAME]' Type='string' Value='1' KeyPath='yes' Name='PIDShortcut'/ /Component Thanks -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Uninstalling someone else's software during install
Hi, I'm trying to figure out how to uninstall software from another manufacturer as part of installing our software. This is required on Windows XP because of limitations that do not allow our two services to run at the same time. So the idea is to present the user with an information screen describing the problem and presenting the choice of either installing our service or keeping the existing one. At first I thought I could use the method described here http://stackoverflow.com/questions/16429687/how-to-make-a-wix-burn-bundle-that-upgrade-a-lite-version-of-my-product using a custom BA. So the MSI wxs that I wish to install would look something like Product Name='MyProduct' Id='*' UpgradeCode='1-1-1-1-1' ... And my Burn wxs file would be Bundle UpgradeCode='2-2-2-2-2' RelatedBundle Id='3-3-3-3-3' Action='Detect' / ... And in my Custom BA I would look for the other manufacturer's upgrade code in OnPlanRelatedBundle and set the requested state to absent. For some reason the related bundle is never detected, it never appears in the log file and I never seem to receive a callback about it being detected even though it is installed on the system. Using a small program that calls MsiEnumRelatedProducts I'm able to see that the upgrade code is the correct one and that there is a related product installed. Is this the correct way of doing this and if so how do I best troubleshoot this? Is there a better way to do this? -- Bjorn Johansson -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Shortcut not being deleted
msiexec /i yourfile.msi /L*v c:\temp\yourinstall.log or enable in windows by default http://support.microsoft.com/kb/223300/ru 2013/9/4 Natalie Carr natalie.c...@measuresoft.com Hi, Thank you, done exactly the same and it still is not deleting :( -Original Message- From: Alexey Ivanov [mailto:alexey.iva...@gmail.com] Sent: 04 September 2013 10:50 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Shortcut not being deleted Separate shortcut from the component. like this: https://github.com/krab/vacuum-im-wix-installer/blob/master/Product.wxs#L20 https://github.com/krab/vacuum-im-wix-installer/blob/master/Files.wxs#L54 2013/9/4 Natalie Carr natalie.c...@measuresoft.com Hi I have this code for a shortcut. This setup is an add on for my main product so the code adds a shortcut to the shortcuts already installed on the target machine. On uninstall however the add on shortcut is never removed, can anyone see what I am doing wrong? Component Id=PIDShortcut Guid=696E79B3-D417-4352-9CEE-378DEECD9295 Directory=ProgramMenuDir Shortcut Id=PIDShortcut Directory=ProgramMenuDir Name=PID Controller Icon=pid_cf.exe IconIndex=0 Target=[BIN]pid_cf.exe Icon Id=pid_cf.exe SourceFile=E:\Products\Measuresoft_SCADA\Processors\PID_Controller\So urces\ PID_CF\res\pid_cf.ico/ ShortcutProperty Key=System.AppUserModel.ExcludeFromShowInNewInstall Value=1/ /Shortcut RemoveFolder Id='ProgramMenuDir' On='uninstall'/ RegistryValue Root='HKCU' Key='Software\ShortcutProperty\[PRODUCTNAME]' Type='string' Value='1' KeyPath='yes' Name='PIDShortcut'/ /Component Thanks -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Shortcut not being deleted
oops http://support.microsoft.com/kb/223300 2013/9/4 Alexey Ivanov alexey.iva...@gmail.com msiexec /i yourfile.msi /L*v c:\temp\yourinstall.log or enable in windows by default http://support.microsoft.com/kb/223300/ru 2013/9/4 Natalie Carr natalie.c...@measuresoft.com Hi, Thank you, done exactly the same and it still is not deleting :( -Original Message- From: Alexey Ivanov [mailto:alexey.iva...@gmail.com] Sent: 04 September 2013 10:50 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Shortcut not being deleted Separate shortcut from the component. like this: https://github.com/krab/vacuum-im-wix-installer/blob/master/Product.wxs#L20 https://github.com/krab/vacuum-im-wix-installer/blob/master/Files.wxs#L54 2013/9/4 Natalie Carr natalie.c...@measuresoft.com Hi I have this code for a shortcut. This setup is an add on for my main product so the code adds a shortcut to the shortcuts already installed on the target machine. On uninstall however the add on shortcut is never removed, can anyone see what I am doing wrong? Component Id=PIDShortcut Guid=696E79B3-D417-4352-9CEE-378DEECD9295 Directory=ProgramMenuDir Shortcut Id=PIDShortcut Directory=ProgramMenuDir Name=PID Controller Icon=pid_cf.exe IconIndex=0 Target=[BIN]pid_cf.exe Icon Id=pid_cf.exe SourceFile=E:\Products\Measuresoft_SCADA\Processors\PID_Controller\So urces\ PID_CF\res\pid_cf.ico/ ShortcutProperty Key=System.AppUserModel.ExcludeFromShowInNewInstall Value=1/ /Shortcut RemoveFolder Id='ProgramMenuDir' On='uninstall'/ RegistryValue Root='HKCU' Key='Software\ShortcutProperty\[PRODUCTNAME]' Type='string' Value='1' KeyPath='yes' Name='PIDShortcut'/ /Component Thanks -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Launching Bootstrapper executable should only show the internal MSI interface.
Dear All, Launching Bootstrapper executable should only show the internal MSI interface. Not to show any of the Bootstrapper UI. Is this Possible? Any one please help me on this? Thanks in Advance. Anil -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] help! How do I launch a file upon install ?
If you follow the example on that web url it should work for you... You can just add the: !-- Step 2: Add UI to your installer / Step 4: Trigger the custom action -- UI UIRef Id=WixUI_Minimal / Publish Dialog=ExitDialog Control=Finish Event=DoAction Value=LaunchApplicationWIXUI_EXITDIALOGOPTIONALCHECKBOX = 1 and NOT Installed/Publish /UI That must be within your Product element... Follow the example and it should work :) Steve -Original Message- From: nkshirsagar [mailto:nkshirsa...@gmail.com] Sent: September-04-13 2:28 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] help! How do I launch a file upon install ? Hello folks.. I've looked at http://wixtoolset.org/documentation/manual/v3/howtos/ui_and_localization/run_program_after_install.html to see the proper way to launch an exe that I'm installing after the user clicks the finish button. I've used the minimal gui, but added it as a reference by right-clicking the references in the wix project in visual studio, so I don't have a UI UIRef Id=WixUI_Minimal / /UI element in my wxs file. So where do I add this code ? Publish Dialog=ExitDialog Control=Finish Event=DoAction Value=LaunchApplicationWIXUI_EXITDIALOGOPTIONALCHECKBOX = 1 and NOT Installed/Publish The tutorial suggest I add it anywhere in the UI element, but as I've added the UI element as a reference through visual studio, I don't have it in my wxs file! Would really appreciate someone's help on this as I've been stuck here for quite some time, and I'm very new to wix ! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/help-How-do-I-launch-a-file-upon-install-tp7588736.html Sent from the wix-users mailing list archive at Nabble.com. -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Shortcut not being deleted
Hi I have this code for a shortcut. This setup is an add on for my main product so the code adds a shortcut to the shortcuts already installed on the target machine. On uninstall however the add on shortcut is never removed, can anyone see what I am doing wrong? Component Id=PIDShortcut Guid=696E79B3-D417-4352-9CEE-378DEECD9295 Directory=ProgramMenuDir Shortcut Id=PIDShortcut Directory=ProgramMenuDir Name=PID Controller Icon=pid_cf.exe IconIndex=0 Target=[BIN]pid_cf.exe Icon Id=pid_cf.exe SourceFile=E:\Products\Measuresoft_SCADA\Processors\PID_Controller\Sources\ PID_CF\res\pid_cf.ico/ ShortcutProperty Key=System.AppUserModel.ExcludeFromShowInNewInstall Value=1/ /Shortcut RemoveFolder Id='ProgramMenuDir' On='uninstall'/ RegistryValue Root='HKCU' Key='Software\ShortcutProperty\[PRODUCTNAME]' Type='string' Value='1' KeyPath='yes' Name='PIDShortcut'/ /Component Thanks -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Launching Bootstrapper executable should only show the internal MSI interface.
Binging wix custom bootstrapper application tutorial gives this: http://bryanpjohnston.com/2012/09/28/custom-wix-managed-bootstrapper-application/ It's a lot of work just to get rid of the bootstrapper UI, but...that's how it is, unfortunately. I decided to circumvent my problem rather than deal with that, so you may also want to consider alternatives. Hopefully forthcoming versions of WiX will make UI customisation easier. -Original Message- From: ak m [mailto:wixak...@gmail.com] Sent: Wednesday, September 4, 2013 10:57 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Launching Bootstrapper executable should only show the internal MSI interface. Could you please give the solution for this? On Wed, Sep 4, 2013 at 7:01 PM, Rob Mensching r...@robmensching.com wrote: Yes. You need a custom BA. On Wed, Sep 4, 2013 at 3:49 AM, ak m wixak...@gmail.com wrote: Dear All, Launching Bootstrapper executable should only show the internal MSI interface. Not to show any of the Bootstrapper UI. Is this Possible? Any one please help me on this? Thanks in Advance. Anil -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Launching Bootstrapper executable should only show the internal MSI interface.
Could you please give the solution for this? On Wed, Sep 4, 2013 at 7:01 PM, Rob Mensching r...@robmensching.com wrote: Yes. You need a custom BA. On Wed, Sep 4, 2013 at 3:49 AM, ak m wixak...@gmail.com wrote: Dear All, Launching Bootstrapper executable should only show the internal MSI interface. Not to show any of the Bootstrapper UI. Is this Possible? Any one please help me on this? Thanks in Advance. Anil -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] FileSearch issues
It will work only during first install, as Rob most likely knows. During repair, feature change, and uninstall the SourceDir location is (IIRC) the installer directory of the cached MSI file. It's not good design to rely on external files in the same location as the MSI. There are too many failure points, as just mentioned. Also, Group Policy and web installs don't work, and a simple mistake in staging the MSI file and the external file to the install source changes the install logic, and that probably can't be corrected later. If there is really a need for an optional external file it would be better to have it in the binary table or have the data as properties, and give customers a tool to add the file (or the data) if necessary. Or change the design. Phil Wilson On Wed, Sep 4, 2013 at 7:15 AM, Kai Peters kpet...@otaksoft.com wrote: Phil, your sample code works for me as well. Off to see where mine is different... On Mon, 2 Sep 2013 10:25:03 -0700, Phil Wilson wrote: My dumb search works just fine - I can't see what the issue is. This works for me: Sample.msi and thing.txt in the same directory. Property Id=FILEEXISTS Secure=yes DirectorySearch Id=CheckFileDir Path=[SourceDir] Depth=0 FileSearch Id=CheckFile Name=thing.txt / /DirectorySearch /Property and a custom action in the execute sequence to display the value... CustomAction Id=Msg Script=vbscriptmsgbox session.property(FILEEXISTS)/CustomAction The custom action correctly shows the file path, and a log of the install shows: MSI (c) (28:38) [10:13:38:811]: PROPERTY CHANGE: Adding FILEEXISTS property. Its value is 'C:\Phil\MyDD\WiX Samples\thing.txt'. So it does all work. I don't think an actual example with SourceDir was ever posted for a sanity check, but this is how to do it. Phil Wilson On Mon, Sep 2, 2013 at 9:19 AM, Edwin Castro 0ptikgh...@gmx.us wrote: I searched for WiX FileSearch in same directory as MSI on google. The first hit [1] I received [2] includes a reply from Phil Wilson suggesting the SourceDir [3] or OriginalDatabase [4] (with some additional parsing) might work. [1] http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-get-the-current-directory- of-msi-is-running-from-td3058873.html [2] I find it frustrating that different people can receive different results. *sigh* [3] http://msdn.microsoft.com/en-us/library/aa371857.aspx [4] http://msdn.microsoft.com/en- us/library/aa370562.aspx -- Edwin G. Castro On 8/31/13 10:21 AM, Kai Peters wrote: Hi Edwin, no need to be suspicious of Depth and AssignToProperty (firstly, omitting them didn't improve things, nor did I expect it to) as Depth can avoid unnecessary file system traversal (don't know how deep the search would go if no Depth is specified but would assume that default should be 0); AssignToProperty seems redundant to me as I would always expect the innermost element of a nested search to be assigned - but I just put it in here to make things absolutely clear. As I wrote (though not put in my example code) BOTH absolute and variable path specifications fail - I would never use absolute paths in production. The idea behind this search is simply that our customers' IT people could place a configuration file template beside our MSI and that during MSI execution this template would be copied into its destination. Since I cannot know from where IT will deploy our MSIs, I have to figure it out on the fly... And it's still failing - son if someone has an idea for me to look at, I'd appreciate it Thanks, Kai On Thu, 29 Aug 2013 13:47:19 -0700, Edwin Castro wrote: I'm highly suspect of the values for the Path, Depth and AssignToProperty attributes in your DirectorySearch. The example sent by John Cooper, replicated below for convenience, didn't set AssignToProperty=no nor Depth=0. Fragment PropertyRef Id=INSTALLLOCATION / Property Id=WEB_CONFIG_PATH Secure=yes DirectorySearch Id=InstallLocationSearch Path=[INSTALLLOCATION] DirectorySearch Id=WebFolderSearch Path=Web DirectorySearch Id=ContractFolderSearch Path=2008 DirectorySearch Id=WebHostFolderSearch Path=ProductName FileSearch Id=WebConfigFileSearch Name=Web.config / /DirectorySearch /DirectorySearch /DirectorySearch /DirectorySearch /Property /Fragment The Path value in your example is hard coded and that seems wrong to me. Even if you can guarantee that the MSI will ALWAYS reside at that location I believe that caching by Windows Installer will cause problems for you. My vague memory tells me that others have attempted this and couldn't reliably determine where the MSI was located in other to find a companion file located in the same directory. An obvious workaround is to provide the path to the companion file via a public
Re: [WiX-users] Add install InstallScopeDlg to WixUI_InstallDir.wxs
I think that's 4 reasons. :) I am trying to make an installer that replaces the VS2010 Setup Project installer, as stated in my first post, and it allows one to set the path and offers both the per-user/per-machine install on the same dialog. So does anyone know how wix differs from VS2010 setup project for the per-user vs. per-machine install choice? Are they equivalent? I have spent a bit of time to make my wix dialog look like the setup project version, but now the functionality seems totally wonky, as no matter what the user puts into their path, this per-user setup will change the path to something different. Ar! On Fri, 2013-08-30 at 20:24 +, John Cooper wrote: Well conceptually, you don't need the InstallDir dialog if you're installing perUser as it's always going into the LocalAppData tree anyway. It's a pretty straight forward translation of WixUI_Advanced. Even the somewhat troublesome custom actions could be moved to another file since they run scheduled in both the Execute and UI sequences. About two hours of work and most of it to verify functionality. No, I don't have ready-made source for you. I've modified FeatureTree, Mondo, and InstallDir extensively, but I've never done. Advanced. Two reasons: 1) management wants compatibility with Windows Installer Service 4.5 and the ability to install on late service packs of XP and Server 2003 (with Windows Installer Service 4.5 installed on them); 2) management wants 100% visibility of all installed products on all machines by one account; 3) management wants patching and upgrading to behave in the same manner (e.g., under one account); and 4) management wants GPO deployability. Just because software has a capability doesn't mean it should be used. There should be a business justification for it. -- John Merryweather Cooper Build Install Engineer -- ESA Jack Henry Associates, Inc.(r) Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: jo...@msli.com [mailto:jo...@msli.com] Sent: Friday, August 30, 2013 2:16 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Add install InstallScopeDlg to WixUI_InstallDir.wxs Thank you for your concern, but Yes, I do want the per-user/per-machine choice in my installer. - Only clients Windows 7 or higher are to be supported. - I only perform major upgrades. - The Setup Project msi allows this choice and thats what I'm replacing, so it must also offer the choice. Have you a WixUI_*.xml that adds to WixUI_InstallDir.wxs a per-user/per-machine choice? On Fri, 2013-08-30 at 18:18 +, John Cooper wrote: Although being able to specify perUser or perMachine is superficially very appealing, it has significant implications for patching and upgrading that are unacceptable in many deployment scenarios. Make sure you're will to live with ALL of those implications. In my experience, too many products are deployed perMachine, but network administrators have certain expectations about who can patch and upgrade across a network or over a farm that perUser breaks (in particular, there's a nearly universal expectation that they can see all installed products from an appropriately permissioned user). Also, I believe this is only really going to work if you limited yourself to installing on Windows Installer Service 5.0 or later. Will that work for you? For example, that will totally cut out support for XP and Server 2003. -- John Merryweather Cooper Build Install Engineer -- ESA Jack Henry Associates, Inc.(r) Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: jo...@msli.com [mailto:jo...@msli.com] Sent: Friday, August 30, 2013 12:59 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Add install InstallScopeDlg to WixUI_InstallDir.wxs Hay anyone modified WixUI_InstallDir.wxs to enable a per-user vs. per-machine install? I really like the flow of WixUI_InstallDir, but I need to add an install scope (per-user vs per-machine), to make it more like the old VS Setup Project. I am trying to take pars of WixUI_Advanced.wxs and add them to a copy of WixUI_InstallDir.wxs, but before I go too deep, I'm wondering if anyone else has done this, or is there a better way? NOTICE: This email may contain confidential information. Please see http://www.meyersound.com/confidential/ for our complete policy. -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of
Re: [WiX-users] Shortcut not being deleted
RemoveFolder doesn't remove the folder if it contains files. It's possible
that you need to explicitly use RemoveFile to delete the shortcut, maybe in
conjunction with RemoveFolder. Also, it wouldn't hurt to verify that the
component associated with the RemoveFolder/RemoveFile is actually being
removed (in case it's shared, permanent).
Phil Wilson
On Wed, Sep 4, 2013 at 5:23 AM, Alexey Ivanov alexey.iva...@gmail.comwrote:
oops http://support.microsoft.com/kb/223300
2013/9/4 Alexey Ivanov alexey.iva...@gmail.com
msiexec /i yourfile.msi /L*v c:\temp\yourinstall.log
or enable in windows by default
http://support.microsoft.com/kb/223300/ru
2013/9/4 Natalie Carr natalie.c...@measuresoft.com
Hi,
Thank you, done exactly the same and it still is not deleting :(
-Original Message-
From: Alexey Ivanov [mailto:alexey.iva...@gmail.com]
Sent: 04 September 2013 10:50
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Shortcut not being deleted
Separate shortcut from the component.
like this:
https://github.com/krab/vacuum-im-wix-installer/blob/master/Product.wxs#L20
https://github.com/krab/vacuum-im-wix-installer/blob/master/Files.wxs#L54
2013/9/4 Natalie Carr natalie.c...@measuresoft.com
Hi I have this code for a shortcut. This setup is an add on for my
main product so the code adds a shortcut to the shortcuts already
installed on the target machine. On uninstall however the add on
shortcut is never removed, can anyone see what I am doing wrong?
Component Id=PIDShortcut
Guid=696E79B3-D417-4352-9CEE-378DEECD9295
Directory=ProgramMenuDir
Shortcut Id=PIDShortcut Directory=ProgramMenuDir
Name=PID Controller Icon=pid_cf.exe IconIndex=0
Target=[BIN]pid_cf.exe
Icon Id=pid_cf.exe
SourceFile=E:\Products\Measuresoft_SCADA\Processors\PID_Controller\So
urces\
PID_CF\res\pid_cf.ico/
ShortcutProperty
Key=System.AppUserModel.ExcludeFromShowInNewInstall Value=1/
/Shortcut
RemoveFolder Id='ProgramMenuDir' On='uninstall'/
RegistryValue Root='HKCU'
Key='Software\ShortcutProperty\[PRODUCTNAME]' Type='string' Value='1'
KeyPath='yes' Name='PIDShortcut'/
/Component
Thanks
--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL
2012, more!
Discover the easy way to master current and previous Microsoft
technologies and advance your career. Get an incredible 1,500+ hours
of step-by-step tutorial videos with LearnDevNow. Subscribe today and
save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.c
lktrk ___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft
technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft
technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Learn the
Re: [WiX-users] Launching Bootstrapper executable should only show the internal MSI interface.
Yes. You need a custom BA. On Wed, Sep 4, 2013 at 3:49 AM, ak m wixak...@gmail.com wrote: Dear All, Launching Bootstrapper executable should only show the internal MSI interface. Not to show any of the Bootstrapper UI. Is this Possible? Any one please help me on this? Thanks in Advance. Anil -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] ARPSYSTEMCOMPONENT and patches
I have two applications, a MSI and a bootstrapper/UI that invokes the MSI. To prevent double ARP entries, we set the ARPSYSTEMCOMPONENT property in the bootstrapper bundle. This works fine, except when we apply a patch. Because the MSI is blocked, so is its patch. We cannot see it, and therefore cannot uninstall the patch. If I force it to show up in ARP by adding registry entries, a patch that is applied to a MSI install (not through bootstrapper) now shows double patch entries in the ARP. What is correct way to handle this problem? I'm using Wix 3.6. Thanks, George -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] FileSearch issues
Phil, your sample code works for me as well. Off to see where mine is different... On Mon, 2 Sep 2013 10:25:03 -0700, Phil Wilson wrote: My dumb search works just fine - I can't see what the issue is. This works for me: Sample.msi and thing.txt in the same directory. Property Id=FILEEXISTS Secure=yes DirectorySearch Id=CheckFileDir Path=[SourceDir] Depth=0 FileSearch Id=CheckFile Name=thing.txt / /DirectorySearch /Property and a custom action in the execute sequence to display the value... CustomAction Id=Msg Script=vbscriptmsgbox session.property(FILEEXISTS)/CustomAction The custom action correctly shows the file path, and a log of the install shows: MSI (c) (28:38) [10:13:38:811]: PROPERTY CHANGE: Adding FILEEXISTS property. Its value is 'C:\Phil\MyDD\WiX Samples\thing.txt'. So it does all work. I don't think an actual example with SourceDir was ever posted for a sanity check, but this is how to do it. Phil Wilson On Mon, Sep 2, 2013 at 9:19 AM, Edwin Castro 0ptikgh...@gmx.us wrote: I searched for WiX FileSearch in same directory as MSI on google. The first hit [1] I received [2] includes a reply from Phil Wilson suggesting the SourceDir [3] or OriginalDatabase [4] (with some additional parsing) might work. [1] http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-get-the-current-directory- of-msi-is-running-from-td3058873.html [2] I find it frustrating that different people can receive different results. *sigh* [3] http://msdn.microsoft.com/en-us/library/aa371857.aspx [4] http://msdn.microsoft.com/en- us/library/aa370562.aspx -- Edwin G. Castro On 8/31/13 10:21 AM, Kai Peters wrote: Hi Edwin, no need to be suspicious of Depth and AssignToProperty (firstly, omitting them didn't improve things, nor did I expect it to) as Depth can avoid unnecessary file system traversal (don't know how deep the search would go if no Depth is specified but would assume that default should be 0); AssignToProperty seems redundant to me as I would always expect the innermost element of a nested search to be assigned - but I just put it in here to make things absolutely clear. As I wrote (though not put in my example code) BOTH absolute and variable path specifications fail - I would never use absolute paths in production. The idea behind this search is simply that our customers' IT people could place a configuration file template beside our MSI and that during MSI execution this template would be copied into its destination. Since I cannot know from where IT will deploy our MSIs, I have to figure it out on the fly... And it's still failing - son if someone has an idea for me to look at, I'd appreciate it Thanks, Kai On Thu, 29 Aug 2013 13:47:19 -0700, Edwin Castro wrote: I'm highly suspect of the values for the Path, Depth and AssignToProperty attributes in your DirectorySearch. The example sent by John Cooper, replicated below for convenience, didn't set AssignToProperty=no nor Depth=0. Fragment PropertyRef Id=INSTALLLOCATION / Property Id=WEB_CONFIG_PATH Secure=yes DirectorySearch Id=InstallLocationSearch Path=[INSTALLLOCATION] DirectorySearch Id=WebFolderSearch Path=Web DirectorySearch Id=ContractFolderSearch Path=2008 DirectorySearch Id=WebHostFolderSearch Path=ProductName FileSearch Id=WebConfigFileSearch Name=Web.config / /DirectorySearch /DirectorySearch /DirectorySearch /DirectorySearch /Property /Fragment The Path value in your example is hard coded and that seems wrong to me. Even if you can guarantee that the MSI will ALWAYS reside at that location I believe that caching by Windows Installer will cause problems for you. My vague memory tells me that others have attempted this and couldn't reliably determine where the MSI was located in other to find a companion file located in the same directory. An obvious workaround is to provide the path to the companion file via a public property. -- Edwin G. Castro On 8/29/13 10:04 AM, K Peters wrote: Hi, I am still struggling with my FileSearch - no matter what I try, it always pops up the File does not exist next to MSI message. I have tried using SourceDir as well as the absolute path to where both the MSI the inifile reside - same negative results. Does anyone have an idea as to where I am screwing up...? Thanks, as always, for any pointers! Property Id=MASTERINIFILE_EXISTS DirectorySearch Id=MI_DirSearch Path=C:\Wix_Installscripts\Release_3.1.3\Regular_Install\ Depth=0 AssignToProperty=no FileSearch Id=MI_FileSearch Name=Master.ini / /DirectorySearch /Property Condition Message=File does not exist next to MSI ![CDATA[Installed and not MASTERINIFILE_EXISTS]] /Condition Condition Message=File does exist next to MSI ![CDATA[Installed and MASTERINIFILE_EXISTS]] /Condition -- Learn
Re: [WiX-users] help! How do I launch a file upon install ?
UI Publish Dialog=ExitDialog Control=Finish Event=DoAction Value=LaunchApplicationWIXUI_EXITDIALOGOPTIONALCHECKBOX = 1 and NOT Installed/Publish /UI worked for me. I had to remove the -UIRef Id=WixUI_Minimal ilne from it otherwise I was getting redefined variables with the UI I had added as a reference through the visual studio properties -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/help-How-do-I-launch-a-file-upon-install-tp7588736p7588749.html Sent from the wix-users mailing list archive at Nabble.com. -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Updated login to: http://wixtoolset.org/issues/
Sorry for the delay in responding to the last post. I updated my user info using the link provided in the email, however it always failed until I used exactly the same optional 'user name' provided originally. Then it liked the new password, and I can now log into the new bug tracker. Thanks for all of this work! Impressive. The new manual has a few broken links, which I can point out if that would be helpful, but I don't want to be a pest about something that is in transition. Thanks. Phill -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/New-Bug-and-Feature-Request-location-http-wixtoolset-org-issues-tp7588281p7588759.html Sent from the wix-users mailing list archive at Nabble.com. -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] VS2013?
I noticed while looking through the history that there were checkins related to VS2013 Preview, including a branch merge. Does this mean that 2013 is supported now (at least the preview version)? Thanks, John -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Major Upgrade Schedule Not Working?
No matter how I define Schedule in the MajorUpgrade node, during a Major update, the installer always acts like Schedule is set to afterInstallExecute. The installer will: 1) Install new version first (two copies show up in Add/Remove Programs temporarily during this process) 2) Uninstall old version In doing so, non-permanent registry entries are removed, and InstallFinalize CA to start the application is called after step 1, but step 2 is then closing the application so it can be prepared for uninstall. Even though Schedule is supposed to default to afterInstallValidate, I still defined it explicitly with no luck. MajorUpgrade DowngradeErrorMessage=A newer version of [ProductName] is already installed. AllowDowngrades=no AllowSameVersionUpgrades=no Schedule=afterInstallValidate / Has anyone else ran across this issue before? I have WIX Toolset v3.7 -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Shortcut in the root of start folder - why?
Hello, I have an strange behaviour with my application. The ApplicationShortcutSqliteStudio is generated inside its folder (ProgramMenuFolder\ApplicationProgramsFolder\utils) as expected, but it is also generated in the root of the start folder. Why the shortcut is also put in the root of the start folder? I don't want it here. Can you help me? Thanks a lot. ?xml version='1.0' encoding='windows-1252'? ?define ProductVersion = 3.0.8? ?define ProductUpgradeCode = 9640CA85-6906-48E8-9ABB-801DBF37DEDB? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; xmlns:util=http://schemas.microsoft.com/wix/UtilExtension; xmlns:netfx=http://schemas.microsoft.com/wix/NetFxExtension; Product Name='BGINFO4X for Windows $(var.ProductVersion)' Id='*' UpgradeCode=$(var.ProductUpgradeCode) Language='1033' Codepage='1252' Version='$(var.ProductVersion)' Manufacturer='KZTSoftware' !-- Main packed declaration -- Package Id='*' Keywords='Installer' Description=BGINFO4X for Windows $(var.ProductVersion) Comments='BGINFO4X is copyrighted at KZTSoftware.com' Manufacturer='KZTSoftware' InstallerVersion='100' Languages='1033' Compressed='yes' SummaryCodepage='1252' InstallScope=perMachine / Upgrade Id='61997F4A-5C91-48AA-B039-61D1EAAF2B3F' UpgradeVersion OnlyDetect='yes' Property='SELFFOUND' Minimum='1.0.0' IncludeMinimum='yes' Maximum='1.0.0' IncludeMaximum='yes' / UpgradeVersion OnlyDetect='yes' Property='NEWERFOUND' Minimum='1.0.0' IncludeMinimum='no' / /Upgrade CustomAction Id='AlreadyUpdated' Error='Foobar 1.0 has already been updated to 1.0.1 or newer.' / CustomAction Id='NoDowngrade' Error='A later version of [ProductName] is already installed.' / InstallExecuteSequence Custom Action='AlreadyUpdated' After='FindRelatedProducts'SELFFOUND/Custom Custom Action='NoDowngrade' After='FindRelatedProducts'NEWERFOUND/Custom /InstallExecuteSequence !-- How data is packed inside the msi -- Media Id='1' Cabinet='Sample.cab' EmbedCab='yes' DiskPrompt=CD-ROM #1 / Property Id='DiskPrompt' Value=BGINFO4X Installation [1] / Icon Id=WIX_32x32.ico SourceFile=WIX_32x32.ico / Property Id=ARPPRODUCTICON Value=WIX_32x32.ico/ Property Id=ARPHELPLINK Value= http://sourceforge.net/p/BGINFO4X/wiki/Documentation// Property Id=ARPURLINFOABOUT Value=http://BGINFO4X.sourceforge.net/ UIRef Id=WixUI_InstallDir/ UIRef Id=WixUI_ErrorProgressText/ WixVariable Id=WixUILicenseRtf Value=gpl3.rtf / WixVariable Id=WixUIDialogBmp Value=WIX_493x312.bmp / WixVariable Id=WixUIBannerBmp Value=WIX_493x58.bmp / WixVariable Id=WixUIExclamationIco Value=WIX_32x32.ico / WixVariable Id=WixUIInfoIco Value=WIX_32x32.ico / Property Id=WIXUI_INSTALLDIR Value=INSTALLDIR/ PropertyRef Id=NETFRAMEWORK20/ Condition Message=This application requires .NET Framework 2.0. Please install the .NET Framework then run this installer again. ![CDATA[Installed OR NETFRAMEWORK20]] /Condition !-- http://wixtoolset.org/documentation/manual/v3/howtos/ui_and_localization/run_program_after_install.html-- UI UIRef Id=WixUI_InstallDir / Publish Dialog=ExitDialog Control=Finish Event=DoAction Value=LaunchApplication WIXUI_EXITDIALOGOPTIONALCHECKBOX = 1 and NOT Installed/Publish /UI Property Id=WIXUI_EXITDIALOGOPTIONALCHECKBOX1/Property Property Id=WIXUI_EXITDIALOGOPTIONALCHECKBOXTEXT Value='Launch BGINFO4X for Windows $(var.ProductVersion)' / Property Id=WixShellExecTarget Value=[INSTALLDIR]BGINFO4X for Windows-hiddenconsole.bat / CustomAction Id=LaunchApplication BinaryKey=WixCA DllEntry=WixShellExec Impersonate=no / !-- Directory Structure -- Directory Id='TARGETDIR' Name='SourceDir' Directory Id='ProgramFilesFolder' Name='PFiles' Directory Id='INSTALLDIR' Name='BGINFO4X for Windows $(var.ProductVersion)'Directory Id='BaseDir'/Directory/Directory /Directory Directory Id=ProgramMenuFolder Directory Id=ApplicationProgramsFolder Name=BGINFO4X for Windows $(var.ProductVersion) Directory Id='Documentation' Name=Documentation/ Directory Id='Utils' Name=Utils/ /Directory /Directory Directory Id=StartupFolder Name=StartUp/ Directory Id=DesktopFolder Name=Desktop/ /Directory DirectoryRef Id=Documentation Component Id=DocumentationShortcuts Guid=18FF8E35-35D1-488C-801B-3EA47BB75F0D util:InternetShortcut Id=WebSite Name=BGINFO4X WebSite Type=url Target=http://BGINFO4X.sourceforge.net/ util:InternetShortcut Id=OnlineDocumentationShortcut Name=BGINFO4X Documentation Type=url Target= http://sourceforge.net/p/BGINFO4X/wiki/Documentation// util:InternetShortcut Id=OnlineHelpShortcut Name=BGINFO4X Help Forum Type=url
Re: [WiX-users] ARPSYSTEMCOMPONENT and patches
Ship the patch in a Bundle. On Wed, Sep 4, 2013 at 10:04 AM, George Fleming gef...@microsoft.comwrote: I have two applications, a MSI and a bootstrapper/UI that invokes the MSI. To prevent double ARP entries, we set the ARPSYSTEMCOMPONENT property in the bootstrapper bundle. This works fine, except when we apply a patch. Because the MSI is blocked, so is its patch. We cannot see it, and therefore cannot uninstall the patch. If I force it to show up in ARP by adding registry entries, a patch that is applied to a MSI install (not through bootstrapper) now shows double patch entries in the ARP. What is correct way to handle this problem? I'm using Wix 3.6. Thanks, George -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Re: Updated login to: http://wixtoolset.org/issues/
Manual is expected to be working now so if you find dead links, please do file bugs about them. On Wed, Sep 4, 2013 at 11:08 AM, Phill Hogland phogl...@rimage.com wrote: Sorry for the delay in responding to the last post. I updated my user info using the link provided in the email, however it always failed until I used exactly the same optional 'user name' provided originally. Then it liked the new password, and I can now log into the new bug tracker. Thanks for all of this work! Impressive. The new manual has a few broken links, which I can point out if that would be helpful, but I don't want to be a pest about something that is in transition. Thanks. Phill -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/New-Bug-and-Feature-Request-location-http-wixtoolset-org-issues-tp7588281p7588759.html Sent from the wix-users mailing list archive at Nabble.com. -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] VS2013?
There are bugs open that track progress of 2013 support. On Wed, Sep 4, 2013 at 11:16 AM, John H Bergman (XPedient) john.berg...@xpdnt.com wrote: I noticed while looking through the history that there were checkins related to VS2013 Preview, including a branch merge. Does this mean that 2013 is supported now (at least the preview version)? Thanks, John -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Re: FileSearch issues
My memory says SourceDir is blank until Source Resolution is executed. On Wed, Sep 4, 2013 at 10:13 AM, Phil Wilson phildgwil...@gmail.com wrote: It will work only during first install, as Rob most likely knows. During repair, feature change, and uninstall the SourceDir location is (IIRC) the installer directory of the cached MSI file. It's not good design to rely on external files in the same location as the MSI. There are too many failure points, as just mentioned. Also, Group Policy and web installs don't work, and a simple mistake in staging the MSI file and the external file to the install source changes the install logic, and that probably can't be corrected later. If there is really a need for an optional external file it would be better to have it in the binary table or have the data as properties, and give customers a tool to add the file (or the data) if necessary. Or change the design. Phil Wilson On Wed, Sep 4, 2013 at 7:15 AM, Kai Peters kpet...@otaksoft.com wrote: Phil, your sample code works for me as well. Off to see where mine is different... On Mon, 2 Sep 2013 10:25:03 -0700, Phil Wilson wrote: My dumb search works just fine - I can't see what the issue is. This works for me: Sample.msi and thing.txt in the same directory. Property Id=FILEEXISTS Secure=yes DirectorySearch Id=CheckFileDir Path=[SourceDir] Depth=0 FileSearch Id=CheckFile Name=thing.txt / /DirectorySearch /Property and a custom action in the execute sequence to display the value... CustomAction Id=Msg Script=vbscriptmsgbox session.property(FILEEXISTS)/CustomAction The custom action correctly shows the file path, and a log of the install shows: MSI (c) (28:38) [10:13:38:811]: PROPERTY CHANGE: Adding FILEEXISTS property. Its value is 'C:\Phil\MyDD\WiX Samples\thing.txt'. So it does all work. I don't think an actual example with SourceDir was ever posted for a sanity check, but this is how to do it. Phil Wilson On Mon, Sep 2, 2013 at 9:19 AM, Edwin Castro 0ptikgh...@gmx.us wrote: I searched for WiX FileSearch in same directory as MSI on google. The first hit [1] I received [2] includes a reply from Phil Wilson suggesting the SourceDir [3] or OriginalDatabase [4] (with some additional parsing) might work. [1] http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-get-the-current-directory- of-msi-is-running-from-td3058873.html [2] I find it frustrating that different people can receive different results. *sigh* [3] http://msdn.microsoft.com/en-us/library/aa371857.aspx [4] http://msdn.microsoft.com/en- us/library/aa370562.aspx -- Edwin G. Castro On 8/31/13 10:21 AM, Kai Peters wrote: Hi Edwin, no need to be suspicious of Depth and AssignToProperty (firstly, omitting them didn't improve things, nor did I expect it to) as Depth can avoid unnecessary file system traversal (don't know how deep the search would go if no Depth is specified but would assume that default should be 0); AssignToProperty seems redundant to me as I would always expect the innermost element of a nested search to be assigned - but I just put it in here to make things absolutely clear. As I wrote (though not put in my example code) BOTH absolute and variable path specifications fail - I would never use absolute paths in production. The idea behind this search is simply that our customers' IT people could place a configuration file template beside our MSI and that during MSI execution this template would be copied into its destination. Since I cannot know from where IT will deploy our MSIs, I have to figure it out on the fly... And it's still failing - son if someone has an idea for me to look at, I'd appreciate it Thanks, Kai On Thu, 29 Aug 2013 13:47:19 -0700, Edwin Castro wrote: I'm highly suspect of the values for the Path, Depth and AssignToProperty attributes in your DirectorySearch. The example sent by John Cooper, replicated below for convenience, didn't set AssignToProperty=no nor Depth=0. Fragment PropertyRef Id=INSTALLLOCATION / Property Id=WEB_CONFIG_PATH Secure=yes DirectorySearch Id=InstallLocationSearch Path=[INSTALLLOCATION] DirectorySearch Id=WebFolderSearch Path=Web DirectorySearch Id=ContractFolderSearch Path=2008 DirectorySearch Id=WebHostFolderSearch Path=ProductName FileSearch Id=WebConfigFileSearch Name=Web.config / /DirectorySearch /DirectorySearch /DirectorySearch /DirectorySearch /Property /Fragment The Path value in your example is hard coded and that seems wrong to me. Even if you can guarantee that the MSI will ALWAYS reside at that location I believe that caching by Windows Installer will
Re: [WiX-users] Add install InstallScopeDlg to WixUI_InstallDir.wxs
On 04-Sep-13 12:44, jo...@msli.com wrote: So does anyone know how wix differs from VS2010 setup project for the per-user vs. per-machine install choice? WiX doesn't offer an equivalent because per-user products that install to shared, per-machine locations are a bad idea. They still require elevation but make it difficult to detect whether another user on the machine has installed them. -- sig://boB http://joyofsetup.com/ -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Major Upgrade Schedule Not Working?
On 04-Sep-13 15:13, Andrew Meyer wrote: No matter how I define Schedule in the MajorUpgrade node, during a Major update, the installer always acts like Schedule is set to afterInstallExecute. Use the Orca tool to verify whether RemoveExistingProducts is actually scheduled. -- sig://boB http://joyofsetup.com/ -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Nit error while trying to run Lux tests.
On 02-Sep-13 06:02, Ihor Horovetskyi wrote: When I try to run the .msi with log, test return value 3: Please open a bug and include which build of WiX you're running, OS version, and which .NET Frameworks are installed. -- sig://boB http://joyofsetup.com/ -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Uninstall bundle by name ?
Hi all - I've managed to upgrade some of our installs to Wix 3.7 with the burn
bootstrapper, hooray !
One thing I haven't quite anticipated is this: after our automated build we
need to push a newly-built installer to a test machine for an automated
smoke/sanity test. First we need to uninstall the old build and install the
new one (silently, can't just use control panel). I know it's possible to run
the old Setup.exe with the /quiet /uninstall command-line params, but is that
the only way ?
With MSI's we could run msiexec /x {product ID} to do the uninstall. Is
there some way to silently run the uninstall by product name or some other ID
which doesn't change from build to build ? It would be nice not to have to
keep the old bundle around for the uninstall.
Thanks for any info !
-Rob
--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58041391iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstall bundle by name ?
Nothing that is documented today.
On Wed, Sep 4, 2013 at 3:57 PM, robert_y...@agilent.com wrote:
Hi all - I've managed to upgrade some of our installs to Wix 3.7 with the
burn bootstrapper, hooray !
One thing I haven't quite anticipated is this: after our automated build
we need to push a newly-built installer to a test machine for an automated
smoke/sanity test. First we need to uninstall the old build and install
the new one (silently, can't just use control panel). I know it's possible
to run the old Setup.exe with the /quiet /uninstall command-line params,
but is that the only way ?
With MSI's we could run msiexec /x {product ID} to do the uninstall. Is
there some way to silently run the uninstall by product name or some other
ID which doesn't change from build to build ? It would be nice not to have
to keep the old bundle around for the uninstall.
Thanks for any info !
-Rob
--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58041391iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58041391iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] This is important
Hello, how is everything? My life is wonderful now that I lost weight. http://bitly.com/16V6AuQ It's free to try, what do you have to lose? I love hearing back on how well this works. -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
