Hi all

Unicode versions of H2Reg.exe & H2Reg.DLL are now available for download. Please
download the H2Reg v2.0 Beta from
http://helpware.net/mshelp2/h2reg.htm

Tests so far have been perfect, with Japanese help and collection
files registering correctly on an English PC. That is directory and file names
containing JP characters have registered correctly.

We've also provided French, German and Japanese translations.

Cheers
Rob
http://helpware.net/

Hi folks

Just about to release a Unicode version of H2Reg.exe (better late than never :-)

I have 20 language Strings in H2Reg.INI to translate

At the moment I have EN, DE, FR, JP

I'm look for help with the following....

[es] ; Spanish
[it] ; Italian
[ko] ; Korean
[cn] ; Chinese (Simplified)
[tw] ; Chinese (Traditional)
[sv] ; Swedish
[nl] ; Dutch
[ru] ; Russian
[ar] ; Arabic
[he] ; Hebrew
[da] ; Danish
[no] ; Norwegian
[fi] ; Finnish
[pt] ; Portuguese
[br] ; Brazilian
[cs] ; Czech
[pl] ; Polish
[hu] ; Hungarian
[el] ; Greek
[tr] ; Turkish
[sl] ; Slovenian
[sk] ; Slovakian
[eu] ; Basque
[ca] ; Catalan

Please email me if you can assist
Thanks
Rob

Rob Chandler
The Helpware Group
http://helpware.net/contact.htm

Hi Celine

Sounds simple enough. You must have installed H2Reg on
your system so please look at that as an example

h2Reg.exe is in
    C:\Program Files\Helpware\H2Reg\
while I install H2Reg_cmd.ini with my source files here
    C:\Program Files\Helpware\H2Reg\h2help\

So I run in INNO installer I run
    "{app}\H2Reg.exe" with param "-r cmdfile={app}\h2help\H2Reg_Cmd.ini"

Alternatively all paths in your cmd file are relative to the cmd file location.

in my cmd file I have

[Reg_Namespace]
;<nsName>|<nsColfile>|<nsDesc>
hw.h2reg|COL_Master.HxC|H2Reg.exe Documentation

If I kept my cmd INI in the same folder as H2Reg.exe then I would
have to adjust
all paths in the cmd file

eg.

[Reg_Namespace]
;<nsName>|<nsColfile>|<nsDesc>
h2help\ hw.h2reg|COL_Master.HxC|H2Reg.exe Documentation

Does that help?

The <UserDir1> type placeholders is just a way you can pass in a path
for the cmd file to use.

H2Reg.exe -r "UserDir1=d:\path1"

[Reg_Namespace]
;<nsName>|<nsColfile>|<nsDesc>
<UserDir1>\ hw.h2reg|COL_Master.HxC|H2Reg.exe Documentation

You can also do things like

[Reg_Namespace]
;<nsName>|<nsColfile>|<nsDesc>
<programfilesdir>\helpware\ hw.h2reg|COL_Master.HxC|H2Reg.exe Documentation

Rob


At 03:43 AM 8/05/2009, you wrote:


>Hello
>
>I'm trying to register files located in folders other than where the
>executable and ini are located. The problem is that the collection
>files and the HxS files are located in different directories. I read
>the documentation on the UsSerDir user-defined directory script
>shortcuts do not fully understand how to use them and whether they
>apply in what I need to do. I'm ok with placing the H2Reg files
>elsewhere that these could perform the registration. I thought that
>it might be easier to reach paths defined from a higher level rather
>than moving up in the structure. The structure of what I need to
>register is as follows:
>
>H2RegFolder
>HxSFilesFolder
>Folder
>CollectionFilesFolder
>
>Regards
>
>Celine
>
>


[Non-text portions of this message have been removed]

Hello

I'm trying to register files located in folders other than where the executable
and ini are located. The problem is that the collection files and the HxS files
are located in different directories. I read the documentation on the UsSerDir
user-defined directory script shortcuts do not fully understand how to use them
and whether they apply in what I need to do. I'm ok with placing the H2Reg files
elsewhere that these could perform the registration. I thought that it might be
easier to reach paths defined from a higher level rather than moving up in the
structure. The structure of what I need to register is as follows:

H2RegFolder
        HxSFilesFolder
        Folder
             CollectionFilesFolder

Regards

Celine

Hi Travis

Rings vague bells.

So what happens if you force a merge after registration?

Please take me though the sequence step by step

Cheers
Rob


At 11:20 AM 17/01/2009, t.maccallum wrote:

>I'm trying to setup a system where there is a parent that multiple
>help plugins are registered to, but where they all aren't necessarily
>registered at the same time. It seems that if a set of plugins aren't
>registered at the same time, they won't show up in visual studio. That
>is that if I register HelpA and HelpB together under HelpCollection
>they'll both show up, but if then I update HelpA and then just
>register HelpA under HelpCollection only HelpA will appear even though
>I previously registered HelpB under HelpCollection.
>
>If I look at the namespaces in FAR, they are all there and registered
>properly. Why the difference between what I see in FAR and in Visual
>Studio? I'm curious if I'm missing some option to enable it so that
>you can sort of build on a collection of plugins all attached to one
>namespace.
>
>Tavis
>
>


[Non-text portions of this message have been removed]

Hi folks

You may have heard that Help 3.x will completely replace the Help 2.x help
engine. R.I.P DExplore.

At WritersUA conference this week Anand (MS Sandcastle Group) announced that VS
2010 Beta 1 will ship with only the online help experience (in the browser).

So we wont be able to test Help 3 integration for some time. We'll need to wait
for a future release.

Registration utilities such as H2Reg.exe wont be required by Help 3.

If you are curious about Help 3 and what sort of work it will take to migrate
your source I've made some notes here....

** Please don't link to this page publicly yet!! I want to keep the exposure low
until Microsoft work out what they are doing.

http://www.helpware.net/mshelp3/h3intro.htm

Questions.

Rob
Web:  http://helpware.net/
blog: http://weblog.helpware.net/
Twitter: helpware

