Buy us a cup of coffee?
This site is powered entirely by coffee. Coffee and love. Or is it that we love coffee? Whatever.
We really do hate to have to ask and don't want to be a nag, but If you would like to see good and helpful stuff continued to be offered, please consider making a donation of any amount to help keep the coffee (and the good stuff) coming!
This month's scry is a bit of an extension from last month's. After outlining how to duplicate projects, some of you kindly wrote me to advise that this is all well and good unless... your project is under source control! Soooo, I figured it would be a natural segue into delving into the mysteries of removing a project from RoboSource Control! (hence the title of "Banishing the sorcery"). As this scry applies only to x5 users, you can happily disregard this issue if you are using an earlier version. Sorry folks. I'll try and do better next month with a more general topic.
Without further hesitation, shall we dive right in?
Okay, being the good do bee that you are, you have made a copy of your project using the instructions in the September Scry. You anxiously cracked the project open and your hopes fell flat when you were prompted to check files out of the RoboSource Control database. Grrrrrr
First, calmly dispense with any and all dialogs and close RoboHelp HTML so that the duplicated project isn't hindered in any way. Now, off with you and don't come back until this task is complete.
Got it closed? Already! Hmmm, well jolly good then. Let's proceed with disconnecting this ornery little Balrog from the location it seems to be so fond of.
The first step is to use Windows Explorer and navigate to the location containing the copied project.
Now select all the files inside the folder (hint - Ctrl+A usually does this quite nicely) change the attributes so that none of them are Read Only. Typically this is done by right clicking the list of selected files and selecting Properties from the context menu.
The Properties dialog displays (Windows XP depicted - Other OS' may vary)
Odds are that the Read-only check box will be shaded. This indicates that some of the selected files have the Read-only flag set and the others don't. Click the Read-only check box until it is clear. This should ensure that none of the files have the Read-only flag set.
Among the files in the folder, you should find one named "ProjectName.CPD". (of course, ProjectName would reflect the actual name of the project you are working on. For example, if your project is named BobsHelp, you would find a BobsHelp.CPD file. Delete this file from the hard drive. (You, um, ARE working locally, right? I've seen a few forum posts lately where the users vehemently declare they work off LANs with no issues. Well, they USED to do this until this or that changed, then the projects don't work any more. Then when we request the files to be moved locally, they rather obstinately declare that they USED to work just FINE off the LAN, thank you very much, and they simply want to argue when we ask to move the files locally. But I digress.) Anyhoo, you want to delete this file. No backup should be necessary, as RoboHelp HTML should happily re-create this file when you restart it.
Among the files in the folder, you should also find one named "pblsvrs.sss". You want to delete this file as well. This file is totally related to source control. So there is no need to worry about saving a backup.
Now you want to locate the file named "ProjectName.XPJ". This is the x5 project file. It's a XML file. Since XML files are simply ASCII text, you can open and edit it using good old Windows Notepad. And this is your goal. Open the file using Windows Notepad. You want to make the following changes:
Remove the section of code beginning with <miscproperties> and ending with </matchedpair>. Leave the </miscproperties> line present and untouched.
Change the </miscproperties> line by relocating the forward slash to the end of the line so that instead, it reads <miscproperties/>.
Close Windows Notepad and save the changes to the ProjectName.XPJ file.
You may now resume working with this project as if it had never been associated with source control.
Until next month... Namasté and Merry part!