Ok, I have Paraffin working nicely now. I initially used Heat.exe with the -suid option so that my IDs have friendly names, then modified the resulting wxs into Paraffin format.
When I run Paraffin however, the resulting .PARAFFIN file only contains the default namespace declaration, and not the one I added to the intial wxs file for the util extension: <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi"; *xmlns:util="http://schemas.microsoft.com/wix/UtilExtension"*> John, can you add a feature request to retain the original attributes on the root element when creating the Paraffin file? I may have a go myself since I have the source, but my C# is very rusty and haven't used LINQ before! Anybody come across this problem and have a solution already? Cheers, Dan On Wed, Jan 11, 2012 at 11:55 AM, Dan Gough <goug...@gmail.com> wrote: > Just tried again and the XmlFile tags are no longer being removed, must > have made a mistake somewhere! Also confirmed that test values for > registry and service entries are left untouched also. > > Plodding on, wish me luck! > > Cheers, > Dan > > > On Wed, Jan 11, 2012 at 11:33 AM, Dan Gough <goug...@gmail.com> wrote: > >> Ok, I've got an initial fragment created and sussed out how to perform an >> update. However, some of my components have <XmlFile> entries, and these >> get dropped when updating. I tried putting these entries into >> .paraffinmold files, but then if I want it associated with the original >> component, I end up getting duplicate component entries which then produces >> errors at compile time. >> >> I will eventually be adding registry and service information to some of >> these components and am thinking Paraffin might strip these out also when >> updating, can anybody confirm? >> >> I would appreciate any advice at this point on the best way forward. >> >> Thanks, >> Dan >> >> >> On Wed, Jan 11, 2012 at 2:25 AM, John Robbins <j...@wintellect.com>wrote: >> >>> Thanks all for the kind words about Paraffin! *blush* >>> >>> If you're just getting started with Paraffin make sure to read the Zen >>> of Paraffin to help you get started. ( >>> http://www.wintellect.com/CS/blogs/jrobbins/archive/2010/08/31/zen-of-paraffin.aspx >>> ) >>> >>> As always, if anyone has any bugs or feature requests, please let me >>> know and I'll get on them. >>> >>> John >>> Wintellect >>> http://www.wintellect.com >>> +1-877-968-5528 >>> >>> On Jan 10, 2012, at 10:00 AM, Bourne, Kevin wrote: >>> >>> > Using it here too, with great success. Easy to use with our TFS build >>> server. Also love the fact that we have the source code. >>> > >>> > >>> > >>> > Kevin Bourne | Software Developer Lead | Chase Paymentech >>> > ... >>> > kevin.bou...@chasepaymentech.com >>> > >>> > JPMorgan Chase & Co. >>> > >>> > >>> > -----Original Message----- >>> > From: Justin Hull [mailto:justin.h...@assetpoint.com] >>> > Sent: Tuesday, January 10, 2012 12:31 PM >>> > To: General discussion for Windows Installer XML toolset. >>> > Subject: Re: [WiX-users] Anybody using Paraffin? >>> > >>> > In short I have used it to good success. It took a little bit to work >>> through the options, but in the end I got a nice fragment file I could >>> include in a dynamic build. After the fact I learned that MISInstaller >>> prefers each file have its own component, I used paraffin to group by >>> directory. When we stich over to a major release I will adjust my scripts >>> to conform to default behavior. >>> > I also like that you can dig into the source code. It is worth a look. >>> > >>> > Justin Hull >>> > Sr. Developer >>> > >>> > >>> > Maximizing Asset Performance >>> > (864) 679-3513 Office >>> > >>> > -----Original Message----- >>> > From: Dan Gough [mailto:goug...@gmail.com] >>> > Sent: Tuesday, January 10, 2012 12:16 PM >>> > To: General discussion for Windows Installer XML toolset. >>> > Subject: [WiX-users] Anybody using Paraffin? >>> > >>> > Hi, >>> > >>> > I want to have my automated WiX build automatically pick up the >>> occasional >>> > new file (and drop the odd deleted one) without regenerating any >>> component >>> > GUIDs. I've found this tool named Paraffin that's designed to solve >>> the >>> > problem, but it hasn't been updated in a while: >>> > >>> > >>> http://www.wintellect.com/CS/blogs/jrobbins/archive/tags/Paraffin/default.aspx >>> > >>> > I'd like to know if any users out there have had experience using this >>> with >>> > WiX v3.6 Beta? >>> > >>> > Thanks in advance, >>> > Dan >>> > >>> ------------------------------------------------------------------------------ >>> > Write once. Port to many. >>> > Get the SDK and tools to simplify cross-platform app development. >>> Create >>> > new or port existing apps to sell to consumers worldwide. Explore the >>> > Intel AppUpSM program developer opportunity. >>> appdeveloper.intel.com/join >>> > http://p.sf.net/sfu/intel-appdev >>> > _______________________________________________ >>> > WiX-users mailing list >>> > WiX-users@lists.sourceforge.net >>> > https://lists.sourceforge.net/lists/listinfo/wix-users >>> > >>> > >>> ------------------------------------------------------------------------------ >>> > Write once. Port to many. >>> > Get the SDK and tools to simplify cross-platform app development. >>> Create >>> > new or port existing apps to sell to consumers worldwide. Explore the >>> > Intel AppUpSM program developer opportunity. >>> appdeveloper.intel.com/join >>> > http://p.sf.net/sfu/intel-appdev >>> > _______________________________________________ >>> > WiX-users mailing list >>> > WiX-users@lists.sourceforge.net >>> > https://lists.sourceforge.net/lists/listinfo/wix-users >>> > ---------- >>> > Learn more about Chase Paymentech Solutions,LLC payment processing >>> services at www.chasepaymentech.com. >>> > >>> > THIS MESSAGE IS CONFIDENTIAL. This e-mail message and any attachments >>> are proprietary and confidential information intended only for the use of >>> the recipient(s) named above. If you are not the intended recipient, you >>> may not print, distribute, or copy this message or any attachments. If you >>> have received this communication in error, please notify the sender by >>> return e-mail and delete this message and any attachments from your >>> computer. >>> > >>> > >>> > >>> > >>> > >>> > >>> ------------------------------------------------------------------------------ >>> > Write once. Port to many. >>> > Get the SDK and tools to simplify cross-platform app development. >>> Create >>> > new or port existing apps to sell to consumers worldwide. Explore the >>> > Intel AppUpSM program developer opportunity. >>> appdeveloper.intel.com/join >>> > http://p.sf.net/sfu/intel-appdev >>> > _______________________________________________ >>> > WiX-users mailing list >>> > WiX-users@lists.sourceforge.net >>> > https://lists.sourceforge.net/lists/listinfo/wix-users >>> > >>> >>> >>> ------------------------------------------------------------------------------ >>> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex >>> infrastructure or vast IT resources to deliver seamless, secure access to >>> virtual desktops. With this all-in-one solution, easily deploy virtual >>> desktops for less than the cost of PCs and save 60% on VDI infrastructure >>> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox >>> _______________________________________________ >>> WiX-users mailing list >>> WiX-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/wix-users >>> >> >> > ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
