This content has been marked as final. Show 3 replies
As long as your developers aren't using the .NET API to make the calls, you shouldn't need anything special. If you need to provide Context Sensitive Help, it's easily accomplished using a standard URL call.
Click here for more
If the developers ARE using API calls, what do I need to do? (I don't know yet if they are, but I'll certainly find out)
Well, I suppose if that turns out to be the case, there's good news and bad news.
First the bad news. (That way the good news is that much better!) The bad news is that you probably will be hard pressed to find someone selling the RoboHelp for DotNet. I believe this is required if that's the approach they are taking.
Now for the good news. Fellow Adobe Community Expert and Certified RoboHelp Instructor John Daigle recently posted here that what eHelp (the former owners of RoboHelp) used to charge for, Adobe is now (are you sitting down?) providing totally within the application at no additional charge! So the DotNet API is now just a part of RoboHelp. So this would provide additional incentive to spring for the upgrade to either the Technical Communication Suite (TCS) or just RoboHelp 7.