We have contacted Adobe for assistance, but I also wanted to post this question in case someone has experienced this and can quickly provide a solution.
Environment
Windows 7 Enterprise
RoboHelp 11.0.3.268
Generating WebHelp
Team Foundation Server
Visual Studio Professional 2010 Source Control
Problem
I'm the original author of the Touchstone Help system. Last week we started getting two colleagues on board to work with me. On their systems, we configured RoboHelp to work with TFS in Visual Studio using MSSCI Provider 2010.
The original project had lots of conditional build tags. I removed them all and the expressions and checked everything into Source Control. When my colleagues got the latest files from Source Control and opened the project from Version Control, we noticed that their projects still had the conditional build tags along with other items that had long ago been deleted. After some research, we deleted the CPD and PSS files from Source Control and let RoboHelp create them when we opened the project. That solved those problems -- no more conditional build tags in the project.
Last Friday colleague A began experiencing significant problems. When she right-clicked a topic to view properties, RoboHelp stopped working. She has not been able to do anything in RoboHelp since.
That same day I attempted to look at the Version Control settings (which I'd had no problem accessing all week). RoboHelp crashed as soon as I clicked Tools > Options. Colleague B experienced the same problem today.
This morning I experienced colleague A's problem.
Bottom line: we are suddenly not able to run RoboHelp 11.
Our in-house Help desk person tried running the Visual Studio debugger. We get "An unhandled win32 exception in RoboHtml.exe [5404]". We also unhandled exceptions at various address with an Access violation reading location hex address.
After looking at Willem's site that lists the RoboHelp updates, we thought about installing them, but we were not sure whether to install ALL the patches or only Patch 11.0.3. If all the patches, we were not sure whether to install them in a particular sequence.
Many thanks for any assistance any of you can provide while we also wait to hear from Adobe Support.
Carol