> Steve > > Not sure if you're still working on this, but I've recently been struggling > with the same issues in WiX v3, and have finally got the help integration > working. >
If you're replying me, my name isn't Steve, but thanks for your detailed explanation! Actually, I also got it working but I took a slightly different approach. I "reverse engineered" the necessary tables (HelpFile, HelpFileToNamespace, HelpNamespace and HelpPlugin) as <CustomTable>:s and got it working that way, that is no errors during compilation and help integrated successfully, I still have the same warnings as you have though. regards, Simon > > > On the LGHT0204 errors (sequencing errors), I had to do the following > > > > <InstallExecuteSequence> > > <InstallFinalize Sequence="7800" /> > > </InstallExecuteSequence> > > > > As per > https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1588180&group_id=105970 > > > > Also referenced there is the Foreign Key issue. WiX v3 currently has an > 'explicit' foreign key between HelpPlugIn and HelpNamespace, whereas the > Merge Modules only assume a 'logical' foreign key. Check the differences > between the resulting MSI and the Merge Modules in the _Validation table > entries for the HelpPlugIn table (Orca is probably the easiest tool to use). > > > > Interestingly, these ICE checks seem to be done on the MSI after it has been > created on disk, i.e. the FK errors don't actually stop the MSI creation. > If you open the MSI with Orca and run the validation you'll see the same > issues appear. If you use Orca to modify the entries in the _Validation > table, to match those of the Merge Modules, the errors will no longer > appear. > > > > The ICE82 warnings referring to ProgramFilesFolder.364… will still appear, > but can apparently be ignored. As can the ICE03 warnings relating to string > overflows. > > > > I'm only new to both building MSIs and using Help2, so I'm far from an > authority on either, just wanted to pass on the little that I had learned > along the way. > > > > Some other notes: > > > > I have a WiX node that looks like <Wix > xmlns="http://schemas.microsoft.com/wix/2006/wi"; > xmlns:vs="http://schemas.microsoft.com/wix/VSExtension";> > > > > And the HelpFile node > > <vs:HelpFile Id="someHxSFile" Name="nameAsPerHxtUrl" /> > > > > As indicated, the Name attribute must match the Url attribute in the > HelpTOCNode of the HxT file, if not the Table of Contents does not deploy > properly (the help will correctly appear in the dexplore Index tab though). > I got this wrong initially, novice mistake I'm assuming, and it took me a > LONG time to find what was wrong. The MSDN help for HxReg.exe eventually > tipped me off to what I'd done wrong. > > > > Then the HelpCollection node looks like > > <vs:HelpCollection Id="someHxC" Description="some > description" Name="company.title.1033"> > > <vs:HelpFileRef Id="someHxSFile" /> > > <vs:PlugCollectionInto > > Attributes="someHxA" > > TableOfContents="someHxT" > > TargetCollection="MS_VSIPCC_v80" > > > TargetTableOfContents="FL_vsipcc_hxt_86880________.3643236F_FC70_11D3_A536_0090278A1BB8"/> > > </vs:HelpCollection> > > > > HelpCollection Name is using format as per recommendation in > http://msdn2.microsoft.com/en-us/library/bb164959(VS.80).aspx > > The Attributes attribute is optional, you may not need it depending on how > you've authored the help content. > > > > I'm assuming than an MST file, in conjunction with MSITRAN.EXE, could be > used to correct the ICE03 errors as a post build step (to correct the > _Validation table), but I haven't tried yet. > http://www.creativedocs.net/blog/archives/32-Patching-the-MSI-file-for-Vista-compliance.html > gave me the idea for this. > > > > > > Whilst it would obviously be nice to get an Error and Warning free compile > done, it appears there is at least a workaround until the WiX team can get > to the issue. > > > > Hope this helps > > > > Regards > > Shannon Lewis > > Systems Architect > > Runge Limited > Value through Planning > > Ph: (+61 7) 3100 7274 > > Fax: (+61 7) 3100 7297 > > www.runge.com > > > ________________________________ > > > LEGAL NOTICE > > The information contained in this e-mail, and any attachments to it, are for > the use of the intended recipient and are confidential. If you are not the > intended recipient, you must not use, commercialise, disclose, read, > forward, copy or retain any of the information. If you have received this > e-mail in error, please delete it and notify the sender by return e-mail or > telephone on +61 7 3100 7200. Runge Limited (ABN 17 010 672 321) does not > warrant that any attachments are free from viruses or any other defects. You > assume all liability for any loss, damage, or other consequences, which may > arise from opening or using the attachments. > Unless otherwise expressly stated by an authorized representative of Runge > Ltd, any views, opinions and other information expressed in this message and > any attachments are solely those of the sender and do not constitute formal > views or opinions of our firm. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
