Manage Hyperlinked Documents

[rlm]

Background: We have a set of documents maintained with MS Word
as .mhtml documents. The documents contain instruction sets. The
documents are cross-referenced. So step N of a set of instructions in
document X may contain a hyperlink to document Y. As it stands the
documents are opened in a standard browser (e.g. MS IE or FireFox) by
the person executing the instructions. The documents are all stored
in one directory structure (a network share) but not in the same
directory. Goal: Our goal is to keep track of when, how long and by
whom the documents are opened (and closed). Language Tool Requirement:
C#.Net 2005. Question: If we use the Web Browser 2.0.0.0 control can
we maintain control of the opening of the documents via hyperlinks? In
other words if one of our documents is open in our custom app and then
the user clicks on a hyperlink within the document can we use the
"Navigate Method" (and "Navigating event") to open the document within
our application as opposed to having the document open in the standard
system browser?

 

[Pavel Minaev]

Background: We have a set of documents maintained with MS Word
as .mhtml documents. The documents contain instruction sets. The
documents are cross-referenced. So step N of a set of instructions in
document X may contain a hyperlink to document Y. As it stands the
documents are opened in a standard browser (e.g. MS IE or FireFox) by
the person executing the instructions.  The documents are all stored
in one directory structure (a network share) but not in the same
directory. Goal: Our goal is to keep track of when, how long and by
whom the documents are opened (and closed). Language Tool Requirement:
C#.Net 2005. Question: If we use the Web Browser 2.0.0.0 control can
we maintain control of the opening of the documents via hyperlinks? In
other words if one of our documents is open in our custom app and then
the user clicks on a hyperlink within the document can we use the
"Navigate Method" (and "Navigating event") to open the document within
our application as opposed to having the document open in the standard
system browser?

Most likely yes. I don't see why .mhtml docs would be treated any
different from plain .html once they're loaded. But of course the
quickest way to get an answer to this, quite specific, question is to
prototype it and see what happens.