> 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
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
Thanks for the advice, Nikolay and Rob.
I hadn't found the problem by searching, because I was searching "H2Reg
Internal Error 2753" and turning up nothing--it hadn't occurred to me
that InstallShield had the problem (which, in hindsight, is
ridiculous--we have *many* more problems with InstallShield!).
Anyway, all is well now.
Cheers,
Dan
[Non-text portions of this message have been removed]
Thanks both for your replies. When my InstallShield expert gets in,
I'll have him try this.
I'll keep you posted.
DC
________________________________
From: H2Reg@yahoogroups.com [mailto:H2Reg@yahoogroups.com] On Behalf Of
Nikolay Dobrev
Sent: Thursday, February 09, 2006 11:49 PM
To: H2Reg@yahoogroups.com
Subject: Re: [H2Reg] Re: Internal Error 2753. h2reg.exe
Hi,
it is definitely an InstallShield problem. Just try a search for
"Internal Error 2753" and you will see how many companies mention this
problem for their install packages (and never related to H2Reg).
I think that the suggestion that Rob gave will do it.
Greetings,
Nikolay
"Rob Chandler [MVP]" <robertc@...> wrote: Never seen that
one.
The most common problem folks find with InstallShield
is they forget to run external apps in "Wait" mode.
Run in "no Wait" mode and you can create problems.
So typically people who like to run 2 Command Script files
will have trouble.
Does this help?
Rob
--- In H2Reg@yahoogroups.com, "ciruli" <dan@...> wrote:
>
> I'm testing the Uninstall feature of our software (we use Helpware
and
> h2reg on installation). We use InstallShield for our
> install/uninstall utility.
>
> When I attempt to uninstall our software, I get the following
error:
> Internal Error 2753. h2reg.exe
>
> I can run the h2reg -U command from the command prompt and it
works
> fine; however, when InstallShield runs it, it gives the internal
error.
>
> It may be relevant that we're registering (and unregistering) two
> different collections (one for VS 2003, one for VS 2005).
>
> Anyone seen this error before?
>
H2Reg Home Page: http://helpware.net/mshelp2/h2reg.htm
SPONSORED LINKS
Peer to peer
Software Peer to peer software
Ms help Peer to peer network
Computer support software
---------------------------------
YAHOO! GROUPS LINKS
Visit your group "H2Reg" on the web.
To unsubscribe from this group, send an email to:
H2Reg-unsubscribe@yahoogroups.com
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
---------------------------------
---------------------------------
Brings words and photos together (easily) with
PhotoMail - it's free and works with Yahoo! Mail.
[Non-text portions of this message have been removed]
H2Reg Home Page: http://helpware.net/mshelp2/h2reg.htm
SPONSORED LINKS
Peer to peer
<http://groups.yahoo.com/gads?t=ms&k=Peer+to+peer&w1=Peer+to+peer&w2=Sof
tware&w3=Peer+to+peer+software&w4=Ms+help&w5=Peer+to+peer+network&w6=Com
puter+support+software&c=6&s=129&.sig=LNmc2cFyEAfhHbh4n7tFkg> Software
<http://groups.yahoo.com/gads?t=ms&k=Software&w1=Peer+to+peer&w2=Softwar
e&w3=Peer+to+peer+software&w4=Ms+help&w5=Peer+to+peer+network&w6=Compute
r+support+software&c=6&s=129&.sig=QpAI56PHEKupl6UjpbBMaQ> Peer to
peer software
<http://groups.yahoo.com/gads?t=ms&k=Peer+to+peer+software&w1=Peer+to+pe
er&w2=Software&w3=Peer+to+peer+software&w4=Ms+help&w5=Peer+to+peer+netwo
rk&w6=Computer+support+software&c=6&s=129&.sig=Ul1F6ehJa5qcPezm1owOug>
Ms help
<http://groups.yahoo.com/gads?t=ms&k=Ms+help&w1=Peer+to+peer&w2=Software
&w3=Peer+to+peer+software&w4=Ms+help&w5=Peer+to+peer+network&w6=Computer
+support+software&c=6&s=129&.sig=J7sgn-wZz_92X0RgO0Xn4Q> Peer to
peer network
<http://groups.yahoo.com/gads?t=ms&k=Peer+to+peer+network&w1=Peer+to+pee
r&w2=Software&w3=Peer+to+peer+software&w4=Ms+help&w5=Peer+to+peer+networ
k&w6=Computer+support+software&c=6&s=129&.sig=LuUGUuNhxm1rWeRGZz_auA>
Computer support software
<http://groups.yahoo.com/gads?t=ms&k=Computer+support+software&w1=Peer+t
o+peer&w2=Software&w3=Peer+to+peer+software&w4=Ms+help&w5=Peer+to+peer+n
etwork&w6=Computer+support+software&c=6&s=129&.sig=TPI-nfRJhJTPJp8oB2EAL
A>
________________________________
YAHOO! GROUPS LINKS
* Visit your group "H2Reg <http://groups.yahoo.com/group/H2Reg> "
on the web.
* To unsubscribe from this group, send an email to:
H2Reg-unsubscribe@yahoogroups.com
<mailto:H2Reg-unsubscribe@yahoogroups.com?subject=Unsubscribe>
* Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service <http://docs.yahoo.com/info/terms/> .
________________________________
[Non-text portions of this message have been removed]
Hi,
it is definitely an InstallShield problem. Just try a search for "Internal Error
2753" and you will see how many companies mention this problem for their install
packages (and never related to H2Reg).
I think that the suggestion that Rob gave will do it.
Greetings,
Nikolay
"Rob Chandler [MVP]" <robertc@...> wrote: Never seen that one.
The most common problem folks find with InstallShield
is they forget to run external apps in "Wait" mode.
Run in "no Wait" mode and you can create problems.
So typically people who like to run 2 Command Script files
will have trouble.
Does this help?
Rob
--- In H2Reg@yahoogroups.com, "ciruli" <dan@...> wrote:
>
> I'm testing the Uninstall feature of our software (we use Helpware
and
> h2reg on installation). We use InstallShield for our
> install/uninstall utility.
>
> When I attempt to uninstall our software, I get the following
error:
> Internal Error 2753. h2reg.exe
>
> I can run the h2reg -U command from the command prompt and it
works
> fine; however, when InstallShield runs it, it gives the internal
error.
>
> It may be relevant that we're registering (and unregistering) two
> different collections (one for VS 2003, one for VS 2005).
>
> Anyone seen this error before?
>
H2Reg Home Page: http://helpware.net/mshelp2/h2reg.htm
SPONSORED LINKS
Peer to peer
Software Peer to peer software
Ms help Peer to peer network
Computer support software
---------------------------------
YAHOO! GROUPS LINKS
Visit your group "H2Reg" on the web.
To unsubscribe from this group, send an email to:
H2Reg-unsubscribe@yahoogroups.com
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
---------------------------------
---------------------------------
Brings words and photos together (easily) with
PhotoMail - it's free and works with Yahoo! Mail.
[Non-text portions of this message have been removed]
Never seen that one.
The most common problem folks find with InstallShield
is they forget to run external apps in "Wait" mode.
Run in "no Wait" mode and you can create problems.
So typically people who like to run 2 Command Script files
will have trouble.
Does this help?
Rob
--- In H2Reg@yahoogroups.com, "ciruli" <dan@...> wrote:
>
> I'm testing the Uninstall feature of our software (we use Helpware
and
> h2reg on installation). We use InstallShield for our
> install/uninstall utility.
>
> When I attempt to uninstall our software, I get the following
error:
> Internal Error 2753. h2reg.exe
>
> I can run the h2reg -U command from the command prompt and it
works
> fine; however, when InstallShield runs it, it gives the internal
error.
>
> It may be relevant that we're registering (and unregistering) two
> different collections (one for VS 2003, one for VS 2005).
>
> Anyone seen this error before?
>
I'm testing the Uninstall feature of our software (we use Helpware and
h2reg on installation). We use InstallShield for our
install/uninstall utility.
When I attempt to uninstall our software, I get the following error:
Internal Error 2753. h2reg.exe
I can run the h2reg -U command from the command prompt and it works
fine; however, when InstallShield runs it, it gives the internal error.
It may be relevant that we're registering (and unregistering) two
different collections (one for VS 2003, one for VS 2005).
Anyone seen this error before?
Thanks Rob. I passed along the info. I'll reply with the verdict.
Bill
On 1/9/06, Rob Chandler <robertc@...> wrote:
> 1. Make sure they they saved the INI file as ANSI not Unicode.
> Unicode will probably work but this system is basically
> ANSI. It detects the Windows environment and loads the appropriate
> INI section and relies on the current code page to read the text.
>
> If the Chinese works but not the Japanese I'll bet that one is in ANSI
> and one is in UNICODE.
>
> 2. Make sure the [ja] ; Japanese section is being read.
> Try adding unique English strings to it first.
>
> If all else fails can you please pass me the INI file so I can have a look.
--
Bill Swallow
HATT List Owner
WWP-Users List Owner
42.8162,-73.7736
http://techcommdood.blogspot.com
============================
I support Char James-Tanny for STC Secretary.
>Hi there.
>
>Seems it's been a while since this list has seen some action...
>
>My L10n department is running into issues with using Japanese resource
>strings in the h2reg.ini. They are getting junk in the registration
>messages. Interestingly enough, Chinese is working fine. Is there a
>bug with regard to Japanese or perhaps something that needs to be done
>differently than Chinese?
>
>Bill
Hi Bill
A few things to check...
1. Make sure they they saved the INI file as ANSI not Unicode.
Unicode will probably work but this system is basically
ANSI. It detects the Windows environment and loads the appropriate
INI section and relies on the current code page to read the text.
If the Chinese works but not the Japanese I'll bet that one is in ANSI
and one is in UNICODE.
2. Make sure the [ja] ; Japanese section is being read.
Try adding unique English strings to it first.
If all else fails can you please pass me the INI file so I can have a look.
Thanks
Rob
Hi there.
Seems it's been a while since this list has seen some action...
My L10n department is running into issues with using Japanese resource
strings in the h2reg.ini. They are getting junk in the registration
messages. Interestingly enough, Chinese is working fine. Is there a
bug with regard to Japanese or perhaps something that needs to be done
differently than Chinese?
Bill
--- In H2Reg@yahoogroups.com, "Marc Scheuner" <mscheuner@p...> wrote:
> HTML Help v2 still continues to amaze and puzzle me....
>
> Where on earth are those namespaces really registered? Don't seem to
> be in the registry.....
>
> I have tons of old namespaces hanging around from testing - is there
a
> way to get rid of those entries (that aren't valid anymore - help
> files might be moved away or deleted).
>
> Thanks for any help or pointers!
> Marc
FAR (h2 Utils win) can be used to remove registrations.
Registration is kept in a folder.
Marc have a read of
http://helpware.net/mshelp2/h2faq.htm
Rob
HTML Help v2 still continues to amaze and puzzle me....
Where on earth are those namespaces really registered? Don't seem to
be in the registry.....
I have tons of old namespaces hanging around from testing - is there a
way to get rid of those entries (that aren't valid anymore - help
files might be moved away or deleted).
Thanks for any help or pointers!
Marc
--- In H2Reg@yahoogroups.com, Nikolay Dobrev <koelera@y...> wrote:
> Hello,
>
> That is exactly what I am doing here with two little exceptions.
> 1. I have MC.VSIPCC+ in the merge section - well that seems not
to be necessary.
Right
> 2. I do not use the "AUTO" option for merging. I prefer to be
absolutely sure, that merging will happen at registration time. Do
you recomment using AUTO mode?
No I wouldn't bother. The AUTO (from memory) is good if there is
lots of things going ... it will look at the files in the H2
registration folder and try and judge if a Merge should really be
done (by checking file dates). In your case you definitely want to
Merge MS.VSCC+ so leave the AUTO off (I probably should have too).
> And thanks for the answer. You were really fast :)
Pleasure.
>
> NIky
Hello,
That is exactly what I am doing here with two little exceptions.
1. I have MC.VSIPCC+ in the merge section - well that seems not to be
necessary.
2. I do not use the "AUTO" option for merging. I prefer to be absolutely sure,
that merging will happen at registration time. Do you recomment using AUTO mode?
And thanks for the answer. You were really fast :)
NIky
Rob Chandler <robertc@...> wrote:
Hi Niky
MS like the big merge delay to be during installation.
But you do what you think your customers would like.
The current VS Beta 2 DExplore wont auto Merge but next version will.
Yes I would merge the base collection MS.VSCC.v80
( see H2Reg Script below where I still use MS.VSCC+ ).
I tested this... the Base collection MS.VSCC.v80
did the trick. When I only Merged MS.VSIPCC.v80 it did not complete
Merge.
I've just uploaded H2Reg V1.4.3 which has updated documentation
and uses the following H2Reg script file to register the H2Reg doc collection.
Notice [Reg_Plugin] and [UnReg_Plugin] registers VS 7.0 and VS 7.1 separately
(since they need to plug into MS.VSCC and MS.VSCC.2003 respectively)
and we use MS.VSIPCC+ which covers VS 8.0 and beyond.
Rob
;------- Register -r switch
[Reg_Namespace]
;<nsName>|<nsColfile>|<nsDesc>
hw.h2reg|COL_Master.HxC|H2Reg.exe Documentation - www.helpware.net
[Reg_Title]
;<nsName>|<TitleID>|<LangId>|<HxS_HelpFile>|<HxI_IndexFile>|<HxQ_QueryFile>|<HxR\
_AttrQueryFile>|<HxsMediaLoc>|<HxqMediaLoc>|<HxrMediaLoc>|<SampleMediaLoc>
hw.h2reg|h2reg|1033|h2reg.HxS|h2reg.HxS||||||
[Reg_Plugin]
;<nsName_Parent>|<HxT_Parent>|<nsName_Child>|<HxT_Child>|<HxA_Child>
MS.VSCC|_DEFAULT|hw.h2reg|_DEFAULT|COL_Master.HxA
MS.VSCC.2003|_DEFAULT|hw.h2reg|_DEFAULT|COL_Master.HxA
MS.VSIPCC+|_DEFAULT|hw.h2reg|_DEFAULT|COL_Master.HxA
[Reg_Filter]
;<nsName>|<FilterName>|<FilterQueryStr>
hw.h2reg|h2reg helpware documentation|("helpware"="h2reg")
;------- UnRegister -u switch
[UnReg_Namespace]
;<nsName>
hw.h2reg
[UnReg_Title]
;<nsName>|<TitleID>|<LangId>
hw.h2reg|h2reg|1033
[UnReg_Plugin]
;<nsName_Parent>|<HxT_Parent>|<nsName_Child>|<HxT_Child>|<HxA_Child>
MS.VSCC|_DEFAULT|hw.h2reg|_DEFAULT|COL_Master.HxA
MS.VSCC.2003|_DEFAULT|hw.h2reg|_DEFAULT|COL_Master.HxA
MS.VSIPCC+|_DEFAULT|hw.h2reg|_DEFAULT|COL_Master.HxA
[UnReg_Filter]
;<nsName>|<FilterName>
hw.h2reg|h2reg helpware documentation
;------ Merge -m switch
[Merge_Namespace]
MS.VSCC+|auto
At 08:02 PM 26/07/2005, Nikolay Dobrev wrote:
>Hello,
>
>As per latest Microsoft help team instructions, we
>manually merge the help during the installation. My
>question is: What would you recommend as namespace to
>be merged? My logic is: we plug into MS.VSIPCC.v80 and
>that's the namespace that should be merged. Or, should
>we merge our namespace instead (i.e. the child of the
>MS.VSIPCC.v80)?
>
>Also if we plug into MS.VSIPCC.v80, should we merge
>ms.vscc.v80 (that's the result of putting ms.vscc+ in
>the merge namespaces section of H2Reg script)?
>
>Please Advise!
>
>Thank you,
>Niky
>
>
>
>____________________________________________________
>Start your day with Yahoo! - make it your home page
>http://www.yahoo.com/r/hs
>
>
>
>MSHelp2 Home Page: http://www.helpware.net/mshelp2/
>Yahoo! Groups Links
>
>
>
>
H2Reg Home Page: http://helpware.net/mshelp2/h2reg.htm
---------------------------------
YAHOO! GROUPS LINKS
Visit your group "H2Reg" on the web.
To unsubscribe from this group, send an email to:
H2Reg-unsubscribe@yahoogroups.com
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
---------------------------------
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
[Non-text portions of this message have been removed]
Hi Niky
MS like the big merge delay to be during installation.
But you do what you think your customers would like.
The current VS Beta 2 DExplore wont auto Merge but next version will.
Yes I would merge the base collection MS.VSCC.v80
( see H2Reg Script below where I still use MS.VSCC+ ).
I tested this... the Base collection MS.VSCC.v80
did the trick. When I only Merged MS.VSIPCC.v80 it did not complete
Merge.
I've just uploaded H2Reg V1.4.3 which has updated documentation
and uses the following H2Reg script file to register the H2Reg doc collection.
Notice [Reg_Plugin] and [UnReg_Plugin] registers VS 7.0 and VS 7.1 separately
(since they need to plug into MS.VSCC and MS.VSCC.2003 respectively)
and we use MS.VSIPCC+ which covers VS 8.0 and beyond.
Rob
;------- Register -r switch
[Reg_Namespace]
;<nsName>|<nsColfile>|<nsDesc>
hw.h2reg|COL_Master.HxC|H2Reg.exe Documentation - www.helpware.net
[Reg_Title]
;<nsName>|<TitleID>|<LangId>|<HxS_HelpFile>|<HxI_IndexFile>|<HxQ_QueryFile>|<HxR\
_AttrQueryFile>|<HxsMediaLoc>|<HxqMediaLoc>|<HxrMediaLoc>|<SampleMediaLoc>
hw.h2reg|h2reg|1033|h2reg.HxS|h2reg.HxS||||||
[Reg_Plugin]
;<nsName_Parent>|<HxT_Parent>|<nsName_Child>|<HxT_Child>|<HxA_Child>
MS.VSCC|_DEFAULT|hw.h2reg|_DEFAULT|COL_Master.HxA
MS.VSCC.2003|_DEFAULT|hw.h2reg|_DEFAULT|COL_Master.HxA
MS.VSIPCC+|_DEFAULT|hw.h2reg|_DEFAULT|COL_Master.HxA
[Reg_Filter]
;<nsName>|<FilterName>|<FilterQueryStr>
hw.h2reg|h2reg helpware documentation|("helpware"="h2reg")
;------- UnRegister -u switch
[UnReg_Namespace]
;<nsName>
hw.h2reg
[UnReg_Title]
;<nsName>|<TitleID>|<LangId>
hw.h2reg|h2reg|1033
[UnReg_Plugin]
;<nsName_Parent>|<HxT_Parent>|<nsName_Child>|<HxT_Child>|<HxA_Child>
MS.VSCC|_DEFAULT|hw.h2reg|_DEFAULT|COL_Master.HxA
MS.VSCC.2003|_DEFAULT|hw.h2reg|_DEFAULT|COL_Master.HxA
MS.VSIPCC+|_DEFAULT|hw.h2reg|_DEFAULT|COL_Master.HxA
[UnReg_Filter]
;<nsName>|<FilterName>
hw.h2reg|h2reg helpware documentation
;------ Merge -m switch
[Merge_Namespace]
MS.VSCC+|auto
At 08:02 PM 26/07/2005, Nikolay Dobrev wrote:
>Hello,
>
>As per latest Microsoft help team instructions, we
>manually merge the help during the installation. My
>question is: What would you recommend as namespace to
>be merged? My logic is: we plug into MS.VSIPCC.v80 and
>that's the namespace that should be merged. Or, should
>we merge our namespace instead (i.e. the child of the
>MS.VSIPCC.v80)?
>
>Also if we plug into MS.VSIPCC.v80, should we merge
>ms.vscc.v80 (that's the result of putting ms.vscc+ in
>the merge namespaces section of H2Reg script)?
>
>Please Advise!
>
>Thank you,
>Niky
>
>
>
>____________________________________________________
>Start your day with Yahoo! - make it your home page
>http://www.yahoo.com/r/hs
>
>
>
>MSHelp2 Home Page: http://www.helpware.net/mshelp2/
>Yahoo! Groups Links
>
>
>
>
Hi Iulian
--- In H2Reg@yahoogroups.com, "Iulian Ionescu" <iulian.ionescu@e...>
wrote:
> Everything seems to be ok, except the fact the the plugin into the
> MS.VSIPCC fails... Any ideas where should I look?
<snip>
OK lets see...
> ----------
> [Reg_Namespace]
> Olvio.PlusDock|Olvio.PlusDock.HxC|Olvio PlusDock Documentation -
> www.olvio.com
Register NS Olvio.PlusDock
> [Reg_Title]
> Olvio.PlusDock|Olvio.PlusDock|1033|Olvio.PlusDock.HxS|||||||
Add title Olvio.PlusDock to it.
I'm not a great fan of having the namespace = Title.
I don't its a problem.
Why not ... NS = Company.ProductSuiteName, Title=ProductTitle
> [Reg_Plugin]
> MS.VSCC+|_DEFAULT|Olvio.PlusDock|Olvio.PlusDock
> MS.VSIPCC+|_DEFAULT|Olvio.PlusDock
In VS 2005 there still a MS.VSCC.v80.
MS.VSIPCC.v80 plugs into that, and we are suppose to plug into
MS.VSIPCC.v80. So you just plugged in twice into the VS 2005
collection.
There is a mizture of formats there ????? Why?
I would do this... Covers all 3 VS and future VS
MS.VSCC|_DEFAULT|Olvio.PlusDock
MS.VSCC.2003|_DEFAULT|Olvio.PlusDock
MS.VSIPCC+|_DEFAULT|Olvio.PlusDock
[UnReg_Plugin]
MS.VSCC|_DEFAULT|Olvio.PlusDock
MS.VSCC.2003|_DEFAULT|Olvio.PlusDock
MS.VSIPCC+|_DEFAULT|Olvio.PlusDock
Try again after a reboot.
Also try FAR v4 Collection Wizard. It will help you. (use the Beta).
Rob
FYI I've just posted 2 new items in the my FAQ
http://helpware.net/mshelp2/h2faq.htm
--
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 (thank God).
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. For some reason these viewers still detect and auto-
merge. I suspect DExplore beta 2 is throwing some undocumented H2
API switch to inhibit detect/auto-merge.
--
Q. What has changes in VS Version 8? [2005-06-25, VS 2005 Beta 2]
Authors should be aware of the following changes to VS 2005 (VS v8.0)
== Where is the Help SDK? ==
Help 2.0 SDK is no longer a separate download. It is now part of the
VSIP 2005 SDK. A free download.
http://msdn.microsoft.com/vstudio/extend/
== Plug into MS.VSIPCC.v80 ==
MS now recommend you now plug into MS.VSIPCC.v80 and not MS.VSCC.v80
(MS.VSIPCC.v80 is plugged into MS.VSCC.v80). I don't see much
difference except maybe that it keeps 3rd party help grouped
together and out of way of the MS collections.
== Control Plug-in Order ==
Under VS 8 you can now control plug-in order. See
http://helpware.net/mshelp2/h2faq.htm#PluginOrder
== Manage VS Plug-ins ==
As in VS 2003 you can use the inbuilt "Collection Manager" page to
plug/unplug collections into VSCC.
Paste this URL into IE6 address bar:
ms-help://MS.VSCC.v80/dv_vscccommon/local/CollectionManager.htm
This utility page covers plug-ins for MS.VSCC.V80, MS.MSDN.V80,
MS.MSDNARCHIVE and MS.VSIPCC.V80 (The page does not list these
collection names unfortunately. All you see is a list of namespaces
and checkboxes).
** END **
I'm assuming test box does not have VSHIK installed?
> None of the collection files have DTD references
Mmm. In 99% of cases this is normally the cause.
Check once more that there is no DTDs referenced in the
collection level files.
Troubleshooting tips here
http://helpware.net/mshelp2/h2reg.htm#Troubleshooting
Send me all the Hx? files if you like.
rob AT Helpware.net
Rob
I have generated MS Help 2 files and they go in fine on my dev box,
but on the test box they appear to register and never show up in
Contents.
Both machines have VSHIK installed
I am using the same files to register in each place
None of the collection files have DTD references
The h2Reg help file does register and integrate into VS help without
problem
The Collection I am trying to register _does_ appear in Collection
Manager
I'm stuck. Ideas?