[WiX-users] Components with no componentIDs
Hi I want to create a few components with no ComponentIDs. Can I do this even if the component is a versioned dll? Thanks Uma -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Trying to build Wix to debug a nasty problem... having problems
I was able to build a while back when I had an x86 machine, but once I upgraded to 64 bit I wasn't able to get a successful build done. I do remember the help file giving a list of prerequisites, as well as a few late nights using your favorite search engine to find random links with bits and pieces. I'm excited to see all that nightmare go away and be replaced by MSBuild. -Original Message- From: Robert MacFadyen [mailto:rmacfad...@rmtrack.com] Sent: Friday, October 19, 2012 2:51 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Trying to build Wix to debug a nasty problem... having problems Thanks Jacob! Is there a guide to hacking on wix36? I haven't used nant in years... what should I be "nant'ng" (for toolsrc and wix itself)? Regard, Rob -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: October-19-12 3:43 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Trying to build Wix to debug a nasty problem... having problems 3.6 is not meant to be built by Visual Studio and MSBuild. 3.6 is a mess of Nant build scripts and is quite fragile. 3.7 is being redone to build using just MSBuild or Visual Studio (though I haven't checked to see any of the progress). -Original Message- From: Robert MacFadyen [mailto:rmacfad...@rmtrack.com] Sent: Friday, October 19, 2012 2:32 PM To: 'General discussion for Windows Installer XML toolset.' Subject: [WiX-users] Trying to build Wix to debug a nasty problem... having problems Hey all, I'm trying to build Wix in VS2010 and I'm having a problem. I've downloaded the source from CodeProject using hg clone/hg update (to wix36 tag). The .sln appears to convert to vs2010 ok. Not sure why it was doing a conversion though... should I be using vs2008? When I try and build a specific extension, WixUtilExtension, I'm getting the following error: Error reading resource file 'c:\its\WixDevelopment\build\debug\x86\\util.wixlib' -- 'The system cannot find the file specified. ' WixUtilExtension When I try and build the entire solution I get several similar messages. So my question is where/when do the XXX.wixlib files get created? Regards Rob -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Conditional util:XmlFile change...
I have a .config file I need to change if the install running is the client install and NOT the server install (we share the services between client and server installations) I have this code: and I want to do something like this: < ! [CDATA[CLIENT_INSTALL="1"] ] > but I can't add that conditional since I get this error: Error 41 Schema validation failed with the following error at line 1, column 3113: The element cannot contain text. Content model is empty. C:\Dev\Core Technologies\Main\Setup\TitusServices\TitusEnterpriseManagementServicesMergeModule\MergeModule.wxs 18 1 TitusEnterpriseManagementServicesMergeModule how can I make a XmlFile change conditional? Can't use XmlConfig element since I have a text in the Value="false" < ! [CDATA[CLIENT_INSTALL="1"] ] > since I get this error: Error 34 The util:XmlConfig/@Value attribute cannot be specified when the element has body text as well. Specify either the attribute or the body, but not both. C:\Dev\Core Technologies\Main\Setup\TitusServices\TitusEnterpriseManagementServicesMergeModule\MergeModule.wxs 34 1 TitusEnterpriseManagementServicesMergeModule Steve -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Conditional-util-XmlFile-change-tp7581487.html Sent from the wix-users mailing list archive at Nabble.com. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Trying to build Wix to debug a nasty problem... having problems
Thanks Jacob! Is there a guide to hacking on wix36? I haven't used nant in years... what should I be "nant'ng" (for toolsrc and wix itself)? Regard, Rob -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: October-19-12 3:43 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Trying to build Wix to debug a nasty problem... having problems 3.6 is not meant to be built by Visual Studio and MSBuild. 3.6 is a mess of Nant build scripts and is quite fragile. 3.7 is being redone to build using just MSBuild or Visual Studio (though I haven't checked to see any of the progress). -Original Message- From: Robert MacFadyen [mailto:rmacfad...@rmtrack.com] Sent: Friday, October 19, 2012 2:32 PM To: 'General discussion for Windows Installer XML toolset.' Subject: [WiX-users] Trying to build Wix to debug a nasty problem... having problems Hey all, I'm trying to build Wix in VS2010 and I'm having a problem. I've downloaded the source from CodeProject using hg clone/hg update (to wix36 tag). The .sln appears to convert to vs2010 ok. Not sure why it was doing a conversion though... should I be using vs2008? When I try and build a specific extension, WixUtilExtension, I'm getting the following error: Error reading resource file 'c:\its\WixDevelopment\build\debug\x86\\util.wixlib' -- 'The system cannot find the file specified. ' WixUtilExtension When I try and build the entire solution I get several similar messages. So my question is where/when do the XXX.wixlib files get created? Regards Rob -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Trying to build Wix to debug a nasty problem... having problems
3.6 is not meant to be built by Visual Studio and MSBuild. 3.6 is a mess of Nant build scripts and is quite fragile. 3.7 is being redone to build using just MSBuild or Visual Studio (though I haven't checked to see any of the progress). -Original Message- From: Robert MacFadyen [mailto:rmacfad...@rmtrack.com] Sent: Friday, October 19, 2012 2:32 PM To: 'General discussion for Windows Installer XML toolset.' Subject: [WiX-users] Trying to build Wix to debug a nasty problem... having problems Hey all, I'm trying to build Wix in VS2010 and I'm having a problem. I've downloaded the source from CodeProject using hg clone/hg update (to wix36 tag). The .sln appears to convert to vs2010 ok. Not sure why it was doing a conversion though... should I be using vs2008? When I try and build a specific extension, WixUtilExtension, I'm getting the following error: Error reading resource file 'c:\its\WixDevelopment\build\debug\x86\\util.wixlib' -- 'The system cannot find the file specified. ' WixUtilExtension When I try and build the entire solution I get several similar messages. So my question is where/when do the XXX.wixlib files get created? Regards Rob -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Trying to build Wix to debug a nasty problem... having problems
Hey all, I'm trying to build Wix in VS2010 and I'm having a problem. I've downloaded the source from CodeProject using hg clone/hg update (to wix36 tag). The .sln appears to convert to vs2010 ok. Not sure why it was doing a conversion though... should I be using vs2008? When I try and build a specific extension, WixUtilExtension, I'm getting the following error: Error reading resource file 'c:\its\WixDevelopment\build\debug\x86\\util.wixlib' -- 'The system cannot find the file specified. ' WixUtilExtension When I try and build the entire solution I get several similar messages. So my question is where/when do the XXX.wixlib files get created? Regards Rob -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Patches for released WIX versions
Hi, Is there any plans to release patches with bug fixes for already released versions?. It would be nice to receive a couple of updates before moving to next version. Thank you. -- Regards, Fyodor Koryazhkin.. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Major upgrade stops working after doing small changes and switching to 3.6
You can find verbose log file here:
http://kloke-witten.dyndns.org/~philipp/Temp/msi_log.zip
There are some lines about finding related products, where it says
"FindRelatedProducts: current install is per-machine. Related install for
product '{1CC8C271-A877-4DF0-B1DE-C1B7D83521BC}' is per-user. Skipping...".
I looked into registry and that GUID seems to be the old existing
installation. But even if I specify InstallScope='perUser', nothing changes.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Major-upgrade-stops-working-after-doing-small-changes-and-switching-to-3-6-tp7581476p7581481.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing to inetpub\wwwroot...
I am now doing this but still not taking on the real port number: -Original Message- From: StevenOgilvie [mailto:sogil...@msn.com] Sent: October-18-12 5:22 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Installing to inetpub\wwwroot... Hi, I am trying to install a web application to the following directory: C:\inetpub\wwwroot\wws\VirtualDirectories\[Web_SITE_PORT] the WEB_SITE_PORT property is set to by default but within the UI of the installer we ask the User if they want to change the port and we verify that the port is closed (not in use) For the life of me I can't get the install dir to work properly :( (my web app is a merge module with a bunch of WIXLIBS) Within the Merge Module I have this: This is how I have the directory elements set up: I get this as the path: C:\inetpub\wwwroot\wss\VirtualDirectories\[WEB_SITE_PORT]\ or Name="WEB_SITE_PORT" (I get this as the path) C:\inetpub\wwwroot\wss\VirtualDirectories\WEB_SITE_PORT\ I tried this: I get this error while "Computing Space Requirements" "Could not access network location . Surely a directory can have only numbers in it!!! What am I doing wrong? Steve -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Installing-to-inetpub-wwwroot-tp7581451.html Sent from the wix-users mailing list archive at Nabble.com. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn: Specifying PackageGroup Id on button click
Check on the OnPackagePlan callbacks. On Fri, Oct 19, 2012 at 5:19 AM, Hans ter Horst wrote: > Hello, i have several simple installers that I would like group behind a > Burn interface and start depending on the button clicked from the > Bootstrapper interface I am designing which will have several buttons. > For a simple bootstrapper I know > I can use Bootstrapper.Engine.Plan(LaunchAction.Install); on hitting an > install button and Bootstrapper.Engine.Plan(LaunchAction.Uninstall); for > an uninstall button. How can I extend this to refer to PackageA or PackageB > in my Bundle.wxs file so i can differentiate between the MSI files started? > > Thanks! > -- > http://monochrome.me.uk/blog/ > > -- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- virtually, Rob Mensching http://RobMensching.com LLC -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Merge Files
Windows installer doesn't really work that way. On Fri, Oct 19, 2012 at 3:22 AM, Chaitanya wrote: > Hi > > I want merge files to one msi to another msi. > > I read an article > > http://wix.sourceforge.net/manual-wix2/authoring_merge_modules.htm > > but I don't want to use msm.i want to use msi. > > And help me in upgrade also. > > Regards > > Chaitanya. > > > -- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- virtually, Rob Mensching http://RobMensching.com LLC -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Major upgrade stops working after doing small changes and switching to 3.6
If theUpgradeCode is stable then I don't see anything obvious. What does verbose logfile for update show? On Fri, Oct 19, 2012 at 9:05 AM, PKEuS wrote: > Hello, > > First of all, sorry for posting this a second time, but my first post (via > nabble) seems to have been rejected, because I hadn't received subscription > confirmation mail before. > > I am a dev of the cppcheck project and I am trying to improve our > installer. > We are using WiX, and the original installer was built using WiX 3.5. You > can see the original installer code here: > https://github.com/danmar/cppcheck/tree/master/win_installer > > I switched to WiX 3.6(.3303), made the necessary changes to source to make > it work and made a few improvements: > I added several features and removed others. > I added some files and added some more > I set UI to > > I did not change existing GUIDs, especially not the UpgradeCode. Id of > is set to "*". > > But it fails to update existing installations (based on old installer built > with 3.5). It moves the new files into the destination directory and a new > entry "Cppcheck 1.57 dev" (If I call this Version 1.57 or 1.56.99 doesn't > matter - it has no impact on the behaviour of the installer) entry appears > in the "Add or Remove a Program" dialog, but the old "Cppcheck 1.56" entry > isn't removed. When trying to uninstall, only files that were not already > in > 1.56 are removed. > > For previous versions, updating worked (e.g. 1.55 -> 1.56). > > You can find modified project here: > http://kloke-witten.dyndns.org/~philipp/Temp/win_installer.zip > > > Any ideas? > > > PKEuS > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Major-upgrade-stops-working-after-doing-small-changes-and-switching-to-3-6-tp7581476.html > Sent from the wix-users mailing list archive at Nabble.com. > > > -- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- virtually, Rob Mensching http://RobMensching.com LLC -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Major upgrade stops working after doing small changes and switching to 3.6
Hello, I am a dev of the cppcheck project and I am trying to improve our installer. We are using WiX, and the original installer was built using WiX 3.5. You can see the original installer code here: https://github.com/danmar/cppcheck/tree/master/win_installer I switched to WiX 3.6(.3303), made the necessary changes to source to make it work and made a few improvements: I added several features and removed others. I added some files and added some more I set UI to I did not change existing GUIDs, especially not the UpgradeCode. Id of is set to "*". But it fails to update existing installations (based on old installer built with 3.5). It moves the new files into the destination directory and a new entry "Cppcheck 1.57 dev" (If I call this Version 1.57 or 1.56.99 doesn't matter - it has no impact on the behaviour of the installer) entry appears in the "Add or Remove a Program" dialog, but the old "Cppcheck 1.56" entry isn't removed. When trying to uninstall, only files that were not already in 1.56 are removed. For previous versions, updating worked (e.g. 1.55 -> 1.56). You can find modified project here: http://kloke-witten.dyndns.org/~philipp/Temp/win_installer.zip Any ideas? PKEuS -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Major-upgrade-stops-working-after-doing-small-changes-and-switching-to-3-6-tp7581475.html Sent from the wix-users mailing list archive at Nabble.com. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Major upgrade stops working after doing small changes and switching to 3.6
Hello, First of all, sorry for posting this a second time, but my first post (via nabble) seems to have been rejected, because I hadn't received subscription confirmation mail before. I am a dev of the cppcheck project and I am trying to improve our installer. We are using WiX, and the original installer was built using WiX 3.5. You can see the original installer code here: https://github.com/danmar/cppcheck/tree/master/win_installer I switched to WiX 3.6(.3303), made the necessary changes to source to make it work and made a few improvements: I added several features and removed others. I added some files and added some more I set UI to I did not change existing GUIDs, especially not the UpgradeCode. Id of is set to "*". But it fails to update existing installations (based on old installer built with 3.5). It moves the new files into the destination directory and a new entry "Cppcheck 1.57 dev" (If I call this Version 1.57 or 1.56.99 doesn't matter - it has no impact on the behaviour of the installer) entry appears in the "Add or Remove a Program" dialog, but the old "Cppcheck 1.56" entry isn't removed. When trying to uninstall, only files that were not already in 1.56 are removed. For previous versions, updating worked (e.g. 1.55 -> 1.56). You can find modified project here: http://kloke-witten.dyndns.org/~philipp/Temp/win_installer.zip Any ideas? PKEuS -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Major-upgrade-stops-working-after-doing-small-changes-and-switching-to-3-6-tp7581476.html Sent from the wix-users mailing list archive at Nabble.com. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditionally Installing Update MSI's in Burn
Have a look at util:ProductSearch too. -Original Message- From: andy smith [mailto:andysmi...@gmail.com] Sent: 18 October 2012 16:37 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Conditionally Installing Update MSI's in Burn I have a burn installer, whereby the original installer can effectively select which items to install via checkBoxes, which relate to individual msi's. These are working via InstallConditions, checking the fact that the checkbox has been checked, and that they are not installed. So far so good and that's it for options on install. I'm trying to run the updates without user invention, so are running them /passive . I'm assuming (this may be where my logic falls down) that all I need to check for is whether they have been installed or not, in order to only update those parts that have been installed, so InstallCondition="Installed" Alas on running an update, everything evaluates to false, and the exe's installed by the original install disapear, as defined in the wix manual - "If the condition evaluates to false and the bundle is being installed, repaired, or modified, the package will be uninstalled." The log states: Detected package: SetupProductA.msi, state: Absent, cached: None Detected package: SetupProductB.msi, state: Absent, cached: None Detected package: SetupProductC.msi, state: Absent, cached: None Detect complete, result: 0x0 Plan 3 packages, action: Install Condition '(chkProductA AND NOT Installed) OR INSTALLED' evaluates to false. Condition '(chkProductB AND NOT Installed) OR INSTALLED' evaluates to false. Condition '(chkProductC AND NOT Installed) OR INSTALLED' evaluates to false. What am I missing with my InstallConditions? Thanks - - Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditionally Installing Update MSI's in Burn
Hi Jacob, I couldn't understand your " Thanks.. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Conditionally-Installing-Update-MSI-s-in-Burn-tp7581445p7581472.html Sent from the wix-users mailing list archive at Nabble.com. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn: Specifying PackageGroup Id on button click
Hello, i have several simple installers that I would like group behind a Burn interface and start depending on the button clicked from the Bootstrapper interface I am designing which will have several buttons. For a simple bootstrapper I know I can use Bootstrapper.Engine.Plan(LaunchAction.Install); on hitting an install button and Bootstrapper.Engine.Plan(LaunchAction.Uninstall); for an uninstall button. How can I extend this to refer to PackageA or PackageB in my Bundle.wxs file so i can differentiate between the MSI files started? Thanks! -- http://monochrome.me.uk/blog/ -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Registering DLL's properly
Opps, silly me. Thanks for all your help Neil, greatly appreciated. -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: 19 October 2012 11:21 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Registering DLL's properly Why would you do that, if they are already installed then they should be registered, if not you should be installing and registering them. Neil >Thanks, I think I will just use the SelfRegCost for now. I am trying to >register DLL's that would be found on the target machine in their >system folder, would you have any idea how I would achieve this? > >-Original Message- >From: Neil Sleightholm [mailto:n...@x2systems.com] >Sent: 19 October 2012 10:51 >To: General discussion for Windows Installer XML toolset. >Subject: Re: [WiX-users] Registering DLL's properly > >I use heat as a starting point and then clean up the output. > >SelfRegCost works ok but it calls DllRegisterServer/DllUnRegisterServer >which means it can be uncontrolled as you don't know what is happening >in those functions, as a replacement for your CA it should be >identical. It should work on 64 bit machines. > >Neil > > >>Is that using heat? Do you know what problems would occur if any using >>the second method? And how these would work on 64 bit machines? Thanks >> >>-Original Message- >>From: Neil Sleightholm [mailto:n...@x2systems.com] >>Sent: 19 October 2012 10:39 >>To: General discussion for Windows Installer XML toolset. >>Subject: Re: [WiX-users] Registering DLL's properly >> >>The "proper" way is to harvest the registry entries. The other way is >>to set File/@SelfRegCost="1". >> >>Neil >> >> >>>Hi I have to register a lot of DLL and I currently have a custom >>>action to do this, however I would like to know the proper MSI way of >>>doing this? >>>Can >>>anyone guide me in the right direction please? And also how to >>>unregister them on uninstall. >>> >>>Kind Regards, >>> >>>Natalie Carr >>> >>> >>> >>> >>> >>>- >>>- >>>- >>>--- >>> >>>Everyone hates slow websites. So do we. >>>Make your web apps faster with AppDynamics Download AppDynamics Lite >>>for free today: >>>http://p.sf.net/sfu/appdyn_sfd2d_oct >>>___ >>>WiX-users mailing list >>>WiX-users@lists.sourceforge.net >>>https://lists.sourceforge.net/lists/listinfo/wix-users >> >> >>-- >>- >>--- >>-- >>-- >>Everyone hates slow websites. So do we. >>Make your web apps faster with AppDynamics Download AppDynamics Lite >>for free today: >>http://p.sf.net/sfu/appdyn_sfd2d_oct >>___ >>WiX-users mailing list >>WiX-users@lists.sourceforge.net >>https://lists.sourceforge.net/lists/listinfo/wix-users >> >> >>-- >>- >>--- >> >>Everyone hates slow websites. So do we. >>Make your web apps faster with AppDynamics Download AppDynamics Lite >>for free today: >>http://p.sf.net/sfu/appdyn_sfd2d_oct >>___ >>WiX-users mailing list >>WiX-users@lists.sourceforge.net >>https://lists.sourceforge.net/lists/listinfo/wix-users > > >--- >--- >-- >-- >Everyone hates slow websites. So do we. >Make your web apps faster with AppDynamics Download AppDynamics Lite >for free today: >http://p.sf.net/sfu/appdyn_sfd2d_oct >___ >WiX-users mailing list >WiX-users@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/wix-users > > >--- >--- > >Everyone hates slow websites. So do we. >Make your web apps faster with AppDynamics Download AppDynamics Lite >for free today: >http://p.sf.net/sfu/appdyn_sfd2d_oct >___ >WiX-users mailing list >WiX-users@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Registering DLL's properly
You also have the option of using registry free COM, if the dlls are suited to it. -Original Message- From: Natalie Carr [mailto:natalie.c...@measuresoft.com] Sent: 19 October 2012 10:27 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Registering DLL's properly Hi I have to register a lot of DLL and I currently have a custom action to do this, however I would like to know the proper MSI way of doing this? Can anyone guide me in the right direction please? And also how to unregister them on uninstall. Kind Regards, Natalie Carr - - Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Merge Files
Hi I want merge files to one msi to another msi. I read an article http://wix.sourceforge.net/manual-wix2/authoring_merge_modules.htm but I don't want to use msm.i want to use msi. And help me in upgrade also. Regards Chaitanya. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Registering DLL's properly
Why would you do that, if they are already installed then they should be registered, if not you should be installing and registering them. Neil >Thanks, I think I will just use the SelfRegCost for now. I am trying to >register DLL's that would be found on the target machine in their system >folder, would you have any idea how I would achieve this? > >-Original Message- >From: Neil Sleightholm [mailto:n...@x2systems.com] >Sent: 19 October 2012 10:51 >To: General discussion for Windows Installer XML toolset. >Subject: Re: [WiX-users] Registering DLL's properly > >I use heat as a starting point and then clean up the output. > >SelfRegCost works ok but it calls DllRegisterServer/DllUnRegisterServer >which means it can be uncontrolled as you don't know what is happening in >those functions, as a replacement for your CA it should be identical. It >should work on 64 bit machines. > >Neil > > >>Is that using heat? Do you know what problems would occur if any using >>the second method? And how these would work on 64 bit machines? Thanks >> >>-Original Message- >>From: Neil Sleightholm [mailto:n...@x2systems.com] >>Sent: 19 October 2012 10:39 >>To: General discussion for Windows Installer XML toolset. >>Subject: Re: [WiX-users] Registering DLL's properly >> >>The "proper" way is to harvest the registry entries. The other way is >>to set File/@SelfRegCost="1". >> >>Neil >> >> >>>Hi I have to register a lot of DLL and I currently have a custom >>>action to do this, however I would like to know the proper MSI way of >>>doing this? >>>Can >>>anyone guide me in the right direction please? And also how to >>>unregister them on uninstall. >>> >>>Kind Regards, >>> >>>Natalie Carr >>> >>> >>> >>> >>> >>>-- >>>- >>>--- >>> >>>Everyone hates slow websites. So do we. >>>Make your web apps faster with AppDynamics Download AppDynamics Lite >>>for free today: >>>http://p.sf.net/sfu/appdyn_sfd2d_oct >>>___ >>>WiX-users mailing list >>>WiX-users@lists.sourceforge.net >>>https://lists.sourceforge.net/lists/listinfo/wix-users >> >> >>--- >>--- >>-- >>-- >>Everyone hates slow websites. So do we. >>Make your web apps faster with AppDynamics Download AppDynamics Lite >>for free today: >>http://p.sf.net/sfu/appdyn_sfd2d_oct >>___ >>WiX-users mailing list >>WiX-users@lists.sourceforge.net >>https://lists.sourceforge.net/lists/listinfo/wix-users >> >> >>--- >>--- >> >>Everyone hates slow websites. So do we. >>Make your web apps faster with AppDynamics Download AppDynamics Lite >>for free today: >>http://p.sf.net/sfu/appdyn_sfd2d_oct >>___ >>WiX-users mailing list >>WiX-users@lists.sourceforge.net >>https://lists.sourceforge.net/lists/listinfo/wix-users > > >-- >-- >-- >Everyone hates slow websites. So do we. >Make your web apps faster with AppDynamics Download AppDynamics Lite for >free today: >http://p.sf.net/sfu/appdyn_sfd2d_oct >___ >WiX-users mailing list >WiX-users@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/wix-users > > >-- > >Everyone hates slow websites. So do we. >Make your web apps faster with AppDynamics >Download AppDynamics Lite for free today: >http://p.sf.net/sfu/appdyn_sfd2d_oct >___ >WiX-users mailing list >WiX-users@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Registering DLL's properly
Thanks, I think I will just use the SelfRegCost for now. I am trying to register DLL's that would be found on the target machine in their system folder, would you have any idea how I would achieve this? -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: 19 October 2012 10:51 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Registering DLL's properly I use heat as a starting point and then clean up the output. SelfRegCost works ok but it calls DllRegisterServer/DllUnRegisterServer which means it can be uncontrolled as you don't know what is happening in those functions, as a replacement for your CA it should be identical. It should work on 64 bit machines. Neil >Is that using heat? Do you know what problems would occur if any using >the second method? And how these would work on 64 bit machines? Thanks > >-Original Message- >From: Neil Sleightholm [mailto:n...@x2systems.com] >Sent: 19 October 2012 10:39 >To: General discussion for Windows Installer XML toolset. >Subject: Re: [WiX-users] Registering DLL's properly > >The "proper" way is to harvest the registry entries. The other way is >to set File/@SelfRegCost="1". > >Neil > > >>Hi I have to register a lot of DLL and I currently have a custom >>action to do this, however I would like to know the proper MSI way of >>doing this? >>Can >>anyone guide me in the right direction please? And also how to >>unregister them on uninstall. >> >>Kind Regards, >> >>Natalie Carr >> >> >> >> >> >>-- >>- >>--- >> >>Everyone hates slow websites. So do we. >>Make your web apps faster with AppDynamics Download AppDynamics Lite >>for free today: >>http://p.sf.net/sfu/appdyn_sfd2d_oct >>___ >>WiX-users mailing list >>WiX-users@lists.sourceforge.net >>https://lists.sourceforge.net/lists/listinfo/wix-users > > >--- >--- >-- >-- >Everyone hates slow websites. So do we. >Make your web apps faster with AppDynamics Download AppDynamics Lite >for free today: >http://p.sf.net/sfu/appdyn_sfd2d_oct >___ >WiX-users mailing list >WiX-users@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/wix-users > > >--- >--- > >Everyone hates slow websites. So do we. >Make your web apps faster with AppDynamics Download AppDynamics Lite >for free today: >http://p.sf.net/sfu/appdyn_sfd2d_oct >___ >WiX-users mailing list >WiX-users@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Registering DLL's properly
I use heat as a starting point and then clean up the output. SelfRegCost works ok but it calls DllRegisterServer/DllUnRegisterServer which means it can be uncontrolled as you don't know what is happening in those functions, as a replacement for your CA it should be identical. It should work on 64 bit machines. Neil >Is that using heat? Do you know what problems would occur if any using the >second method? And how these would work on 64 bit machines? Thanks > >-Original Message- >From: Neil Sleightholm [mailto:n...@x2systems.com] >Sent: 19 October 2012 10:39 >To: General discussion for Windows Installer XML toolset. >Subject: Re: [WiX-users] Registering DLL's properly > >The "proper" way is to harvest the registry entries. The other way is to >set >File/@SelfRegCost="1". > >Neil > > >>Hi I have to register a lot of DLL and I currently have a custom action >>to do this, however I would like to know the proper MSI way of doing >>this? >>Can >>anyone guide me in the right direction please? And also how to >>unregister them on uninstall. >> >>Kind Regards, >> >>Natalie Carr >> >> >> >> >> >>--- >>--- >> >>Everyone hates slow websites. So do we. >>Make your web apps faster with AppDynamics Download AppDynamics Lite >>for free today: >>http://p.sf.net/sfu/appdyn_sfd2d_oct >>___ >>WiX-users mailing list >>WiX-users@lists.sourceforge.net >>https://lists.sourceforge.net/lists/listinfo/wix-users > > >-- >-- >-- >Everyone hates slow websites. So do we. >Make your web apps faster with AppDynamics Download AppDynamics Lite for >free today: >http://p.sf.net/sfu/appdyn_sfd2d_oct >___ >WiX-users mailing list >WiX-users@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/wix-users > > >-- > >Everyone hates slow websites. So do we. >Make your web apps faster with AppDynamics >Download AppDynamics Lite for free today: >http://p.sf.net/sfu/appdyn_sfd2d_oct >___ >WiX-users mailing list >WiX-users@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Registering DLL's properly
Is that using heat? Do you know what problems would occur if any using the second method? And how these would work on 64 bit machines? Thanks -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: 19 October 2012 10:39 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Registering DLL's properly The "proper" way is to harvest the registry entries. The other way is to set File/@SelfRegCost="1". Neil >Hi I have to register a lot of DLL and I currently have a custom action >to do this, however I would like to know the proper MSI way of doing this? >Can >anyone guide me in the right direction please? And also how to >unregister them on uninstall. > >Kind Regards, > >Natalie Carr > > > > > >--- >--- > >Everyone hates slow websites. So do we. >Make your web apps faster with AppDynamics Download AppDynamics Lite >for free today: >http://p.sf.net/sfu/appdyn_sfd2d_oct >___ >WiX-users mailing list >WiX-users@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Registering DLL's properly
The "proper" way is to harvest the registry entries. The other way is to set File/@SelfRegCost="1". Neil >Hi I have to register a lot of DLL and I currently have a custom action to >do this, however I would like to know the proper MSI way of doing this? >Can >anyone guide me in the right direction please? And also how to unregister >them on uninstall. > >Kind Regards, > >Natalie Carr > > > > > >-- > >Everyone hates slow websites. So do we. >Make your web apps faster with AppDynamics >Download AppDynamics Lite for free today: >http://p.sf.net/sfu/appdyn_sfd2d_oct >___ >WiX-users mailing list >WiX-users@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Registering DLL's properly
Hi I have to register a lot of DLL and I currently have a custom action to do this, however I would like to know the proper MSI way of doing this? Can anyone guide me in the right direction please? And also how to unregister them on uninstall. Kind Regards, Natalie Carr -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Properties in deferred sequence
http://msdn.microsoft.com/en-us/library/windows/desktop/aa370543%28v=vs.85%29 .aspx -Original Message- From: Uma Harano [mailto:uhar...@esri.com] Sent: 18 October 2012 22:30 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Properties in deferred sequence Hi Are ProductVersion and ProductLanguage properties available during the deferred sequence of the msi? Thanks Uma - - Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Getting started writing a custom Bootstrapper interface
Thanks Daniel, this is precisely what I needed!
On Fri, Oct 19, 2012 at 9:32 AM, Daniel Bruce wrote:
> To resolve Microsoft.Tools.WindowsInstallerXml.Bootstrapper, you need to
> add a reference to BootstrapperCore, which in my installation was located
> under C:\Program Files (x86)\WiX Toolset v3.7\SDK\BootstrapperCore.dll. You
> should be able to find yours in a similar location.
>
> You are correct that there is little information about how to get started
> with Burn, and the little information there is to find is scattered around
> the net and pretty terse, so I'll give you enough to get started, then you
> should be able to look at the source code for the WiX BA to continue (I
> highly recommend having the source around to look at either way, because
> there is really no other way to get information about most things).
>
> For my WPF-based bootstrapper interface, I started a regular WPF
> application project and changed its output type to "class library". Then I
> have a class that inherits from BootstrapperApplication looking something
> like this:
>
> public class MyBA : BootstrapperApplication
> {
> static public Threading.Dispatcher Dispatcher { get; private set; }
> static public View.InstallerWindow Window { get; private set; }
> static public App TheApp { get; private set; }
>
> protected override void Run()
> {
> TheApp = new App();
> TheApp.InitializeComponent();
> // Send a reference to the Application to access things, if
> necessary
> TheApp.BA = this;
> MyBA.Dispatcher = Threading.Dispatcher.CurrentDispatcher;
> TheApp.Run();
> this.Engine.Quit(TheApp.ExitCode);
> }
> }
>
> And in my WPF Application class I have code like this to bring up a pretty
> standard MVVM application window:
>
> public partial class App : Application
> {
> public View.InstallerWindow Window { get; private set; }
> public
> Microsoft.Tools.WindowsInstallerXml.Bootstrapper.BootstrapperApplication BA
> { get; set; }
> public int ExitCode
> {
> get
> {
> return state.InstallerResult;
> }
> }
>
> private InstallationState state;
>
> protected override void OnStartup(StartupEventArgs e)
> {
> base.OnStartup(e);
>
> InstallationState state = new InstallationState(BA, ...);
> this.state = state;
> InstallerViewModel vm = new InstallerViewModel(state, ...,
> Threading.Dispatcher.CurrentDispatcher);
> var Window = new View.InstallerWindow(vm);
> state.ParentHwnd = new WindowInteropHelper(Window).Handle;
> Window.Show();
> state.Initialize();
> }
> }
>
> You also need to create a config file so the Burn managed bootstrapper
> host can find your application, which should be named something like
> YourAssemblyName.BootstrapperCore.config and look something like this,
> replacing "YourAssemblyName" with your own assembly's name:
>
>
>
>
> type="Microsoft.Tools.WindowsInstallerXml.Bootstrapper.BootstrapperSectionGroup,
> BootstrapperCore">
>type="Microsoft.Tools.WindowsInstallerXml.Bootstrapper.HostSection,
> BootstrapperCore" />
>
>
>
>
>
>
>
>
>
>
>
>
>
> Then, finally, in your bundle.wxs file add a reference to your assembly
> and put in this snippet to refer to your bootstrapper application properly,
> again replacing as necessary:
>
>
>SourceFile='$(var.YourAssemblyName.TargetDir)\YourAssemblyName.BootstrapperCore.config'
> />
>
>
>
> Now if you want to be able to run this with F5 from Visual Studio, you
> should build your bundle once first, then set your WPF assembly as the
> startup project, go into its project properties under Debug, set it to
> Start external program and point it to the exe file from your bundle. This
> is necessary because you can't set wixprojects as startup projects. If you
> want to debug the bootstrapper application and set breakpoints and whatnot,
> you need to attach to the process manually (ctrl+alt+p in my VS2010) after
> pressing F5, because of how Burn works. To facilitate this, I created a
> function like this that I call at the very beginning of my
> BootstrapperApplication.Run method:
>
> [Conditional("DEBUG")]
> private void ShowDebugMessageBox()
> {
> MessageBox.Show("If you want to debug the Bootstrapper Application,
> you should attach the debugger to the .NET process now and click the
> button.");
> }
>
> Sorry if any of this got horribly mangled in transport, but hopefully you
> can pick out what to do and this gives you something to work from.
>
> Regards,
> Daniel E. Bruce
>
> > -Original Message-
> > From: Hans ter Horst [mailto:hoshis...@gmail.com]
> > Sent: 19. oktober 2012 09:32
> > To: wix-users@lists.sourceforge.net
> > Subject: Re: [WiX-users] Getting started writing a custom Bootstrapper
> > interface
> >
> > Hello, could you please help me get started building my own boot
Re: [WiX-users] Getting started writing a custom Bootstrapper interface
To resolve Microsoft.Tools.WindowsInstallerXml.Bootstrapper, you need to add a
reference to BootstrapperCore, which in my installation was located under
C:\Program Files (x86)\WiX Toolset v3.7\SDK\BootstrapperCore.dll. You should be
able to find yours in a similar location.
You are correct that there is little information about how to get started with
Burn, and the little information there is to find is scattered around the net
and pretty terse, so I'll give you enough to get started, then you should be
able to look at the source code for the WiX BA to continue (I highly recommend
having the source around to look at either way, because there is really no
other way to get information about most things).
For my WPF-based bootstrapper interface, I started a regular WPF application
project and changed its output type to "class library". Then I have a class
that inherits from BootstrapperApplication looking something like this:
public class MyBA : BootstrapperApplication
{
static public Threading.Dispatcher Dispatcher { get; private set; }
static public View.InstallerWindow Window { get; private set; }
static public App TheApp { get; private set; }
protected override void Run()
{
TheApp = new App();
TheApp.InitializeComponent();
// Send a reference to the Application to access things, if necessary
TheApp.BA = this;
MyBA.Dispatcher = Threading.Dispatcher.CurrentDispatcher;
TheApp.Run();
this.Engine.Quit(TheApp.ExitCode);
}
}
And in my WPF Application class I have code like this to bring up a pretty
standard MVVM application window:
public partial class App : Application
{
public View.InstallerWindow Window { get; private set; }
public
Microsoft.Tools.WindowsInstallerXml.Bootstrapper.BootstrapperApplication BA {
get; set; }
public int ExitCode
{
get
{
return state.InstallerResult;
}
}
private InstallationState state;
protected override void OnStartup(StartupEventArgs e)
{
base.OnStartup(e);
InstallationState state = new InstallationState(BA, ...);
this.state = state;
InstallerViewModel vm = new InstallerViewModel(state, ...,
Threading.Dispatcher.CurrentDispatcher);
var Window = new View.InstallerWindow(vm);
state.ParentHwnd = new WindowInteropHelper(Window).Handle;
Window.Show();
state.Initialize();
}
}
You also need to create a config file so the Burn managed bootstrapper host can
find your application, which should be named something like
YourAssemblyName.BootstrapperCore.config and look something like this,
replacing "YourAssemblyName" with your own assembly's name:
Then, finally, in your bundle.wxs file add a reference to your assembly and put
in this snippet to refer to your bootstrapper application properly, again
replacing as necessary:
Now if you want to be able to run this with F5 from Visual Studio, you should
build your bundle once first, then set your WPF assembly as the startup
project, go into its project properties under Debug, set it to Start external
program and point it to the exe file from your bundle. This is necessary
because you can't set wixprojects as startup projects. If you want to debug the
bootstrapper application and set breakpoints and whatnot, you need to attach to
the process manually (ctrl+alt+p in my VS2010) after pressing F5, because of
how Burn works. To facilitate this, I created a function like this that I call
at the very beginning of my BootstrapperApplication.Run method:
[Conditional("DEBUG")]
private void ShowDebugMessageBox()
{
MessageBox.Show("If you want to debug the Bootstrapper Application, you
should attach the debugger to the .NET process now and click the button.");
}
Sorry if any of this got horribly mangled in transport, but hopefully you can
pick out what to do and this gives you something to work from.
Regards,
Daniel E. Bruce
> -Original Message-
> From: Hans ter Horst [mailto:hoshis...@gmail.com]
> Sent: 19. oktober 2012 09:32
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Getting started writing a custom Bootstrapper
> interface
>
> Hello, could you please help me get started building my own bootstrappe
> DLL? It is a Wix bootstrapper newbie question, but I guess there are
> plenty of us around :-)
>
> Thanks,
>
> Hans
>
> On Thu, Oct 18, 2012 at 5:43 PM, Hans ter Horst
> wrote:
>
> > Hello, I would like to add an interface to the Wix bootstrapper and
> > started Googling around but found few examples to get started.
> >
> > I have the following basic questions:
> >
> >- What project template would be best to use in VS 2010 or VS 2012? I
> >am thinking of a WPF based interface, should I select one of the WPF
> >library project templates? Or should I pick the plain vanilla
Re: [WiX-users] Getting started writing a custom Bootstrapper interface
Just in case others are wondering how to get started, this site did get me started: http://bryanpjohnston.wordpress.com/2012/09/28/custom-wix-managed-bootstrapper-application/ Hans On Thu, Oct 18, 2012 at 5:43 PM, Hans ter Horst wrote: > Hello, I would like to add an interface to the Wix bootstrapper and > started Googling around but found few examples to get started. > > I have the following basic questions: > >- What project template would be best to use in VS 2010 or VS 2012? I >am thinking of a WPF based interface, should I select one of the WPF >library project templates? Or should I pick the plain vanilla DLL template >and build on that? >- I started playing around a little already with a simple project and >the line of code* **using >Microsoft.Tools.WindowsInstallerXml.Bootstrapper;* ran into a missing >reference, I couldn't find any reference that would resolve this, what >assembly do I add? > > Thanks, > > Hans. > -- > http://monochrome.me.uk/blog/ > > -- http://monochrome.me.uk/blog/ -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Getting started writing a custom Bootstrapper interface
Hello, could you please help me get started building my own bootstrappe DLL? It is a Wix bootstrapper newbie question, but I guess there are plenty of us around :-) Thanks, Hans On Thu, Oct 18, 2012 at 5:43 PM, Hans ter Horst wrote: > Hello, I would like to add an interface to the Wix bootstrapper and > started Googling around but found few examples to get started. > > I have the following basic questions: > >- What project template would be best to use in VS 2010 or VS 2012? I >am thinking of a WPF based interface, should I select one of the WPF >library project templates? Or should I pick the plain vanilla DLL template >and build on that? >- I started playing around a little already with a simple project and >the line of code* **using >Microsoft.Tools.WindowsInstallerXml.Bootstrapper;* ran into a missing >reference, I couldn't find any reference that would resolve this, what >assembly do I add? > > Thanks, > > Hans. > -- > http://monochrome.me.uk/blog/ > > -- http://monochrome.me.uk/blog/ -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] execute wix msi through cmd
On 19/10/2012 00:26, Senthil Chandran wrote: > That did not work either :( > msiexec /i MyApplication.msi /qn WIXUI_LABNAME="TestSilent" > WIXUI_LABOWNER="Me" WIXUI_LABDESCRIPTION="description" WIXUI_LABACCESS="1" > did not work either. Try it without the quotes round the values. Log the installation and see what it reports for the property values. Rob > > Any other ideas? > > Thanks, > Senthil. > > -Original Message- > From: Rob Hamflett [mailto:rob_hamfl...@sn.scee.net] > Sent: Thursday, October 11, 2012 12:37 AM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] execute wix msi through cmd > > Try this: > msiexec /i MyApplication.msi /qn WIXUI_LABNAME=TestSilent WIXUI_LABOWNER=Me > WIXUI_LABDESCRIPTION=description WIXUI_LABACCESS=1 > > Rob > > On 10/10/2012 22:34, Senthil Chandran wrote: >> I wrote a wix project that generates a msi to execute my exe. >> Part of the installer, I collect data from users that I pass on to my exe. >> It works fine when I run the installer UI. >> >> Is there a way to run the installer from cmd without launching the UI, but >> still collect the data from users through arguments and pass it to my exe? >> I tried this and it is not working >> >> MyApplication.msi /qn [WIXUI_LABNAME="TestSilent"] >> [WIXUI_LABOWNER="Me"] [WIXUI_LABDESCRIPTION="description"] >> [WIXUI_LABACCESS="1"] >> >> Thanks, >> Senthil. >> -- >> Don't let slow site performance ruin your business. Deploy >> New Relic APM Deploy New Relic app performance management and know >> exactly what is happening inside your Ruby, Python, PHP, Java, and >> .NET app Try New Relic at no cost today and get our sweet Data Nerd >> shirt too! >> http://p.sf.net/sfu/newrelic-dev2dev >> > > > > -- > Don't let slow site performance ruin your business. Deploy New Relic APM > Deploy New Relic app performance management and know exactly what is > happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at > no cost today and get our sweet Data Nerd shirt too! > http://p.sf.net/sfu/newrelic-dev2dev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > -- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