I'm trying to setup a system where there is a parent that multiple
help plugins are registered to, but where they all aren't necessarily
registered at the same time. It seems that if a set of plugins aren't
registered at the same time, they won't show up in visual studio. That
is that if I register HelpA and HelpB together under HelpCollection
they'll both show up, but if then I update HelpA and then just
register HelpA under HelpCollection only HelpA will appear even though
I previously registered HelpB under HelpCollection.

If I look at the namespaces in FAR, they are all there and registered
properly. Why the difference between what I see in FAR and in Visual
Studio? I'm curious if I'm missing some option to enable it so that
you can sort of build on a collection of plugins all attached to one
namespace.


Tavis

Hi Carlo

With H2 if you get one thing wrong it wont work correctly.

This tutorial is a good place to start
http://helpware.net/mshelp2/h2tutorial.htm

Looking at your code I see you are using a HxS
file as collection file. I'd try using a HxC file.

My best advice... Use the Collection Wizard in the
latest FAR Beta to create your collection H2Reg
script. This will eliminate most problems.

http://helpware.net/mshelp2/CollectionWizard/ColWizard.htm

Also remember that getting the H2 attributes embedded in
your HTML files wrong can create problems such as TOC not showing.

http://helpware.net/mshelp2/attribs.htm

Email back if you have more questions.

Rob



