The only thing that you (as a Fortran
project vendor perhaps) have to worry about is the keyword. To push a link
into my ktable, your sender topic--which I like to think of as a
"vs_NewProjectDialog_ProjectType" as an A-keyword.
Easy, huh? Of course, the sender
topic must reside in an HTML Help 2.x HXS file that has been properly registered
into the same collection as my topic's hxs (MSDN Combined Collection). But once
it's there, a link to your topic appears in my topic dynamically at
K-links can be formatted as tables, lists,
bulleted lists, numbered lists, or symbol-delimited lists. In my opinion,
all VS.NET and .NET topics should be klink-enabled in the See Also list.
Here are some arguments
for and against the blanket implementation of k-links across the Visual Studio
.NET and .NET Frameworks documentation (or any similar HTML Help 2.x collection
for that matter).
By the way, the K in
K-Links does not, as popular myth might have you believe, derive from
my first name. For more information about how to create HTML Help 2.x hxs'
and collections, see Visual
Studio .NET Help Integration Kit. You must have either VS.NET 2002 or 2003
on your computer and you must install the appropriate VSHIK package to
access the help topics.
Well, back to the VSS
and SCS docs.... Meine kleine
disclaimer: Microsoft kann für die Richtigkeit
und Vollständigkeit der Inhalte in dieser Newsgroup keine Haftung