Re: [WiX-users] Active directory browser
I don't know if it would be any use, but Apache has a suite of AD/LDAP tools/libraries at http://directory.apache.org/studio/ . -- Bruce > On Nov 11, 2014, at 10:12 PM, pezmannen wrote: > > My setup includes several dialogs where you need to specify different Active > Directory accounts. For now, they are all free text and it's pretty easy to > miss spell. I found Msiext (http://dblock.github.io/msiext/) but was > wondering if there is something out there that can be used without starting > compiling cpp-code? > > Thanks > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Active-directory-browser-tp7597858.html > Sent from the wix-users mailing list archive at Nabble.com. > > -- > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn doesn't warn if package names collide
On 10/31/2014 11:55 AM, Rob Mensching wrote: > Could you file a bug to say that there should be an error message too? Done: http://wixtoolset.org/issues/4574/ . -- Bruce -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn doesn't warn if package names collide
Yup, that's what I did - I could also have changed source or destination filenames. -- Bruce On 10/31/2014 11:28 AM, Hoover, Jacob wrote: > A possible workaround would be to provide a MsiPackage/@Name putting them in > different directories in the layout. Ie: > > > ForcePerMachine="yes" > SourceFile="Win7\driver.msi" > Name="Win7\driver.msi" > Vital="yes" Compressed="yes" > SuppressSignatureVerification="yes" > InstallCondition="VersionNT = v6.1 AND NTProductType > = 1"> > > > ... > > Though I could see this as being a valid feature request to emit a warning. > > -Original Message- > From: Bruce Cran [mailto:br...@cran.org.uk] > Sent: Friday, October 31, 2014 11:54 AM > To: General discussion about the WiX toolset. > Subject: Re: [WiX-users] Burn doesn't warn if package names collide > > On 10/31/2014 12:11 AM, Rob Mensching wrote: >> Just so I'm sure I follow exactly, can you provide snippet of example code >> that demonstrates the issue? > > ForcePerMachine="yes" > SourceFile="Win7\driver.msi" > Vital="yes" Compressed="yes" > SuppressSignatureVerification="yes" > InstallCondition="VersionNT = v6.1 AND NTProductType > = 1"> > > > > ForcePerMachine="yes" > SourceFile="Win8\driver.msi" > Vital="yes" Compressed="yes" > SuppressSignatureVerification="yes" > InstallCondition="VersionNT > v6.1 OR NOT > NTProductType = 1"> > > > > SourceFile="utils.msi" > Vital="yes" Compressed="yes" > SuppressSignatureVerification="yes"> > > > -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn doesn't warn if package names collide
On 10/31/2014 12:11 AM, Rob Mensching wrote: > Just so I'm sure I follow exactly, can you provide snippet of example code > that demonstrates the issue? -- Bruce -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn doesn't warn if package names collide
I noticed that Burn (in 3.9 RC4) doesn't provide any warning or error if two packages in a chain are in different directories with the same file name: it appears to silently overwrite one of the copies. -- Bruce -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn: different bundles, same msi package - not detected
I have two different products/bundles that install different versions of the same msi package. I had expected that the bundle would detect the existing installation of the msi and log it as an upgrade, but instead it's logging it as "absent" and the subsequent execution of the package runs the upgrade anyway. I'm using WiX 3.9.203.0. Is this expected with different bundles, or should the msi package be found by both? -- Bruce -- Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eXo Platform Software Java Based Open Source Intranet - Social, Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A Collaboration Platform http://p.sf.net/sfu/ExoPlatform ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn: doing an Administrative Installation
On 4/10/2014 3:13 AM, David Watson wrote: > You can do a /layout to get the contents of the bundle, then you would need > to do an admin install with the msi. > > Don't know if there is a /admin on the bundle, you could make one if not that > calls each msi in turn with admin parameters. Unfortunately, since we embed everything in the exe /layout just gets a copy of the exe, not the contents - need to use "burn.exe -x out installer.exe" instead. -- Bruce -- Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn: doing an Administrative Installation
We package our MSI using Burn, and have had a request to allow users to dump the files in one of the MSIs to a directory instead of installing them - i.e. doing an Administrative installation (http://msdn.microsoft.com/en-us/library/aa367541%28v=vs.85%29.aspx). Does the functionality exist in Burn to do this? -- Bruce -- Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn: "Failed to initialize COM"
I have a machine running Windows 8.1 where the Burn uninstaller is
failing since it appears that the call to CoInitialize() is failing:
Burn v3.9.203.0, Windows v6.3 (Build 9600: Service Pack 0), path:
C:\ProgramData\Package Cache\{GUID}\product.exe, cmdline:
'/uninstall /quiet /norestart -burn.unelevated BurnPipe.{GUID1} {GUID2}
2660' Initializing string variable 'InstallFolder' to value
'[ProgramFiles64Folder][WixBundleName]' Setting string variable
'WixBundleLog' to value
'C:\Users\ADMINI~1\AppData\Local\Temp\ProductName_20140322065504.log'
Error 0x80070008: Failed to initialize COM. Shutting down, exit code:
0x8
I've verified that a simple application *can* call CoInitialize()
successfully (I guess if that was broken Windows wouldn't be running!)
- any ideas what might be wrong?
--
Bruce
--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Using Heat to harvest by both project and dir and outputs going to same directory
I am struggling with best technique to take output from each heat harvest session in pre-build in VS2012. The application associated dlls go into the same directory as the executable as well as large directory structure from application content. Sorry, the email client doesn't support the tabbing when pasting from VS Here are my pre-build scripts D:\WIXBIN\heat dir "D:\AAA\CT\CT_2012\CT_2010\CRM\bin\x86\Release" -var var.ReleaseDIR -dr APPLICATIONFOLDER -cg CRM.ApplicationBinaries -sreg -ag -template fragment -t D:\AAA\CT\CT_2012\CT_2010\CT.Server.Setup\Transform.xls -out D:\AAA\CT\CT_2012\CT_2010\CT.Server.Setup\CTBinaries.wxs D:\WIXBIN\heat project D:\AAA\CT\CT_2012\CT_2010\CRM\CRM5.vbproj -var var.SourcePath -dr APPLICATIONFOLDER -pog Satellites -directoryid APPLICATIONFOLDER -pog Content -cg ContentComponentGroup -ag -t D:\AAA\CT\CT_2012\CT_2010\CT.Server.Setup\Transform.xls -template fragment -v -out D:\AAA\CT\CT_2012\CT_2010\CT.Server.Setup\CTContent.wxs the Folders.wxs fragment . http://schemas.microsoft.com/wix/NetFxExtension"xmlns="http://schemas.microsoft.com/wix/2006/wi";> starting OUTPUT OF HEAT DIR ... into CTBinaries.wxs http://schemas.microsoft.com/wix/2006/wi";> the starting OUTPUT from HEAT Project into CTContent.wxs http://schemas.microsoft.com/wix/2006/wi";> I would appreciate a pointer into the right direction. The associated dlls get put into the Release subdirectory as pointed from the HEAT dir output. Thanks in advance Bruce Heath DreamOn Software br...@dreamonsoftware.com 989-785-9055 -- Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Question about versioning with regard to GUIDs using a VS2012 project, and TFS build
I am trying to manage the GUIDs in the component fragments using Project Output for binaries and content so that they remain the same for dll's/content between builds associated with project through the GUI. This also has to work through TFS MSBuilds as well. What is the best approach? Bruce Heath DreamOn Software br...@dreamonsoftware.com 989-785-9055 -- Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn: util:ProductSearch logging 3 errors when no matching product found
I'm using WiX 3.9.120.0 - in Burn, is util:ProductSearch supposed to log errors when it doesn't find a matching product? I'm using: The log contains: [13E8:23D4][2014-01-30T12:01:15]e000: Error 0x80020005: Failed to copy variant value. [13E8:23D4][2014-01-30T12:01:15]e000: Error 0x80020005: Failed to change value type. [13E8:23D4][2014-01-30T12:01:15]i000: MsiProductSearch failed: ID 'wps1090C0D2C764DBC84EF5829FA1F83DB9', HRESULT 0x80020005 -- Bruce -- WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [SPAM] Re: 0x80096005: timestamp signature and/or certificate could not be verified
On 1/28/2014 3:27 PM, Phill Hogland wrote: > There are other similar reports on the internet which are not related to Wix, > so the root problem is probably more along the lines that Christopher > suggested. When you recompiled did you consider using > MsiPackage/@SuppressSignatureVerification? This can happen if the machine can't contact the Microsoft servers to download the root certificate. At least on Vista, if the machine is never connected to the Internet our Burn packages won't install because the Verisign certificate isn't on the machine. I don't know if the same issue exists on Windows 7 and newer though. -- Bruce -- WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Signing all DLLs and EXEs in project
On 12/18/2013 1:21 PM, John Cooper wrote: > If you're signing more than a dozen or so files in one pass, you've got > bigger problems. :) Besides which, like many build-related tasks, signing > is an activity best done in the same project generating the binary. +1. Unless you're talking about signing custom action DLLs, then signing is best done before the packaging/installer task. -- Bruce -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Signing all DLLs and EXEs in project
I guess the OP is talking about native binaries, not .NET assemblies
since he mentioned signtool - sn is the .NET signing tool.
--
Bruce
On 12/18/2013 1:23 PM, John Cooper wrote:
> You'll have to correctly handle the case where a binary cannot be signed
> because it has references to unsigned assemblies. We run into this all the
> time with our UI controls.
>
> --
> John Merryweather Cooper
> Build & Install Engineer - ESA
> Jack Henry & Associates, Inc.®
> Shawnee Mission, KS 66227
> Office: 913-341-3434 x791011
> jocoo...@jackhenry.com
> www.jackhenry.com
>
>
>
> -Original Message-
> From: Dror, Tomer [mailto:tomer.d...@intergraph.com]
> Sent: Wednesday, December 18, 2013 1:44 PM
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] Signing all DLLs and EXEs in project
>
> If you can explain how do you want to sign the dll I can try to create wix
> extension for you
>
> something like
>
>
> yourNameSpace:SignKeyPathFile="yes"
>
> Guid="{87DFBD51-5DA7-46D2-9FB5-8A602A87EA71}"
>Id="ComponentAA1.txt">
> Source="Content\FeatureA\FeatureA1\ComponentAA1\ComponentAA1.txt"/>
>
>
>
>
>
>
>
> Tomer Dror
>
> SmartPlant Explorer Development Manager.
> Intergraph Corporation.
> Intergraph Israel.
>
> Nesher 36881 - 4, Hacharoshet St.
> P: +972 (4) 8779191-1222
>
> Skype:tomer.dee
> http://www.intergraph.com
>
>
>
> .
>
>
> From: Rob Mensching [r...@robmensching.com]
> Sent: Wednesday, December 18, 2013 9:26 PM
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] Signing all DLLs and EXEs in project
>
> Not today. Something considering for v4 (maybe).
>
> -Original Message-
> From: Brian Enderle [mailto:bria...@gmail.com]
> Sent: Wednesday, December 18, 2013 11:22 AM
> To: General discussion about the WiX toolset.
> Subject: [WiX-users] Signing all DLLs and EXEs in project
>
> Is there a way I can sign all the DLLs and EXEs in my project using WiX via
> signtool?
>
> I was hoping there might be something available in the @Component element
> that would allow me to selectively sign DLL/EXE files so that I could avoid
> signing DLLs that I did not create.
>
> Brian
>
> If you can't explain it simply, you don't understand it well enough. -
> Albert Einstein
> --
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> --
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> --
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> NOTICE: This electronic mail message and any files transmitted with it are
> intended
> exclusively for the individual or entity to which it is addressed. The
> message,
> together with any attachment, may contain confidential and/or pr
Re: [WiX-users] Microsoft Reciprocal License explaination
On 11/20/2013 8:52 AM, John Ludlow wrote: > The only reason I can see not to do this is because it depends on > proprietary code, which either has no use outside your environment, or is > considered part of your own product and can't be distributed. Or if you think the changes are so awesome you want to prevent your competitors from getting the improvements :) -- Bruce Cran -- Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom action was working now it isn't.... HELP...
On 10/31/2013 7:50 PM, Steven Ogilvie wrote: > So weird... > > Was working before, stopped working... function name had 26 characters > removed 7 characters now it works... Something we discussed today was how the CA log name when calling WcaInitialize() has a maximum of 32 characters - anything more than that and it fails with an "Insufficient buffer" error. Could something similar be happening? -- Bruce Cran -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [SPAM] Re: [SPAM] Re: Errors installing 3.7
On 9/25/2013 2:47 PM, keith.doug...@statcan.gc.ca wrote: > Hi everyone, I thought I'd update the answer to my question from last week: > > For what it is worth, our server support team found KB931125, which seems to > have been the correct one for Server 2003 R2 Enterprise. By the way don't install KB931125 on Windows Server 2008 or newer - it's only designed for XP/2003 and client builds (i.e. XP, Server2003, Vista, Win7, Win8, Win8.1). See http://blogs.technet.com/b/windowsserver/archive/2013/01/12/fix-available-for-root-certificate-update-issue-on-windows-server.aspx for details of what can go wrong. You're supposed to import just the specific certificates you need from another machine. -- Bruce Cran -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] repair does not repair file that was changed
On 10/28/2013 1:35 PM, Andrew Makhorin wrote: > Is there any way to tell the installer to always install original files > provided in .msi on repairing/reinstalling the product? See http://technet.microsoft.com/en-us/library/cc759262%28v=ws.10%29.aspx?ppud=4#BKMK_Repair . -- Bruce -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Signing binaries and msi...
On 10/23/2013 2:13 AM, darren.benn...@listech.com wrote: > I'm interested to know how you went about implementing > your own task for code signing? I wrote an inline task in C# that shells out to signtool.exe with retries. It has thumbprint, crosscertificate, timestamp, retries and signingtargets parameters. -- Bruce Cran -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Signing binaries and msi...
On 10/22/2013 6:47 PM, Tony wrote: > Answering my own question... > > ".(though now I see it needs to be "property", so I'll give that a try)" > <-- that was it. I don't know why I was thinking it need to be a WiX > property and/or preprocessor variable. **OBVIOUSLY** it needs to be a > "property" within the project file. Duh! > > Now the signing attempt fails as expected. I'll go grab our signing cert > and give it try. When you install the cert you might want to change the signtool commands to specify its thumbprint instead of relying on signtool's auto-selection: signtool sign /sha1 cert-thumbprint or, specify the cert's Subject Name with /n. I realised my previous email used the wrong parameter for the description: I think it's actually /d. Another thing: MSBuild has a built-in task for running signtool, SignFile - http://msdn.microsoft.com/en-us/library/ms164304.aspx. But I ended up writing my own implementation which retries 10 times with pauses in-between to try and handle network problems which prevent the timestamp server being reached. -- Bruce Cran -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Signing binaries and msi...
On 10/22/2013 3:00 PM, Tony wrote: > > > To avoid the signature going invalid when the certificate expires, you probably want to add a timestamp: http://timestamp.verisign.com/scripts/timstamp.dll /> (that isn't a typo - "timstamp.dll" is 8.3 format). If you have a Globalsign cert, you might want to use timestamp.globalsign.com instead etc. And for the MSI file, you might want to add: /n text-that-should-appear-in-UAC-elevation-prompt-description Otherwise, the description will contain a randomly-generated filename. -- Bruce Cran -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] wixtoolset.org weekly builds downloads missing (404)
On 10/11/2013 5:42 PM, Bruce Cran wrote: > None of the builds via wixtoolset.org are working. For example trying > to download 3.8.1007 results in the broken link > http://wixtoolset.org/downloads/v3.8.1007.0/wix38.exe. > After refreshing each page it now works. -- Bruce Cran -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] wixtoolset.org weekly builds downloads missing (404)
None of the builds via wixtoolset.org are working. For example trying to download 3.8.1007 results in the broken link http://wixtoolset.org/downloads/v3.8.1007.0/wix38.exe. -- Bruce Cran -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Howto override variables from a file using MSBuild/VS2012
On 10/8/2013 1:03 AM, Blair Murri wrote: > The rest (of us) buy the book > (http://www.amazon.com/gp/product/0735626286?ie=UTF8&tag=sedodream-20&linkCode=xm2&camp=1789&creativeASIN=0735626286) Note that the link is for the first edition, not the second. -- Bruce Cran -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] wixtoolset.org reporting 503 - service unavailable
http://wixtoolset.org/ reports: Service Unavailable HTTP Error 503. The service is unavailable. -- Bruce Cran -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] install only on server 2012 and server 2008
On 9/23/2013 5:23 AM, Steven Ogilvie wrote: > Check out VersionNT and NTProductType (Google them to get the proper values > for the two OS's you want) Or read my reply :) -- Bruce Cran -- LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] install only on server 2012 and server 2008
On 9/20/2013 12:20 PM, nkshirsagar wrote: > I need to be able to install only on windows server 2012 and windows server > 2008 r2, everything else is a no-no.. (no client OS, no vista, no xp, no > windows 7/8) what condition should I use? See http://msdn.microsoft.com/en-us/library/windows/desktop/aa370905%28v=vs.85%29.aspx#operating_system_properties You'll probably want VersionNT >= 6.1 And VersionNT < 6.3 And MsiNTProductType > 1 With Windows Server 2012 R2 now released to MSDN you might want to drop the "VersionNT < 6.3" condition if you want to support it and future versions of Windows (2008R2 is 6.1, 2012 is 6.2, 2012 R2 is 6.3). -- Bruce Cran -- LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Add text to final window in burn bootstrapper/installer
On 18/09/2013 14:08, Steven Ogilvie wrote: > So it is not currently supported? I don't think so. At least, the WixStdBA doesn't. -- Bruce Cran -- LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Add text to final window in burn bootstrapper/installer
That's another feature I'm hoping to implement: Burn should support 'Modifying'
the installation, displaying the options page during maintenance.
--
Bruce
Sent from my iPhone
On 16 Sep 2013, at 15:59, Steven Ogilvie wrote:
> Did I send you updated code?
>
> Different question...
>
> If I have two check boxes, each one a different installer, if I install one,
> how can I run the boostrapper again and choose to install the other?
> Currently it installs the 1 I have checked, run bootstrapper again and it
> wants to uninstall :(
>
> Steve
>
> -Original Message-
> From: Neil Sleightholm [mailto:n...@x2systems.com]
> Sent: August-31-13 5:02 AM
> To: General discussion for Windows Installer XML toolset.
> Cc: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Add text to final window in burn
> bootstrapper/installer
>
> If you like to post diff on the code plea site I'll add it to the extended
> BA.
>
> Neil
>
> On 30 Aug 2013, at 14:48, "Steven Ogilvie" wrote:
>
>> No sorry
>>
>> I am not using 3.8 I am using 3.7 with the Extended BA from Neil
>>
>> -Original Message-
>> From: Bruce Cran [mailto:br...@cran.org.uk]
>> Sent: August-30-13 9:00 AM
>> To: General discussion for Windows Installer XML toolset.
>> Subject: Re: [WiX-users] Add text to final window in burn
>> bootstrapper/installer
>>
>> Do you have a diff (e.g. using 'git diff') you can attach?
>>
>> --
>> Bruce
>>
>> Sent from my iPhone
>>
>> On 28 Aug 2013, at 18:29, Steven Ogilvie wrote:
>>
>>> Here is the code from BA
>>>
>>> Theme wxl file
>>> Setup Successful >> Id="SuccessSetupHeader">Setup Successful >> Id="SuccessUninstallHeader">Uninstall Successful
>>>
>>> Setup Failed >> Id="FailureSetupHeader">Setup Failed >> Id="FailureUninstallHeader">Uninstall Failed
>>>
>>> Theme xml file
>>>
>>> >> FontId="2" HideWhenDisabled="yes"
>>> DisablePrefix="yes">#(loc.SuccessHeader)
>>> >> FontId="2" HideWhenDisabled="yes"
>>> DisablePrefix="yes">#(loc.SuccessSetupHeader)
>>> >> Height="30" FontId="2" HideWhenDisabled="yes"
>>> DisablePrefix="yes">#(loc.SuccessUninstallHeader)
>>>
>>>
>>> >> FontId="2" HideWhenDisabled="yes"
>>> DisablePrefix="yes">#(loc.FailureHeader)
>>> >> FontId="2" HideWhenDisabled="yes"
>>> DisablePrefix="yes">#(loc.FailureSetupHeader)
>>> >> Height="30" FontId="2" HideWhenDisabled="yes"
>>> DisablePrefix="yes">#(loc.FailureUninstallHeader)
>>>
>>> WixStandardBootstrapperApplication.cpp
>>>
>>> // Success page
>>> WIXSTDBA_CONTROL_SUCCESS_HEADER,
>>> WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER,
>>> WIXSTDBA_CONTROL_SUCCESS_UNINSTALL_HEADER,
>>>
>>> // Failure page
>>> WIXSTDBA_CONTROL_FAILURE_HEADER,
>>> WIXSTDBA_CONTROL_FAILURE_SETUP_HEADER,
>>> WIXSTDBA_CONTROL_FAILURE_UNINSTALL_HEADER,
>>>
>>> { WIXSTDBA_CONTROL_SUCCESS_HEADER, L"SuccessHeader" },
>>> { WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER, L"SuccessSetupHeader" },
>>> { WIXSTDBA_CONTROL_SUCCESS_UNINSTALL_HEADER,
>>> L"SuccessUninstallHeader" },
>>>
>>> { WIXSTDBA_CONTROL_FAILURE_HEADER, L"FailureHeader" },
>>> { WIXSTDBA_CONTROL_FAILURE_SETUP_HEADER, L"FailureSetupHeader" },
>>> { WIXSTDBA_CONTROL_FAILURE_UNINSTALL_HEADER,
>>> L"FailureUninstallHeader" },
>>>
>>> In method OnChangeState:
>>> ..
>>> else if (m_rgdwPageIds[WIXSTDBA_PAGE_SUCCESS] == dwNewPageId) // on the
>>> "Success" page, check if the restart or launch button should be enabled.
>>> ...
>>> // Set the header of the failure page to either Setup or Uninstall
>>> if (ThemeControlExists(m_pTheme,
>>> WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER))
>>> {
>>> ThemeControlEnable(m_pTheme,
>>> WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER, BOOTSTRAPPER_ACTION_UNINSTALL <
>>> m_plannedAction);
>>>
Re: [WiX-users] Add text to final window in burn bootstrapper/installer
On 30/08/2013 14:46, Steven Ogilvie wrote: > No sorry > > I am not using 3.8 I am using 3.7 with the Extended BA from Neil Steven, I can't commit your code due to copyright issues, so would you be willing to sign the WiX copyright assignment agreement and upload the code to wix.codeplex.com yourself? -- Bruce Cran -- 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=58041391&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Add text to final window in burn bootstrapper/installer
Can't Steven put the change in the public domain and someone who's already signed the agreement can commit it? -- Bruce Sent from my iPhone On 31 Aug 2013, at 04:10, Bob Arnson wrote: > On 28-Aug-13 13:29, Steven Ogilvie wrote: >> > FontId="2" HideWhenDisabled="yes" >> DisablePrefix="yes">#(loc.SuccessHeader) >> > FontId="2" HideWhenDisabled="yes" >> DisablePrefix="yes">#(loc.SuccessSetupHeader) >> > Height="30" FontId="2" HideWhenDisabled="yes" >> DisablePrefix="yes">#(loc.SuccessUninstallHeader) > Why separate controls? ThemeSetTextControl could be used with the > appropriate loc string. Also, differentiating uninstall is fine but > certainly other actions should get the same treatment, no? > > Logistics: You'd have to sign an assignment agreement since you're the > one providing the change. > > -- > 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=58040911&iu=/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=58040911&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Add text to final window in burn bootstrapper/installer
I'm working on a patch against 3.8 that I hope to put on codeplex later today.
--
Bruce
Sent from my iPhone
On 31 Aug 2013, at 10:02, Neil Sleightholm wrote:
> If you like to post diff on the code plea site I'll add it to the extended
> BA.
>
> Neil
>
> On 30 Aug 2013, at 14:48, "Steven Ogilvie" wrote:
>
>> No sorry
>>
>> I am not using 3.8 I am using 3.7 with the Extended BA from Neil
>>
>> -Original Message-
>> From: Bruce Cran [mailto:br...@cran.org.uk]
>> Sent: August-30-13 9:00 AM
>> To: General discussion for Windows Installer XML toolset.
>> Subject: Re: [WiX-users] Add text to final window in burn
>> bootstrapper/installer
>>
>> Do you have a diff (e.g. using 'git diff') you can attach?
>>
>> --
>> Bruce
>>
>> Sent from my iPhone
>>
>> On 28 Aug 2013, at 18:29, Steven Ogilvie wrote:
>>
>>> Here is the code from BA
>>>
>>> Theme wxl file
>>> Setup Successful >> Id="SuccessSetupHeader">Setup Successful >> Id="SuccessUninstallHeader">Uninstall Successful
>>>
>>> Setup Failed >> Id="FailureSetupHeader">Setup Failed >> Id="FailureUninstallHeader">Uninstall Failed
>>>
>>> Theme xml file
>>>
>>> >> FontId="2" HideWhenDisabled="yes"
>>> DisablePrefix="yes">#(loc.SuccessHeader)
>>> >> FontId="2" HideWhenDisabled="yes"
>>> DisablePrefix="yes">#(loc.SuccessSetupHeader)
>>> >> Height="30" FontId="2" HideWhenDisabled="yes"
>>> DisablePrefix="yes">#(loc.SuccessUninstallHeader)
>>>
>>>
>>> >> FontId="2" HideWhenDisabled="yes"
>>> DisablePrefix="yes">#(loc.FailureHeader)
>>> >> FontId="2" HideWhenDisabled="yes"
>>> DisablePrefix="yes">#(loc.FailureSetupHeader)
>>> >> Height="30" FontId="2" HideWhenDisabled="yes"
>>> DisablePrefix="yes">#(loc.FailureUninstallHeader)
>>>
>>> WixStandardBootstrapperApplication.cpp
>>>
>>> // Success page
>>> WIXSTDBA_CONTROL_SUCCESS_HEADER,
>>> WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER,
>>> WIXSTDBA_CONTROL_SUCCESS_UNINSTALL_HEADER,
>>>
>>> // Failure page
>>> WIXSTDBA_CONTROL_FAILURE_HEADER,
>>> WIXSTDBA_CONTROL_FAILURE_SETUP_HEADER,
>>> WIXSTDBA_CONTROL_FAILURE_UNINSTALL_HEADER,
>>>
>>> { WIXSTDBA_CONTROL_SUCCESS_HEADER, L"SuccessHeader" },
>>> { WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER, L"SuccessSetupHeader" },
>>> { WIXSTDBA_CONTROL_SUCCESS_UNINSTALL_HEADER,
>>> L"SuccessUninstallHeader" },
>>>
>>> { WIXSTDBA_CONTROL_FAILURE_HEADER, L"FailureHeader" },
>>> { WIXSTDBA_CONTROL_FAILURE_SETUP_HEADER, L"FailureSetupHeader" },
>>> { WIXSTDBA_CONTROL_FAILURE_UNINSTALL_HEADER,
>>> L"FailureUninstallHeader" },
>>>
>>> In method OnChangeState:
>>> ..
>>> else if (m_rgdwPageIds[WIXSTDBA_PAGE_SUCCESS] == dwNewPageId) // on the
>>> "Success" page, check if the restart or launch button should be enabled.
>>> ...
>>> // Set the header of the failure page to either Setup or Uninstall
>>> if (ThemeControlExists(m_pTheme,
>>> WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER))
>>> {
>>> ThemeControlEnable(m_pTheme,
>>> WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER, BOOTSTRAPPER_ACTION_UNINSTALL <
>>> m_plannedAction);
>>> ThemeControlEnable(m_pTheme,
>>> WIXSTDBA_CONTROL_SUCCESS_HEADER, FALSE);
>>> }
>>> else
>>> {
>>> ThemeControlEnable(m_pTheme,
>>> WIXSTDBA_CONTROL_SUCCESS_HEADER, TRUE);
>>> }
>>> if (ThemeControlExists(m_pTheme,
>>> WIXSTDBA_CONTROL_SUCCESS_UNINSTALL_HEADER))
>>> {
>>> ThemeControlEnable(m_pTheme,
>>> WIXSTDBA_CONTROL_SUCCESS_UNINSTALL_HEADER, BOOTSTRAPPER_ACTION_INSTALL >
>>> m_plannedAction);
>>> ThemeControlEnable(m_pTheme,
>>>
Re: [WiX-users] Add text to final window in burn bootstrapper/installer
Do you have a diff (e.g. using 'git diff') you can attach?
--
Bruce
Sent from my iPhone
On 28 Aug 2013, at 18:29, Steven Ogilvie wrote:
> Here is the code from BA
>
> Theme wxl file
> Setup Successful
> Setup Successful
> Uninstall Successful
>
> Setup Failed
> Setup Failed
> Uninstall Failed
>
> Theme xml file
>
> FontId="2" HideWhenDisabled="yes"
> DisablePrefix="yes">#(loc.SuccessHeader)
> FontId="2" HideWhenDisabled="yes"
> DisablePrefix="yes">#(loc.SuccessSetupHeader)
> FontId="2" HideWhenDisabled="yes"
> DisablePrefix="yes">#(loc.SuccessUninstallHeader)
>
>
> FontId="2" HideWhenDisabled="yes"
> DisablePrefix="yes">#(loc.FailureHeader)
> FontId="2" HideWhenDisabled="yes"
> DisablePrefix="yes">#(loc.FailureSetupHeader)
> FontId="2" HideWhenDisabled="yes"
> DisablePrefix="yes">#(loc.FailureUninstallHeader)
>
> WixStandardBootstrapperApplication.cpp
>
> // Success page
>WIXSTDBA_CONTROL_SUCCESS_HEADER,
>WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER,
>WIXSTDBA_CONTROL_SUCCESS_UNINSTALL_HEADER,
>
> // Failure page
>WIXSTDBA_CONTROL_FAILURE_HEADER,
>WIXSTDBA_CONTROL_FAILURE_SETUP_HEADER,
>WIXSTDBA_CONTROL_FAILURE_UNINSTALL_HEADER,
>
> { WIXSTDBA_CONTROL_SUCCESS_HEADER, L"SuccessHeader" },
>{ WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER, L"SuccessSetupHeader" },
>{ WIXSTDBA_CONTROL_SUCCESS_UNINSTALL_HEADER, L"SuccessUninstallHeader" },
>
> { WIXSTDBA_CONTROL_FAILURE_HEADER, L"FailureHeader" },
>{ WIXSTDBA_CONTROL_FAILURE_SETUP_HEADER, L"FailureSetupHeader" },
>{ WIXSTDBA_CONTROL_FAILURE_UNINSTALL_HEADER, L"FailureUninstallHeader" },
>
> In method OnChangeState:
> ..
> else if (m_rgdwPageIds[WIXSTDBA_PAGE_SUCCESS] == dwNewPageId) // on the
> "Success" page, check if the restart or launch button should be enabled.
> ...
> // Set the header of the failure page to either Setup or Uninstall
>if (ThemeControlExists(m_pTheme,
> WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER))
>{
>ThemeControlEnable(m_pTheme,
> WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER, BOOTSTRAPPER_ACTION_UNINSTALL <
> m_plannedAction);
>ThemeControlEnable(m_pTheme,
> WIXSTDBA_CONTROL_SUCCESS_HEADER, FALSE);
>}
>else
>{
>ThemeControlEnable(m_pTheme,
> WIXSTDBA_CONTROL_SUCCESS_HEADER, TRUE);
>}
>if (ThemeControlExists(m_pTheme,
> WIXSTDBA_CONTROL_SUCCESS_UNINSTALL_HEADER))
>{
>ThemeControlEnable(m_pTheme,
> WIXSTDBA_CONTROL_SUCCESS_UNINSTALL_HEADER, BOOTSTRAPPER_ACTION_INSTALL >
> m_plannedAction);
>ThemeControlEnable(m_pTheme,
> WIXSTDBA_CONTROL_SUCCESS_HEADER, FALSE);
>}
>else
>{
>ThemeControlEnable(m_pTheme,
> WIXSTDBA_CONTROL_SUCCESS_HEADER, TRUE);
>}
> ...
> else if (m_rgdwPageIds[WIXSTDBA_PAGE_FAILURE] == dwNewPageId) // on the
> "Failure" page, show error message and check if the restart button should be
> enabled.
> ...
> // Set the header of the failure page to either Setup or Uninstall
>if (ThemeControlExists(m_pTheme,
> WIXSTDBA_CONTROL_FAILURE_SETUP_HEADER))
>{
>ThemeControlEnable(m_pTheme,
> WIXSTDBA_CONTROL_FAILURE_SETUP_HEADER, BOOTSTRAPPER_ACTION_UNINSTALL <
> m_plannedAction);
>ThemeControlEnable(m_pTheme,
> WIXSTDBA_CONTROL_FAILURE_HEADER, FALSE);
>}
>else
>{
>ThemeControlEnable(m_pTheme,
> WIXSTDBA_CONTROL_FAILURE_HEADER, TRUE);
>}
>if (ThemeControlExists(m_pTheme,
> WIXSTDBA_CONTROL_FAILURE_UNINSTALL_HEADER))
>{
>ThemeControlEnable(m_pTheme,
> WIXSTDBA_CONTROL_FAILURE_UNINSTALL_HEADER, BOOTSTRAPPER_ACTION_INSTALL >
> m_plannedAction);
>ThemeControlEnable(m_pTheme,
> WIXSTDBA_CONTROL_FAILURE_HEADER, FALSE);
>}
>else
> {
>ThemeControlEnable(m_pTheme,
> WIXSTDBA_CONTROL_
Re: [WiX-users] Add text to final window in burn bootstrapper/installer
I'll submit the pull request tomorrow: it'll then be up to Bob to decide
if/when it gets committed.
--
Bruce
Sent from my iPhone
On 28 Aug 2013, at 19:14, "Alain Forget" wrote:
> Will this functionality be available on Monday (or sooner) at
> http://wixtoolset.org/releases/ ?
>
> If so, how will I be able to add text to the Setup Complete box? My apologies
> if I seem a tad dense, but this is very unfamiliar territory for me.
>
> -Original Message-
> From: Bruce Cran [mailto:br...@cran.org.uk]
> Sent: Wednesday, August 28, 2013 2:02 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Add text to final window in burn
> bootstrapper/installer
>
> Okay, I can submit it.
>
> --
> Bruce
>
> Sent from my iPhone
>
> On 28 Aug 2013, at 18:13, Steven Ogilvie wrote:
>
>> You want me to make the change for 3.8 or your going to make the change?
>>
>> I can send you my code for the BA if you want :)
>>
>> -Original Message-
>> From: Bruce Cran [mailto:br...@cran.org.uk]
>> Sent: August-28-13 12:34 PM
>> To: afor...@cmu.edu; General discussion for Windows Installer XML toolset.
>> Subject: Re: [WiX-users] Add text to final window in burn
>> bootstrapper/installer
>>
>> Yes that was for Steven: he's made exactly the same changes I was hoping to
>> get around to making, and I'd like to see them get into WiX 3.8 if possible.
>>
>> --
>> Bruce
>>
>> Sent from my iPhone
>>
>> On 28 Aug 2013, at 16:52, "Alain Forget" wrote:
>>
>>> I hope that's directed at Steven, because I don't know what that means (and
>>> I have yet to figure out where and how to modify .wxl files).
>>>
>>> Alain
>>>
>>> -Original Message-
>>> From: Bruce Cran [mailto:br...@cran.org.uk]
>>> Sent: Wednesday, August 28, 2013 11:39 AM
>>> To: General discussion for Windows Installer XML toolset.
>>> Subject: Re: [WiX-users] Add text to final window in burn
>>> bootstrapper/installer
>>>
>>> Could you sent a pull request to integrate this change upstream please?
>>>
>>> --
>>> Bruce Cran
>>>
>>> Sent from my iPhone
>>>
>>> On 28 Aug 2013, at 14:28, Steven Ogilvie wrote:
>>>
>>>> Yes exactly
>>>>
>>>> BA is using the same property for Setup/Uninstall for the
>>>> success/failure string
>>>>
>>>> I fixed this by changing the code in BA and adding a few extra string
>>>> properties in the theme wxl file Setup
>>>> Successful Setup
>>>> Successful Uninstall
>>>> Successful Setup Failed
>>>> Setup Failed >>> Id="FailureUninstallHeader">Uninstall Failed
>>>>
>>>> BA:
>>>>
>>>> { WIXSTDBA_CONTROL_SUCCESS_HEADER, L"SuccessHeader" },
>>>> { WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER, L"SuccessSetupHeader" },
>>>> { WIXSTDBA_CONTROL_SUCCESS_UNINSTALL_HEADER,
>>>> L"SuccessUninstallHeader" },
>>>>
>>>> { WIXSTDBA_CONTROL_FAILURE_HEADER, L"FailureHeader" },
>>>> { WIXSTDBA_CONTROL_FAILURE_SETUP_HEADER, L"FailureSetupHeader" },
>>>> { WIXSTDBA_CONTROL_FAILURE_UNINSTALL_HEADER,
>>>> L"FailureUninstallHeader" },
>>>>
>>>> The in OnChangeState is where I set the correct string
>>>>
>>>>
>>>> -Original Message-
>>>> From: Bruce Cran [mailto:br...@cran.org.uk]
>>>> Sent: August-28-13 2:26 AM
>>>> To: General discussion for Windows Installer XML toolset.
>>>> Subject: Re: [WiX-users] Add text to final window in burn
>>>> bootstrapper/installer
>>>>
>>>> On 28/08/2013 06:07, Blair Murri wrote:
>>>>> As I understand it, page "Success" will be shown whenever the result of
>>>>> bundle application is successful but not when a failure occurs (when
>>>>> instead the "Failure" page will be shown). So, successful install,
>>>>> successful removal, successful modification, etc.
>>>>> If you can set bundle properties you can use that property's value as
>>>>> your text, maybe...
>>>>
>>>> There was a discussion on wix-devs about this a few months ago: the
>>>> WixStdBA bootstrapper needs changed
Re: [WiX-users] Add text to final window in burn bootstrapper/installer
Okay, I can submit it.
--
Bruce
Sent from my iPhone
On 28 Aug 2013, at 18:13, Steven Ogilvie wrote:
> You want me to make the change for 3.8 or your going to make the change?
>
> I can send you my code for the BA if you want :)
>
> -Original Message-
> From: Bruce Cran [mailto:br...@cran.org.uk]
> Sent: August-28-13 12:34 PM
> To: afor...@cmu.edu; General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Add text to final window in burn
> bootstrapper/installer
>
> Yes that was for Steven: he's made exactly the same changes I was hoping to
> get around to making, and I'd like to see them get into WiX 3.8 if possible.
>
> --
> Bruce
>
> Sent from my iPhone
>
> On 28 Aug 2013, at 16:52, "Alain Forget" wrote:
>
>> I hope that's directed at Steven, because I don't know what that means (and
>> I have yet to figure out where and how to modify .wxl files).
>>
>> Alain
>>
>> -Original Message-
>> From: Bruce Cran [mailto:br...@cran.org.uk]
>> Sent: Wednesday, August 28, 2013 11:39 AM
>> To: General discussion for Windows Installer XML toolset.
>> Subject: Re: [WiX-users] Add text to final window in burn
>> bootstrapper/installer
>>
>> Could you sent a pull request to integrate this change upstream please?
>>
>> --
>> Bruce Cran
>>
>> Sent from my iPhone
>>
>> On 28 Aug 2013, at 14:28, Steven Ogilvie wrote:
>>
>>> Yes exactly
>>>
>>> BA is using the same property for Setup/Uninstall for the
>>> success/failure string
>>>
>>> I fixed this by changing the code in BA and adding a few extra string
>>> properties in the theme wxl file Setup
>>> Successful Setup
>>> Successful Uninstall
>>> Successful Setup Failed
>>> Setup Failed >> Id="FailureUninstallHeader">Uninstall Failed
>>>
>>> BA:
>>>
>>> { WIXSTDBA_CONTROL_SUCCESS_HEADER, L"SuccessHeader" },
>>> { WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER, L"SuccessSetupHeader" },
>>> { WIXSTDBA_CONTROL_SUCCESS_UNINSTALL_HEADER,
>>> L"SuccessUninstallHeader" },
>>>
>>> { WIXSTDBA_CONTROL_FAILURE_HEADER, L"FailureHeader" },
>>> { WIXSTDBA_CONTROL_FAILURE_SETUP_HEADER, L"FailureSetupHeader" },
>>> { WIXSTDBA_CONTROL_FAILURE_UNINSTALL_HEADER,
>>> L"FailureUninstallHeader" },
>>>
>>> The in OnChangeState is where I set the correct string
>>>
>>>
>>> -Original Message-
>>> From: Bruce Cran [mailto:br...@cran.org.uk]
>>> Sent: August-28-13 2:26 AM
>>> To: General discussion for Windows Installer XML toolset.
>>> Subject: Re: [WiX-users] Add text to final window in burn
>>> bootstrapper/installer
>>>
>>> On 28/08/2013 06:07, Blair Murri wrote:
>>>> As I understand it, page "Success" will be shown whenever the result of
>>>> bundle application is successful but not when a failure occurs (when
>>>> instead the "Failure" page will be shown). So, successful install,
>>>> successful removal, successful modification, etc.
>>>> If you can set bundle properties you can use that property's value as your
>>>> text, maybe...
>>>
>>> There was a discussion on wix-devs about this a few months ago: the
>>> WixStdBA bootstrapper needs changed to allow better text on the 'success'
>>> pages. In particular, people have complained to me about the fact that
>>> when uninstall completes it reports "Setup Success".
>>>
>>> --
>>> Bruce Cran
>>>
>>> -
>>> - 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=58040911&iu=/4140/ostg.
>>> clktrk ___
>>> WiX-users mailing list
>>> WiX-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>>
>>> -
>>> - Lea
Re: [WiX-users] Add text to final window in burn bootstrapper/installer
Yes that was for Steven: he's made exactly the same changes I was hoping to get
around to making, and I'd like to see them get into WiX 3.8 if possible.
--
Bruce
Sent from my iPhone
On 28 Aug 2013, at 16:52, "Alain Forget" wrote:
> I hope that's directed at Steven, because I don't know what that means (and I
> have yet to figure out where and how to modify .wxl files).
>
> Alain
>
> -Original Message-
> From: Bruce Cran [mailto:br...@cran.org.uk]
> Sent: Wednesday, August 28, 2013 11:39 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Add text to final window in burn
> bootstrapper/installer
>
> Could you sent a pull request to integrate this change upstream please?
>
> --
> Bruce Cran
>
> Sent from my iPhone
>
> On 28 Aug 2013, at 14:28, Steven Ogilvie wrote:
>
>> Yes exactly
>>
>> BA is using the same property for Setup/Uninstall for the success/failure
>> string
>>
>> I fixed this by changing the code in BA and adding a few extra string
>> properties in the theme wxl file
>> Setup Successful
>> Setup Successful
>> Uninstall Successful
>> Setup Failed
>> Setup Failed
>> Uninstall Failed
>>
>> BA:
>>
>> { WIXSTDBA_CONTROL_SUCCESS_HEADER, L"SuccessHeader" },
>> { WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER, L"SuccessSetupHeader" },
>> { WIXSTDBA_CONTROL_SUCCESS_UNINSTALL_HEADER, L"SuccessUninstallHeader" },
>>
>> { WIXSTDBA_CONTROL_FAILURE_HEADER, L"FailureHeader" },
>> { WIXSTDBA_CONTROL_FAILURE_SETUP_HEADER, L"FailureSetupHeader" },
>> { WIXSTDBA_CONTROL_FAILURE_UNINSTALL_HEADER, L"FailureUninstallHeader" },
>>
>> The in OnChangeState is where I set the correct string
>>
>>
>> -Original Message-
>> From: Bruce Cran [mailto:br...@cran.org.uk]
>> Sent: August-28-13 2:26 AM
>> To: General discussion for Windows Installer XML toolset.
>> Subject: Re: [WiX-users] Add text to final window in burn
>> bootstrapper/installer
>>
>> On 28/08/2013 06:07, Blair Murri wrote:
>>> As I understand it, page "Success" will be shown whenever the result of
>>> bundle application is successful but not when a failure occurs (when
>>> instead the "Failure" page will be shown). So, successful install,
>>> successful removal, successful modification, etc.
>>> If you can set bundle properties you can use that property's value as your
>>> text, maybe...
>>
>> There was a discussion on wix-devs about this a few months ago: the WixStdBA
>> bootstrapper needs changed to allow better text on the 'success' pages. In
>> particular, people have complained to me about the fact that when uninstall
>> completes it reports "Setup Success".
>>
>> --
>> Bruce Cran
>>
>> --
>> 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=58040911&iu=/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=58040911&iu=/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.double
Re: [WiX-users] Add text to final window in burn bootstrapper/installer
Could you sent a pull request to integrate this change upstream please?
--
Bruce Cran
Sent from my iPhone
On 28 Aug 2013, at 14:28, Steven Ogilvie wrote:
> Yes exactly
>
> BA is using the same property for Setup/Uninstall for the success/failure
> string
>
> I fixed this by changing the code in BA and adding a few extra string
> properties in the theme wxl file
> Setup Successful
> Setup Successful
> Uninstall Successful
> Setup Failed
> Setup Failed
> Uninstall Failed
>
> BA:
>
> { WIXSTDBA_CONTROL_SUCCESS_HEADER, L"SuccessHeader" },
>{ WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER, L"SuccessSetupHeader" },
>{ WIXSTDBA_CONTROL_SUCCESS_UNINSTALL_HEADER, L"SuccessUninstallHeader" },
>
> { WIXSTDBA_CONTROL_FAILURE_HEADER, L"FailureHeader" },
>{ WIXSTDBA_CONTROL_FAILURE_SETUP_HEADER, L"FailureSetupHeader" },
>{ WIXSTDBA_CONTROL_FAILURE_UNINSTALL_HEADER, L"FailureUninstallHeader" },
>
> The in OnChangeState is where I set the correct string
>
>
> -Original Message-
> From: Bruce Cran [mailto:br...@cran.org.uk]
> Sent: August-28-13 2:26 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Add text to final window in burn
> bootstrapper/installer
>
> On 28/08/2013 06:07, Blair Murri wrote:
>> As I understand it, page "Success" will be shown whenever the result of
>> bundle application is successful but not when a failure occurs (when instead
>> the "Failure" page will be shown). So, successful install, successful
>> removal, successful modification, etc.
>> If you can set bundle properties you can use that property's value as your
>> text, maybe...
>
> There was a discussion on wix-devs about this a few months ago: the WixStdBA
> bootstrapper needs changed to allow better text on the 'success' pages. In
> particular, people have complained to me about the fact that when uninstall
> completes it reports "Setup Success".
>
> --
> Bruce Cran
>
> --
> 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=58040911&iu=/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=58040911&iu=/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=58040911&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Add text to final window in burn bootstrapper/installer
On 28/08/2013 06:07, Blair Murri wrote: > As I understand it, page "Success" will be shown whenever the result of > bundle application is successful but not when a failure occurs (when instead > the "Failure" page will be shown). So, successful install, successful > removal, successful modification, etc. > If you can set bundle properties you can use that property's value as your > text, maybe... There was a discussion on wix-devs about this a few months ago: the WixStdBA bootstrapper needs changed to allow better text on the 'success' pages. In particular, people have complained to me about the fact that when uninstall completes it reports "Setup Success". -- Bruce Cran -- 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=58040911&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn, signature verification and failure on Vista
I recently discovered the certificate auto-download feature in Vista/2008 when I found that our installer (which uses Burn) fails due to an authenticode verification error when the machine isn't connected to the Internet. It seems that when Burn asks Windows to check the signature, if the root certificate is missing (which it will be if it's not been asked to check before) Windows downloads it from Microsoft. If it can't, verification fails and so does the installation. What I'm wondering is if this is only something likely to happen on test systems - in production is there some other way Windows is likely to have the updated certificates? Or, should I remove the signature on the installer and MSI file to avoid this problem? Or is there a way to ask Burn to skip the verification step? -- Bruce Cran -- 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=58040911&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn uninstalls product instead of upgrading it
On 23/08/2013 21:58, Rob Mensching wrote: > Might be related to: http://wixtoolset.org/issues/3643/ Thanks, that was the problem. -- Bruce -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [Wix]: Create silent MSI using Wix
On 23/08/2013 15:20, Alain Forget wrote: > Don't WiX-built MSIs have no UI by default? > > See the second paragraph of > http://wix.tramontana.co.hu/tutorial/user-interface > > So just follow the steps of the Getting Started tutorial, and don't do > anything in the UI section? I think there's a single noninteractive dialog that pops up that I suspect you can't avoid other than by using /quiet. -- Bruce -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn uninstalls product instead of upgrading it
I seem to have managed to get Burn rather confused. I have an MSI
package with new product and upgrade codes in version 2.0 due to
different builds being produced. I ask Windows Installer (in the MSI) to
upgrade from the previous one with:
Snippet
NOT OTHER_PRODUCT_INSTALLED
However, when I run the installer, Burn logs:
Detected related bundle: {BUNDLE_GUID}, type: Upgrade, scope:
PerMachine, version: 1.0.0, operation: MajorUpgrade
Detected related package: {OLD_PRODUCT_CODE}, scope: PerMachine,
version: 1.0.0, language: 0 operation: MajorUpgrade
Detected related package: {OLD_PRODUCT_CODE}, scope: PerMachine,
version: 1.0.0, language: 0 operation: Downgrade
Detected package: Product.msi, state: Obsolete, cached: None
...
Planned package: Product.msi, state: Obsolete, default requested: None,
ba requested: None, execute: None, rollback: None, cache: No, uncache:
No, dependency: None
Planned related bundle: {BUNDLE_GUID}, type: Upgrade, default requested:
Absent, ba requested: Absent, execute: Uninstall, rollback: Install,
dependency: None
...
It then proceeeds to uninstall the product but leave the new version in
Add/Remove Programs.
Any idea what I'm doing wrong?
--
Bruce Cran
--
Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resources for efficient Application Performance Management.
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Win8.1 + DIFx problem...
Have you filed a bug report with Microsoft? -- Bruce Cran Sent from my iPhone On 16 Jul 2013, at 13:27, "Gonzalez, John" wrote: > I have the same, or similar, issue. It is not expected and showed up around > the 9419 build release. Currently have no ETA of a fix. > > Thanks, > John > > > -Original Message- > From: Robert Randall [mailto:robert.r.rand...@gmail.com] > Sent: Tuesday, July 16, 2013 12:03 PM > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] Win8.1 + DIFx problem... > > I have a device driver install which is working just fine. However, I'm > getting different behavior on Win8.1 compared to the previous releases of > Windows (Vista, Win7, Win8). > > On the previous releases of Windows, removing the MSI package from the > Control Panel->Programs and Features results in the device driver being > removed from the driver store. It also results in the replacement of the > active drivers instances with the nul device driver. I don't know if this is > default DIFx behavior or something that WiX is asking DIFx to do for me. > > On Win8.1, the driver package is removed from the driver store but the driver > instances are not being changed in any way. > > Is this expected behavior? > > I'll do some digging and see if DIFx is installing the nul driver based on > the DIFx action or if WiX is doing it just to be kind (and yes, it is kind of > WiX). > > Best regards, > Robert. > > -- > Robert Randall | robert.r.rand...@gmail.com > -- > See everything from the browser to the database with AppDynamics Get > end-to-end visibility with application monitoring from AppDynamics Isolate > bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Windows updates
On 12/07/2013 10:56, Pally Sandher wrote: > Question is if these machines don't have internet access, why is keeping them > up to date an issue? One problem with machines that don't have Internet access is that installers which are Authenticode-signed won't install unless the root certificate has already been installed - Windows tries to automatically download it. On a plain Server 2008 machine for example installation fails if it has never been connected to the Internet because the signature can't be verified. -- Bruce Cran -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn: installer doesn't restart after reboot when variables are specified on cmdline
It appear there's a bug in WiX 3.8 that causes the bootstrapper not to restart installation after a reboot (at least on Server 2003 x64) if variables are specified on the command line. For example if I run: ProductNameSetup.exe /passive The the system will reboot and installation will complete afterwards. However, with: ProductNameSetup.exe /passive DESKTOP_SHORTCUT=0 Where DESKTOP_SHORTCUT is defined as: the system will reboot but the installer doesn't run again. Running it manually causes the progress bar to appear immediately and installation continues, so it seems it's just missing the RunOnce entry to start it after login. -- Bruce Cran -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] File version always 1.0.0.0
On 01/06/2013 16:40, Alain Forget wrote: >Name="MyBundle Installer" > UpgradeCode="MY-GUID" > Version="$(var.PRODUCTVERSION)" > Copyright="Copyright © Us" > IconSourceFile="lib/logo.ico" > Manufacturer="Us" > Condition="Privileged AND (VersionNT = v6.1 OR VersionNT = v6.2)" > DisableModify="yes" Off-topic, but Windows Blue will be a free upgrade from Windows 8 and Server 2012 and will be v6.3 - so using such a restrictive Condition may be a bad idea. -- Bruce Cran -- Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn incorrectly logging 'MajorUpgrade' operation
I'm installing an MSI file via Burn that detects if another product is
installed (that's not included in the bundle). The UpgradeVersion line
has OnlyDetect="yes" so it just puts the result in a property. However,
Burn is logging:
Detected related package: {GUID}, scope: PerMachine, version: a.b.c.d,
language: 0 operation: MajorUpgrade
Shouldn't it be logging 'operation: None'?
--
Bruce Cran
--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] RelatedBundle, 'Detect' action and result
I'm trying to detect products that can't be installed at the same time as ours, and found RelatedBundle's 'Detect' action. However, I can't see a way of getting the result - is there a way to put the result in a variable? -- Bruce Cran -- Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] REMOVE ME PLEASE
On 24/04/2013 10:01, Kagiso Seboni wrote: > Please remove me from the Mailing List You can unsubscribe via the mailing list interface at: https://lists.sourceforge.net/lists/listinfo/wix-users -- Bruce Cran -- Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX vs NSIS
On 17/04/2013 14:39, Alain Forget wrote: > 3) Finally, throw in the fact that NSIS hasn't been supported since 2009, > while WiX is a very active and supportive open-source community. Even > further, if he wants some time down the line, it would be possible to contact > a consulting company to outsource the WiX installer infrastructure and add > functionality to WiX, since one of the founders of WiX (*cough* Rob *cough, > cough*) will soon be providing such a service. I'm not sure this is really correct: there haven't been any releases on the main site since 2009, but http://nsis.svn.sourceforge.net/viewvc/nsis/NSIS/trunk/ shows that work is going on, and the Unicode version at http://www.scratchpaper.com/ had a release last year. -- Bruce Cran -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX vs NSIS
On 16/04/2013 23:44, Nick Miller wrote: > My company is evaluating two different Windows installer solutions, WiX and > Nullsoft installer (NSIS). I was wondering if anyone has had experience with > both, and could weigh in on the pros and cons, benefits, limitations, etc. You might think XML in WiX is bad, but this is the sort of code you get in NSIS unless you use one of the libraries (from http://nsis.sourceforge.net/CharStrip_%26_StrStrip:_Remove_character_or_string_from_another_string): Exch $R0 #char Exch Exch $R1 #in string Push $R2 Push $R3 Push $R4 StrCpy $R2 -1 IntOp $R2 $R2 +1 StrCpy $R3 $R1 1 $R2 StrCmp $R3 "" +8 StrCmp $R3 $R0 0 -3 StrCpy $R3 $R1 $R2 IntOp $R2 $R2 +1 StrCpy $R4 $R1 "" $R2 StrCpy $R1 $R3$R4 IntOp $R2 $R2 -2 Goto -9 StrCpy $R0 $R1 Pop $R4 Pop $R3 Pop $R2 Pop $R1 -- Bruce Cran -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Can't install Wix 3.8 on Windows XP
On 11/04/2013 14:23, Sergey Yukhno wrote: > Can't install Wix 3.8 on Windows XP. > "Wix38.exe is not valid Win32 application." That looks like a problem with the VS 2012 settings. I thought we'd fixed them all - what build are you trying to install? -- Bruce Cran -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] system32 install issue
On 07/04/2013 16:40, David Steadman wrote: > I need to install these modules to the system32 directory .. how do > you recommend doing this seeing it is a 64bit installer..? On 64-bit machines the system32 directory contains 64-bit binaries, and is accessible using the System64Folder property; the syswow64 folder contains 32-bit binaries. -- Bruce Cran -- Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Sign the msi
On 28/03/2013 07:21, Karkare,Aparna wrote: > Can someone tell me how to sign the WiX msi generating project with a key > (.snk) file? > I do not see 'Signing' tab under project properties unlike other VS projects. You can't use a strong name keypair to sign .msi files since they're not .NET assemblies - instead you'd need to use a .pfx Authenticode certificate, by editing the .wixproj file. You can do this by adding SignMsi and SignCabs targets as per http://wix.sourceforge.net/manual-wix3/insignia.htm . You can't use the MSBuild SignFile task (http://msdn.microsoft.com/en-us/library/ms164304.aspx) because it doesn't work with .cab files (d'oh!). I'd recommend adding a description and timestamp URL: e.g.: http://timestamp.globalsign.com/scripts/timstamp.dll /d "%(SignMsi.FullPath)"" /> Or, if you really want it to auto-select which certificate to use! http://timestamp.globalsign.com/scripts/timstamp.dll /d "%(SignMsi.FullPath)"" /> The timestamp URL might be comodo, verisign, globalsign etc. depending on who your Authenticode certificate was purchased from. -- Bruce Cran -- Own the Future-Intel® Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Question about conditional statements in elements
On 22/03/2013 17:24, Daniel Madill wrote:
> Hi Alain,
>
> In general, Product ID="*" is a good thing. Each new build should generate a
> new product code because it typically means you've made changes to the
> product (i.e. made a new version). If you want to test the Maintenance dialog
> then run the same MSI (without rebuilding it!) twice.
>
> When you use the element in WiX it handles removing the old
> version and installing the new version when you upgrade. Hence, in many cases
> the Welcome dialog is entirely appropriate because the user experience on
> upgrade or new installation from a UI perspective is similar. The
> MajorUpgrade element has options for displaying messages if the user tries to
> upgrade or downgrade and should not be allowed, etc. if that's what you need.
> If you want something more complicated on upgrade then you will have to do a
> little more work.
Microsoft says the Product Code should identify a particular release
(http://msdn.microsoft.com/en-gb/library/windows/desktop/aa370854(v=vs.85).aspx):
"The ProductCode property is a unique identifier for the particular
product release, represented as a string GUID, for example
"{12345678-1234-1234-1234-123456789012}"."
That seems to imply it shouldn't be changed from one build to the next
but only when the major, minor or revision fields are changed.
--
Bruce Cran
--
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_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to pass some arguments during major upgrade to obsoleted msi to prevent removing RegistryKey
On 22/03/2013 11:26, AK wrote: > Is some way available to pass some custom arguments to obsoleted msi? One possible hack is to schedule RemoveExistingProducts after InstallExecute and to add an empty component with the same Guid as the existing one. That way, Windows Installer won't remove the key. -- Bruce Cran -- 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_d2d_mar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Building Wix 3.6
On 19/03/2013 12:31, Bruce Cran wrote: > Clone https://hg.codeplex.com/wix : > > hg clone https://hg.codeplex.com/wix -b wix38 Sorry ignore most of that - those instructions are for WiX 3.8 not 3.6. To get 3.6 you just need to use "-b wix36" when cloning and follow the instructions in the documentation. -- Bruce Cran -- 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_d2d_mar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Building Wix 3.6
On 13/03/2013 20:13, jeamis wrote: > So how do I enlist to the Mercurial repository? All I want to do is > compile burn. I want to confirm our static analysis and debugging. > > Any direction is appreciated. Clone https://hg.codeplex.com/wix : hg clone https://hg.codeplex.com/wix -b wix38 To create a build that can be installed on different machines you'll need Visual Studio 2008, 2010 and 2012 along with the Visual Studio 2008, 2010 and 2012 SDKs from the Extensibility Center. You also need HTML Help SDK from http://msdn.microsoft.com/en-gb/library/windows/desktop/ms670169(v=vs.85).aspx, Sandcastle and Sandcastle Help File Builder from http://shfb.codeplex.com/ . Create a strong name keypair: sn -k wix.snk sn -p wix.snk wix.pub sn -tp wix.pub Copy the public key and add new InternalsVisibleTo lines in: src\Votive\sconce\Properties\AssemblyInfo.cs src\Votive\sdk_vs2010\common\source\csharp\project\AssemblyInfo.cs src\Votive\sdk_vs2010\common\source\csharp\project\attributes.cs Then run: msbuild /p:VisualStudioVersion="11.0" /p:OFFICIAL_WIX_BUILD= The binaries will be put in build\debug. You should also be able to open src\Burn.sln and build the projects individually. -- Bruce Cran -- 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_d2d_mar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] how to deal with the service removal during upgrade and repair in WIX?
On 07/01/2013 18:34, Wang, Zhongsheng wrote: > > > > > Unless you're setting those yourself, MAJORUPGRADE and MINORUPGRADE won't exist - they're not standard properties. I think you'll want to use 'UPGRADINGPRODUCTCODE' instead. e.g. http://stackoverflow.com/questions/320921/how-to-add-a-wix-custom-action-that-happens-only-on-uninstall-via-msi -- Bruce Cran -- 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_d2d_mar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Platform-specific references (difxapp_x64 etc.)
Does the Visual Studio plugin for WiX 3.7 have logic for selecting the correct platform-specific reference when building both 32-bit and 64-bit configurations so workarounds like http://stackoverflow.com/questions/8713683/installing-32-64-bit-drivers-with-wix are unnecessary now? For example I have to choose to reference either difxapp_x86 _or_ difxapp_x64, but building a 32-bit msi with difxapp_x64 referenced seems to work. -- Bruce Cran -- 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_d2d_mar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn: hang after "Apply Complete" on Vista
On 12/03/2013 20:49, Rob Mensching wrote: > Is the task scheduler enabled and running? If not, try that and see if the > problem goes away. Unfortunately it is already running. I'll do some more debugging to see what's going on. -- Bruce > On Tue, Mar 12, 2013 at 12:32 PM, Bruce Cran wrote: > >> I have a bundle built using WiX 3.7.1224.0 that installs 2 MSI files. It >> works perfectly when run from the desktop on Server 2008 (R1) but when >> run (with /quiet /norestart) from a service which is logged on as >> Administrator it installs the last package, logs "Apply Complete, >> result: 0x0, restart: None, ba requested restart: No" and then always >> hangs, with all 3 threads stuck in GetMessageW. It works with 2008R2: >> is there a known bug with Vista/2008R1? -- 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_d2d_mar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn: hang after "Apply Complete" on Vista
I have a bundle built using WiX 3.7.1224.0 that installs 2 MSI files. It works perfectly when run from the desktop on Server 2008 (R1) but when run (with /quiet /norestart) from a service which is logged on as Administrator it installs the last package, logs "Apply Complete, result: 0x0, restart: None, ba requested restart: No" and then always hangs, with all 3 threads stuck in GetMessageW. It works with 2008R2: is there a known bug with Vista/2008R1? -- Bruce Cran -- 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_d2d_mar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Debugging VS2012 plugin crashes?
I created an MSI project where if I go into the Build tab in the project settings and try to change anything, Visual Studio 2012 crashes. Is there any way of finding out what's going wrong? -- Bruce Cran -- 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_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] "This collection is read-only" error in Visual Studio 2012
I've come across a few problems with the WiX 3.7 plugin with Visual Studio 2012. Today I tried to add a reference to a bootstrapper project by double-clicking on the project name was told "This collection is read-only"; trying it again but clicking the "Add" button worked. Has anyone else come across issues like this? -- Bruce -- 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_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Mail from Rob marked as spam
On 20/02/2013 17:15, Bernd wrote: > I don't know if this is specific to my email client (Thunderbird with > SpamAssassin as external filter) but a lot of mail answered by Rob > Mensching gets marked as spam. > Just thought I'd let you know, if it helps... It's being marked as spam by sourceforge: my mail server gives it a negative score. It might be due to the SPF failure recorded in the headers: Received-SPF: fail (sog-mx-3.v43.ch3.sourceforge.com: domain of robmensching.com does not designate 184.173.107.18 as permitted sender) client-ip=184.173.107.18; envelope-from=r...@robmensching.com; helo=allium.arvixe.com; -- Bruce Cran -- 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_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bundle registered in ARP after prerequesitesare installed
On 13/02/2013 08:01, Ogrodowski, Sabine (ehem. Frauenhoffer) wrote: > Thank you for your reply. I know, that it can be that simple to use the > WixNetFxExtension. Unfortunately I need to also install on machines that have > no internet access and so I can't use it. That's why I copied some part from > the WixNetFxExtension and adjusted it to use the .Net exe I put on the disk. > > Nonetheless I tried your approach. The result is the same: If I install .Net > an ARP entry for my bundle is created and if I cancel the custom bootstrapper > and start it again, it comes up in maintenance mode because > WixBundleInstalled is 1. > > I even tried with the WiX v3.7 setup itself and it showed the same behavior. I'm fairly sure this is a known bug, with a ticket on Sourceforge. I found a similar issue today: if I run 2 copies of the installer, the second as the first is in the process of installing, the 2nd will fail and cause no ARP entry to be created once the first finishes. -- Bruce -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Creating a bootstrap application and need a more simple UI
On 11/02/2013 20:53, Neil Sleightholm wrote: > You might find this useful: http://wixextba.codeplex.com/. Take a look at the > example Bundle7.wxs it is a pretty basic UI and the dialog is designed to be > the same size as the WiX MSI UI. > > You might also want to consider writing your UI in burn rather than using the > MSI UI. Neil, From an earlier message: "My issue isn't the installer UI but rather the bootstrapper UI (If that makes sense)." So this _is_ about the Burn UI. -- Bruce Cran -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Creating a bootstrap application and need a more simple UI
On 11/02/2013 20:43, joshh wrote: > That is really close to what I am looking for. The only improvement I can > think of would be to reduce the size and have a short message. And maybe a > background logo like the wix ui can have. I agree - it's a bit bare without the eula. -- Bruce Cran -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Creating a bootstrap application and need a more simple UI
On 11/02/2013 20:12, joshh wrote: > I have done this but the UI is too complex. The big problem is that it > forces the user to accept a license and this is not needed at this point. I > would like for the bootstrapper to just load and start installing the chain > of packages or give a simple "Install" button. >From http://neilsleightholm.blogspot.co.uk/2012/05/wix-burn-tipstricks.html all you need to do is use the WixStandardBootstrapperApplication.HyperlinkLicense BA and set WixStdbaLicenseUrl to be empty. -- Bruce Cran -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Redisplay MSI's UI when Bootstrapper is run a second time
You can't display a feature tree, but it does support adding checkboxes to the options page which can be used to select features. -- Bruce Cran Sent from my iPhone On 31 Jan 2013, at 17:54, Karl Werner wrote: > Can you have the wix standard bootstrapper prompt the user for feature > selection? I haven't seen it do that . . . > > On Thu, Jan 31, 2013 at 11:05 AM, Rob Mensching wrote: > >> You can modify feature states via the BootstrapperApplication. >> >> >> On Thu, Jan 31, 2013 at 8:44 AM, Karl Werner >> wrote: >> >>> To close the loop on this, I ended up doing the following: >>> >>> 1) Reverting to the Wix Standard Bootstrapper. (There is probably a way >> to >>> get my custom bootstrapper to work, but I exhausted enough time trying to >>> figure it out. Somehow the Wix Standard Bootstrapper knows what mode to >> go >>> into early in the process and I never found it in the code) >>> 2) Providing a name for Bundle so that it now registers in ARP. >>> 3) Setting the MsiPackage to Visible="no" so they no longer register in >>> ARP. >>> 4) Having different Package and Upgrade Codes for 32 vs. 64-bit MSIs so >>> that the various entry points (namely Repair) all work correctly. >>> >>> The functionality I lose is the ability to modify msi features after >>> install. I'd really like a way to have the MSI registered in ARP and not >>> the bundle, but any time I did that there were negative side effects when >>> the bootstrapper was launched a second time. >>> >>> Wish list item ;-) >>> >>> Thanks for the responses on this item! >>> >>> Karl >>> >>> On Wed, Jan 30, 2013 at 7:47 AM, Karl Werner >>> wrote: >>> >>>> Do basically there is no way to simulate the old bootstrapper from the >>> old >>>> vdproj setup projects? It would be nice if we could configure for this >>>> behavior. I would expect many other shops would want the same behavior >> . >>> . . >>>> >>>> Maybe something like an attribute on MSIPackage that is equivalent to >>>> "always execute if InstallCondition is true", then show the UI if >>>> DisplayInternalUI is "yes"... >>>> >>>> I'll log a feature request ... >>>> >>>> Karl >>>> >>>> >>>> On Tue, Jan 29, 2013 at 10:02 PM, Bob Arnson >> wrote: >>>> >>>>> On 29-Jan-13 16:10, Karl Werner wrote: >>>>>> However, still stuck on the original problem -> How can I get the >>> MSI's >>>>> UI >>>>>> invoked on the second run of the bootstrapper. >>>>> You can't. Burn needs to know the operation being performed which it >>>>> can't if the operation is determined during the execution of the >>> package. >>>>> >>>>> -- >>>>> sig://boB >>>>> http://joyofsetup.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_d2d_jan >>>>> ___ >>>>> 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_d2d_jan >>> ___ >>> 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_d2d_jan >> ___ >> 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_d2d_jan > ___ > 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_d2d_jan ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Set font color in WiXUIExtension UIs
Isn't it just a case of overriding the strings in an additional wxl file? I've done that when using dark backgrounds. -- Bruce Cran Sent from my iPhone On 31 Jan 2013, at 17:51, Rob Mensching wrote: > It is possible. You can create your own UI. I guess I disagree that it > should be a simple, basic thing provided in the default WixUI. I honestly > thought the WixUI design was to make the text color "almost black" but not > quite black such that high contrast wouldn't pick it up and flip it. Maybe > that wasn't implemented... or maybe it was implemented but someone didn't > bother to contribute it back to the community. > > > > On Thu, Jan 31, 2013 at 9:29 AM, The Ouizard wrote: > >> I've posted this twice already with no response; does no one have any idea >> how to solve this? >> >> It doesn't seem outlandish to want to support users who don't use the >> default display configuration. Setting/overriding a font color >> seems like it should be a simple and basic thing, but I haven't found >> anything in the documentation, the mailing list archives, or >> through searches on how to do it. >> >> If this truly isn't possible, maybe it should be posted as a feature >> request? >> >> -Original Message- >> From: The Ouizard [mailto:the.ouiz...@gmail.com] >> Sent: January 17, 2013 17:26 >> To: 'wix-users@lists.sourceforge.net' >> Subject: RE: Text accessibility >> >> How can I use the provided WiXUIExtension interfaces (such as WiXUI_Mondo >> or WiXUI_Minimal) but change the text colour to force it >> to be black? >> >> Context: >> >> Some users set their Personalise display settings to high-contrast white >> text on black background. In the provided WiX installer >> UIs, the result is white text (taking the system setting, I assume), and >> putting it on the default white background, making the text >> illegible. >> >> So it seems the simplest solution would be to purposefully make the text >> black no matter what, so it is always legible on the white >> background. Yes, this will annoy said users, but not as much as not being >> able to read the installer text at all. A second, more >> elegant but more complicated, solution would be to somehow detect the >> system's default font colour, and set the background to the >> opposite. >> >> Any suggestions would be appreciated. Thank you. >> >> >> >> -- >> 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_d2d_jan >> ___ >> 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_d2d_jan > ___ > 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_d2d_jan ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Repairs and runtimes
On 16/01/2013 09:26, Rob Hamflett wrote: > Doesn't this just bring back DLL Hell? It seems that we have to > completely abandon using merge modules for runtime deployment. How is a > user performing a command line installation or repair supposed to know > whether or not it's safe to use the 'a' option for file replacement? > They probably don't know (and have no easy way to find out) whether or > not the installer contains the runtime. It seems like the only safe > option is to copy the runtime DLLs into your application's folder. Sure > you could use the redistributable exe and then link to the system ones, > but given that these could be accidentally downgraded, that's not really > an option. Deploying the DLLs locally doesn't get you any of the > benefits when the shared DLLs are updated, but at least they're less > likely to be downgraded without your knowledge. Yes, it brings back DLL hell - but isn't the answer not to use 'a' for exactly this reason? -- Bruce Cran -- Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery and much more. Keep your Java skills current with LearnJavaNow - 200+ hours of step-by-step video tutorials by Java experts. SALE $49.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122612 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Repairs and runtimes
On 15/01/2013 15:42, Rob Hamflett wrote: > Aren't security patches implemented by redirecting the > loader to the new assemblies? It seems strange having a system where > the security of potentially hundreds of programs could be reduced by a > command line typo. >From http://social.msdn.microsoft.com/Forums/en/vcgeneral/thread/4eba883d-d14b-4fc5-912d-aaafcf0bffab : "Visual C++ libraries no longer depend on manifests and are no longer installed in the WinSxS folder. Normally, the higher minor version have compatibility with the lower one. Once Microsoft provides a hotfix, which is a patched version of the affected library, Microsoft automatically updates library files that are centrally-deployed (installed in System32 Directory)." -- Bruce Cran -- Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only - learn more at: http://p.sf.net/sfu/learnmore_122512 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Identical left and right sub-expressions in plan.cpp - bug?
In plan.cpp:1166 there's a line of code with identical left and right expressions. Is this a bug? // If we are going to take any action on this package, add progress for it. if (BOOTSTRAPPER_ACTION_STATE_NONE != pRelatedBundle->package.execute || BOOTSTRAPPER_ACTION_STATE_NONE != pRelatedBundle->package.execute) -- Bruce Cran -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122412 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Adding/deleting project configurations
Is adding or deleting project configurations in Visual Studio supposed to work (in WiX 3.7)? With VS2010 when I try and add or remove a configuration to the WiX project in the solution's Configuration Manager it doesn't give any error message but no changes are applied. -- Bruce Cran -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122912 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Transition from InstallShield to WiX
On 29/12/2012 14:12, Rob Mensching wrote: > Visualt Studio and Windows SDK are two that I know about off the top of my > head. WiX v3.6 is still relatively young so I expect more will show in time. Also the Windows Driver Kit 8.0. The WDF CoInstaller package is just a plain WiX msi (with the red UI). -- Bruce Cran -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122912 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WDK 8.0, Driver Verifier and XP/2003 compatiblity
On 19/12/2012 21:09, Bruce Cran wrote: > I know this isn't recommended, but is there some incompatibility > between WDK 8.0 and XP/2003 that prevents drivers running correctly > with Driver Verifier? > We're finding that when Driver Verifier is enabled our driver gets so > far initializing and then any memory allocation calls end up calling > ExFreePoolWithTag and the driver hangs in RtlpUnwindPrologue (it runs > fine without DV enabled). The system's still active, but the driver > just never gets any further. > Sorry, I sent this to the wrong mailing list - please ignore. -- Bruce Cran -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WDK 8.0, Driver Verifier and XP/2003 compatiblity
I know this isn't recommended, but is there some incompatibility between WDK 8.0 and XP/2003 that prevents drivers running correctly with Driver Verifier? We're finding that when Driver Verifier is enabled our driver gets so far initializing and then any memory allocation calls end up calling ExFreePoolWithTag and the driver hangs in RtlpUnwindPrologue (it runs fine without DV enabled). The system's still active, but the driver just never gets any further. -- Bruce Cran -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Feature or Chained MSI?
On 05/12/2012 15:15, Rob Mensching wrote: > I would definitely consider using a Bundle for your scenario. I believe the > world is moving (has moved?) to a place where .msi files are building > blocks stacked together and wrapped with a bootstrapper (Burn Bundles in > WiX toolset). You do need to think about the problem a little differently > when using Bundles because you'll get many more degrees of freedom which > may come with a bit extra work (particularly in the UI department) since > Bundles are still pretty young. Something I've been wondering is how automated deployment is supposed to work. I've not used GPO, but I think it needs a .msi file in order to install an application? -- Bruce Cran -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WixStdBA retry 'cancel' button not working?
On 04/12/2012 15:06, Rob Mensching wrote:
> Can you share a chunk of the log file for that. I expect the issue is the
> automatic retry code on errors is incorrectly catching this scenario.
[07E0:0640][2012-12-03T14:00:33]i301: Applying execute package:
package.msi, action: Install, path: C:\ProgramData\Package
Cache\{guid}v1.0.0.0\package.msi, arguments: ' ALLUSERS="1"
ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7" APPLICATIONFOLDER="C:\Program
Files\Install"'
[07E0:0640][2012-12-03T14:01:12]e000: Error 0x80070643: Failed to
install MSI package.
[07E0:0640][2012-12-03T14:01:12]e000: Error 0x80070643: Failed to
execute MSI package.
[0654:0178][2012-12-03T14:01:12]e000: Error 0x80070643: Failed to
configure per-machine MSI package.
[0654:0178][2012-12-03T14:01:12]w348: Application requested retry of
package: package.msi, encountered error: 0x80070643. Retrying...
[07E0:0640][2012-12-03T14:01:15]i301: Applying execute package:
package.msi, action: Install, path: C:\ProgramData\Package
Cache\{guid}v1.0.0.0\package.msi, arguments: ' ALLUSERS="1"
ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7" APPLICATIONFOLDER="C:\Program
Files\Install"'
[07E0:0640][2012-12-03T14:02:08]e000: Error 0x80070643: Failed to
install MSI package.
[07E0:0640][2012-12-03T14:02:08]e000: Error 0x80070643: Failed to
execute MSI package.
[0654:0178][2012-12-03T14:02:08]e000: Error 0x80070643: Failed to
configure per-machine MSI package.
[0654:0178][2012-12-03T14:02:08]w348: Application requested retry of
package: package.msi, encountered error: 0x80070643. Retrying...
--
Bruce Cran
--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] v3.7.1126.0 on Monday, November 26, 2012
On 03/12/2012 20:16, Neil Sleightholm wrote: > I just tried again with 7-zip and do indeed get the "Unsupported Compression > Method for" error but the files do extract ok - personally I think there is a > bug in the compress code. I get "unsupported compression method" for directories, but none of the files. -- Bruce Cran -- Keep yourself connected to Go Parallel: BUILD Helping you discover the best ways to construct your parallel projects. http://goparallel.sourceforge.net ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WixStdBA retry 'cancel' button not working?
Has anyone else found that the "cancel" button on the error retry dialog in WixStdBA doesn't work (in 3.7 RC)? I find clicking it displays the same error with an OK button before just retrying anyway. The error when this occurs is "Could not access network location". -- Bruce Cran -- Keep yourself connected to Go Parallel: BUILD Helping you discover the best ways to construct your parallel projects. http://goparallel.sourceforge.net ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Extract packages from bootstrapper?
On 30/11/2012 21:39, Steven Ogilvie wrote: > Thanks very much Bruce... > > Do you know if this will be done for 3.7? Since we've had 3.7 RC I suspect not. I suspect it's quite low down the priority list and so would need someone to contribute a patch. -- Bruce Cran -- Keep yourself connected to Go Parallel: TUNE You got it built. Now make it sing. Tune shows you how. http://goparallel.sourceforge.net ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Extract packages from bootstrapper?
On 30/11/2012 21:24, StevenOgilvie wrote: > Can I extract the packages/msi's from the exe for someone using GPO? Currently the only way is using dark.exe - there's a feature request open on the sourceforge tracker to add a /extract switch to WixStdBA so anyone can get a copy of the embedded packages. -- Bruce Cran -- Keep yourself connected to Go Parallel: TUNE You got it built. Now make it sing. Tune shows you how. http://goparallel.sourceforge.net ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX Bootstrapper Bundle creating uninstall shortcut in program files
On 27/11/2012 17:18, rpriest12 wrote: > I am in the same boat - I need the product code. there seem to be several > questions about this for various reasons. Surely the answer can be to troll > the uninstall registry key looking for "Bundle*"? What if you have multiple > applications that installed using Burn? I have two on my box now. Am I > supposed to compare strings? surely exposing the Product Code and allowing > it to be set to something static would be better... You could use the upgrade code instead - there's a BundleUpgradeCode entry in the Uninstall key, though I'm not sure it's documented and so might disappear. -- Bruce Cran -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] wcautil.lib in 3.7 RC: LNK4099 warnings (vc110.pdb not found; linking as if no debug info)
Something seems to have changed with the way wcautil.lib and dutil.lib (at least) are built betwen 3.6 and 3.7 RC - I've started getting warnings like: dutil.lib(strutil.obj) : warning LNK4099: PDB 'vc110.pdb' was not found with 'dutil.lib(strutil.obj)' or at 'C:\Release\vc110.pdb'; linking object as if no debug info wcautil.lib in 3.7 is 528KB vs. 1.5MB in 3.6. What's changed, and should I update my project settings to fix the warning? -- Bruce Cran -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn: won't /layout with reboot pending
I understand the reason for blocking installation if a reboot from a previous installation hasn't occurred, but shouldn't users be able to layout installation files without rebooting? I just found that the VS2012 Update 1 installer required a reboot before it would download the installation files. -- Bruce Cran -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn: associating checkbox with feature installation of specific MSI?
On 13/11/2012 15:49, Rob Mensching wrote: > What about using a Feature/Condition instead? Thanks, that works. -- Bruce Cran -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WixStdBA: options browse dialog doesn't work in Server Core
Should WixStdBA work on Server Core? It mostly seems to, but Options -> Browse isn't functional since Core doesn't have the common dialogs - apparently it can be made to work by adding some flags (http://social.technet.microsoft.com/Forums/en-GB/winservercore/thread/f9f1f6f1-960a-4ddf-94d4-86b7ce3796bb). -- Bruce Cran -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn: FailureRestartText mentions 'rollback'
When a reboot is pending, Burn fails with the message: You must restart your computer to complete the rollback of the software. I'm wondering why it mentions 'rollback' because in this case the reboot is pending following a successful installation of a driver. -- Bruce Cran -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn: associating checkbox with feature installation of specific MSI?
Is there currently any simple way to associate a checkbox with feature installation for a specific MSI? From what I've read the only way would be to do conditional installation with ADDLOCAL MsiProperty's set to the feature name, e.g. -- Bruce Cran -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ 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
Sourceforge cooperated with me now, so I filed a feature request: https://sourceforge.net/p/wix/feature-requests/709/ Daniel E. Bruce > -Original Message- > From: Daniel Bruce [mailto:daniel.br...@prediktor.no] > Sent: 22. oktober 2012 13:00 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Getting started writing a custom Bootstrapper > interface > > > -Original Message- > > From: Igor Brejc [mailto:igor.br...@gmail.com] > > Sent: 20. oktober 2012 20:04 > > To: General discussion for Windows Installer XML toolset. > > Subject: Re: [WiX-users] Getting started writing a custom Bootstrapper > > interface > > > > Hi, > > > > Some more pointers from me. I've implemented a custom managed > > bootstrapper using WinForms. The GUI actually looks pretty much the > > same as the standard MSI setup wizard, but implemented with custom > C# > > code using MVP > > (model-view-presenter) pattern. This enables me to unit-test the > > wizard without actually running the installation. > > > > I've also "hidden" the WiX bootstrapper engine behind an adapter > > interface (I called it IInstallEngine). This way I can run the wizard > > as a "normal" > > Windows Forms application and click through it (again, without the > > need to run the actual Windows installation), since in that mode the > > wizard uses a mocked implementation of IInstallEngine. I just simply > > added the static Main method which has the similar logic to the Run(). > > > > (Note to Rob: perhaps it would be a good idea to change the design of > > the managed bootstrapper so that it works with interfaces instead of > > concrete implementations, this would be really helpful for unit > > testing and simulation). > > I absolutely agree with this point. It would be very helpful to have > interfaces defined for BootstrapperApplication containing the events it > exposes, as well as for the Engine class. It's nigh impossible to do unit > tests on the interface classes without this step. I've created my own, but > that feels kind of hacky. > > I would file a feature request, but the sourceforge website seems to be > throwing Error 500s right now. > > > The wizard has one added feature: a debug window which can be > turned > > on through the command line and displays all the install log messages > > directly in the setup wizard. > > > > The documentation for the managed BS is pretty scarce, so I had to > > look into WiX's source code and do a lot of trials and errors to get > > to this point (and I still have some issues to work through). > > Pretty much what I had to do too. I really hope the documentation > situation is going to improve before the 3.7 release, because right now > it's kind of ridiculous. I feel like I just have wishful thinking and > half-truths > to go on and many times during the development process things broke > because my assumptions (based on what I could glean from source code > and random > postings) were not correct. I'm kind of worrying about what's going to > break next due to something that is not obvious from the source code. > > > Best regards, > > Igor Brejc > > Regards, > Daniel E. Bruce > -- 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
> -Original Message- > From: Igor Brejc [mailto:igor.br...@gmail.com] > Sent: 20. oktober 2012 20:04 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Getting started writing a custom Bootstrapper > interface > > Hi, > > Some more pointers from me. I've implemented a custom managed > bootstrapper using WinForms. The GUI actually looks pretty much the > same as the standard MSI setup wizard, but implemented with custom > C# code using MVP > (model-view-presenter) pattern. This enables me to unit-test the wizard > without actually running the installation. > > I've also "hidden" the WiX bootstrapper engine behind an adapter > interface (I called it IInstallEngine). This way I can run the wizard as a > "normal" > Windows Forms application and click through it (again, without the need > to run the actual Windows installation), since in that mode the wizard > uses a mocked implementation of IInstallEngine. I just simply added the > static Main method which has the similar logic to the Run(). > > (Note to Rob: perhaps it would be a good idea to change the design of > the managed bootstrapper so that it works with interfaces instead of > concrete implementations, this would be really helpful for unit testing > and simulation). I absolutely agree with this point. It would be very helpful to have interfaces defined for BootstrapperApplication containing the events it exposes, as well as for the Engine class. It's nigh impossible to do unit tests on the interface classes without this step. I've created my own, but that feels kind of hacky. I would file a feature request, but the sourceforge website seems to be throwing Error 500s right now. > The wizard has one added feature: a debug window which can be turned > on through the command line and displays all the install log messages > directly in the setup wizard. > > The documentation for the managed BS is pretty scarce, so I had to look > into WiX's source code and do a lot of trials and errors to get to this point > (and I still have some issues to work through). Pretty much what I had to do too. I really hope the documentation situation is going to improve before the 3.7 release, because right now it's kind of ridiculous. I feel like I just have wishful thinking and half-truths to go on and many times during the development process things broke because my assumptions (based on what I could glean from source code and random postings) were not correct. I'm kind of worrying about what's going to break next due to something that is not obvious from the source code. > Best regards, > Igor Brejc Regards, Daniel E. Bruce -- 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
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
Re: [WiX-users] Elevation of Bootstrapper Application
Thank you for your answers, Neil and Rob. I have dabbled with persist="yes" before, and it didn't seem like it worked for me, but I may just have not been doing it correctly. Am I right in assuming that doing a definition like this would cause the variable to persist and when uninstalling it will retain the value it had at the end of the initial installation, with no extra work involved? I would prefer to not do it this way, as doing so would require pushing the responsibility for defining the persisted data into the bundle.wxs, which splits my data in a way I would like to avoid. We use the same MBA with multiple bundle.wxs files (with various subsets of our product suite), so it would make the installers less DRY if we had to define the variables each bundle.wxs needed. However, if it were possible to mark variables for persisting from the MBA, that would be perfectly fine for our solution, as we are right now just persisting certain Burn variables written to during the installation process. Regarding elevation, looking into the problem more seems to indicate that my options are to either put a manifest on our bundle executable, or launch a child process with elevated privileges and communicate data I need handled in an elevated context to that child process (from what I can tell, this is what burn does). Is this correct, or have I missed any simpler ways of elevating? Daniel E. Bruce > -Original Message- > From: Rob Mensching [mailto:r...@robmensching.com] > Sent: 15. oktober 2012 19:14 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Elevation of Bootstrapper Application > > It remembers them for a specific Bundle. There is not currently a > mechanism to get to the state of another Bundle (I think there is a > feature request open to enable that). > > On Mon, Oct 15, 2012 at 10:10 AM, Neil Sleightholm > wrote: > > > >> you can set Variables and mark them Persist='yes' and Burn will > > remember them for you. > > > > Am I correct that it remembers them for Uninstall/Repair but there is > > no way to recall them if you do an upgrade? > > > > Neil > > > > -Original Message- > > From: Rob Mensching [mailto:r...@robmensching.com] > > Sent: 15 October 2012 17:50 > > To: General discussion for Windows Installer XML toolset. > > Subject: Re: [WiX-users] Elevation of Bootstrapper Application > > > > Neil is correct. The BA is not elevated because it does not rollback > > but the package installs do. > > > > If you just want to store settings for your BA, you can set Variables > > and mark them Persist='yes' and Burn will remember them for you. > That > > sounds like it might be more applicable for you anyway. > > > > > > > > -- > > 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 > > > > > > -- > virtually, > >Rob Mensching >http://RobMensching.com LLC > -- > 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 > > ___ > ___ > This email has been scanned by the Symantec Email Security.cloud > service. > For more information please visit http://www.symanteccloud.com > ___ > ___ -- 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
Re: [WiX-users] Elevation of Bootstrapper Application
The values are set by our custom Managed Bootstrapper Application via the standard .NET Registry API, and not by any of the included packages. Since the information to be stored is on the bundle-level (which packages are selected for installation), it can't be moved into an MSI. I have attempted using IBurnEngine->Elevate(), but as far as I can see (and as I expect from it being a method of the engine), that does not give the managed bootstrapper application process elevated privileges. Daniel E. Bruce Software Developer, +47 91918893 Prediktor AS Habornveien 48B, N-1630 Gamle Fredrikstad, Norway > -Original Message- > From: Neil Sleightholm [mailto:n...@x2systems.com] > Sent: 15. oktober 2012 14:28 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Elevation of Bootstrapper Application > > How are you setting the values? Burn automatically prompts to elevate if > it detects an MSI that is set to all users but you can also set this with > MsiPackage/@ForcePerMachine. > > Neil > > > >Hi. > > > >We are trying to keep some state alongside our bundle about which > >packages have been chosen for installation. The solution we envisioned > >was to put some registry entries within HKLM, but this fails on Windows > >7 (and probably Vista) due to HKLM requiring admin privileges. We > could > >work around this issue by writing to HKCU, but that would cause issues > >if another user ran the uninstallation (for instance) later. > > > >Is it possible to elevate the bootstrapper application in some way, so > >that we can write to HKLM? As a sideline question, does Burn store any > >information about what packages has been installed for later retrieval > >or persist any of the variables set during the installation on its own > >(if using a custom BA)? > > > >Daniel E. Bruce > >Software Developer, +47 91918893 > >Prediktor AS > >Habornveien 48B, N-1630 Gamle Fredrikstad, Norway > > > > > > > >--- > >--- > > > >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 > > > -- > 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 > > ___ > ___ > This email has been scanned by the Symantec Email Security.cloud > service. > For more information please visit http://www.symanteccloud.com > ___ > ___ -- 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
[WiX-users] Elevation of Bootstrapper Application
Hi. We are trying to keep some state alongside our bundle about which packages have been chosen for installation. The solution we envisioned was to put some registry entries within HKLM, but this fails on Windows 7 (and probably Vista) due to HKLM requiring admin privileges. We could work around this issue by writing to HKCU, but that would cause issues if another user ran the uninstallation (for instance) later. Is it possible to elevate the bootstrapper application in some way, so that we can write to HKLM? As a sideline question, does Burn store any information about what packages has been installed for later retrieval or persist any of the variables set during the installation on its own (if using a custom BA)? Daniel E. Bruce Software Developer, +47 91918893 Prediktor AS Habornveien 48B, N-1630 Gamle Fredrikstad, Norway -- 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
Re: [WiX-users] WIC as a prereq before .NET 4.0 in Burn with custom BA
Thank you for the answer, however I can't see how you specify that this is to be run by the prerequisite installer that usually installs .NET before launching the managed BA. Is this then not necessary, or was I unclear on our problem? Our problem is not in specifying the packages (though thank you for that), but getting them to run prior to the .NET 4.0 package in the native installer that is launched if .NET 4.0 is not present on the machine. We think this would require setting the variable WixMbaPrereqPackageId to some package that does this for us, but it's unclear what this value would be or if this is actually the solution we need. Daniel E. Bruce Software Developer, +47 91918893 Prediktor AS Habornveien 48B, N-1630 Gamle Fredrikstad, Norway > -Original Message- > From: Neil Sleightholm [mailto:n...@x2systems.com] > Sent: 8. oktober 2012 10:22 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] WIC as a prereq before .NET 4.0 in Burn with > custom BA > > This is my WIC install: > > Variable="windowscodecs" Result="exists" /> > > > >Id="WIC_x86" > Compressed="yes" > Permanent="yes" > Name="Redist\wic_x86_enu.exe" > SourceFile="..\Packages\wic_x86_enu.exe" > InstallCommand="/quiet /norestart" > DetectCondition="windowscodecs" > InstallCondition="VersionNT=v5.2 AND NOT VersionNT64" > Vital="yes"> > > > >Id="WIC_x64" > Compressed="yes" > Permanent="yes" > Name="Redist\wic_x64_enu.exe" > SourceFile="..\Packages\wic_x64_enu.exe" > InstallCommand="/quiet /norestart" > DetectCondition="windowscodecs" > InstallCondition="VersionNT=v5.2 AND VersionNT64" > Vital="yes"> > > > > > I have manually downloaded the file and embed them in my bundle. > > > Neil > > > > >Hello, > > > >We are attempting to roll out a managed bootstrapper that depends on > >.NET 4.0. On some platforms this requires WIC (Windows Imaging > >Component) to be installed prior to running the .NET 4.0 installer, > >which is giving us some issues. > > > >We have tried to solve this issue in a few ways, but none have worked, > >so I posted to stack overflow about it. Nobody has responded so far, so > >I'm crossposting here to see if anybody has any input. If so, it would > >be nice if you could take a look at the SO question, which has all the > >details, and perhaps shoot me an answer either there or here. > > > >http://stackoverflow.com/questions/12727583/adding-wic-as-a- > requirement > >-be fore-net-4-0-in-wix-burn-custom-managed-bootstrap > > > >Daniel E. Bruce > >Software Developer, +47 91918893 > >Prediktor AS > >Habornveien 48B, N-1630 Gamle Fredrikstad, Norway > > > > > >--- > >--- > > > >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 > > > -- > 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 > > ___ > ___ > This email has been scanned by the Symantec Email Security.cloud > service. > For more information please visit http://www.symanteccloud.com > ___ > ___ -- 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
[WiX-users] WIC as a prereq before .NET 4.0 in Burn with custom BA
Hello, We are attempting to roll out a managed bootstrapper that depends on .NET 4.0. On some platforms this requires WIC (Windows Imaging Component) to be installed prior to running the .NET 4.0 installer, which is giving us some issues. We have tried to solve this issue in a few ways, but none have worked, so I posted to stack overflow about it. Nobody has responded so far, so I'm crossposting here to see if anybody has any input. If so, it would be nice if you could take a look at the SO question, which has all the details, and perhaps shoot me an answer either there or here. http://stackoverflow.com/questions/12727583/adding-wic-as-a-requirement-before-net-4-0-in-wix-burn-custom-managed-bootstrap Daniel E. Bruce Software Developer, +47 91918893 Prediktor AS Habornveien 48B, N-1630 Gamle Fredrikstad, Norway -- 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