--- In H2Reg@yahoogroups.com, "ckok_1" <ck@...> wrote:
>
>
> With the log file below I'm trying to register ahelp collection and
> plug one into another (vs 2008).the remobjects.oxygene namespace
> register fine but doesn't plug into it (though it registers fine,
> error only says registration failed). However the keyword list for
> remobjects.oxygene does show opening vs.net help, the TOC however does
> not show. I tried registering the remobjects.oxygene one under another
> namespace but that also fails. the original (before compilation) hxt
> file for remobjects.oxygene looks like:
>
> <?xml version="1.0"?><!DOCTYPE HelpTOC><HelpTOC DTDVersion = "1.0"
> LangId = "1033" ParentNodeIcon = "Book" PluginStyle =
> "Flat"><HelpTOCNode Title = "Delphi Prism" Icon="0" >
> <HelpTOCNode Title = "Main Method - Delphi Prism"
> Url="Main_Method.html" />
> <HelpTOCNode Title = "Language - Delphi Prism" Url="Language.html" />
> </HelpTOCNode>
> </HelpTOC>
>
> the hxc looks like:
>
> <?xml version="1.0"?>
> <!DOCTYPE HelpCollection>
> <HelpCollection
>   DTDVersion="1.0"
>   Id=""
>   FileVersion="1.0.0.0"
>   LangId="1033"
>   Font=""
>   FontSize=""
>   Charset=""
>   Title="Delphi Prism"
>   Copyright="">
>
>   <TOCDef File="Delphi Prism.HxT"/>
>
>   <KeywordIndexDef File="Delphi Prism.HxK"/>
>   <KeywordIndexDef File="Delphi Prism_F.HxK"/>
>   <KeywordIndexDef File="Delphi Prism_N.HxK"/>
>   <KeywordIndexDef File="Delphi Prism_A.HxK"/>
>   <KeywordIndexDef File="Delphi Prism_D.HxK"/>
>
>   <ItemMoniker Name="!DefaultFullTextSearch"
> ProgId="HxDs.HxFullTextSearch" InitData="AnyString"/>
>   <ItemMoniker Name="!DefaultTOC" ProgId="HxDs.HxHierarchy"
> InitData="Delphi Prism"/>
>   <ItemMoniker Name="!DefaultKeywordIndex" ProgId="HxDs.HxIndex"
> InitData="K"/>
>   <ItemMoniker Name="!DefaultAssociativeIndex" ProgId="HxDs.HxIndex"
> InitData="A"/>
>   <ItemMoniker Name="!DefaultContextWindowIndex" ProgId="HxDs.HxIndex"
> InitData="F"/>
>   <ItemMoniker Name="!DefaultDynamicLinkIndex" ProgId="HxDs.HxIndex"
> InitData="D"/>
>   <ItemMoniker Name="!DefaultNamedUrlIndex" ProgId="HxDs.HxIndex"
> InitData="NamedUrlIndex"/>
>
>   <ToolData Name="MSVHWNamespace" Value="delphi_Prism"/>
>   <ToolData Name="MSVHWUniqueID" Value="delphi_Prism"/>
>   <ToolData Name="FAR.CommandLine" Value="C:\Program Files
> (x86)\Helpware\FAR\FAR.exe"/>
>   <ToolData Name="FAR.CommandLineArgs" Value="ms-help://$NAMESPACE"/>
>   <ToolData Name="FAR.IncBuildNumber" Value="0"/>
>   <ToolData Name="MSVHWLogFile" Value="delphi Prism.log"/>
>   <ToolData Name="MSVHWLogLevel" Value="3"/>
> </HelpCollection>
>
> Currently I'm only deploying the compiled .hxs file. What can I check
> to figure out where this error comes from and what i can do to fix it ?
>
>
===============================================================================
> Log File:              D:\1\WIKOF\out\H2Reg_Log.txt
> Date:                  15-12-2008 10:10:51
> Operating System:       Windows NT 6.0 (Build 6001) Service Pack 1
> SysLocale.DefaultLCID:  0x0413 (1043)
> SysLocale.PriLangID:    0x0013 (19)
> SysLocale.SubLangID:    0x0001 (1)
> DecimalSeparator:       ,
>
-------------------------------------------------------------------------------
> EXE Path =           D:\1\WIKOF\out\H2Reg.exe
> EXE Version =        1.6.0.0
> Cmdline Param(s) =   -r
> Actual CmdLine =   h2reg  -r
> _RunDir =            D:\1\WIKOF\out
> _ModuleName =        H2Reg.exe
> _ModuleDir =         D:\1\WIKOF\out
> _ModulePath =         D:\1\WIKOF\out\H2Reg.exe
> Module Version =        1.6.0.0
>
-------------------------------------------------------------------------------
> _hhInstalled =       YES
> _hhVerStr =          6.0.6001.18000
> _hhFriendlyVerStr =  > 1.4a
>
-------------------------------------------------------------------------------
> _ieInstalled =       YES
> _ieVerStr =          6.0.6001.18000
> _ieFriendlyVerStr =  Internet Explorer 6 (Windows Server 2003)
>
===============================================================================
> MS Help 2.x Runtime Found: YES
>     2.7.61224.0, C:\Program Files (x86)\Common Files\Microsoft
> Shared\Help\hxds.dll
>     2.7.61224.0, C:\Program Files (x86)\Common Files\microsoft
> shared\Help\hxvz.dll
> NT Admin Log On: YES
> PC Language ID = nl
>
-------------------------------------------------------------------------------
> Quiet Mode (-Q): No
> Registration Mode (-R): Yes
> UnRegistration Mode (-U): No
> Append Log Mode (-A): No
> No NT Admin Check (-N): No
> Merge Indexes Mode (-M): No
> Cmd Script File (CmdFile=): D:\1\WIKOF\out\H2Reg.ini
> User Dir 1 (UserDir1=):
> User Dir 2 (UserDir2=):
> User Dir 3 (UserDir3=):
> User Dir 4 (UserDir4=):
>
===============================================================================
> CmdFile = D:\1\WIKOF\out\H2Reg.ini
> <windir> = C:\Windows
> <winsysdir> = C:\Windows\system32
> <programfilesdir> = C:\Program Files (x86)
> <exedir> = D:\1\WIKOF\out
> <exedirparent> = D:\1\WIKOF
> <cmdfiledir> = D:\1\WIKOF\out
> <cmdfiledirparent> = D:\1\WIKOF
> <userdir1> =
> <userdir1parent> =
> <userdir2> =
> <userdir2parent> =
> <userdir3> =
> <userdir3parent> =
> <userdir4> =
> <userdir4parent> =
>
-------------------------------------------------------------------------------
> [Reg_Namespace]
> remobjects.oxygene|Delphi Prism.HxS|Delphi Prism
>
> [Reg_Title]
> remobjects.oxygene|remobjects.oxygene|1033|Delphi Prism.HxS
>
> [Reg_Plugin]
> MS.VSIPCC.v90|_DEFAULT|remobjects.oxygene|_DEFAULT
>
> [Reg_Filter]
> remobjects.oxygene|Delphi Prism|("Product"="Delphi Prism")
>
> [UnReg_Namespace]
> remobjects.oxygene|Delphi Prism
>
> [UnReg_Title]
> remobjects.oxygene|remobjects.oxygene|1033
>
> [UnReg_Plugin]
> remobjects.oxygene|Delphi Prism|("Product"="Delphi Prism")
>
> [UnReg_Filter]
> remobjects.oxygene|Delphi Prism
>
-------------------------------------------------------------------------------
> 10:10:51   [Reg_Namespace] - Lines To Process = 1
> 10:10:51     <nsName>="remobjects.oxygene"
> 10:10:51     <nsColfile>="D:\1\WIKOF\out\Delphi Prism.HxS"
> 10:10:51     <nsDesc>="Delphi Prism"
> 10:10:51     +Mode = Not Enabled
> 10:10:51     Preparation: Old Namespace "remobjects.oxygene"
> successfully removed. Its important to start with a clean slate.
> 10:10:51    -->Registered OK
>
-------------------------------------------------------------------------------
> 10:10:51   [Reg_Title] - Lines To Process = 1
> 10:10:51     <nsName>="remobjects.oxygene"
> 10:10:51     <TitleID>="remobjects.oxygene"
> 10:10:51     <LangID>="1033"
> 10:10:51     <HxS_HelpFile>="D:\1\WIKOF\out\Delphi Prism.HxS"
> 10:10:51     <HxI_IndexFile>=""
> 10:10:51     <HxQ_QueryFile>=""
> 10:10:51     <HxR_AttrQueryFile>=""
> 10:10:51     <HxsMediaLoc>=""
> 10:10:51     <HxqMediaLoc>=""
> 10:10:51     <HxrMediaLoc>=""
> 10:10:51     <SampleMediaLoc>=""
> 10:10:51    -->Registered OK
>
-------------------------------------------------------------------------------
> 10:10:51   [Reg_Plugin] - Lines To Process = 1
> 10:10:51     <nsName_Parent>="MS.VSIPCC.v90"
> 10:10:51     <HxT_Parent>="_DEFAULT"
> 10:10:51     <nsName_Child>="remobjects.oxygene"
> 10:10:51     <HxT_Child>="_DEFAULT"
> 10:10:51     <HxA_Child>=""
> 10:10:51   Plug Child "remobjects.oxygene" into "MS.VSIPCC.v90"
> 10:10:51   ** Reg Error **: Registration Failed
>
-------------------------------------------------------------------------------
> 10:10:51   [Reg_Filter] - Lines To Process = 1
> 10:10:51     <nsName>="remobjects.oxygene"
> 10:10:51     <FilterName>="Delphi Prism"
> 10:10:51     <FilterQueryStr>="("Product"="Delphi Prism")"
> 10:10:51    -->Registered OK
>
===============================================================================
>
> --END OF FILE--
>

With the log file below I'm trying to register ahelp collection and
plug one into another (vs 2008).the remobjects.oxygene namespace
register fine but doesn't plug into it (though it registers fine,
error only says registration failed). However the keyword list for
remobjects.oxygene does show opening vs.net help, the TOC however does
not show. I tried registering the remobjects.oxygene one under another
namespace but that also fails. the original (before compilation) hxt
file for remobjects.oxygene looks like:

<?xml version="1.0"?><!DOCTYPE HelpTOC><HelpTOC DTDVersion = "1.0"
LangId = "1033" ParentNodeIcon = "Book" PluginStyle =
"Flat"><HelpTOCNode Title = "Delphi Prism" Icon="0" >
<HelpTOCNode Title = "Main Method - Delphi Prism"
Url="Main_Method.html" />
<HelpTOCNode Title = "Language - Delphi Prism" Url="Language.html" />
</HelpTOCNode>
</HelpTOC>

