>It's a cliché but... I can imagine Rob saying/thinking "Do you know who I >am!?" Of course, Rob would never actually say or think anything like that. ;-)
Well I could say the same about myself and I think most first time visitors to WiX could as well. For the most part we're fairly experienced IT people. Being new to WiX doesn't make us idiots. And those offering help would be well advised to keep that in mind. Also, being new to WiX doesn't mean our critiques are necessarily without merit. If it was such a perfect product would there be this much email in the WiX-users group? >I generally take what Rob says as gospel. He did work with the Windows >Installer team as an intern and has been authoring Windows Installer packages >for a very, very long time. Essentially since the beginning of Windows >>Installer packages. You should consider twice before you tell Rob how Windows >Installer works. And considering that Rob started WiX as a tool to help author >Windows Installer packages I am very comfortable with his >understanding of >how WiX relates to Windows Installer and how to use WiX to author Windows >Installer packages. Your putting words in my mouth. Regarding item 4 I clearly stated that my understanding was based on the explanation given in Nick's book and the contents of msi log files. If anyone wants to refute these facts then please do, these are verifiable facts not my opinions. Please stick to the facts and don't create some bogus argument that misrepresents and distorts my position. FWIW what Rob said exactly is " Also, I don't think #4 is correct.". That is not a strong assertion of fact like "#4 is not correct". Maybe you and Rob can remember every nuance of every software project you've ever worked on, and good for you if you can, but most of us mere mortals can't. So when someone starts a purported correction/refutation with " Also, I don't think" it signals that they are reporting something with less than 100% certainty. To which a response describing my findings is entirely appropriate. Furthermore I qualified my response to make it clear I'm referring to my scenario. I don't like these sorts of emails, but when someone misconstrues my position in a public forum I'm compelled to respond. Hopefully this will be the end of it and we can confine future exchanges to the subject matter. Thank you. -----Original Message----- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Friday, July 29, 2011 11:52 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] RemoveExistingProducts doesn't work in 3.5 > > Maybe it just requires looking at the problem from a different point > > of > view. Trying to be very procedural tends to be very frustrating in a > declarative system. You end up fighting the design constantly. I'm > still not terribly clear >on your requirements but what you've > described thus far seems like it should be pretty easy to do with the > Windows Installer, with the right approach. > > Rob, there are multiple sequences involved. With coordination between > sequences and dependencies between nodes within the same sequence. > One cannot help dealing with this procedurally. Nick's book makes it > pretty clear that these sequences require close attention. > > > Also, I don't think #4 is correct. Costing will be applied to > > Components > which then roll up into Feature costing. As you turn Features on and > off, the costing will be adjusted. > > If features were specified at installer invocation time or in a dialog > early in the UI sequence you would be correct. But they are not. As I > explained they are being determined in a dialog that runs after CostFinalize. > It's a cliché but... I can imagine Rob saying/thinking "Do you know who I am!?" Of course, Rob would never actually say or think anything like that. ;-) I generally take what Rob says as gospel. He did work with the Windows Installer team as an intern and has been authoring Windows Installer packages for a very, very long time. Essentially since the beginning of Windows Installer packages. You should consider twice before you tell Rob how Windows Installer works. And considering that Rob started WiX as a tool to help author Windows Installer packages I am very comfortable with his understanding of how WiX relates to Windows Installer and how to use WiX to author Windows Installer packages. Edwin G. Castro Software Developer - Staff Digital Channels Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail ------------------------------------------------------------------------------ Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
