[WiX-users] Pyro error: PYRO0227
Hi all, I'm having trouble with pyro, I get the PYRO0227 error even though I know there are changes between the files it's comparing. I even debugged the pyro c# code, what I saw was that the FileManager.CompareFiles works great, and the rows are marked RowOperation.Modify. but the GenerateTransform method that calls the MsiInterop.MsiDatabaseGenerateTransform returns the "ERROR_NO_DATA(0xE8) means no differences were found" I don't know why... When I go and change something manually in one of the text files I have everything works fine... but the .NET assemblies that is KNOW changed won't make it work... when it does work I get everything inside the msp files... Please help! Thanks. -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wow!
Dogfooding is very important. It's the way we learn how to do things better than we are doing them now (aka: we make mistakes, get feedback and adjust appropriately). As I noted above, it is pretty clear that we need to focus on improving the /layout experience for the WiX toolset. The WDK did this by incorporating the /layout option into their UI. I expect the answer is for the WiX BA to do the same. Also, I've toyed with putting together a "WiX Toolset Build Machine Edition" Bundle primarily as a way to dogfood the wixstdba. It would target the build machine scenario where you want the minimal pieces installed and you choose your NETFX since WiX command-line tools support NETFX2 or NETFX4. Basically, this would be a lot like the binaries.zip but with automatic MSBuild integration. Anyway, thank you all for feedback. Definitely helps us find the gaps. On Mon, Mar 5, 2012 at 1:43 PM, Neil Sleightholm wrote: > I don't believe there is any value in WiX being a web based install (other > than the very valid point about dog fooding the code). In addition the new > install forces me to install .Net 4.0 just because the installer needs it; > I would like that to be optional as I don't like polluting build machines > with more than it really necessary (I know I could manually install the > files but would rather not). I work in a company that has very little > internet access and have to request downloads, asking someone to download > the exe and then run it with the /Layout is a pain. > > Neil > > -Original Message- > From: Albert van Peppen [mailto:alb...@insad.nl] > Sent: 05 March 2012 16:52 > To: chr...@iswix.com; General discussion for Windows Installer XML > toolset. > Subject: Re: [WiX-users] Wow! > > I agree 100% with this. That is basically why I keep the entire history of > WiX in my repository (diskspace isn't that expensive nowadays :) ) > > > Best regards, > > Albert van Peppen > Senior System Engineer > > Insad Grafisch b.v. > Mollevite 28 > 6931 KG Westervoort > The Netherlands > > Phone: *31 (0) 26 319 01 50 > Email: alb...@insad.nl > Website: www.insad.nl > > -Oorspronkelijk bericht- > Van: Christopher Painter [mailto:chr...@iswix.com] > Verzonden: 05 March 2012 16:49 > Aan: Rob Mensching; General discussion for Windows Installer XML toolset. > Onderwerp: Re: [WiX-users] Wow! > > Rob, > > Regarding /layout, all developers *SHOULD* be doing it despite losing > those "savings". (Assuming any savings is actually realized based on how > many developers are installing the software. ) > > > Anyone involved in the process of developing software ( especially build > and release engineering ) should have mature policies regarding the > ability to track and archive changes to the development environment.If > I have to rebuild a build machine or developer machine I have to be able > go back and reinstall all of the tools exactly the way they were originally > intended. > > > Relying on content for a web-enabled installer to be available 1,5,10 > years down the road ( we still get requests to rebuild VB6 applications! ) > is a horrible practice as the external dependency is outside of your > control. > You must keep your own archive of the tool to ensure the SLA can b met. > Everyone who understands CM should be doing this. > > > Thus /layout is not only an annoyance to me, it's an antipattern. > > > Chris > > > > From: "Rob Mensching" > > Sent: Monday, March 05, 2012 9:38 AM > > To: chr...@iswix.com, "General discussion for Windows Installer XML > toolset." > > Subject: Re: [WiX-users] Wow! > > > 1. The WiX install *does* chain NETFX 4 in because that is needed before > the WiX BA can show UI (since the WiX BA is written in WPF). > > 2. Dogfooding is the primary reason. > > 3. We save *significant* bandwidth using Burn because during normal > installs it only downloads the portions of the product that you actually > need. > > If *everyone* start using /layout those savings will be lost. > > 4. The wixstdba UI is not as functional as we'd like but the web install > experience is significantly better. Click download like, survive the web > browser screening process (this gets better if we can get WiX signed), > click "Run" and in a second the ~500kb exe is verified and running. Then > you have a nice experience while the process downloads and installs only > the parts you need. > > Admittedly, if you want a full layout, then you do "Save" and have to run > another command-line. That scenario is not optimized. > > 5. ISOs are inferior to /layout because they do not get the built-in > robust downloading of Burn. You could use a 3rd party downloader but that > 3rd party download cannot verify the downloaded ISO file the way Burn will > verify and retry each file. > > > We are moving the cheese a little bit here to challenge the status quo and > see if we can't make things better for advanced users and less-advanced > users at the same t
Re: [WiX-users] Registering/Unregistering ActiveX contolrs
Brad,
One time I used the tools that were with WIX 2.0, but I can't remember the name
anymore.
After that I just manually register the file, and then look in
HKEY_CLASSES_ROOT looking for the object names and then the CLASSID\{guid}
keys. These were the two pieces I export and work from.
How much work this is depends on how much the control implements.
Also I had some information from the INF file as the ActiveX control started
life as a CAB file download.
Michael
-Original Message-
From: Brad Smith [mailto:brads...@tpg.com.au]
Sent: Tuesday, 6 March 2012 1:08 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Registering/Unregistering ActiveX contolrs
Hi Mike,
Thanks for your insights - just a question What tool(s) did you use to
find the differences in the registry?
Brad.
-Original Message-
From: Michael Osmond [mailto:mosm...@baytech.com.au]
Sent: Tuesday, 6 March 2012 10:24 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Registering/Unregistering ActiveX contolrs
Hi Brad,
My experience is that you need to work out what the class registrations are
(either by Harvesting or otherwise) and do these using the Registry elements
in the installation. Doing so gives you "registration" on install and
removal afterwards. It's a bit of a pain to setup the first time, but once
it is there it's pretty easy to maintain.
I think I "harvested" the hard way by registering and then using Regedit to
export the different keys I expected to a Reg file and building the WIX file
from that.
Michael
-Original Message-
From: Brad Smith [mailto:brads...@tpg.com.au]
Sent: Tuesday, 6 March 2012 12:06 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Registering/Unregistering ActiveX contolrs
Hi,
I'm wanting to register my old-school ActiveX control (PDFViewer.ocx) during
installation to use in my .NET application.
Umm, how do I do it in WIX?
I'm new to WIX, and from what I've seen so far this product looks very good.
My research has lead me to the following choices:
1. I could use a Custom Action (gotta work out how to do that yet). I'm sure
I can do this because I've got it registering & unregistering via native
method calls from C# (and no, i don't just call regsvr32.exe!). I'll have to
work out how to convert it to C++ (i.e. C++ Custom Action Project). I can go
down this path but my problem is that I don't know how to set up the
'unregistering' of the ActiveX control during un-installation. Do I make a
custom Action for unregistering, and if so, when/how do I get it to run?
2. I had a go at harvesting the registry, but I just couldn't get it
working. I cannot afford any more days on this-surely there is an easier
way? I tried to use an older Wix tool (is there one now?). I tried another
tool, but to no avail.
...or is there a simple ActiveX registration/un-registration feature in Wix?
I wasn't able to find much in documentation with this - can anyone help with
some links?
Any guidance from anyone would be greatly appreciated, as I'm keen to switch
over to using this product more regularly. I'm using .NET 4.0, Wix
v3.6.2627.0
Thanks,
Brad.
--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Keep Your Developer Skills Current with L
Re: [WiX-users] Registering/Unregistering ActiveX contolrs
Hi Mike, Thanks for your insights - just a question What tool(s) did you use to find the differences in the registry? Brad. -Original Message- From: Michael Osmond [mailto:mosm...@baytech.com.au] Sent: Tuesday, 6 March 2012 10:24 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Registering/Unregistering ActiveX contolrs Hi Brad, My experience is that you need to work out what the class registrations are (either by Harvesting or otherwise) and do these using the Registry elements in the installation. Doing so gives you "registration" on install and removal afterwards. It's a bit of a pain to setup the first time, but once it is there it's pretty easy to maintain. I think I "harvested" the hard way by registering and then using Regedit to export the different keys I expected to a Reg file and building the WIX file from that. Michael -Original Message- From: Brad Smith [mailto:brads...@tpg.com.au] Sent: Tuesday, 6 March 2012 12:06 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Registering/Unregistering ActiveX contolrs Hi, I'm wanting to register my old-school ActiveX control (PDFViewer.ocx) during installation to use in my .NET application. Umm, how do I do it in WIX? I'm new to WIX, and from what I've seen so far this product looks very good. My research has lead me to the following choices: 1. I could use a Custom Action (gotta work out how to do that yet). I'm sure I can do this because I've got it registering & unregistering via native method calls from C# (and no, i don't just call regsvr32.exe!). I'll have to work out how to convert it to C++ (i.e. C++ Custom Action Project). I can go down this path but my problem is that I don't know how to set up the 'unregistering' of the ActiveX control during un-installation. Do I make a custom Action for unregistering, and if so, when/how do I get it to run? 2. I had a go at harvesting the registry, but I just couldn't get it working. I cannot afford any more days on this-surely there is an easier way? I tried to use an older Wix tool (is there one now?). I tried another tool, but to no avail. ...or is there a simple ActiveX registration/un-registration feature in Wix? I wasn't able to find much in documentation with this - can anyone help with some links? Any guidance from anyone would be greatly appreciated, as I'm keen to switch over to using this product more regularly. I'm using .NET 4.0, Wix v3.6.2627.0 Thanks, Brad. -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Registering/Unregistering ActiveX contolrs
Hi Brad, My experience is that you need to work out what the class registrations are (either by Harvesting or otherwise) and do these using the Registry elements in the installation. Doing so gives you "registration" on install and removal afterwards. It's a bit of a pain to setup the first time, but once it is there it's pretty easy to maintain. I think I "harvested" the hard way by registering and then using Regedit to export the different keys I expected to a Reg file and building the WIX file from that. Michael -Original Message- From: Brad Smith [mailto:brads...@tpg.com.au] Sent: Tuesday, 6 March 2012 12:06 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Registering/Unregistering ActiveX contolrs Hi, I'm wanting to register my old-school ActiveX control (PDFViewer.ocx) during installation to use in my .NET application. Umm, how do I do it in WIX? I'm new to WIX, and from what I've seen so far this product looks very good. My research has lead me to the following choices: 1. I could use a Custom Action (gotta work out how to do that yet). I'm sure I can do this because I've got it registering & unregistering via native method calls from C# (and no, i don't just call regsvr32.exe!). I'll have to work out how to convert it to C++ (i.e. C++ Custom Action Project). I can go down this path but my problem is that I don't know how to set up the 'unregistering' of the ActiveX control during un-installation. Do I make a custom Action for unregistering, and if so, when/how do I get it to run? 2. I had a go at harvesting the registry, but I just couldn't get it working. I cannot afford any more days on this-surely there is an easier way? I tried to use an older Wix tool (is there one now?). I tried another tool, but to no avail. ...or is there a simple ActiveX registration/un-registration feature in Wix? I wasn't able to find much in documentation with this - can anyone help with some links? Any guidance from anyone would be greatly appreciated, as I'm keen to switch over to using this product more regularly. I'm using .NET 4.0, Wix v3.6.2627.0 Thanks, Brad. -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Registering/Unregistering ActiveX contolrs
Hi, I'm wanting to register my old-school ActiveX control (PDFViewer.ocx) during installation to use in my .NET application. Umm, how do I do it in WIX? I'm new to WIX, and from what I've seen so far this product looks very good. My research has lead me to the following choices: 1. I could use a Custom Action (gotta work out how to do that yet). I'm sure I can do this because I've got it registering & unregistering via native method calls from C# (and no, i don't just call regsvr32.exe!). I'll have to work out how to convert it to C++ (i.e. C++ Custom Action Project). I can go down this path but my problem is that I don't know how to set up the 'unregistering' of the ActiveX control during un-installation. Do I make a custom Action for unregistering, and if so, when/how do I get it to run? 2. I had a go at harvesting the registry, but I just couldn't get it working. I cannot afford any more days on this-surely there is an easier way? I tried to use an older Wix tool (is there one now?). I tried another tool, but to no avail. ...or is there a simple ActiveX registration/un-registration feature in Wix? I wasn't able to find much in documentation with this - can anyone help with some links? Any guidance from anyone would be greatly appreciated, as I'm keen to switch over to using this product more regularly. I'm using .NET 4.0, Wix v3.6.2627.0 Thanks, Brad. -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Mouseover
I'm not sure if the ToolTip attribute works on a Text Control. I'll let you experiment. -Original Message- From: James DellaRosa [mailto:jdellar...@aspexcorp.com] Sent: Monday, March 05, 2012 1:10 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Mouseover That works as far as a hover over event is concerned thanks! Now a more difficult concept... is there a way to make it so that the ToolTip attribute can reference another control, say a text control? -Original Message- From: Chad Petersen [mailto:chad.peter...@harlandfs.com] Sent: Monday, March 05, 2012 3:59 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Mouseover Check out the ToolTip attribute of the Control element. Should do exactly what you are looking for. At least that is how I use it. -Original Message- From: James DellaRosa [mailto:jdellar...@aspexcorp.com] Sent: Monday, March 05, 2012 12:35 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Mouseover I was wondering if there was any way to have text show up when a user hover's over a checkbox? For example let's say that someone has a few checkboxes that they can select from that would allow them to install separate products (FeatureX, FeatureY, FeatureZ). I want to be able to have the use hover over the checkbox for FeatureX and have a more in-depth description of what FeatureX does appear next to the checkbox. If anyone has any insight on this subject could let please let me know, thank you in advance for your time and help. -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wow!
I don't believe there is any value in WiX being a web based install (other than the very valid point about dog fooding the code). In addition the new install forces me to install .Net 4.0 just because the installer needs it; I would like that to be optional as I don't like polluting build machines with more than it really necessary (I know I could manually install the files but would rather not). I work in a company that has very little internet access and have to request downloads, asking someone to download the exe and then run it with the /Layout is a pain. Neil -Original Message- From: Albert van Peppen [mailto:alb...@insad.nl] Sent: 05 March 2012 16:52 To: chr...@iswix.com; General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Wow! I agree 100% with this. That is basically why I keep the entire history of WiX in my repository (diskspace isn't that expensive nowadays :) ) Best regards, Albert van Peppen Senior System Engineer Insad Grafisch b.v. Mollevite 28 6931 KG Westervoort The Netherlands Phone: *31 (0) 26 319 01 50 Email: alb...@insad.nl Website: www.insad.nl -Oorspronkelijk bericht- Van: Christopher Painter [mailto:chr...@iswix.com] Verzonden: 05 March 2012 16:49 Aan: Rob Mensching; General discussion for Windows Installer XML toolset. Onderwerp: Re: [WiX-users] Wow! Rob, Regarding /layout, all developers *SHOULD* be doing it despite losing those "savings". (Assuming any savings is actually realized based on how many developers are installing the software. ) Anyone involved in the process of developing software ( especially build and release engineering ) should have mature policies regarding the ability to track and archive changes to the development environment.If I have to rebuild a build machine or developer machine I have to be able go back and reinstall all of the tools exactly the way they were originally intended. Relying on content for a web-enabled installer to be available 1,5,10 years down the road ( we still get requests to rebuild VB6 applications! ) is a horrible practice as the external dependency is outside of your control. You must keep your own archive of the tool to ensure the SLA can b met. Everyone who understands CM should be doing this. Thus /layout is not only an annoyance to me, it's an antipattern. Chris From: "Rob Mensching" Sent: Monday, March 05, 2012 9:38 AM To: chr...@iswix.com, "General discussion for Windows Installer XML toolset." Subject: Re: [WiX-users] Wow! 1. The WiX install *does* chain NETFX 4 in because that is needed before the WiX BA can show UI (since the WiX BA is written in WPF). 2. Dogfooding is the primary reason. 3. We save *significant* bandwidth using Burn because during normal installs it only downloads the portions of the product that you actually need. If *everyone* start using /layout those savings will be lost. 4. The wixstdba UI is not as functional as we'd like but the web install experience is significantly better. Click download like, survive the web browser screening process (this gets better if we can get WiX signed), click "Run" and in a second the ~500kb exe is verified and running. Then you have a nice experience while the process downloads and installs only the parts you need. Admittedly, if you want a full layout, then you do "Save" and have to run another command-line. That scenario is not optimized. 5. ISOs are inferior to /layout because they do not get the built-in robust downloading of Burn. You could use a 3rd party downloader but that 3rd party download cannot verify the downloaded ISO file the way Burn will verify and retry each file. We are moving the cheese a little bit here to challenge the status quo and see if we can't make things better for advanced users and less-advanced users at the same time. My takeaway is that we may have deprioritized the /layout scenario too much and should evaluate that going into the home stretch. On Mon, Mar 5, 2012 at 7:06 AM, Christopher Painter wrote: Other then being allowing WiX to dogfood Burn, what benefit does the WiX installer even gain from using Burn? I thought the old Mondo UI looked just fine and it was a simpler 1 MSI story to boot. My experience with the Burn based WiX installers is that user experience is inferior relative to what it was. It doesn't seem like to me that WiX.msi needed any of the capabilities of Burn as it doesn't do things like install the .NET framework for you or chain multiple packages together. Personally, I still want my Visual Studio in ISO format and when SP1 comes out I'd appreciate a service release that contains it. I get sick of spending 20 minutes to install Visual Studio and 60 minutes to patch it. From: "Bruce Cran" Sent: Monday, March 05, 2012 8:43 AM To: "General discussion for Windows Installe
Re: [WiX-users] Mouseover
That works as far as a hover over event is concerned thanks! Now a more difficult concept... is there a way to make it so that the ToolTip attribute can reference another control, say a text control? -Original Message- From: Chad Petersen [mailto:chad.peter...@harlandfs.com] Sent: Monday, March 05, 2012 3:59 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Mouseover Check out the ToolTip attribute of the Control element. Should do exactly what you are looking for. At least that is how I use it. -Original Message- From: James DellaRosa [mailto:jdellar...@aspexcorp.com] Sent: Monday, March 05, 2012 12:35 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Mouseover I was wondering if there was any way to have text show up when a user hover's over a checkbox? For example let's say that someone has a few checkboxes that they can select from that would allow them to install separate products (FeatureX, FeatureY, FeatureZ). I want to be able to have the use hover over the checkbox for FeatureX and have a more in-depth description of what FeatureX does appear next to the checkbox. If anyone has any insight on this subject could let please let me know, thank you in advance for your time and help. -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Mouseover
Check out the ToolTip attribute of the Control element. Should do exactly what you are looking for. At least that is how I use it. -Original Message- From: James DellaRosa [mailto:jdellar...@aspexcorp.com] Sent: Monday, March 05, 2012 12:35 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Mouseover I was wondering if there was any way to have text show up when a user hover's over a checkbox? For example let's say that someone has a few checkboxes that they can select from that would allow them to install separate products (FeatureX, FeatureY, FeatureZ). I want to be able to have the use hover over the checkbox for FeatureX and have a more in-depth description of what FeatureX does appear next to the checkbox. If anyone has any insight on this subject could let please let me know, thank you in advance for your time and help. -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Mouseover
I was wondering if there was any way to have text show up when a user hover's over a checkbox? For example let's say that someone has a few checkboxes that they can select from that would allow them to install separate products (FeatureX, FeatureY, FeatureZ). I want to be able to have the use hover over the checkbox for FeatureX and have a more in-depth description of what FeatureX does appear next to the checkbox. If anyone has any insight on this subject could let please let me know, thank you in advance for your time and help. -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wow!
Also agree 100% on this for the reasons Chris mentions. The rest of this message is my (perhaps strong) opinion on web setups. Web setups for development tools in general encourage bad habits. It might not be such a big deal with "consumer" software on home computers, like Acrobat Reader & company - which fits in with the general consumer business of "buy this mobile device [cell phone, tablet, MP3 player, laptop], don't worry about maintenance - you'll throw it in the trash bin in a year anyway". These vendors don't think about long-term maintenance - a web setup is one aspect of this. But WiX is not consumer software, and a web setup has no place with WiX users who are correctly managing their development environment & processes - for the reasons Chris mentions. (Unless you are developing throw-away software that won't last a year). I need to be able to check out code from my repository 5 years down the road, and recompile it with exactly the same tools used to originally build that software from 5 years ago. Web setups don't provide a guarantee that I can reproduce the same development environment. The best way of distributing long-lifetime software is a complete image provided by the vendor that has not been contaminated with customer-specific license information. For smaller packages (like WiX), that is often a single setup executable. For larger packages (e.g. Office or Visual Studio), it MUST take the form of an ISO file. Send me my product key separately, thank you. I recently bought a copy of Office 2010 Pro online. The setup was provided in a self-extracting EXE with the product key already embedded in it. I specifically sought out the option to order a "backup DVD" - especially because I wanted a perfect, unmodified image of MS Office that wasn't contaminated with customer-specific information, and didn't require a self-extractor. Why can't they just provide the ISO for download after I buy the software? Beats me. Heck, why don't they just put the Office ISO available for public download on the web site? With Office Product Activation, there's really no reason why not - the ISO would install a trial version until you activate it... I really don't want to see Visual Studio go down the path Office has taken with distribution. I was happy with the way WiX 3.0 was distributed: full MSI file, full binary archive, and source code archive. Please keep those options, it was perfect. :) No need to mess with funny distribution methods like MS Office, Adobe, etc. do. More ranting: web setups have been one of my biggest annoyances in setup for the past several years. Call me old-fashioned, but when the vendor then makes it difficult to find a direct link to an "offline" installer to bypass the web install junk, I then start getting irate. Requiring me to run with some "/layout" option instead of providing a complete, offline image definitely falls under the category of getting me irate. (What if I don't run it perfectly and get a perfect, definitive image of everything needed for an offline distribution?) A downloader that installs itself onto my computer (separate from the software being installed, and requiring me to later remove it using Add/Remove Programs) is another highly offensive behavior. Making me install ActiveX controls is another way. So at the end of the day, there would have better be an offline installer ready for one-click download. Oftentimes, the built-in downloader in my web browser provides a better, consistent experience (e.g. pause/resume, and better handling if the connection drops) - and it doesn't leave behind additional unwanted cruft on my computer. I realize Burn might not offend in all these different ways - but with every software vendor doing their own thing, it is better for me to not waste my time, and just get the offline installer. -Original Message- From: Christopher Painter [mailto:chr...@iswix.com] Sent: Monday, March 05, 2012 15:49 To: Rob Mensching; General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Wow! Rob, Regarding /layout, all developers *SHOULD* be doing it despite losing those "savings". (Assuming any savings is actually realized based on how many developers are installing the software. ) Anyone involved in the process of developing software ( especially build and release engineering ) should have mature policies regarding the ability to track and archive changes to the development environment.If I have to rebuild a build machine or developer machine I have to be able go back and reinstall all of the tools exactly the way they were originally intended. Relying on content for a web-enabled installer to be available 1,5,10 years down the road ( we still get requests to rebuild VB6 applications! ) is a horrible practice as the external dependency is outside of your control. You must keep your own archive of the tool to ensure the SLA can b met. Everyone who understands CM
Re: [WiX-users] Wow!
On 05/03/2012 17:13, Bruce Cran wrote: > There was a rather lengthy discussion about this wrt driver > development at > http://www.osronline.com/cf.cfm?PageURL=showlists.cfm?list=NTDEV a few > days ago. The link to the actual thread is http://www.osronline.com/showthread.cfm?link=220737 -- Bruce Cran -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wow!
Bruce, can you provide a direct link to the thread? I'm having trouble finding it. Edwin G. Castro Software Developer - Staff Digital Channels Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail > -Original Message- > From: Bruce Cran [mailto:br...@cran.org.uk] > Sent: Monday, March 05, 2012 9:14 AM > To: General discussion for Windows Installer XML toolset. > Cc: Castro, Edwin G. (Hillsboro); chr...@iswix.com > Subject: Re: [WiX-users] Wow! > > On 05/03/2012 17:03, Castro, Edwin G. (Hillsboro) wrote: > > Often corporate policies restrict internet access in such a way where asking > each development machine to download the packages is actually very painful. > Local caches (which should be accessible directly on the target server _or_ a > local network share _or_ on a local web server) should be supported for > enterprise deployments. > > > > I'm not saying that download and verification provides absolutely no value > because that functionality provides value to the average user that is > installing > software to their home computer. What I'm saying is that when there is an IT > department between you and management of your machine then features like > download and verification only provide marginal value because IT departments > often want to be in more control. > > There was a rather lengthy discussion about this wrt driver development at > http://www.osronline.com/cf.cfm?PageURL=showlists.cfm?list=NTDEV a few > days ago. > > -- > Bruce Cran -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wow!
On 05/03/2012 17:03, Castro, Edwin G. (Hillsboro) wrote: > Often corporate policies restrict internet access in such a way where asking > each development machine to download the packages is actually very painful. > Local caches (which should be accessible directly on the target server _or_ a > local network share _or_ on a local web server) should be supported for > enterprise deployments. > > I'm not saying that download and verification provides absolutely no value > because that functionality provides value to the average user that is > installing software to their home computer. What I'm saying is that when > there is an IT department between you and management of your machine then > features like download and verification only provide marginal value because > IT departments often want to be in more control. There was a rather lengthy discussion about this wrt driver development at http://www.osronline.com/cf.cfm?PageURL=showlists.cfm?list=NTDEV a few days ago. -- Bruce Cran -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wow!
Often corporate policies restrict internet access in such a way where asking each development machine to download the packages is actually very painful. Local caches (which should be accessible directly on the target server _or_ a local network share _or_ on a local web server) should be supported for enterprise deployments. I'm not saying that download and verification provides absolutely no value because that functionality provides value to the average user that is installing software to their home computer. What I'm saying is that when there is an IT department between you and management of your machine then features like download and verification only provide marginal value because IT departments often want to be in more control. Edwin G. Castro Software Developer - Staff Digital Channels Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail > -Original Message- > From: Albert van Peppen [mailto:alb...@insad.nl] > Sent: Monday, March 05, 2012 8:52 AM > To: chr...@iswix.com; General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Wow! > > I agree 100% with this. That is basically why I keep the entire history of > WiX in > my repository (diskspace isn't that expensive nowadays :) ) > > > Best regards, > > Albert van Peppen > Senior System Engineer > > Insad Grafisch b.v. > Mollevite 28 > 6931 KG Westervoort > The Netherlands > > Phone: *31 (0) 26 319 01 50 > Email: alb...@insad.nl > Website: www.insad.nl > > -Oorspronkelijk bericht- > Van: Christopher Painter [mailto:chr...@iswix.com] > Verzonden: 05 March 2012 16:49 > Aan: Rob Mensching; General discussion for Windows Installer XML toolset. > Onderwerp: Re: [WiX-users] Wow! > > Rob, > > Regarding /layout, all developers *SHOULD* be doing it despite losing those > "savings". (Assuming any savings is actually realized based on how many > developers are installing the software. ) > > > Anyone involved in the process of developing software ( especially build and > release engineering ) should have mature policies regarding the > ability to track and archive changes to the development environment.If > I have to rebuild a build machine or developer machine I have to be able go > back and reinstall all of the tools exactly the way they were originally > intended. > > > Relying on content for a web-enabled installer to be available 1,5,10 years > down the road ( we still get requests to rebuild VB6 applications! ) is a > horrible > practice as the external dependency is outside of your control. > You must keep your own archive of the tool to ensure the SLA can b met. > Everyone who understands CM should be doing this. > > > Thus /layout is not only an annoyance to me, it's an antipattern. > > > Chris > > > > From: "Rob Mensching" > > Sent: Monday, March 05, 2012 9:38 AM > > To: chr...@iswix.com, "General discussion for Windows Installer XML toolset." > > > Subject: Re: [WiX-users] Wow! > > > 1. The WiX install *does* chain NETFX 4 in because that is needed before the > WiX BA can show UI (since the WiX BA is written in WPF). > > 2. Dogfooding is the primary reason. > > 3. We save *significant* bandwidth using Burn because during normal installs > it > only downloads the portions of the product that you actually need. > > If *everyone* start using /layout those savings will be lost. > > 4. The wixstdba UI is not as functional as we'd like but the web install > experience is significantly better. Click download like, survive the web > browser > screening process (this gets better if we can get WiX signed), click "Run" > and in > a second the ~500kb exe is verified and running. Then you have a nice > experience while the process downloads and installs only the parts you need. > > Admittedly, if you want a full layout, then you do "Save" and have to run > another command-line. That scenario is not optimized. > > 5. ISOs are inferior to /layout because they do not get the built-in robust > downloading of Burn. You could use a 3rd party downloader but that 3rd party > download cannot verify the downloaded ISO file the way Burn will verify and > retry each file. > > > We are moving the cheese a little bit here to challenge the status quo and see > if we can't make things better for advanced users and less-advanced users at > the same time. My takeaway is that we may have deprioritized the /layout > scenario too much and should evaluate that going into the home stretch. > > > > On Mon, Mar 5, 2012 at 7:06 AM, Christopher Painter > wrote: > > Other then being allowing WiX to dogfood Burn, what benefit does the WiX > > installer even gain from using Burn? I thought the old Mondo UI looked > > just fine and it was a simpler 1 MSI story to boot. My experience with > > the Burn based WiX installers is that user experience is inferior relative > > to w
Re: [WiX-users] Wow!
I agree 100% with this. That is basically why I keep the entire history of WiX in my repository (diskspace isn't that expensive nowadays :) ) Best regards, Albert van Peppen Senior System Engineer Insad Grafisch b.v. Mollevite 28 6931 KG Westervoort The Netherlands Phone: *31 (0) 26 319 01 50 Email: alb...@insad.nl Website: www.insad.nl -Oorspronkelijk bericht- Van: Christopher Painter [mailto:chr...@iswix.com] Verzonden: 05 March 2012 16:49 Aan: Rob Mensching; General discussion for Windows Installer XML toolset. Onderwerp: Re: [WiX-users] Wow! Rob, Regarding /layout, all developers *SHOULD* be doing it despite losing those "savings". (Assuming any savings is actually realized based on how many developers are installing the software. ) Anyone involved in the process of developing software ( especially build and release engineering ) should have mature policies regarding the ability to track and archive changes to the development environment.If I have to rebuild a build machine or developer machine I have to be able go back and reinstall all of the tools exactly the way they were originally intended. Relying on content for a web-enabled installer to be available 1,5,10 years down the road ( we still get requests to rebuild VB6 applications! ) is a horrible practice as the external dependency is outside of your control. You must keep your own archive of the tool to ensure the SLA can b met. Everyone who understands CM should be doing this. Thus /layout is not only an annoyance to me, it's an antipattern. Chris From: "Rob Mensching" Sent: Monday, March 05, 2012 9:38 AM To: chr...@iswix.com, "General discussion for Windows Installer XML toolset." Subject: Re: [WiX-users] Wow! 1. The WiX install *does* chain NETFX 4 in because that is needed before the WiX BA can show UI (since the WiX BA is written in WPF). 2. Dogfooding is the primary reason. 3. We save *significant* bandwidth using Burn because during normal installs it only downloads the portions of the product that you actually need. If *everyone* start using /layout those savings will be lost. 4. The wixstdba UI is not as functional as we'd like but the web install experience is significantly better. Click download like, survive the web browser screening process (this gets better if we can get WiX signed), click "Run" and in a second the ~500kb exe is verified and running. Then you have a nice experience while the process downloads and installs only the parts you need. Admittedly, if you want a full layout, then you do "Save" and have to run another command-line. That scenario is not optimized. 5. ISOs are inferior to /layout because they do not get the built-in robust downloading of Burn. You could use a 3rd party downloader but that 3rd party download cannot verify the downloaded ISO file the way Burn will verify and retry each file. We are moving the cheese a little bit here to challenge the status quo and see if we can't make things better for advanced users and less-advanced users at the same time. My takeaway is that we may have deprioritized the /layout scenario too much and should evaluate that going into the home stretch. On Mon, Mar 5, 2012 at 7:06 AM, Christopher Painter wrote: Other then being allowing WiX to dogfood Burn, what benefit does the WiX installer even gain from using Burn? I thought the old Mondo UI looked just fine and it was a simpler 1 MSI story to boot. My experience with the Burn based WiX installers is that user experience is inferior relative to what it was. It doesn't seem like to me that WiX.msi needed any of the capabilities of Burn as it doesn't do things like install the .NET framework for you or chain multiple packages together. Personally, I still want my Visual Studio in ISO format and when SP1 comes out I'd appreciate a service release that contains it. I get sick of spending 20 minutes to install Visual Studio and 60 minutes to patch it. From: "Bruce Cran" Sent: Monday, March 05, 2012 8:43 AM To: "General discussion for Windows Installer XML toolset." Subject: Re: [WiX-users] Wow! On 05/03/2012 14:01, keith.doug...@statcan.gc.ca wrote: > The below news is somewhat distressing for those of us who have no Internet connection at all on our development workstations and have to use others (non-development machines) to get such access. Is downloading the /layout way and then (say) moving a directory or something going to work, or does /layout change other things (registry)? If it is going to work, will the procedure be well documented? If not, what do you propose people in my sort of situation to do? > > (And if Visual Studio 2011 works either of those ways we're going to > be in a world of hurt here ...) As I understand it, /layout does nothing more than grab a copy of the files for offline u
Re: [WiX-users] Cached MSI getting deleted in maintenance mode
Resending
Regards
Meera
On Sat, Mar 3, 2012 at 9:25 PM, Meera Jindal wrote:
> Hi,
>
> We are using Wix version 2 in our product and at some point in the future
> we would be migrating to version 3.5/3.6.
>
> Our product is localized and for achieving localization we use Wix
> bootstrapper(setupbld.exe) to apply a language transform on top of an
> English msi.
> Hence, when the user doubleclicks a setup.exe(which contains the MSI and
> language transforms), I see two files being cached to the directory
> specified by the
> InstallSource folder(as specified by the value of registry
> key
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\
> .
> These two files are the msi and the transform file.
>
> The product installation works fine. However, after the product
> installation if the user double clicks the setup.exe again,
> a maintenance mode screen pulls up.
> If a user clicks cancel after this dialog pulls up, then the msi in the
> InstallSource folder gets deleted. This has the consequence that future
> uninstalls or repair/change from the
> Add or Remove programs fail with the error "The feature you are trying to
> use is on a network resource that is unavailable". The log messages in MSI
> log are
>
> MSI (s) (8C:7C) [20:33:59:072]: Machine policy value 'AllowLockdownPatch'
> is 0
> MSI (s) (8C:7C) [20:33:59:072]: Machine policy value 'DisableLUAPatching'
> is 0
> MSI (s) (8C:7C) [20:33:59:072]: Using cached product context: machine
> assigned for product: BDDF47C439EE2C04ABDCCF98726286F0
> MSI (s) (8C:7C) [20:33:59:072]: Using cached product context: machine
> assigned for product: BDDF47C439EE2C04ABDCCF98726286F0
> MSI (s) (8C:7C) [20:33:59:072]: Machine policy value
> 'DisableFlyWeightPatching' is 0
> MSI (s) (8C:7C) [20:33:59:072]: Enabling baseline caching for this
> transaction since all active patches are MSI 3.0 style MSPs or at least one
> MSI 3.0 minor update patch is active
> MSI (s) (8C:7C) [20:33:59:072]: Looking for secure file transform:
> MSI (s) (8C:7C) [20:33:59:072]: Note: 1: 2343
> MSI (s) (8C:7C) [20:33:59:072]: Unable to create a temp copy of transform
> ''.
> MSI (s) (8C:7C) [20:33:59:072]: Note: 1: 2203 2: 3: -2147287037
> MSI (s) (8C:7C) [20:33:59:072]: Couldn't find cached transform . Looking
> for it at the source.
> MSI (s) (8C:7C) [20:33:59:072]: Resolving source.
> MSI (s) (8C:7C) [20:33:59:072]: Using cached product context: machine
> assigned for product: BDDF47C439EE2C04ABDCCF98726286F8
> MSI (s) (8C:7C) [20:33:59:072]: Using cached product context: machine
> assigned for product: BDDF47C439EE2C04ABDCCF98726286F8
> MSI (s) (8C:7C) [20:33:59:072]: Note: 1: 1402 2:
> HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer
> 3: 2
> MSI (s) (8C:7C) [20:33:59:072]: User policy value 'SearchOrder' is 'nmu'
> MSI (s) (8C:7C) [20:33:59:072]: User policy value 'DisableMedia' is 0
> MSI (s) (8C:7C) [20:33:59:072]: Machine policy value 'AllowLockdownMedia'
> is 1
> MSI (s) (8C:7C) [20:33:59:072]: SOURCEMGMT: Looking for sourcelist for
> product {4C74FDDB-EE93-40C2-BACD-FC8927266898}
> MSI (s) (8C:7C) [20:33:59:072]: Using cached product context: machine
> assigned for product: BDDF47C439EE2C04ABDCCF98726286F8
> MSI (s) (8C:7C) [20:33:59:072]: SOURCEMGMT: Adding
> {4C74FDDB-EE93-40C2-BACD-FC892726680F}; to potential sourcelist list
> (pcode;disk;relpath).
> MSI (s) (8C:7C) [20:33:59:072]: Using cached product context: machine
> assigned for product: BDDF47C439EE2C04ABDCCF98726286F0
> MSI (s) (8C:7C) [20:33:59:072]: SOURCEMGMT: Now checking product
> {4C74FDDB-EE93-40C2-BACD-FC8927266898}
> MSI (s) (8C:7C) [20:33:59:072]: SOURCEMGMT: Attempting to use
> LastUsedSource from source list.
> MSI (s) (8C:7C) [20:33:59:072]: SOURCEMGMT: Trying source
> C:\ProgramData\Applications\Cache\.
> MSI (s) (8C:7C) [20:33:59:072]: Note: 1: 2203 2:
> C:\ProgramData\Applications\Cache\{3983C254-9118-46FA-A63E-E71653414BFC}v4.999.2.0.msi
> 3: -2147287038
> MSI (s) (8C:7C) [20:33:59:072]: SOURCEMGMT: Source is invalid due to
> missing/inaccessible package.
> MSI (s) (8C:7C) [20:33:59:072]: Note: 1: 1706 2: -2147483647 3:
> {3983C254-9118-46FA-A63E-E71653414BFC}v4.999.2.0.msi
>
> However, if I enter into the maintenance mode from the change/repair tab
> in Add or Remove Programs then the cached MSI does not get deleted. We
> explicitly do not
> schedule a ResolveSource action.
>
> My questions are
>
> 1) Is there any way in which I can prevent the deletion of the cached MSI
> file in the InstallSource directory if the user were to double click the
> setup.exe to open the maintenance mode and then cancel
> the operation?
> 2) Currently the MaintainenceDlg opens if the following condition is
> satisfied(Installed AND NOT RESUME AND NOT Preselected). Can I change the
> condition so that the dialog
> does not open if the user double clicks the setup.exe, but opens if the
> user were to try it from Add or Remove Programs?
>
> Apolo
Re: [WiX-users] Wow!
Rob, Regarding /layout, all developers *SHOULD* be doing it despite losing those "savings". (Assuming any savings is actually realized based on how many developers are installing the software. ) Anyone involved in the process of developing software ( especially build and release engineering ) should have mature policies regarding the ability to track and archive changes to the development environment.If I have to rebuild a build machine or developer machine I have to be able go back and reinstall all of the tools exactly the way they were originally intended. Relying on content for a web-enabled installer to be available 1,5,10 years down the road ( we still get requests to rebuild VB6 applications! ) is a horrible practice as the external dependency is outside of your control. You must keep your own archive of the tool to ensure the SLA can b met. Everyone who understands CM should be doing this. Thus /layout is not only an annoyance to me, it's an antipattern. Chris From: "Rob Mensching" Sent: Monday, March 05, 2012 9:38 AM To: chr...@iswix.com, "General discussion for Windows Installer XML toolset." Subject: Re: [WiX-users] Wow! 1. The WiX install *does* chain NETFX 4 in because that is needed before the WiX BA can show UI (since the WiX BA is written in WPF). 2. Dogfooding is the primary reason. 3. We save *significant* bandwidth using Burn because during normal installs it only downloads the portions of the product that you actually need. If *everyone* start using /layout those savings will be lost. 4. The wixstdba UI is not as functional as we'd like but the web install experience is significantly better. Click download like, survive the web browser screening process (this gets better if we can get WiX signed), click "Run" and in a second the ~500kb exe is verified and running. Then you have a nice experience while the process downloads and installs only the parts you need. Admittedly, if you want a full layout, then you do "Save" and have to run another command-line. That scenario is not optimized. 5. ISOs are inferior to /layout because they do not get the built-in robust downloading of Burn. You could use a 3rd party downloader but that 3rd party download cannot verify the downloaded ISO file the way Burn will verify and retry each file. We are moving the cheese a little bit here to challenge the status quo and see if we can't make things better for advanced users and less-advanced users at the same time. My takeaway is that we may have deprioritized the /layout scenario too much and should evaluate that going into the home stretch. On Mon, Mar 5, 2012 at 7:06 AM, Christopher Painter wrote: Other then being allowing WiX to dogfood Burn, what benefit does the WiX installer even gain from using Burn? I thought the old Mondo UI looked just fine and it was a simpler 1 MSI story to boot. My experience with the Burn based WiX installers is that user experience is inferior relative to what it was. It doesn't seem like to me that WiX.msi needed any of the capabilities of Burn as it doesn't do things like install the .NET framework for you or chain multiple packages together. Personally, I still want my Visual Studio in ISO format and when SP1 comes out I'd appreciate a service release that contains it. I get sick of spending 20 minutes to install Visual Studio and 60 minutes to patch it. From: "Bruce Cran" Sent: Monday, March 05, 2012 8:43 AM To: "General discussion for Windows Installer XML toolset." Subject: Re: [WiX-users] Wow! On 05/03/2012 14:01, keith.doug...@statcan.gc.ca wrote: > The below news is somewhat distressing for those of us who have no Internet connection at all on our development workstations and have to use others (non-development machines) to get such access. Is downloading the /layout way and then (say) moving a directory or something going to work, or does /layout change other things (registry)? If it is going to work, will the procedure be well documented? If not, what do you propose people in my sort of situation to do? > > (And if Visual Studio 2011 works either of those ways we're going to be in a world of hurt here ...) As I understand it, /layout does nothing more than grab a copy of the files for offline use - for example the WDK 8 beta comes as a .zip that looks like it's been created by running /layout since there's wdksetup.exe and an 'Installers' directory. If you rename the directory, wdksetup.exe goes online to fetch the files. Of course it doesn't help if you want to do the download using your Mac. -- Bruce Cran -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio
Re: [WiX-users] Visual Studio 11 Support Timeline?
Thanks ... now migrating VS setup projects. - Raphael -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Samstag, 3. März 2012 04:38 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Visual Studio 11 Support Timeline? WiX v3.6 Beta does not support VS 11. You need a more recent build from http://wixtoolset.org/releases On Fri, Mar 2, 2012 at 7:53 AM, Raphael Schweizer < rschwei...@schweizer-informatik.ch> wrote: > Hi WiX users > > Rob Mensching wrote: > > Latest WiX v3.6 builds support Dev11. You may need to run devenv.exe > /setup > > right now... we're trying to track down a real answer on that. > > Any hints how to get that to work? I downloaded and installed WiX > 3.6.2221.0 but had no WiX project types in VS 11.0.50214.1 even after > running "devenv.exe /setup". WiX projects created in VS 2010 are > unknown to VS 11. > > Thanks > - Raphael > > -- > Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing also > focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- virtually, Rob Mensching - http://RobMensching.com LLC -- Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wow!
1. The WiX install *does* chain NETFX 4 in because that is needed before the WiX BA can show UI (since the WiX BA is written in WPF). 2. Dogfooding is the primary reason. 3. We save *significant* bandwidth using Burn because during normal installs it only downloads the portions of the product that you actually need. If *everyone* start using /layout those savings will be lost. 4. The wixstdba UI is not as functional as we'd like but the web install experience is significantly better. Click download like, survive the web browser screening process (this gets better if we can get WiX signed), click "Run" and in a second the ~500kb exe is verified and running. Then you have a nice experience while the process downloads and installs only the parts you need. Admittedly, if you want a full layout, then you do "Save" and have to run another command-line. That scenario is not optimized. 5. ISOs are inferior to /layout because they do not get the built-in robust downloading of Burn. You could use a 3rd party downloader but that 3rd party download cannot verify the downloaded ISO file the way Burn will verify and retry each file. We are moving the cheese a little bit here to challenge the status quo and see if we can't make things better for advanced users and less-advanced users at the same time. My takeaway is that we may have deprioritized the /layout scenario too much and should evaluate that going into the home stretch. On Mon, Mar 5, 2012 at 7:06 AM, Christopher Painter wrote: > Other then being allowing WiX to dogfood Burn, what benefit does the WiX > installer even gain from using Burn? I thought the old Mondo UI looked > just fine and it was a simpler 1 MSI story to boot. My experience with > the Burn based WiX installers is that user experience is inferior relative > to what it was. It doesn't seem like to me that WiX.msi needed any of the > capabilities of Burn as it doesn't do things like install the .NET > framework for you or chain multiple packages together. > > Personally, I still want my Visual Studio in ISO format and when SP1 comes > out I'd appreciate a service release that contains it. I get sick of > spending 20 minutes to install Visual Studio and 60 minutes to patch it. > > > > From: "Bruce Cran" > > Sent: Monday, March 05, 2012 8:43 AM > > To: "General discussion for Windows Installer XML toolset." > > > Subject: Re: [WiX-users] Wow! > > > On 05/03/2012 14:01, keith.doug...@statcan.gc.ca wrote: > > > The below news is somewhat distressing for those of us who have no > Internet connection at all on our development workstations and have to use > others (non-development machines) to get such access. Is downloading the > /layout way and then (say) moving a directory or something going to work, > or does /layout change other things (registry)? If it is going to work, > will the procedure be well documented? If not, what do you propose people > in my sort of situation to do? > > > > > > (And if Visual Studio 2011 works either of those ways we're going to be > in a world of hurt here ...) > > > As I understand it, /layout does nothing more than grab a copy of the > > files for offline use - for example the WDK 8 beta comes as a .zip that > > looks like it's been created by running /layout since there's > > wdksetup.exe and an 'Installers' directory. If you rename the directory, > > wdksetup.exe goes online to fetch the files. > > Of course it doesn't help if you want to do the download using your Mac. > > > -- > > Bruce Cran > > > > > -- > > Try before you buy = See our experts in action! > > The most comprehensive online learning library for Microsoft developers > > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > > Metro Style Apps, more. Free future releases when you subscribe now! > > http://p.sf.net/sfu/learndevnow-dev2 > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > -- > Try before you buy = See our experts in action! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-dev2 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- virtually, Rob Mensching - http://RobMensching.com LLC -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, Sha
Re: [WiX-users] Wow!
Bruce is correct. You will need to be connected to the internet to get the executable and then run the /layout switch. The /layout switch will create a full "DVD" image locally that will not need internet access. Doing all this on a Mac was never a goal. On Mon, Mar 5, 2012 at 6:37 AM, Bruce Cran wrote: > On 05/03/2012 14:01, keith.doug...@statcan.gc.ca wrote: > > The below news is somewhat distressing for those of us who have no > Internet connection at all on our development workstations and have to use > others (non-development machines) to get such access. Is downloading the > /layout way and then (say) moving a directory or something going to work, > or does /layout change other things (registry)? If it is going to work, > will the procedure be well documented? If not, what do you propose people > in my sort of situation to do? > > > > (And if Visual Studio 2011 works either of those ways we're going to be > in a world of hurt here ...) > > As I understand it, /layout does nothing more than grab a copy of the > files for offline use - for example the WDK 8 beta comes as a .zip that > looks like it's been created by running /layout since there's > wdksetup.exe and an 'Installers' directory. If you rename the directory, > wdksetup.exe goes online to fetch the files. > Of course it doesn't help if you want to do the download using your Mac. > > -- > Bruce Cran > > > -- > Try before you buy = See our experts in action! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-dev2 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- virtually, Rob Mensching - http://RobMensching.com LLC -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wow!
Other then being allowing WiX to dogfood Burn, what benefit does the WiX installer even gain from using Burn? I thought the old Mondo UI looked just fine and it was a simpler 1 MSI story to boot. My experience with the Burn based WiX installers is that user experience is inferior relative to what it was. It doesn't seem like to me that WiX.msi needed any of the capabilities of Burn as it doesn't do things like install the .NET framework for you or chain multiple packages together. Personally, I still want my Visual Studio in ISO format and when SP1 comes out I'd appreciate a service release that contains it. I get sick of spending 20 minutes to install Visual Studio and 60 minutes to patch it. From: "Bruce Cran" Sent: Monday, March 05, 2012 8:43 AM To: "General discussion for Windows Installer XML toolset." Subject: Re: [WiX-users] Wow! On 05/03/2012 14:01, keith.doug...@statcan.gc.ca wrote: > The below news is somewhat distressing for those of us who have no Internet connection at all on our development workstations and have to use others (non-development machines) to get such access. Is downloading the /layout way and then (say) moving a directory or something going to work, or does /layout change other things (registry)? If it is going to work, will the procedure be well documented? If not, what do you propose people in my sort of situation to do? > > (And if Visual Studio 2011 works either of those ways we're going to be in a world of hurt here ...) As I understand it, /layout does nothing more than grab a copy of the files for offline use - for example the WDK 8 beta comes as a .zip that looks like it's been created by running /layout since there's wdksetup.exe and an 'Installers' directory. If you rename the directory, wdksetup.exe goes online to fetch the files. Of course it doesn't help if you want to do the download using your Mac. -- Bruce Cran -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wow!
On 05/03/2012 14:01, keith.doug...@statcan.gc.ca wrote: > The below news is somewhat distressing for those of us who have no Internet > connection at all on our development workstations and have to use others > (non-development machines) to get such access. Is downloading the /layout way > and then (say) moving a directory or something going to work, or does /layout > change other things (registry)? If it is going to work, will the procedure be > well documented? If not, what do you propose people in my sort of situation > to do? > > (And if Visual Studio 2011 works either of those ways we're going to be in a > world of hurt here ...) As I understand it, /layout does nothing more than grab a copy of the files for offline use - for example the WDK 8 beta comes as a .zip that looks like it's been created by running /layout since there's wdksetup.exe and an 'Installers' directory. If you rename the directory, wdksetup.exe goes online to fetch the files. Of course it doesn't help if you want to do the download using your Mac. -- Bruce Cran -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wow!
Hi Bruce, etc. The below news is somewhat distressing for those of us who have no Internet connection at all on our development workstations and have to use others (non-development machines) to get such access. Is downloading the /layout way and then (say) moving a directory or something going to work, or does /layout change other things (registry)? If it is going to work, will the procedure be well documented? If not, what do you propose people in my sort of situation to do? (And if Visual Studio 2011 works either of those ways we're going to be in a world of hurt here ...) Keith Douglas Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6 keith.doug...@statcan.gc.ca Telephone | Téléphone 613-951-4405 Facsimile | Télécopieur 613-951-1966 Government of Canada | Gouvernement du Canada -Original Message- From: Bruce Cran [mailto:br...@cran.org.uk] Sent: March-05-12 2:43 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Wow! On 05/03/2012 07:04, Dirk Räder wrote: > will there be any kind of offline installer available? I mean a real > installer that does all the necessary registry and environment > operations, not the /layout switch that just drops the file structure. /layout just gets any .cab or .msi files that the installer needs. When you run the bootstrapper without /layout it still does all the registry operations etc. but will use the local files instead of downloading them again. -- Bruce Cran -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [WIX-users] Patch in Wix 3.6 is empty. warning PYRO1079: The cabinet '***.cab' does not contain any files
Does it make any difference if you add a PatchFamily element ? -Original Message- From: Leo Koivuniemi [mailto:universalserial...@gmail.com] Sent: 02 March 2012 08:46 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] [WIX-users] Patch in Wix 3.6 is empty. warning PYRO1079: The cabinet '***.cab' does not contain any files Hi all, Hope you can help me with this one. I have been google-ing but found no solution. What I have done is upgraded from Wix v3 to Wix v3.6 (because of VS2010 support). I have managed to get everything working just fine except for when building a patch. I get this warning from pyro.exe pyro.exe -nologo ..\Patch\obj\Deploy\Patch_7.17.8.3550.WixMsp -out ..\output\Deploy\Patch_7.17.8.3550.msp -t RTM ..\Patch\obj\Deploy\Diff.wixmst C:\Project\***\Setup\Patch\patch.wxs(10): warning PYRO1079: The cabinet 'RTM.cab' does not contain any files. If this installation contains no files, this warning can likely be safely ignored. Otherwise, please add files to the cabinet or remove it. So, the patch is empty even though I have modified a file which thereby should be included in the patch (and which worked before upgrading wix). Now the CAB-file is always empty in the patch for some reason. The best I could google was this link: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Applying-a-patc h-msp-doesn-t-increase-the-product-version-td7173238.html He has almost the exact same problem and he says in hist first post that he got it working when going to v3.5, Is this bug confirmed in 3.6 or is there something other that is wrong? In Diff.wixmst I can see that the file I have altered is mentioned in there but I have no idea if that means it is considered modified or not. I can see some tags there that have a "modified="yes" " attribute, but the filed tags associated with the altered file do not seem to have that attribute. Like the guy in the link above I have tried changing the size and version of the file but to no avail in my case. In my patch.wxs it looks like this: http://schemas.microsoft.com/wix/2006/wi";> I read somewhere that the most common reason for this error is that the PatchBaseline is not matched up correctly with the first argument to pyro after the "-t" flag. But it seems in my case they are both called "RTM"... So, patch gets built without errors but does not include the files for the patch after upgrade to WIX v3.6. Anyone, any ideas? - - Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ 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. -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wow!
2012/3/5 Bruce Cran : > On 05/03/2012 07:04, Dirk Räder wrote: >> >> will there be any kind of offline installer available? I mean a real >> installer that does all the necessary registry and environment >> operations, not the /layout switch that just drops the file structure. > > > /layout just gets any .cab or .msi files that the installer needs. When you > run the bootstrapper without /layout it still does all the registry > operations etc. but will use the local files instead of downloading them > again. > > -- > Bruce Cran Hi Bruce, thanks, this tackles my concerns. /Dirk -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