the hxc looks like:

<?xml version="1.0"?>
<!DOCTYPE HelpCollection>
<HelpCollection
   DTDVersion="1.0"
   Id=""
   FileVersion="1.0.0.0"
   LangId="1033"
   Font=""
   FontSize=""
   Charset=""
   Title="Delphi Prism"
   Copyright="">

   <TOCDef File="Delphi Prism.HxT"/>

   <KeywordIndexDef File="Delphi Prism.HxK"/>
   <KeywordIndexDef File="Delphi Prism_F.HxK"/>
   <KeywordIndexDef File="Delphi Prism_N.HxK"/>
   <KeywordIndexDef File="Delphi Prism_A.HxK"/>
   <KeywordIndexDef File="Delphi Prism_D.HxK"/>

   <ItemMoniker Name="!DefaultFullTextSearch"
ProgId="HxDs.HxFullTextSearch" InitData="AnyString"/>
   <ItemMoniker Name="!DefaultTOC" ProgId="HxDs.HxHierarchy"
InitData="Delphi Prism"/>
   <ItemMoniker Name="!DefaultKeywordIndex" ProgId="HxDs.HxIndex"
InitData="K"/>
   <ItemMoniker Name="!DefaultAssociativeIndex" ProgId="HxDs.HxIndex"
InitData="A"/>
   <ItemMoniker Name="!DefaultContextWindowIndex" ProgId="HxDs.HxIndex"
InitData="F"/>
   <ItemMoniker Name="!DefaultDynamicLinkIndex" ProgId="HxDs.HxIndex"
InitData="D"/>
   <ItemMoniker Name="!DefaultNamedUrlIndex" ProgId="HxDs.HxIndex"
InitData="NamedUrlIndex"/>

   <ToolData Name="MSVHWNamespace" Value="delphi_Prism"/>
   <ToolData Name="MSVHWUniqueID" Value="delphi_Prism"/>
   <ToolData Name="FAR.CommandLine" Value="C:\Program Files
(x86)\Helpware\FAR\FAR.exe"/>
   <ToolData Name="FAR.CommandLineArgs" Value="ms-help://$NAMESPACE"/>
   <ToolData Name="FAR.IncBuildNumber" Value="0"/>
   <ToolData Name="MSVHWLogFile" Value="delphi Prism.log"/>
   <ToolData Name="MSVHWLogLevel" Value="3"/>
</HelpCollection>

Currently I'm only deploying the compiled .hxs file. What can I check
to figure out where this error comes from and what i can do to fix it ?

===============================================================================
Log File:              D:\1\WIKOF\out\H2Reg_Log.txt
Date:                  15-12-2008 10:10:51
Operating System:       Windows NT 6.0 (Build 6001) Service Pack 1
SysLocale.DefaultLCID:  0x0413 (1043)
SysLocale.PriLangID:    0x0013 (19)
SysLocale.SubLangID:    0x0001 (1)
DecimalSeparator:       ,
-------------------------------------------------------------------------------
EXE Path =           D:\1\WIKOF\out\H2Reg.exe
EXE Version =        1.6.0.0
Cmdline Param(s) =   -r
Actual CmdLine =   h2reg  -r
_RunDir =            D:\1\WIKOF\out
_ModuleName =        H2Reg.exe
_ModuleDir =         D:\1\WIKOF\out
_ModulePath =         D:\1\WIKOF\out\H2Reg.exe
Module Version =        1.6.0.0
-------------------------------------------------------------------------------
_hhInstalled =       YES
_hhVerStr =          6.0.6001.18000
_hhFriendlyVerStr =  > 1.4a
-------------------------------------------------------------------------------
_ieInstalled =       YES
_ieVerStr =          6.0.6001.18000
_ieFriendlyVerStr =  Internet Explorer 6 (Windows Server 2003)
===============================================================================
MS Help 2.x Runtime Found: YES
     2.7.61224.0, C:\Program Files (x86)\Common Files\Microsoft
Shared\Help\hxds.dll
     2.7.61224.0, C:\Program Files (x86)\Common Files\microsoft
shared\Help\hxvz.dll
NT Admin Log On: YES
PC Language ID = nl
-------------------------------------------------------------------------------
Quiet Mode (-Q): No
Registration Mode (-R): Yes
UnRegistration Mode (-U): No
Append Log Mode (-A): No
No NT Admin Check (-N): No
Merge Indexes Mode (-M): No
Cmd Script File (CmdFile=): D:\1\WIKOF\out\H2Reg.ini
User Dir 1 (UserDir1=):
User Dir 2 (UserDir2=):
User Dir 3 (UserDir3=):
User Dir 4 (UserDir4=):
===============================================================================
CmdFile = D:\1\WIKOF\out\H2Reg.ini
<windir> = C:\Windows
<winsysdir> = C:\Windows\system32
<programfilesdir> = C:\Program Files (x86)
<exedir> = D:\1\WIKOF\out
<exedirparent> = D:\1\WIKOF
<cmdfiledir> = D:\1\WIKOF\out
<cmdfiledirparent> = D:\1\WIKOF
<userdir1> =
<userdir1parent> =
<userdir2> =
<userdir2parent> =
<userdir3> =
<userdir3parent> =
<userdir4> =
<userdir4parent> =
-------------------------------------------------------------------------------
[Reg_Namespace]
remobjects.oxygene|Delphi Prism.HxS|Delphi Prism

[Reg_Title]
remobjects.oxygene|remobjects.oxygene|1033|Delphi Prism.HxS

[Reg_Plugin]
MS.VSIPCC.v90|_DEFAULT|remobjects.oxygene|_DEFAULT

[Reg_Filter]
remobjects.oxygene|Delphi Prism|("Product"="Delphi Prism")

[UnReg_Namespace]
remobjects.oxygene|Delphi Prism

[UnReg_Title]
remobjects.oxygene|remobjects.oxygene|1033

