I really enjoyed reading about Kathy's setup. Never ceases to
amaze me how RoboHelp is used in workflows I've never dreamed of
Just to add to what Peter and Rick have mentioned. There
remains a lot of confusion about the old product names.
Fortunately, one of the first things Adobe did was to consolidate a
lot of "RoboInfo this" and "RoboHelp for .Net that" confusion. Now
you are only dealing with RoboHelp the authoring client and the
RoboHelp Server (which is optional).
There are others but the two main reasons for using RoboHelp
Server 6 (or the new 7) are:
1. Ability to search the text of PDF and MS Office (Word,
Excel, etc.) files natively rather than convert them to HTML
topics.
2. Generate User Feedback reports in order to update future
topic content based on that feedback.
As for .NET, the good news is that you no longer have to buy
anything extra to use the .NET API (pre-cooked code that developers
can use to link topics to Web Applications for context sensitive
help, etc.) This is optional. Some developers use it, some "roll
their own." But it's there for free beginning with RoboHelp 6
you'll find it on your hard drive here:
C:\Program Files\Adobe\RoboHelp 6.0\CSH API\RoboHelp.NET
Another nice thing Adobe did was eliminate the need for
purchasing extra licenses for additional domains on the RoboHelp
Server. This helps authoring teams create reports from different
sub sets of end users. In the old days you had to purchase a
license for each new domain, but no more.
You can read a bit more about this subject in this Developer
Network article
http://www.adobe.com/devnet/robohelp/articles/rhserver.html
Thanx,
john
John Daigle
Adobe Certified RoboHelp and Captivate Instructor
Newport, Oregon