This content has been marked as final. Show 7 replies
RH will only work from a local drive.
Could you please elaborate on this because I'm sure my superiors will be asking my why it only works from a local drive and what does that have to do with SharePoint.
My understanding is you have moved the project to a network drive as part of sharepoint, correct? Quite simply RH is not designed to work on projects across a network. It is underpinned by an Access database and they do not work well across networks.
I am not understanding why you want the project in Sharepoint anyway.
We were trying to do version control of the online help since we can't seem to get RoboSource 3.1 working. Having all kinds of problems talking to the database. That was our reasoning.
Thanks for all your help.
With RoboSource, or any version control, RH checks the required files out and copies them locally while you work. That is OK.
If you can use Sharepoint in that way, OK, but I don't think anyone has reported using Sharepoint with RH, never mind successfully.
Has anyone done this? If so, please speak up.
One of my colleagues has posted WebHelp output files to a SharePoint site in the past, and that shouldn't be any different than moving them to any other server. But it sounds like Bill is talking about placing all the source files in SharePoint, which would then place them on a network server. All the usual caveats about working on source files stored on a network probably apply.
We did try hosting our output build onto Sharepoint, and found some problems with the URLs from RH being too long for Sharepoint to handle... We stuck to our trusty Unix server in the end!
As for using SP to store the project, we've not tried that, but as the others have said, the Source Control needs to store files locally to work effectively.