[UnReg_Plugin]
remobjects.oxygene|Delphi Prism|("Product"="Delphi Prism")

[UnReg_Filter]
remobjects.oxygene|Delphi Prism
-------------------------------------------------------------------------------
10:10:51   [Reg_Namespace] - Lines To Process = 1
10:10:51     <nsName>="remobjects.oxygene"
10:10:51     <nsColfile>="D:\1\WIKOF\out\Delphi Prism.HxS"
10:10:51     <nsDesc>="Delphi Prism"
10:10:51     +Mode = Not Enabled
10:10:51     Preparation: Old Namespace "remobjects.oxygene"
successfully removed. Its important to start with a clean slate.
10:10:51    -->Registered OK
-------------------------------------------------------------------------------
10:10:51   [Reg_Title] - Lines To Process = 1
10:10:51     <nsName>="remobjects.oxygene"
10:10:51     <TitleID>="remobjects.oxygene"
10:10:51     <LangID>="1033"
10:10:51     <HxS_HelpFile>="D:\1\WIKOF\out\Delphi Prism.HxS"
10:10:51     <HxI_IndexFile>=""
10:10:51     <HxQ_QueryFile>=""
10:10:51     <HxR_AttrQueryFile>=""
10:10:51     <HxsMediaLoc>=""
10:10:51     <HxqMediaLoc>=""
10:10:51     <HxrMediaLoc>=""
10:10:51     <SampleMediaLoc>=""
10:10:51    -->Registered OK
-------------------------------------------------------------------------------
10:10:51   [Reg_Plugin] - Lines To Process = 1
10:10:51     <nsName_Parent>="MS.VSIPCC.v90"
10:10:51     <HxT_Parent>="_DEFAULT"
10:10:51     <nsName_Child>="remobjects.oxygene"
10:10:51     <HxT_Child>="_DEFAULT"
10:10:51     <HxA_Child>=""
10:10:51   Plug Child "remobjects.oxygene" into "MS.VSIPCC.v90"
10:10:51   ** Reg Error **: Registration Failed
-------------------------------------------------------------------------------
10:10:51   [Reg_Filter] - Lines To Process = 1
10:10:51     <nsName>="remobjects.oxygene"
10:10:51     <FilterName>="Delphi Prism"
10:10:51     <FilterQueryStr>="("Product"="Delphi Prism")"
10:10:51    -->Registered OK
===============================================================================

--END OF FILE--

This was a very helpful response. I figured out how to do it.

Thanks,

Tavis


--- On Mon, 11/10/08, Rob Chandler <robertc@...> wrote:

> From: Rob Chandler <robertc@...>
> Subject: Re: [H2Reg] Generating help files and registering via command  line
> To: H2Reg@yahoogroups.com
> Received: Monday, November 10, 2008, 2:52 PM
> Hi Travis
>
> So you notice in H2 work there are 2 categories of
> HxC/HxK/HxT etc files.
> One has DTD ref at the top and are used by the H2 compiler
> to
> compile your content to a HxS title. So every Help project
> has a set of these
> and produces one HxS.
>
> The other set of Hx files do not have a DTD. These get
> shipped with
> your compiled HxS files and allow H2 runtime to register
> the collection.
>
> So when you run the FAR Wizard to create the collection
> level Hx files
> (no DTD header, that ship with your HxS help files)... I
> would do
> this once only.
> Refresh only if Hx filenames change, or you add new HxS.
>
> -
>
> Now HxConv.exe is a lame little tool which is just meant to
> help you
> port a project from HH to H2. Use this once only. It is not
> meant
> for production work.
>
> If you need to managing help both in HH and H2 formats,
> then
> I suggest do what I do with H2Reg help.
> * HTML files - Easy they work with either compiler
> * HHP / HxC - The 2 project files wont change.  Once
> created leave as
> is or tweak individual projects as required.
> * Toc and Index - FAR allows you to edit in one type and
> "save as" to
> the other.
>      So if you create new TOC or Index items just remember
> at some stage to
>      perform a Save As to the other format. Alternatively
> FAR has a
> batch command
>      that you can use in your build to convert from say HHC
> -> HxT,
> HHK -> HxK or
>      visa-versa.
> ExportNav=file1, file2
> http://helpware.net/FAR/help/hh_goto.htm#farbatch.htm#HTML_Help_Commands
>
>
> Is any of this helping?
>
> Back to you
> Rob
>
> At 06:10 AM 11/11/2008, you wrote:
>
> >I'm trying to setup a system where from a set of
> doxygen generated
> >html files I can generate a help 2.0 file and register
> it to VS2005
> >via H2Reg.
> >
> >I feel like I should be able to do it via running
> >
> >HxConv.exe to generate a .HxC file
> >HxComp.exe to generate a .HxS file and other files
> >
> >and then register with H2Reg. I can go through this
> process and
> >H2Reg's log will show that everything registered
> fine, but it doesn't
> >show up in VS2005.
> >
> >I've read a bit that DTD refrences can mess this
> up, so I tried
> >manually getting rid of the DTD reference from the
> generated .HxC
> >file. If I do this and run the "H2 Collection
> Wizard" in FAR it
> >registers fine. However if I remove the DTD reference
> from the .HxC
> >file and then try to continue on doing this via a
> command line only
> >method, running HxComp won't work.
> >
> >I'm not sure, surely there is a way to do this just
> via the command
> >line? Doing things in the wizard in Far works, but
> I'd like to just
> >run a single command to do all of this.
> >
> >Thanks,
> >
> >Tavis
> >
> >
>
>
> [Non-text portions of this message have been removed]


       __________________________________________________________________
Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your
favourite sites. Download it now at
http://ca.toolbar.yahoo.com.

Hi Travis

So you notice in H2 work there are 2 categories of HxC/HxK/HxT etc files.
One has DTD ref at the top and are used by the H2 compiler to
compile your content to a HxS title. So every Help project has a set of these
and produces one HxS.

The other set of Hx files do not have a DTD. These get shipped with
your compiled HxS files and allow H2 runtime to register the collection.

