Re: [WiX-users] Bootstrapper.Engine.Detect() never calls event?
it giveses you the Package Id. The Package Id defaults to the name of the package if you don't specify it. On Wed, Oct 24, 2012 at 8:15 AM, Hans ter Horst wrote: > Oops, sorry, I think it works fine. I expected to find the PackageGroup Id > string, but instead it games me the last part of the SourceFile of the > MsiPackage or ExePacke, which is absolutely fine. > > Hans > > On Wed, Oct 24, 2012 at 3:26 PM, Hans ter Horst > wrote: > > > Hello, > > I would like to know the individual names of the packages installed and > > one of the first things I do is to register the event handlers: > > > >this.Bootstrapper.ApplyComplete += this.OnApplyComplete; > >this.Bootstrapper.DetectPackageComplete += > > this.OnDetectPackageComplete; > >this.Bootstrapper.PlanComplete += this.OnPlanComplete; > > > > The next thing I do is to call Bootstrapper.Engine.Detect(); in my Run > > method before calling the Dispatcher.Run();. > > > > As far as I can tell, OnDetectPackageComplete is never called. If I > > inspect the Bootstrapper.Engine.StringVariables["WixBundleInstalled"] > > variable it returns either a 1 or a 0 to let me know if a component is > > installed but I was hoping to find out the names of the packages > installed. > > > > Hans > > > > -- > > http://monochrome.me.uk/blog/ > > > > > > > -- > http://monochrome.me.uk/blog/ > > -- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- virtually, Rob Mensching http://RobMensching.com LLC -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Differences in Heat output when run on 32 vs 64 bit build machine
Heat simply calls the ::DllRegisterServer() entry point and captures the data. The DLL must be writing different values on different OSs. On Wed, Oct 24, 2012 at 9:59 AM, john.burak wrote: > Hi, > > We recently automated Heat on our COM-registered libraries. I ran it on > the > same DLLs on a 64-bit machine and a 32-bit machine and noticed a couple > differences in the .wxs output. Heat on the 32-bit machine added > ProxyStubClassId32 attributes to the elements, and added > ThreadingModel="apartment" to some of the elements. > > Is there a reason the generated source-code should differ when built on a > 32 > vs 64 bit machine, or is it just a Heat quirk? It seems like the generated > code should ideally be the same. > > Thanks! > > - John Burak > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Differences-in-Heat-output-when-run-on-32-vs-64-bit-build-machine-tp7581551.html > Sent from the wix-users mailing list archive at Nabble.com. > > > -- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Product Version via (bind.FileVersion.$(var.MAINEXE))
Nothing supported natively in WiX toolset. On Wed, Oct 24, 2012 at 5:44 PM, Johann A. Hough < joh...@silverskysoftware.com.au> wrote: > Thanks Peter, good to know. > > I however re-use the $(var.VERSION) variable in quite a few other places > like directories, shortcuts, websites, etc. and find that have four are > excessive, so I'm trying to see if there is a simple way to reduce it to 3 > or even 2 for those usages. > > Any ideas? > > -Original Message- > From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] > Sent: Thursday, 25 October 2012 1:47 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Product Version via > (bind.FileVersion.$(var.MAINEXE)) > > You can use a 4 field version for a product. Windows stores but ignores > the final field. > > -Original Message- > From: Johann A. Hough [mailto:joh...@silverskysoftware.com.au] > Sent: 24 October 2012 16:44 > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Product Version via (bind.FileVersion.$(var.MAINEXE)) > > Hi All > > I'm using the approach of defining a variable for the product version > which is bound from one of the assemblies. > > > This ends up as a number like "1.0.0.0" - how can I strip this down to > "1.0.0"? > > Thanks, > Johann > > - > - > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics Download AppDynamics Lite for > free > today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > SDL PLC confidential, all rights reserved. > If you are not the intended recipient of this mail SDL requests and > requires that you delete it without acting upon or copying any of its > contents, and we further request that you advise us. > SDL PLC is a public limited company registered in England and Wales. > Registered number: 02675207. > Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 > 7DY, UK. > > > > -- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics Download AppDynamics Lite for > free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > -- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- virtually, Rob Mensching http://RobMensching.com LLC -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How to deal with same applications installed by two different installers?
I’ve been using WiX for a few years. I have a question that’s about installation but not strictly about WiX. But this is the only forum I know dealing with installation on Windows. If this is out of place please feel free to redirect me elsewhere, I’d appreciate it. My company currently has Product A with an installer that installs Application A. We also have a Product B which installs a Device Driver B consisting of a few DLLs. These are already released and available for download. Now I am being asked to make an installer for new Product C. The installer must be a single file that is downloaded from a web page and then executed. It must include Application A, Device Driver B, and a new Application C. The old Product A and Product B will still exist separately though. Product C does not replace them. A quick and dirty way: I could create a separate installer for just Application C, then put all three installers for A, B and C in a self-extracting Zip file so that they get run one at a time. But that is not atomic, ugly for the end user, and it’s bad for upgrades. What if only one of the three get upgraded? The other two installers will get launched anyway and prompt the user for repair or removal. Not only that, what if the user sees an upgrade for the separate Product A on our website and install that? So my best solution so far is to create a single installer for Product C that that includes all three of Application A, Driver for Device B, and Application C. But I need to forbid users from installing Product A or B since I cannot have two of Application A or Device Driver B on the same computer. So I was thinking I need to consider Product A’s Application A and Product C’s Application A as two separate things with different component GUIDs, even though they are really the same application. The same goes for the Device Driver component. One thing I’d like to know is whether the following makes sense. Could I give Application A the same component GUIDs in both Product A and Product C installers? Then if a user tried to install Product A after Product C was already installed (or an upgrade to Application A via a Product A installer) would it not harm anything? It would just be like one Application A on the system. Then could I still apply Product C upgrades later without trouble? (I can already imagine problems though with the Start Menu shortcuts if they install it to a different location on disk, by default.) I really need a multi-level install, but I know Windows Installer doesn’t work that way. Are there any better ways to handle this? Sheesh, managers don’t realize what trouble they cause when they hand you these kind of requirements. Thanks, Jim -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] wix uninstall of service
Hi, I have a windows service project called MyExe.exe, which takes arguments to its Main method. I created below wix installer project to install my service using ServiceInstall below, everything works fine. What I want to accomplish now is do something on the uninstall of this service. Is there a way in wix to specify a custom action to perform inside MyExe.exe only during the uninstall? I cannot accomplish this task on OnStop, needs to accomplished on uninstall. Thanks, Senthil. -- 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] Product Version via (bind.FileVersion.$(var.MAINEXE))
Thanks Peter, good to know. I however re-use the $(var.VERSION) variable in quite a few other places like directories, shortcuts, websites, etc. and find that have four are excessive, so I'm trying to see if there is a simple way to reduce it to 3 or even 2 for those usages. Any ideas? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Thursday, 25 October 2012 1:47 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Product Version via (bind.FileVersion.$(var.MAINEXE)) You can use a 4 field version for a product. Windows stores but ignores the final field. -Original Message- From: Johann A. Hough [mailto:joh...@silverskysoftware.com.au] Sent: 24 October 2012 16:44 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Product Version via (bind.FileVersion.$(var.MAINEXE)) Hi All I'm using the approach of defining a variable for the product version which is bound from one of the assemblies. This ends up as a number like "1.0.0.0" - how can I strip this down to "1.0.0"? Thanks, Johann - - Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- 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] TARGETDIR not being set
Thanks Narina! Just for future new WiXers, I ended up modifying the wxs as follows: And Much appreciated, Filip -Original Message- From: Narina, Chandra [mailto:chandra.nar...@wolterskluwer.com] Sent: Wednesday, October 24, 2012 2:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] TARGETDIR not being set Hi, Use Directory attribute instead of property. (it's a Type 35 Custom Action) and Schedule this action after InstallValidate in the Execute sequence - that's when directories are checked for write access and truly set. Something like this... Thanks & Regards Narina Chandra Sekhar -Original Message- From: Filip Balas [mailto:fba...@petersco.com] Sent: Wednesday, October 24, 2012 12:48 PM To: 'wix-users@lists.sourceforge.net' Subject: [WiX-users] TARGETDIR not being set NOOB Alert: I have been learning the ins and outs of WiX for appoximately a day. I am having problems setting the TARGETDIR path. I used dark.exe to reverse engineer a working MSI and read any posts I could find on this subject but I seem to be unable to set the TARGETDIR to point to the path ProgramFiles\Manufacturer\Product. Below is a distilation of my wxs file which results in my application being installed to the root of my D-drive for some reason: http://schemas.microsoft.com/wix/2006/wi";> I'm sure I am missing something simple but I cannot find any further information on what to do from here. Thanks, Filip Disclaimer: The information transmitted is intended only for the use of the individual or entity to which it is addressed, and may contain confidential, proprietary and/or privileged material. If you are not an intended recipient, you are advised that disclosing, copying, forwarding or other distribution of this e-mail is strictly prohibited. E-mail transmission cannot be guaranteed to be secure or error-free and the sender will not be liable for these risks. All e-mail to or from this address is subject to archival, monitoring and/or review, by and/or disclosure to, someone other than the recipient. Regulatory Disclosure: http://www.petersco.com/research_disclosure.cfm -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] calling a deferred customaction dll using CAQuietExec
I have a custom action:
NOT Installed
if execute=immediate runs before it should BUT the MSI properties are read
in by my customaction dll, however it fails since the files haven't been
installed yet :(
If I set the execute=deferred it runs when it is supposed to BUT the
properties are not read in to my custom action dll they are blank...
set up MessageBox.Show("this is a property: " + myProperty);
What is going on?
Steve
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/calling-a-deferred-customaction-dll-using-CAQuietExec-tp7581555p7581564.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing outside ProgramFilesFolder
Try adding Sequence="ui" to your SetProperty element. I can't remember if AppSearch is executed twice. The next question would be how would you allow a user to override this when installing with no UI, which I would suggest using the "remember me property pattern" Rob had blogged about a while back. Another option from a quick search shows: http://kentie.net/article/wixtipstricks/ TARGETDIR and the system partition When trying to install to a subdirectory of the system drive root (e.g. 'C:\application'), it might sense to assume that in something like TARGETDIR refers to the system partition, as ProgramFilesFolder is always given as a child of TARGETDIR. This is not the case; TARGETDIR is the partition with the most free disk space. It can even be a partition on an external hard drive. To set it to the true system partition, use the below approach: -Original Message- From: Gavin Bray [mailto:gavb...@gmail.com] Sent: Wednesday, October 24, 2012 4:42 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Installing outside ProgramFilesFolder If I use the following then the value specified by the user does get used. So, I assume it somehow is related to using but I'm not sure how. Any suggestions are most welcome. Regards Gavin On Thu, Oct 25, 2012 at 5:20 AM, Phil Wilson wrote: > It's hard to be specific, but it looks like the dialog you're using > with its BrowseFolder result is not propagating the user input to > TARGETDIR or INSTALLFOLDER. > > Phil W > > -Original Message- > From: Gavin Bray [mailto:gavb...@gmail.com] > Sent: Tuesday, October 23, 2012 11:29 PM > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Installing outside ProgramFilesFolder > > Hi > > I have a requirement to use C:\MyApp as the default installation > directory rather than being user Program Files (x86). > > I also give the user the opportunity to specify a different directory. > > I'm using: > > > > Before="AppSearch"/> > > > > At install time, the > correct default directory of C:\MyApp is displayed (assuming the > Windows volume is C:). > > However, if I specify a different directory (eg C:\MyApp2) during the > setup then the default C:\MyApp is still used. > > How do I get this to work so that it defaults to C:\MyApp but the user > supplied directory, if specified, is used? > > Thanks > Gavin > > -- > -- > -- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics Download AppDynamics Lite > for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > -- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics Download AppDynamics Lite > for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [WiX-usrs] execute wix msi through cmd
Thanks everyone, finally got this working. There were several mistakes from syntax error to using the right property name. I had something like this in my wix project for all properties My first mistake was assigning custom value from cmd to WIXUI_LABNAME, instead you should assign it to LABNAME. msiexec /i MyApplication.msi /qn INSTALLDIR="C:\Program Files (x86)\ MyApplication \" LABNAME="test" LABOWNER="Me" LABDESCRIPTION="my description" LABACCESS="1" USER_NAME="domain\administrator" PASSWORD="password" Phil, you were right, after enabling logging by using /l* errors.txt, I was able to identify and fix one issue after another. Thanks, Senthil. -Original Message- From: Phil Wilson [mailto:phil.wil...@mvps.org] Sent: Sunday, October 21, 2012 10:40 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] [WiX-usrs] execute wix msi through cmd and adding some detail about "did not work" would help. Maybe you saw an msiexec message box showing the correct syntax because yours was incorrect, or maybe it started and failed in some way. Phil W -Original Message- From: Rob Hamflett [mailto:rob_hamfl...@sn.scee.net] Sent: Friday, October 19, 2012 12:10 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] execute wix msi through cmd On 19/10/2012 00:26, Senthil Chandran wrote: > That did not work either :( > msiexec /i MyApplication.msi /qn WIXUI_LABNAME="TestSilent" WIXUI_LABOWNER="Me" WIXUI_LABDESCRIPTION="description" WIXUI_LABACCESS="1" did not work either. Try it without the quotes round the values. Log the installation and see what it reports for the property values. Rob > > Any other ideas? > > Thanks, > Senthil. > > -Original Message- > From: Rob Hamflett [mailto:rob_hamfl...@sn.scee.net] > Sent: Thursday, October 11, 2012 12:37 AM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] execute wix msi through cmd > > Try this: > msiexec /i MyApplication.msi /qn WIXUI_LABNAME=TestSilent > WIXUI_LABOWNER=Me WIXUI_LABDESCRIPTION=description WIXUI_LABACCESS=1 > > Rob > > On 10/10/2012 22:34, Senthil Chandran wrote: >> I wrote a wix project that generates a msi to execute my exe. >> Part of the installer, I collect data from users that I pass on to my exe. It works fine when I run the installer UI. >> >> Is there a way to run the installer from cmd without launching the >> UI, but still collect the data from users through arguments and pass it to my exe? >> I tried this and it is not working >> >> MyApplication.msi /qn [WIXUI_LABNAME="TestSilent"] >> [WIXUI_LABOWNER="Me"] [WIXUI_LABDESCRIPTION="description"] >> [WIXUI_LABACCESS="1"] >> >> Thanks, >> Senthil. >> - >> - >> Don't let slow site performance ruin your business. Deploy >> New Relic APM Deploy New Relic app performance management and know >> exactly what is happening inside your Ruby, Python, PHP, Java, and >> .NET app Try New Relic at no cost today and get our sweet Data Nerd >> shirt too! >> http://p.sf.net/sfu/newrelic-dev2dev >> > > > > -- > Don't let slow site performance ruin your business. Deploy > New Relic APM Deploy New Relic app performance management and know > exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! > http://p.sf.net/sfu/newrelic-dev2dev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > -- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics Download AppDynamics Lite > for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appd
Re: [WiX-users] Installing outside ProgramFilesFolder
If I use the following then the value specified by the user does get used. So, I assume it somehow is related to using but I'm not sure how. Any suggestions are most welcome. Regards Gavin On Thu, Oct 25, 2012 at 5:20 AM, Phil Wilson wrote: > It's hard to be specific, but it looks like the dialog you're using with > its > BrowseFolder result is not propagating the user input to TARGETDIR or > INSTALLFOLDER. > > Phil W > > -Original Message- > From: Gavin Bray [mailto:gavb...@gmail.com] > Sent: Tuesday, October 23, 2012 11:29 PM > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Installing outside ProgramFilesFolder > > Hi > > I have a requirement to use C:\MyApp as the default installation directory > rather than being user Program Files (x86). > > I also give the user the opportunity to specify a different directory. > > I'm using: > > > > Before="AppSearch"/> > > > > At install time, the > correct > default directory of C:\MyApp is displayed (assuming the Windows volume is > C:). > > However, if I specify a different directory (eg C:\MyApp2) during the setup > then the default C:\MyApp is still used. > > How do I get this to work so that it defaults to C:\MyApp but the user > supplied directory, if specified, is used? > > Thanks > Gavin > > > -- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics Download AppDynamics Lite for > free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > -- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] TARGETDIR not being set
Hi, Use Directory attribute instead of property. (it's a Type 35 Custom Action) and Schedule this action after InstallValidate in the Execute sequence - that's when directories are checked for write access and truly set. Something like this... Thanks & Regards Narina Chandra Sekhar -Original Message- From: Filip Balas [mailto:fba...@petersco.com] Sent: Wednesday, October 24, 2012 12:48 PM To: 'wix-users@lists.sourceforge.net' Subject: [WiX-users] TARGETDIR not being set NOOB Alert: I have been learning the ins and outs of WiX for appoximately a day. I am having problems setting the TARGETDIR path. I used dark.exe to reverse engineer a working MSI and read any posts I could find on this subject but I seem to be unable to set the TARGETDIR to point to the path ProgramFiles\Manufacturer\Product. Below is a distilation of my wxs file which results in my application being installed to the root of my D-drive for some reason: http://schemas.microsoft.com/wix/2006/wi";> I'm sure I am missing something simple but I cannot find any further information on what to do from here. Thanks, Filip Disclaimer: The information transmitted is intended only for the use of the individual or entity to which it is addressed, and may contain confidential, proprietary and/or privileged material. If you are not an intended recipient, you are advised that disclosing, copying, forwarding or other distribution of this e-mail is strictly prohibited. E-mail transmission cannot be guaranteed to be secure or error-free and the sender will not be liable for these risks. All e-mail to or from this address is subject to archival, monitoring and/or review, by and/or disclosure to, someone other than the recipient. Regulatory Disclosure: http://www.petersco.com/research_disclosure.cfm -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] TARGETDIR not being set
NOOB Alert: I have been learning the ins and outs of WiX for appoximately a day. I am having problems setting the TARGETDIR path. I used dark.exe to reverse engineer a working MSI and read any posts I could find on this subject but I seem to be unable to set the TARGETDIR to point to the path ProgramFiles\Manufacturer\Product. Below is a distilation of my wxs file which results in my application being installed to the root of my D-drive for some reason: http://schemas.microsoft.com/wix/2006/wi";> I'm sure I am missing something simple but I cannot find any further information on what to do from here. Thanks, Filip Disclaimer: The information transmitted is intended only for the use of the individual or entity to which it is addressed, and may contain confidential, proprietary and/or privileged material. If you are not an intended recipient, you are advised that disclosing, copying, forwarding or other distribution of this e-mail is strictly prohibited. E-mail transmission cannot be guaranteed to be secure or error-free and the sender will not be liable for these risks. All e-mail to or from this address is subject to archival, monitoring and/or review, by and/or disclosure to, someone other than the recipient. Regulatory Disclosure: http://www.petersco.com/research_disclosure.cfm -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing outside ProgramFilesFolder
It's hard to be specific, but it looks like the dialog you're using with its BrowseFolder result is not propagating the user input to TARGETDIR or INSTALLFOLDER. Phil W -Original Message- From: Gavin Bray [mailto:gavb...@gmail.com] Sent: Tuesday, October 23, 2012 11:29 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Installing outside ProgramFilesFolder Hi I have a requirement to use C:\MyApp as the default installation directory rather than being user Program Files (x86). I also give the user the opportunity to specify a different directory. I'm using: At install time, the correct default directory of C:\MyApp is displayed (assuming the Windows volume is C:). However, if I specify a different directory (eg C:\MyApp2) during the setup then the default C:\MyApp is still used. How do I get this to work so that it defaults to C:\MyApp but the user supplied directory, if specified, is used? Thanks Gavin -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Repair doesn't find MSI
There are some things you can do based around the MsiSourceListAddSource () function (and scripting equivalents) that let you define alternate paths to locate the MSI that Windows requires. So you can put it on a network server and then tell Windows to look there for repair (or adding features etc). I don't know what "new download of the MSI" means. The MSI needed for repair must be the same one used in the original install. If you rebuild the MSI and change something in it, then you need to do some kind of update, not do a repair with the new MSI thinking it will repair from there, just in case that's where you're going with this. Phil W -Original Message- From: Osanger, Martin [mailto:martin.osan...@fabasoft.com] Sent: Wednesday, October 24, 2012 2:40 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Repair doesn't find MSI Hello, I have the following question: What can I do, that the repair function works from the "add or remove programs" panel, or from the same MSI? If the MSI package was installed via msiexec /qn /I ".msi", the MSI searches for the original package only in the folder , not where the operating system stores a copy of the MSI, or where I try to repair from a new location, with a new download of the MSI. Uninstall works fine. regards, Martin -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] calling a deferred customaction dll using CAQuietExec
I have a deferred custom action in a merge module that is a call to a C# customaction dll I created, but I want it to be quiet so I did this: CA: Setting CustomAction to configure the connection strings for Web.config... CA: Configuring the connection strings for Web.config... NOT Installed NOT Installed but I get this compile time error: Error 92 The CustomAction/@BinaryKey attribute cannot coexist with a previously specified attribute on this element. The CustomAction element may only have one of the following source attributes specified at a time: BinaryKey, Directory, FileKey, Property, or Script. C:\Dev\Core Technologies\Main\Setup\TitusAdmin\TitusAdminMergeModule\MergeModule.wxs 619 1 TitusAdminMergeModule -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/calling-a-deferred-customaction-dll-using-CAQuietExec-tp7581555.html Sent from the wix-users mailing list archive at Nabble.com. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix problems
You guys all rock. The latest version worked perfectly. I should of thought of that. Thanks for all your quick responses and help. Thanks Jacob for the info. Definitely owe you guys a drink if you are ever in Canada LOL Richard Compton On Oct 24, 2012 12:11 PM, "Hoover, Jacob" wrote: > That is where Wix caches packages if you have told the bundle to save them > for later offline or without a CD reinstall/repair/uninstall operations. I > have a feeling that your bundle left some files behind during a previous > uninstall. If you were using a VM, I'd tell you to revert to a clean > state. If you are certain you have none of your bundles installed, and > there is a sub folder with your bundle in it, you could try renaming the > folder to see if the bundle then succeeds. On an end users machine, this > would not be a good thing to do but if this is simply a test PC for testing > your bundles, then it should be a valid test. > > (I seem to remember the bundle caches anything it downloads here, and > removes them after the install completes if the package wasn't set to be > persisted.) > > -Original Message- > From: Richard Compton [mailto:rich.comp...@curvedental.com] > Sent: Wednesday, October 24, 2012 12:07 PM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Wix problems > > Just trying the latest WIX to see if that helps. > > What exactly am I looking for in the Program Cache. On my test machine > (where the installer works) I see some folders with my msi in them. Is > that normal? Other folders have a data folder in them? What should I see? > What should I not see? > > Thanks again for your help. This is huge. > > > *Rich Compton* | Senior Software Developer > tel:1.877.245.4088 x106 > > > *Curve Dental* > /A Fresh, Web-based Alternative to Dental Software www.curvedental.com/On > 24/10/2012 10:10 AM, Hoover, Jacob wrote: > > If you check in %ProgramData%\PackageCache, are there any sub folders? > It may be as Neil suggested that you are using an outdated version > (non-stable release). > > > > -Original Message- > > From: Richard Compton [mailto:rich.comp...@curvedental.com] > > Sent: Wednesday, October 24, 2012 10:58 AM > > To: wix-users@lists.sourceforge.net > > Subject: Re: [WiX-users] Wix problems > > > > Thanks for the quick response. > > > > It is a clean enough machine. Our product is not on this machine. As > far as I can tell no related bundles to our product are there. How would I > find this out? Just by scrolling through the programs installed? How do I > check this file you speak of? Or the package cache? > > > > Thanks again > > > > > > *Rich Compton* | Senior Software Developer > > tel:1.877.245.4088 x106 > > > > > > *Curve Dental* > > /A Fresh, Web-based Alternative to Dental Software www.curvedental.com/On > > 24/10/2012 9:53 AM, Hoover, Jacob wrote: > >> Is this a clean machine or did you have the bundle on it before? Are > >> there any related bundles already on the machine? Just a gut feel > >> tells me there will be a bundle in the package cache and possibly the > >> state data file is corrupt. (There is a file alongside the bundle in > >> the package cache which stores information for the bundle.) > >> > >> Jacob > >> > >> -Original Message- > >> From: Richard Compton [mailto:rich.comp...@curvedental.com] > >> Sent: Wednesday, October 24, 2012 9:41 AM > >> To: wix-users@lists.sourceforge.net > >> Subject: [WiX-users] Wix problems > >> > >> I have an installer that we are currently using. I am using a > Bootstrapper. When I click on the installer it does nothing. The log file > shows the following. > >> > >> [0690:1054][2012-10-24T08:43:02]: Burn v3.6.2221.0, path: > >> C:\Users\Owner6\Desktop\CurveImage-1_2_0-live.exe, cmdline: '' > >> [0690:1054][2012-10-24T08:43:02]: Setting string variable > 'WixBundleName' to value 'Curve Image Installer' > >> [0690:1054][2012-10-24T08:43:02]: Setting string variable 'WixBundleLog' > >> to value > >> > 'C:\Users\Owner6\AppData\Local\Temp\Curve_Image_Installer_20121024084302.log' > >> [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to read > Resume value. > >> [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to detect > resume type. > >> [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to query > registration. > >> [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to run > per-user mode. > >> > >> Any ideas? Need anymore information? > >> > >> > >> Thanks in advance > >> > >> > >> > >> -- > >> *Rich Compton* | Senior Software Developer > >> tel:1.877.245.4088 x106 > >> > >> > >> *Curve Dental* > >> /A Fresh, Web-based Alternative to Dental Software > >> www.curvedental.com/ > >> - > >> - > >> Everyone hates slow websites. So do we. > >> Make your web apps faster with AppDynamics Download AppDynamics Lite > >> for free today: > >> http://p.sf.net/sfu/appdyn_sfd2d_oct >
Re: [WiX-users] Wix problems
That is where Wix caches packages if you have told the bundle to save them for later offline or without a CD reinstall/repair/uninstall operations. I have a feeling that your bundle left some files behind during a previous uninstall. If you were using a VM, I'd tell you to revert to a clean state. If you are certain you have none of your bundles installed, and there is a sub folder with your bundle in it, you could try renaming the folder to see if the bundle then succeeds. On an end users machine, this would not be a good thing to do but if this is simply a test PC for testing your bundles, then it should be a valid test. (I seem to remember the bundle caches anything it downloads here, and removes them after the install completes if the package wasn't set to be persisted.) -Original Message- From: Richard Compton [mailto:rich.comp...@curvedental.com] Sent: Wednesday, October 24, 2012 12:07 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Wix problems Just trying the latest WIX to see if that helps. What exactly am I looking for in the Program Cache. On my test machine (where the installer works) I see some folders with my msi in them. Is that normal? Other folders have a data folder in them? What should I see? What should I not see? Thanks again for your help. This is huge. *Rich Compton* | Senior Software Developer tel:1.877.245.4088 x106 *Curve Dental* /A Fresh, Web-based Alternative to Dental Software www.curvedental.com/ On 24/10/2012 10:10 AM, Hoover, Jacob wrote: > If you check in %ProgramData%\PackageCache, are there any sub folders? It > may be as Neil suggested that you are using an outdated version (non-stable > release). > > -Original Message- > From: Richard Compton [mailto:rich.comp...@curvedental.com] > Sent: Wednesday, October 24, 2012 10:58 AM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Wix problems > > Thanks for the quick response. > > It is a clean enough machine. Our product is not on this machine. As far as > I can tell no related bundles to our product are there. How would I find > this out? Just by scrolling through the programs installed? How do I check > this file you speak of? Or the package cache? > > Thanks again > > > *Rich Compton* | Senior Software Developer > tel:1.877.245.4088 x106 > > > *Curve Dental* > /A Fresh, Web-based Alternative to Dental Software www.curvedental.com/ On > 24/10/2012 9:53 AM, Hoover, Jacob wrote: >> Is this a clean machine or did you have the bundle on it before? Are >> there any related bundles already on the machine? Just a gut feel >> tells me there will be a bundle in the package cache and possibly the >> state data file is corrupt. (There is a file alongside the bundle in >> the package cache which stores information for the bundle.) >> >> Jacob >> >> -Original Message- >> From: Richard Compton [mailto:rich.comp...@curvedental.com] >> Sent: Wednesday, October 24, 2012 9:41 AM >> To: wix-users@lists.sourceforge.net >> Subject: [WiX-users] Wix problems >> >> I have an installer that we are currently using. I am using a Bootstrapper. >> When I click on the installer it does nothing. The log file shows the >> following. >> >> [0690:1054][2012-10-24T08:43:02]: Burn v3.6.2221.0, path: >> C:\Users\Owner6\Desktop\CurveImage-1_2_0-live.exe, cmdline: '' >> [0690:1054][2012-10-24T08:43:02]: Setting string variable 'WixBundleName' to >> value 'Curve Image Installer' >> [0690:1054][2012-10-24T08:43:02]: Setting string variable 'WixBundleLog' >> to value >> 'C:\Users\Owner6\AppData\Local\Temp\Curve_Image_Installer_20121024084302.log' >> [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to read Resume >> value. >> [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to detect resume >> type. >> [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to query >> registration. >> [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to run per-user >> mode. >> >> Any ideas? Need anymore information? >> >> >> Thanks in advance >> >> >> >> -- >> *Rich Compton* | Senior Software Developer >> tel:1.877.245.4088 x106 >> >> >> *Curve Dental* >> /A Fresh, Web-based Alternative to Dental Software >> www.curvedental.com/ >> - >> - >> Everyone hates slow websites. So do we. >> Make your web apps faster with AppDynamics Download AppDynamics Lite >> for free today: >> http://p.sf.net/sfu/appdyn_sfd2d_oct >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> - >> - >> Everyone hates slow websites. So do we. >> Make your web apps faster with AppDynamics Download AppDynamics Lite >> for free today: >> http://p.sf.net/sfu/appdyn_sfd2d_oct >> _
Re: [WiX-users] Wix problems
Just trying the latest WIX to see if that helps. What exactly am I looking for in the Program Cache. On my test machine (where the installer works) I see some folders with my msi in them. Is that normal? Other folders have a data folder in them? What should I see? What should I not see? Thanks again for your help. This is huge. *Rich Compton* | Senior Software Developer tel:1.877.245.4088 x106 *Curve Dental* /A Fresh, Web-based Alternative to Dental Software www.curvedental.com/ On 24/10/2012 10:10 AM, Hoover, Jacob wrote: > If you check in %ProgramData%\PackageCache, are there any sub folders? It > may be as Neil suggested that you are using an outdated version (non-stable > release). > > -Original Message- > From: Richard Compton [mailto:rich.comp...@curvedental.com] > Sent: Wednesday, October 24, 2012 10:58 AM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Wix problems > > Thanks for the quick response. > > It is a clean enough machine. Our product is not on this machine. As far as > I can tell no related bundles to our product are there. How would I find > this out? Just by scrolling through the programs installed? How do I check > this file you speak of? Or the package cache? > > Thanks again > > > *Rich Compton* | Senior Software Developer > tel:1.877.245.4088 x106 > > > *Curve Dental* > /A Fresh, Web-based Alternative to Dental Software www.curvedental.com/ On > 24/10/2012 9:53 AM, Hoover, Jacob wrote: >> Is this a clean machine or did you have the bundle on it before? Are >> there any related bundles already on the machine? Just a gut feel >> tells me there will be a bundle in the package cache and possibly the >> state data file is corrupt. (There is a file alongside the bundle in >> the package cache which stores information for the bundle.) >> >> Jacob >> >> -Original Message- >> From: Richard Compton [mailto:rich.comp...@curvedental.com] >> Sent: Wednesday, October 24, 2012 9:41 AM >> To: wix-users@lists.sourceforge.net >> Subject: [WiX-users] Wix problems >> >> I have an installer that we are currently using. I am using a Bootstrapper. >> When I click on the installer it does nothing. The log file shows the >> following. >> >> [0690:1054][2012-10-24T08:43:02]: Burn v3.6.2221.0, path: >> C:\Users\Owner6\Desktop\CurveImage-1_2_0-live.exe, cmdline: '' >> [0690:1054][2012-10-24T08:43:02]: Setting string variable 'WixBundleName' to >> value 'Curve Image Installer' >> [0690:1054][2012-10-24T08:43:02]: Setting string variable 'WixBundleLog' >> to value >> 'C:\Users\Owner6\AppData\Local\Temp\Curve_Image_Installer_20121024084302.log' >> [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to read Resume >> value. >> [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to detect resume >> type. >> [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to query >> registration. >> [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to run per-user >> mode. >> >> Any ideas? Need anymore information? >> >> >> Thanks in advance >> >> >> >> -- >> *Rich Compton* | Senior Software Developer >> tel:1.877.245.4088 x106 >> >> >> *Curve Dental* >> /A Fresh, Web-based Alternative to Dental Software >> www.curvedental.com/ >> -- >> Everyone hates slow websites. So do we. >> Make your web apps faster with AppDynamics Download AppDynamics Lite >> for free today: >> http://p.sf.net/sfu/appdyn_sfd2d_oct >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> -- >> Everyone hates slow websites. So do we. >> Make your web apps faster with AppDynamics Download AppDynamics Lite >> for free today: >> http://p.sf.net/sfu/appdyn_sfd2d_oct >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users > -- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics Download AppDynamics Lite for free > today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -
[WiX-users] Differences in Heat output when run on 32 vs 64 bit build machine
Hi, We recently automated Heat on our COM-registered libraries. I ran it on the same DLLs on a 64-bit machine and a 32-bit machine and noticed a couple differences in the .wxs output. Heat on the 32-bit machine added ProxyStubClassId32 attributes to the elements, and added ThreadingModel="apartment" to some of the elements. Is there a reason the generated source-code should differ when built on a 32 vs 64 bit machine, or is it just a Heat quirk? It seems like the generated code should ideally be the same. Thanks! - John Burak -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Differences-in-Heat-output-when-run-on-32-vs-64-bit-build-machine-tp7581551.html Sent from the wix-users mailing list archive at Nabble.com. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix problems
If you check in %ProgramData%\PackageCache, are there any sub folders? It may be as Neil suggested that you are using an outdated version (non-stable release). -Original Message- From: Richard Compton [mailto:rich.comp...@curvedental.com] Sent: Wednesday, October 24, 2012 10:58 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Wix problems Thanks for the quick response. It is a clean enough machine. Our product is not on this machine. As far as I can tell no related bundles to our product are there. How would I find this out? Just by scrolling through the programs installed? How do I check this file you speak of? Or the package cache? Thanks again *Rich Compton* | Senior Software Developer tel:1.877.245.4088 x106 *Curve Dental* /A Fresh, Web-based Alternative to Dental Software www.curvedental.com/ On 24/10/2012 9:53 AM, Hoover, Jacob wrote: > Is this a clean machine or did you have the bundle on it before? Are > there any related bundles already on the machine? Just a gut feel > tells me there will be a bundle in the package cache and possibly the > state data file is corrupt. (There is a file alongside the bundle in > the package cache which stores information for the bundle.) > > Jacob > > -Original Message- > From: Richard Compton [mailto:rich.comp...@curvedental.com] > Sent: Wednesday, October 24, 2012 9:41 AM > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Wix problems > > I have an installer that we are currently using. I am using a Bootstrapper. > When I click on the installer it does nothing. The log file shows the > following. > > [0690:1054][2012-10-24T08:43:02]: Burn v3.6.2221.0, path: > C:\Users\Owner6\Desktop\CurveImage-1_2_0-live.exe, cmdline: '' > [0690:1054][2012-10-24T08:43:02]: Setting string variable 'WixBundleName' to > value 'Curve Image Installer' > [0690:1054][2012-10-24T08:43:02]: Setting string variable 'WixBundleLog' > to value > 'C:\Users\Owner6\AppData\Local\Temp\Curve_Image_Installer_20121024084302.log' > [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to read Resume > value. > [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to detect resume > type. > [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to query > registration. > [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to run per-user > mode. > > Any ideas? Need anymore information? > > > Thanks in advance > > > > -- > *Rich Compton* | Senior Software Developer > tel:1.877.245.4088 x106 > > > *Curve Dental* > /A Fresh, Web-based Alternative to Dental Software > www.curvedental.com/ > -- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics Download AppDynamics Lite > for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics Download AppDynamics Lite > for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix problems
Will try that thanks. We have narrowed it down to what I think is a bootstrapper (Bindle) problem. We have a Bundle that will check for a few pre-requisites, download and install them then finally install the main msi. I run the main msi alone and all goes well. Not sure if that helps. *Rich Compton* | Senior Software Developer tel:1.877.245.4088 x106 *Curve Dental* /A Fresh, Web-based Alternative to Dental Software www.curvedental.com/ On 24/10/2012 9:58 AM, Neil Sleightholm wrote: > Might not matter but would suggest using the release version of WiX v3.6.3303 > yours is quite old. > > Neil > > -Original Message- > From: Richard Compton [mailto:rich.comp...@curvedental.com] > Sent: 24 October 2012 15:41 > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Wix problems > > I have an installer that we are currently using. I am using a Bootstrapper. > When I click on the installer it does nothing. The log file shows the > following. > > [0690:1054][2012-10-24T08:43:02]: Burn v3.6.2221.0, path: > C:\Users\Owner6\Desktop\CurveImage-1_2_0-live.exe, cmdline: '' > [0690:1054][2012-10-24T08:43:02]: Setting string variable 'WixBundleName' to > value 'Curve Image Installer' > [0690:1054][2012-10-24T08:43:02]: Setting string variable 'WixBundleLog' > to value > 'C:\Users\Owner6\AppData\Local\Temp\Curve_Image_Installer_20121024084302.log' > [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to read Resume > value. > [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to detect resume > type. > [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to query > registration. > [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to run per-user > mode. > > Any ideas? Need anymore information? > > > Thanks in advance > > > > -- > *Rich Compton* | Senior Software Developer > tel:1.877.245.4088 x106 > > > *Curve Dental* > /A Fresh, Web-based Alternative to Dental Software > www.curvedental.com/ > -- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- 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] Wix problems
Thanks for the quick response. It is a clean enough machine. Our product is not on this machine. As far as I can tell no related bundles to our product are there. How would I find this out? Just by scrolling through the programs installed? How do I check this file you speak of? Or the package cache? Thanks again *Rich Compton* | Senior Software Developer tel:1.877.245.4088 x106 *Curve Dental* /A Fresh, Web-based Alternative to Dental Software www.curvedental.com/ On 24/10/2012 9:53 AM, Hoover, Jacob wrote: > Is this a clean machine or did you have the bundle on it before? Are there > any related bundles already on the machine? Just a gut feel tells me there > will be a bundle in the package cache and possibly the state data file is > corrupt. (There is a file alongside the bundle in the package cache which > stores information for the bundle.) > > Jacob > > -Original Message- > From: Richard Compton [mailto:rich.comp...@curvedental.com] > Sent: Wednesday, October 24, 2012 9:41 AM > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Wix problems > > I have an installer that we are currently using. I am using a Bootstrapper. > When I click on the installer it does nothing. The log file shows the > following. > > [0690:1054][2012-10-24T08:43:02]: Burn v3.6.2221.0, path: > C:\Users\Owner6\Desktop\CurveImage-1_2_0-live.exe, cmdline: '' > [0690:1054][2012-10-24T08:43:02]: Setting string variable 'WixBundleName' to > value 'Curve Image Installer' > [0690:1054][2012-10-24T08:43:02]: Setting string variable 'WixBundleLog' > to value > 'C:\Users\Owner6\AppData\Local\Temp\Curve_Image_Installer_20121024084302.log' > [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to read Resume > value. > [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to detect resume > type. > [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to query > registration. > [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to run per-user > mode. > > Any ideas? Need anymore information? > > > Thanks in advance > > > > -- > *Rich Compton* | Senior Software Developer > tel:1.877.245.4088 x106 > > > *Curve Dental* > /A Fresh, Web-based Alternative to Dental Software > www.curvedental.com/ > -- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- 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] Wix problems
Might not matter but would suggest using the release version of WiX v3.6.3303 yours is quite old. Neil -Original Message- From: Richard Compton [mailto:rich.comp...@curvedental.com] Sent: 24 October 2012 15:41 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Wix problems I have an installer that we are currently using. I am using a Bootstrapper. When I click on the installer it does nothing. The log file shows the following. [0690:1054][2012-10-24T08:43:02]: Burn v3.6.2221.0, path: C:\Users\Owner6\Desktop\CurveImage-1_2_0-live.exe, cmdline: '' [0690:1054][2012-10-24T08:43:02]: Setting string variable 'WixBundleName' to value 'Curve Image Installer' [0690:1054][2012-10-24T08:43:02]: Setting string variable 'WixBundleLog' to value 'C:\Users\Owner6\AppData\Local\Temp\Curve_Image_Installer_20121024084302.log' [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to read Resume value. [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to detect resume type. [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to query registration. [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to run per-user mode. Any ideas? Need anymore information? Thanks in advance -- *Rich Compton* | Senior Software Developer tel:1.877.245.4088 x106 *Curve Dental* /A Fresh, Web-based Alternative to Dental Software www.curvedental.com/ -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix problems
Is this a clean machine or did you have the bundle on it before? Are there any related bundles already on the machine? Just a gut feel tells me there will be a bundle in the package cache and possibly the state data file is corrupt. (There is a file alongside the bundle in the package cache which stores information for the bundle.) Jacob -Original Message- From: Richard Compton [mailto:rich.comp...@curvedental.com] Sent: Wednesday, October 24, 2012 9:41 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Wix problems I have an installer that we are currently using. I am using a Bootstrapper. When I click on the installer it does nothing. The log file shows the following. [0690:1054][2012-10-24T08:43:02]: Burn v3.6.2221.0, path: C:\Users\Owner6\Desktop\CurveImage-1_2_0-live.exe, cmdline: '' [0690:1054][2012-10-24T08:43:02]: Setting string variable 'WixBundleName' to value 'Curve Image Installer' [0690:1054][2012-10-24T08:43:02]: Setting string variable 'WixBundleLog' to value 'C:\Users\Owner6\AppData\Local\Temp\Curve_Image_Installer_20121024084302.log' [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to read Resume value. [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to detect resume type. [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to query registration. [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to run per-user mode. Any ideas? Need anymore information? Thanks in advance -- *Rich Compton* | Senior Software Developer tel:1.877.245.4088 x106 *Curve Dental* /A Fresh, Web-based Alternative to Dental Software www.curvedental.com/ -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Wix problems
I have an installer that we are currently using. I am using a Bootstrapper. When I click on the installer it does nothing. The log file shows the following. [0690:1054][2012-10-24T08:43:02]: Burn v3.6.2221.0, path: C:\Users\Owner6\Desktop\CurveImage-1_2_0-live.exe, cmdline: '' [0690:1054][2012-10-24T08:43:02]: Setting string variable 'WixBundleName' to value 'Curve Image Installer' [0690:1054][2012-10-24T08:43:02]: Setting string variable 'WixBundleLog' to value 'C:\Users\Owner6\AppData\Local\Temp\Curve_Image_Installer_20121024084302.log' [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to read Resume value. [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to detect resume type. [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to query registration. [0690:1054][2012-10-24T08:43:02]: Error 0x8007070c: Failed to run per-user mode. Any ideas? Need anymore information? Thanks in advance -- *Rich Compton* | Senior Software Developer tel:1.877.245.4088 x106 *Curve Dental* /A Fresh, Web-based Alternative to Dental Software www.curvedental.com/ -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Product Version via (bind.FileVersion.$(var.MAINEXE))
You can use a 4 field version for a product. Windows stores but ignores the final field. -Original Message- From: Johann A. Hough [mailto:joh...@silverskysoftware.com.au] Sent: 24 October 2012 16:44 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Product Version via (bind.FileVersion.$(var.MAINEXE)) Hi All I'm using the approach of defining a variable for the product version which is bound from one of the assemblies. This ends up as a number like "1.0.0.0" - how can I strip this down to "1.0.0"? Thanks, Johann - - Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Product Version via (bind.FileVersion.$(var.MAINEXE))
Hi All I'm using the approach of defining a variable for the product version which is bound from one of the assemblies. This ends up as a number like "1.0.0.0" - how can I strip this down to "1.0.0"? Thanks, Johann -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Wix - Planned release cycle
Rob, From http://robmensching.com/blog/posts/2012/8/21/Enter-WiX-v3.7-toolset, you hinted at 3.7 being a very short release cycle. I'm very interested in the build system improvements but was wondering if you had even a rough estimate of when you plan to have 3.7 in a RC. Thanks, Jacob -- 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] Bootstrapper.Engine.Detect() never calls event?
Oops, sorry, I think it works fine. I expected to find the PackageGroup Id string, but instead it games me the last part of the SourceFile of the MsiPackage or ExePacke, which is absolutely fine. Hans On Wed, Oct 24, 2012 at 3:26 PM, Hans ter Horst wrote: > Hello, > I would like to know the individual names of the packages installed and > one of the first things I do is to register the event handlers: > >this.Bootstrapper.ApplyComplete += this.OnApplyComplete; >this.Bootstrapper.DetectPackageComplete += > this.OnDetectPackageComplete; >this.Bootstrapper.PlanComplete += this.OnPlanComplete; > > The next thing I do is to call Bootstrapper.Engine.Detect(); in my Run > method before calling the Dispatcher.Run();. > > As far as I can tell, OnDetectPackageComplete is never called. If I > inspect the Bootstrapper.Engine.StringVariables["WixBundleInstalled"] > variable it returns either a 1 or a 0 to let me know if a component is > installed but I was hoping to find out the names of the packages installed. > > Hans > > -- > http://monochrome.me.uk/blog/ > > -- http://monochrome.me.uk/blog/ -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Bootstrapper.Engine.Detect() never calls event?
Hello, I would like to know the individual names of the packages installed and one of the first things I do is to register the event handlers: this.Bootstrapper.ApplyComplete += this.OnApplyComplete; this.Bootstrapper.DetectPackageComplete += this.OnDetectPackageComplete; this.Bootstrapper.PlanComplete += this.OnPlanComplete; The next thing I do is to call Bootstrapper.Engine.Detect(); in my Run method before calling the Dispatcher.Run();. As far as I can tell, OnDetectPackageComplete is never called. If I inspect the Bootstrapper.Engine.StringVariables["WixBundleInstalled"] variable it returns either a 1 or a 0 to let me know if a component is installed but I was hoping to find out the names of the packages installed. Hans -- http://monochrome.me.uk/blog/ -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Getting started writing a custom Bootstrapper interface
Hi Christian,
If it was up to me, I would gladly open-source it, I think I too would
benefit from other people's ideas, since I'm not really an expert in the
Win Installer field. This bootstrapper thing is just a side project I'm
working on. Anyway, if you or anyone else on this list have any questions
about implementing custom .net bootstrappers, I'm ready to help if I can.
Best regards,
Igor
On Tue, Oct 23, 2012 at 10:34 AM, Christian Hausknecht <
chauskne...@beracom.de> wrote:
> Hi Igor,
>
> I allready guessed that... unfortunately not much developers create such
> things for Open Source or Free Software projects :-(
>
> But thanks for telling us about your BA design and the decisions you took!
> That also helps :-)
>
> Best regards,
>
> Christian
>
> -Ursprüngliche Nachricht-
> Von: Igor Brejc [mailto:igor.br...@gmail.com]
> Gesendet: Dienstag, 23. Oktober 2012 10:13
> An: General discussion for Windows Installer XML toolset.
> Betreff: Re: [WiX-users] Getting started writing a custom Bootstrapper
> interface
>
> Hi Christian,
>
> Unfortunately I cannot release the source code, it's the property of the
> company I work for.
>
> Best regards,
> Igor
>
> On Mon, Oct 22, 2012 at 8:30 AM, Christian Hausknecht <
> chauskne...@beracom.de> wrote:
>
> > Hello Igor,
> >
> > is there any chance that you could provide us the source code?
> >
> > Bets regards,
> >
> > Christian
> >
> >
> > -Ursprüngliche Nachricht-
> > Von: Igor Brejc [mailto:igor.br...@gmail.com]
> > Gesendet: Samstag, 20. Oktober 2012 20:04
> > An: General discussion for Windows Installer XML toolset.
> > Betreff: 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).
> >
> > 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).
> >
> > Best regards,
> > Igor Brejc
> >
> > On Fri, Oct 19, 2012 at 10:39 AM, Hans ter Horst > >wrote:
> >
> > > Thanks Daniel, this is precisely what I needed!
> > >
> > > On Fri, Oct 19, 2012 at 9:32 AM, Daniel Bruce
> > > > > >wrote:
> > >
> > > > To resolve Microsoft.Tools.WindowsInstallerXml.Bootstrapper, you
> > > > need to add a reference to BootstrapperCore, which in my
> > > > installation was located under C:\Program Files (x86)\WiX Toolset
> > v3.7\SDK\BootstrapperCore.dll.
> > > You
> > > > should be able to find yours in a similar location.
> > > >
> > > > You are correct that there is little information about how to get
> > > > started with Burn, and the little information there is to find is
> > > > scattered
> > > around
> > > > the net and pretty terse, so I'll give you enough to get started,
> > > > then
> > > you
> > > > should be able to look at the source code for the WiX BA to
> > > > continue (I highly recommend having the source around to look at
> > > > either way, because there is really no other way to get
> > > > information about most
> > things).
> > > >
> > > > For my WPF-based bootstrapper interface, I started a regular WPF
> > > > application project and changed its output type to "class library".
> > > > Then
> > > I
> > > > have a class that inherits from BootstrapperApplication looking
> > > > something like this:
> > > >
> > > > public class MyBA : BootstrapperApplication {
> > > > static public Threading.Dispatcher Dispatcher { get; private
> set; }
> > > > static public View.InstallerWindow Window { get; private set; }
> > > > static public App TheApp { get; private set; }
> > > >
> > > > protected override void Run()
> > > > {
> > > > TheApp = new App();
> > > > TheApp.InitializeComponent();
> > > > // Send a ref
[WiX-users] Repair doesn't find MSI
Hello, I have the following question: What can I do, that the repair function works from the "add or remove programs" panel, or from the same MSI? If the MSI package was installed via msiexec /qn /I ".msi", the MSI searches for the original package only in the folder , not where the operating system stores a copy of the MSI, or where I try to repair from a new location, with a new download of the MSI. Uninstall works fine. regards, Martin -- 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
