Deploying upgraded Project to Server

Question

Hi,
Last year we upgraded our RoboHelp Projects to X5 from X3. I
made the upgrade on all local PCs used to edit but I never deployed
the new .xpj versions files to the Server in Production. We can
still deploy pages but I did run into an issue recently and was
wondering if that might be related to the fact that we upgraded the
Project (xpj) but didn't deploy it to the server.
I was recently contacted by individuals we make updates for
their OLH pages. I was asked to change the Title in the Task bar
above the page like you see in any Browser's top horizontal
frame/tab. So I proceeded to make the change through the Project
Title options menu and saved and redployed the .hhp file where I
believe this change occurs. However, I never saw the change in
Production and was wondering could it be that certain changes,
beside page edits, are related to the original settings of the
project that were first created and the old settings are sitting on
the server because either the new upgraded prj needs to get
deployed or some new file that is created through X5 needs to be
deployed? I don't know what is preventing me from making Project
settings changes on the server after I have deployed them. By the
way I can see the tile change in the Compiled primary preview
within RoboHelp. The change can also be seen in the deployed .hhp
file in notepad.
Please Advise.

Answer 1

Wow! Where to start?
1. Open the destination.xpj project in Program Files\RoboHelp
Office\RoboHTML\Tutorial\Destination.
2. Generate WebHelp output (already set as Primary Layout) to
the default folder (\!SSL!\WebHelp\destination.htm.
(IMPORTANT! RoboHelp will actually newly create the
destination.htm as its "start page," which is: a) the page that
contains frameset and browser information, but none of your
content; b) named by you (most applications use the browser
standard "index.htm" instead of using the project's name as the
default).
3. In addition to viewing the resulting output, take a look
at the folder and file structure under \!SSL!\WebHelp\. The only
file here with a "whstart" name is a JavaScript file created and
used by RoboHelp for its output presentation. ALL of the files
under this folder umbrella must be provided into the area where
users will access them. IMPORTANT: The output files should never be
involved with VSS at all! VSS, after all, is a
Source Control product; therefore, only
source files should be checked in/checked out (except for
the CPD, HHP, LDB, and PSS files).
4. Now right click on "Single Source Layouts > Microsoft
HTML Help" and select "Set as Primary Layout".
5. Generate HTML Help output to the default folder
(\!SSL!\Microsoft_HTML_Help\destination.chm).
6. In addition to viewing the resulting output, take a look
at the folder and file structure under \!SSL!\Microsoft_HTML_Help\.
Hopefully, this will give you and your people a better view
of just how you're repeatedly shooting yourselves in the foot. I
mean, really, you're killing yourselves with this totally
unorthodox use of the product.
Good luck,
Leon