So when you run the FAR Wizard to create the collection level Hx files
(no DTD header, that ship with your HxS help files)... I would do
this once only.
Refresh only if Hx filenames change, or you add new HxS.

-

Now HxConv.exe is a lame little tool which is just meant to help you
port a project from HH to H2. Use this once only. It is not meant
for production work.

If you need to managing help both in HH and H2 formats, then
I suggest do what I do with H2Reg help.
* HTML files - Easy they work with either compiler
* HHP / HxC - The 2 project files wont change.  Once created leave as
is or tweak individual projects as required.
* Toc and Index - FAR allows you to edit in one type and "save as" to
the other.
      So if you create new TOC or Index items just remember at some stage to
      perform a Save As to the other format. Alternatively FAR has a
batch command
      that you can use in your build to convert from say HHC -> HxT,
HHK -> HxK or
      visa-versa.
ExportNav=file1, file2
http://helpware.net/FAR/help/hh_goto.htm#farbatch.htm#HTML_Help_Commands


Is any of this helping?

Back to you
Rob

At 06:10 AM 11/11/2008, you wrote:

>I'm trying to setup a system where from a set of doxygen generated
>html files I can generate a help 2.0 file and register it to VS2005
>via H2Reg.
>
>I feel like I should be able to do it via running
>
>HxConv.exe to generate a .HxC file
>HxComp.exe to generate a .HxS file and other files
>
>and then register with H2Reg. I can go through this process and
>H2Reg's log will show that everything registered fine, but it doesn't
>show up in VS2005.
>
>I've read a bit that DTD refrences can mess this up, so I tried
>manually getting rid of the DTD reference from the generated .HxC
>file. If I do this and run the "H2 Collection Wizard" in FAR it
>registers fine. However if I remove the DTD reference from the .HxC
>file and then try to continue on doing this via a command line only
>method, running HxComp won't work.
>
>I'm not sure, surely there is a way to do this just via the command
>line? Doing things in the wizard in Far works, but I'd like to just
>run a single command to do all of this.
>
>Thanks,
>
>Tavis
>
>


[Non-text portions of this message have been removed]

I'm trying to setup a system where from a set of doxygen generated
html files I can generate a help 2.0 file and register it to VS2005
via H2Reg.

I feel like I should be able to do it via running

HxConv.exe to generate a .HxC file
HxComp.exe to generate a .HxS file and other files

and then register with H2Reg. I can go through this process and
H2Reg's log will show that everything registered fine, but it doesn't
show up in VS2005.

I've read a bit that DTD refrences can mess this up, so I tried
manually getting rid of the DTD reference from the generated .HxC
file. If I do this and run the "H2 Collection Wizard" in FAR it
registers fine. However if I remove the DTD reference from the .HxC
file and then try to continue on doing this via a command line only
method, running HxComp won't work.

I'm not sure, surely there is a way to do this just via the command
line? Doing things in the wizard in Far works, but I'd like to just
run a single command to do all of this.

Thanks,

Tavis

Hi Miguel

Not a silly Q at all. Normally H2 documentation is only used to merge
your H2 Collections into the VS/MSDN collection. So normally we just
open DEXPLORE (VS help viewer) and you will see your help collection
in with the others.

Now if you registered your collection but forgot to merge it into MSDN
you can still view it standalone. But you have to use a DExplore
command line switch. Run DEXPLORE.exe /help to view the command line
options that allow you to view another collection.

Back to you
Rob



--- In H2Reg@yahoogroups.com, "miguel4063" <miguel4063@...> wrote:
>
> I know this is kind of stupid to ask, but I've just created my first
> DLL documentation and have no idea how do I access the help collection
> once it has been registered??
>
> Please, HELP!
> Thanks
>

I know this is kind of stupid to ask, but I've just created my first
DLL documentation and have no idea how do I access the help collection
once it has been registered??

Please, HELP!
Thanks

Hi all,

I have created two help collections:
1. Using Sandcastle converted documentation comments to a help collection.
2. Using help studio lite converted a word document to a help collection.


Tried to combine these with help integration wizard and failed. So, I have
create the Hxc and Hxt etc file to combine the collection and used H2reg to
register. I have checked all the files to see whether they have any DTD
references, but no DTD reference exists.

When I register help menu is appearing in VS2003, but not in VS2005. When I
install VS SDK, the menu appears in VS2005.

I couldn't find any solution to handle this situation. Any you please
suggest, what has gone wrong?

Thanks

>Description of problem:
>
>I am able to merge my help files into the MSDN "F1" help. The problem
>is after doing so only "VistaDB 3" shows up in the filter and the
>table of contents is wiped out. Is there something missing or wrong
>inside my INI? Please let me know if you need anything else in order
>to evaluate the problem.
>
>Mike

Hi Mike
Send me some screen shots so I can understand.
    robertc at helpware dot net
Are you saying you only see your filter in the filter drop down?

1. Try using the FAR Collection Wizard to make the
      Hx? collection level files. It will eliminate any human error.

2.  Setting correct HTML attributes is essential to making
      filters perform correctly.
      http://helpware.net/mshelp2/attribs.htm

Back to you
Rob


>[Reg_Filter]
>;<nsName>|<FilterName>|<FilterQueryStr>
>VistaDBSoftwareInc.vistadb3help|VistaDB 3|("DocSet"="vistadb3help")

Here is my INI:

;------- Register -r switch

[Reg_Namespace]
;<nsName>|<nsColfile>|<nsDesc>
VistaDBSoftwareInc.vistadb3help|COL_vistadb3-help.HxC|VistaDB 3

[Reg_Title]
;<nsName>|<TitleID>|<LangId>|<HxS_HelpFile>|<HxI_IndexFile>|<HxQ_Query
File>|<HxR_AttrQueryFile>|<HxsMediaLoc>|<HxqMediaLoc>|<HxrMediaLoc>|<S
ampleMediaLoc>
VistaDBSoftwareInc.vistadb3help|vistadb3help|1033|vistadb3-
help.HxS|vistadb3-help.HxS||||||

