VS 2005 (v8) Beta 2 help Authoring Info
Hi all
I have been updating my FAQ: http://helpware.net/mshelp2/h2faq.htm
This may help those playing with H2 collection under VS 2005 (v8) Beta 2
Cheers
Rob Chander
MS Help MVP
http://helpware.net/FAR/
http://mshelpwiki.com/
---
* Q. Where is VSHIK Help SDK? [2005-06-25, VS 2005 Beta 2]
Help 2.0 SDK is no longer a separate download. It is now part of the VS SDK
(formerly VSIP SDK).
A free download from: http://msdn.microsoft.com/vstudio/extend/
---
* Compile Warning HXC6048 with VS v8 Beta 2 [2005-07-02, VS 2005 Beta 2]
Don't worry we all seem to get this warning compiling help under VS v8 Beta
2. Things that compiled fine under VS 2003 now display the warning...
Warning: HXC6048: File D:\..\h2reg.HxK, Line 0, Char 0: No Term defined in
tag <Keyword ...>. Ignored.
(Paul O'Rear [MS] to confirm if this is fixed in the RTM bits).
---
* Plug into MS.VSIPCC.v80 not MS.VSCC.v80 [2005-06-25, VS 2005 Beta 2]
MS now recommend you plug into MS.VSIPCC.v80 and not MS.VSCC.v80
(MS.VSIPCC.v80 is plugged into MS.VSCC.v80). It is designed to keep 3rd
party help grouped together and out of way of the MS collections.
---
* Q. Can I control Plug-in Order? [2004-11-26, VSHIK 2.5, VS 2005]
Only MS Help 2.5.x and greater supports plug-in order. MS Help 2.5.x is
installed with VS 2005, as well as later versions of MSDN etc. Plug-in order
is achieved by adding IDs to your Master TOC and to the TOCs of collections
that plug into that. Thus you can control the order when plugging into your
own collections but not when plugging into say MS.VSCC (since you do not
control the source and it's TOC IDs).
See the TOC Update White Paper: VSHIK Download Page
---
* Q. Why wont DExplore detect/auto-merge my registration? [2005-06-25, VS
2005 Beta 2]
For VS v8 Beta 2 MS decided to disable the DExplore detect/auto-merge
feature. Thus under Beta2 you will register and plug-in your collection but
it will never merge or show unless you performed a merge at registration
time (which is what they wanted to encourage). This decision has now been
reversed and the RTM (release to manufacturing) version has gone back to the
old way (thankyou!).
In beta 2 then how do you force a merge so I can see my plug-ins?
The easiest way is to view ms.vscc.v8 in the FAR H2 viewer or our free
H2Viewer. Third-party viewers still detect and auto-merge. Only MS DExplore
beta 2 inhibits the detect/auto-merge feature.
---
* Q. Fatal Error HXC2064: Unable to initialize the full-text index engine
[2005-02-22]
Earl Seugling contacted me after his compiles all started failing on the
build machine with error HXC2064. I contacted the MS help team who very
kindly checked the code and suggested two possible situations that could
cause this compiler error.
The system has become corrupted and requires a reinstall or repair. In all
probability, one or more of the IT DLLs is no longer registered (ITCC.dll,
MSITSS.dll or ITIRCL.dll). Either re-register the DLLs, or re-install the
VSIP or VSHIK to fix this.
The user has run out of temporary file system space (the partition is the
one that the environment variable %TEMP% points to). Free up some TEMP space
and re-try.
We discovered that every time you compile a HxS file there is a file
TMP*.tmp created (approx 100K with a ITOLITLS signiture) in the %TEMP%
folder. In Earl's case their build machine had produced 7.6GB of .tmp files
completely filling the drive. Removing the .tmp files fixed the problem.
--- END ---
date: Sat, 2 Jul 2005 12:54:44 +1000
author: Rob Chandler [MVP]
