O-Script / Binary file Code Management

To support our customization of our livelink application, we started to implement a source control tool (Microsoft Visual Source Safe - VSS). However, we found that this tool does not support the binary files that are created by the builder through the modification of the O script files. We need to separate our core production code from development projects, but maintain the ability to respond to production bugs (through a patch). We may also have the case that we have two, concurrent but separate development initiatives.Assistance with the following would be greatly appreciated:1) What is Opentext's recommendation for a source control tool for o script files?2) Can VSS be adopted or configured to address this need?3) Does Opentext have resources or materials that addresses source code management of o script files?4) Other than Visual Sourse Safe is anyone using somehting else to manage code e.g. iScmTool or Subversion?Thanks and looking forward to some feedback

Find more posts tagged with

Comments

Finney_Bryan_(x-giantuser2_-_(deleted))

Message from Finney, Bryan via eLink1) We could never get any recommendation2) No. (I wish)3) None that we could ever find!4) We developed our ownBuilder is a single person development environment I have the module attached, but it is unsupported and undocumented.Thanks and good luck,Bryan FinneyGiant Eagle Inc.-----Original Message-----From: eLink Discussion: Development Discussion[mailto:development@elinkkc.opentext.com] Sent: Monday, October 25, 2004 1:57 PMTo: eLink RecipientSubject: O-Script / Binary file Code ManagementO-Script / Binary file Code ManagementPosted by Support, Hatch on 10/25/2004 01:54 PMTo support our customization of our livelink application, we started toimplement a source control tool (Microsoft Visual Source Safe - VSS).However, we found that this tool does not support the binary files thatare created by the builder through the modification of the O scriptfiles. We need to separate our core production code from developmentprojects, but maintain the ability to respond to production bugs(through a patch). We may also have the case that we have two,concurrent but separate development initiatives.Assistance with the following would be greatly appreciated:1) What is Opentext's recommendation for a source control tool for oscript files?2) Can VSS be adopted or configured to address this need?3) Does Opentext have resources or materials that addresses source codemanagement of o script files?4) Other than Visual Sourse Safe is anyone using somehting else tomanage code e.g. iScmTool or Subversion?Thanks and looking forward to some feedback[To reply to this thread, use your normal E-mail reply function.]============================================================Discussion: Development Discussionhttps://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=786303&objAction=viewLivelink Server:https://knowledge.opentext.com/knowledge/livelink.exe

Shawn Borden

Thanks for the feedback - I will investigate and post findings

Magnus_S_(novnoruser_-_(deleted))

Cool maybe use the dump files...I think I have seen that version management can be done rather good on the dumpfiles you get e.g. when you use Produce in the customizationrt module ....It is a littlebit sad that Open Text doesn't point in any direction as the owner of a plattform for developing a bigger companies document management .....RegardsMagnus

Finney_Bryan_(x-giantuser2_-_(deleted))

Message from Finney, Bryan via eLinkThe way we developed the solution I have attached in the previous replyis based on using the unlock ospace (checkout) and lock ospace (checkin)from the ospace menu. You have to have a table to store who and if the module is checked outby a user and a network shared area to store your currentversions andoldversions of the modules. It actually works very well and could be something worth while for OT tolook into building into core builder.