; --- Register in VS.NET Help Collection
[Reg_Plugin]
;<nsName_Parent>|<HxT_Parent>|<nsName_Child>|<HxT_Child>|<HxA_Child>
MS.VSCC+|_DEFAULT|VistaDBSoftwareInc.vistadb3help|_DEFAULT|COL_vistadb
3-help.HxA
MS.VSIPCC+|_DEFAULT|VistaDBSoftwareInc.vistadb3help|_DEFAULT|COL_vista
db3-help.HxA

[Reg_Filter]
;<nsName>|<FilterName>|<FilterQueryStr>
VistaDBSoftwareInc.vistadb3help|VistaDB 3|("DocSet"="vistadb3help")

;------- UnRegister -u switch

[UnReg_Namespace]
;<nsName>
VistaDBSoftwareInc.vistadb3help

[UnReg_Title]
;<nsName>|<TitleID>|<LangId>
VistaDBSoftwareInc.vistadb3help|vistadb3help|1033

[UnReg_Plugin]
;<nsName_Parent>|<HxT_Parent>|<nsName_Child>|<HxT_Child>|<HxA_Child>
MS.VSCC+|_DEFAULT|VistaDBSoftwareInc.vistadb3help|_DEFAULT|COL_vistadb
3-help.HxA
MS.VSIPCC+|_DEFAULT|VistaDBSoftwareInc.vistadb3help|_DEFAULT|COL_vista
db3-help.HxA


[UnReg_Filter]
;<nsName>|<FilterName>
VistaDBSoftwareInc.vistadb3help|VistaDB 3

;------- Merge -m switch

[Merge_Namespace]
ms.vsipcc+
ms.vscc+
ms.vsexpresscc+



Description of problem:

I am able to merge my help files into the MSDN "F1" help. The problem
is after doing so only "VistaDB 3" shows up in the filter and the
table of contents is wiped out. Is there something missing or wrong
inside my INI? Please let me know if you need anything else in order
to evaluate the problem.

Mike

> Can you post me a few screen shots so I can see this.
Rob,

I'll have to do that in PM as I don't seem to be able to upload
files/images in here.

--
Stuart

Hi Stuart
Can you post me a few screen shots so I can see this.
Thanks
Rob
robertc AT helpware.net

At 08:35 PM 13/12/2007, sejhemming wrote:

> > I think if you read the H2Reg doc it wants you to use a -M
> > switch to actually make the pre-merge work during registration
> >
> > So h2Reg -r -m
>Sorry, I see what you mean. I'm doing that...
>
>H2Reg.exe -R -M "cmdfile=H2Reg_cmd.ini"
>
> > Also try merging the VSCC as well as the VSIPCC
> >
> > [Merge_Namespace]
> > ms.vsipcc+
> > ms.vscc+
>Well, that had /am/ impact but not the one expected.
>
>My collection didn't end up in the standalone library, but did end up
>TWICE in the VS "F1" library!
>
>I'm beginning to think that there may be Black Magic involved in
>getting my collection in to this other version of the library, so I'm
>off to find a chicken I can sacrifice.
>
>--
>Stuart
>
>


[Non-text portions of this message have been removed]

> I think if you read the H2Reg doc it wants you to use a -M
> switch to actually make the pre-merge work during registration
>
> So h2Reg -r -m
Sorry, I see what you mean. I'm doing that...

H2Reg.exe -R -M "cmdfile=H2Reg_cmd.ini"


> Also try merging the VSCC as well as the VSIPCC
>
> [Merge_Namespace]
> ms.vsipcc+
> ms.vscc+
Well, that had /am/ impact but not the one expected.

My collection didn't end up in the standalone library, but did end up
TWICE in the VS "F1" library!

I'm beginning to think that there may be Black Magic involved in
getting my collection in to this other version of the library, so I'm
off to find a chicken I can sacrifice.

--
Stuart

At 11:23 PM 12/12/2007, sejhemming wrote:

> > First make sure you download the latest FAR Beta and try again.
> > There have been some tweaks in that area.
>I've some small success to report with this; my collection ended up in
>the VS Help! That's a lot further than I've managed to get so far.
>
>However, I'm still not seeing it added to my standalone MSDN library
>and wondered if this was a namespace problem?
>
>I'm adding my collection to the "ms.vsipcc+" namespace but wondered if
>there was another I should be using too?
>
> > Can you try again and send me the H2Reg LOG file so can
> > see better what is happening.
>Sure, I'm attaching it to you in PM.
>
> > Early versions of VS 2005 wouldn't autodetect the change - You had
> > to use that switch that forced the merge at registration time.
>What switch?

I think if you read the H2Reg doc it wants you to use a -M
switch to actually make the pre-merge work during registration

So h2Reg -r -m

Also try merging the VSCC as well as the VSIPCC

[Merge_Namespace]
ms.vsipcc+
ms.vscc+

Thanks for sending the log file :-)

Cheers
Rob


> > However I'd be sure you have an RTM version of VS.
>Indeed, and one patched with SP1, if it makes a difference.
>
>--
>Stuart
>
>


[Non-text portions of this message have been removed]

> First make sure you download the latest FAR Beta and try again.
>   There have been some tweaks in that area.
I've some small success to report with this; my collection ended up in
the VS Help! That's a lot further than I've managed to get so far.

However, I'm still not seeing it added to my standalone MSDN library
and wondered if this was a namespace problem?

I'm adding my collection to the "ms.vsipcc+" namespace but wondered if
there was another I should be using too?

> Can you try again and send me the H2Reg LOG file so can
> see better what is happening.
Sure, I'm attaching it to you in PM.

> Early versions of VS 2005 wouldn't autodetect the change - You had
> to use that switch that forced the merge at registration time.
What switch?

> However I'd be sure you have an RTM version of VS.
Indeed, and one patched with SP1, if it makes a difference.

--
Stuart

Hi Stuart

a few things come to mind.

First make sure you download the latest FAR Beta and try again.
   There have been some tweaks in that area.

Can you try again and send me the H2Reg LOG file so can
see better what is happening.

Early versions of VS 2005 wouldn't autodetect the change - You had
to use that switch that forced the merge at registration time.
However I'd be sure you have an RTM version of VS.
And of course try this on other machines too incase you have a quirky setup.

Cheers
Rob

At 08:57 PM 12/12/2007, you wrote:


>I keep reading that it is/should be possible to take the results of
>running DocProject and get them in to MSDN (I'm running VS2K5, if it
>makes any difference) using the FAR tools.
>
>The problem is that I can only find examples of using the FAR tools
>starting with the output from something other than DocProject. I
>thought that the process should be the same, but nothing I've tried works
>
>Just so you know what's occurring...
>
>I'm generating my .HxS file then firing up FAR.
>
>I go to the "H2 collection Wizard" and create a new .HxC file, point
>it at my .HxS file, allow it to create all of the other files it needs
>and let it generate the .ini file. If I register the collection using
>the FAR tool it works and the H2 File viewer can see the namespace.
>
>If I try and merge the collection with the ms.vsipcc+ namespace (which
>I'm given to understand I should as I'm using VS2K5) using the command
>H2Reg.exe -R -M "cmdfile=H2Reg_cmd.ini", it tells me that it's
>merging. At the end of the process I open the MSDN library and don't
>get a warning that new items are being added to the collection and the
>help for my namespace isn't there.
>
>Now, is this a problem with something I'm doing or is there a
>fundamental difference with the output that DocProject produces that
>prevents this process from working?
>
>If you have experience of doing this and would like to share, by
>private mail if TPTB here object to a slightly off-topic thread then
>please (PLEASE!!!) either let me know here or mail me at
>sejhemming-at-gmail-doc-com.
>
>--
>Stuart
>
>


[Non-text portions of this message have been removed]

I keep reading that it is/should be possible to take the results of
running DocProject and get them in to MSDN (I'm running VS2K5, if it
makes any difference) using the FAR tools.

The problem is that I can only find examples of using the FAR tools
starting with the output from something other than DocProject. I
thought that the process should be the same, but nothing I've tried works

Just so you know what's occurring...

I'm generating my .HxS file then firing up FAR.

I go to the "H2 collection Wizard" and create a new .HxC file, point
it at my .HxS file, allow it to create all of the other files it needs
and let it generate the .ini file. If I register the collection using
the FAR tool it works and the H2 File viewer can see the namespace.

If I try and merge the collection with the ms.vsipcc+ namespace (which
I'm given to understand I should as I'm using VS2K5) using the command
H2Reg.exe -R -M "cmdfile=H2Reg_cmd.ini", it tells me that it's
merging. At the end of the process I open the MSDN library and don't
get a warning that new items are being added to the collection and the
help for my namespace isn't there.

Now, is this a problem with something I'm doing or is there a
fundamental difference with the output that DocProject produces that
prevents this process from working?

If you have experience of doing this and would like to share, by
private mail if TPTB here object to a slightly off-topic thread then
please (PLEASE!!!) either let me know here or mail me at
sejhemming-at-gmail-doc-com.

--
Stuart

Hi Don

Lets assume the HxS is OK for now (although there may be some
problem).
Try running FAR to generate the registration support files (usually
pretty fool proof).

http://helpware.net/mshelp2/CollectionWizard/ColWizard.htm
Download the FAR Beta for the most robust version.


Rob

--- In H2Reg@yahoogroups.com, "Don Eddleman" <don.eddleman@...> wrote:
>
> I am getting a registration error when pluging into VSIPCC. I have
in
> my ini file MS.VSIPCC+ and it just shows ** Reg Error **:
Registration
> Faild. Everything else works fine and I can see the collection
using
> FAR. Is there any way to get additional information as to what is
> failing? The Hxs is being created using Sandcastle Builder and the
> June Sandcastle release.
>
> thanks,
> Don
>

I am getting a registration error when pluging into VSIPCC. I have in
my ini file MS.VSIPCC+ and it just shows ** Reg Error **: Registration
Faild. Everything else works fine and I can see the collection using
FAR. Is there any way to get additional information as to what is
failing? The Hxs is being created using Sandcastle Builder and the
June Sandcastle release.

thanks,
Don

Hi Mark
Sure H2Reg allows you to register :- Namespaces, Titles, Plug-ins, and Filters.
See the h2reg online help for examples. Ping me if you get stuck.
Note that Search filters changed with VS 2005
    www.helpware.net/mshelp2/h2reg.htm#vs8search
Of course Filtering only works if you put the correct attributes in your topics
    www.helpware.net/mshelp2/attribs.htm
Cheers
Rob


At 11:10 PM 20/07/2007, mark_collard wrote:

>Hello
>
>Is it possible to make H2Reg add a value in the Filtered By drop down
>box in Visual Studio when it's registering a HxS file.
>
>Thanks for your help.

Hello

Is it possible to make H2Reg add a value in the Filtered By drop down
box in Visual Studio when it's registering a HxS file.

Thanks for your help.

> Great thanks Paulo! Apprecite the report.
> We'll try and get that fixed in the next few weeks.
> Rob

Thanks for the rapid response, Rob.
I'm looking forward to seeing the next release.

Thanks again,
Paulo França

Great thanks Paulo! Apprecite the report.
We'll try and get that fixed in the next few weeks.
Rob

At 12:35 PM 18/12/2006, you wrote:

>Hello!
>
>First of all, congratulations for this Great Tool!
>
>I was playing with the localization section and came across an
>aparently bug: the "Msg_Merging" key is never read! So I unpacked the
>executable just to take a look at it from an hexa editor, and,
>indeed, such entry is not referenced in the executable.
>The "Msg_Merging_Namespaces" entry is there (inside the .exe), as
>well as others, but not the "Msg_Merging".
>
>That causes the respective message always to show in english:
>Merging "..."
>
>Not a big deal, but it seems to affect whatever language, since the
>executable is not reading/using that entry in the ini file.
>
>Thanks for the owesome tool.
>
>Paulo França
>AthraSoft Components