Using CVS as source control with Sybase PowerBuilder - CodeProject 10,338,625 members (70,331 online) 1 Your email address needs to be confirmed. KENSHU1 My Settings My Contact info My Bookmarks My Watched Items My Articles My Messages My Questions My Answers My Comments 319 Sign out home articles Chapters and Sections> Search Latest Articles Latest Tips/Tricks Top Articles Beginner Articles Technical Blogs Posting/Update Guidelines Article Help Forum Article Competition Submit an article or tip Post your Blog quick answers Ask a Question about this article Ask a Question View Unanswered Questions View All Questions... C# questions ASP.NET questions VB.NET questions C#4.0 questions C++ questions discussions All Message Boards... Application Lifecycle> Running a Business Sales / Marketing Collaboration / Beta Testing Work & Training Issues Design and Architecture ASP.NET JavaScript C / C++ / MFC> ATL / WTL / STL Managed C++/CLI Adobe Technologies C# Free Tools Objective-C Ruby On Rails Database Hardware & Devices> System Admin Hosting and Servers Java .NET Framework Android Mobile Sharepoint Silverlight / WPF Visual Basic Web Development Site Bugs / Suggestions features CodeProject.TV Discuss CodeProject.TV Component & Service Catalog Competitions News The Insider Newsletter The Daily Build Newsletter Newsletter archive Surveys Product Showcase Research Library CodeProject Stuff community The Insider News The Lounge ? The Weird & The Wonderful The Soapbox Press Releases Who's Who Most Valuable Professionals Company Listings Non-English Language > General Indian Topics General Chinese Topics help What is 'CodeProject'? General FAQ Ask a Question Bugs and Suggestions Article Help Forum Site Map Advertise with us Employment Opportunities About Us Search within: Articles Videos Quick Answers Messages Product Catalog Articles » General Reading » Uncategorised Technical Blogs » General Next ArticleBrowse CodeStatsRevisions (2)Alternatives Comments & Discussions Add your ownalternative version Using CVS as source control with Sybase PowerBuilder By voloda2, 25 Jun 2010 0.00 (No votes) Rate: Add a reason or comment to your vote: x Votes of 3 or less require a comment Is your email address OK? You are signed up for our newsletters but your email address is either unconfirmed, or has not been reconfirmed in a long time. Please click here to have a confirmation email sent so we can confirm your email address and start sending you newsletters again. Alternatively, you can update your subscriptions. This article briefly describes how to use CVS for PowerBuilder. We are using this solution for about 6 years and it works very well. PBL Problems The main difficulty of the Sybase Power Builder is in PBL libraries. PBL libraries are binary libraries containing both - sources and precompiled sources. This solution causes many problems: PBLs are also very inclined to faults (in Power Builder 7, it was not very surprising that after fullrebuild failure, PBLs were completely broken). Object sources saved in PBLs are not easily comparable. Also, built-in support for inefficiencies (sources are checked-out to temporary PBL library, offline access is not very comfortable, etc.). In the case of multiple developers working on the same project, this causes many problems with sources synchronization (you can use many utilities, but it was always hell after one week track all changes and put them together - it took about half a day per week and it was quite often that some changes were lost). Solution Use CVS as source control (you can use both *nix or Windows solution). Use TortoiseCVS (or any other free CVS GUI clients) for access to sources. Use Winmerge or any other free utility for sources differences comparison. Export all sources into CVS project source tree (the best way is to export every PBL library into the separate directory in the CVS source tree). On building machine, use PowerGen for project compilation and PBLs restore. In each build, you can take your PBLs from scratch (PowerGen can resolve all dependencies between objects and import them back into PBLs in the correct order). Every developer takes fresh PBLs after every build. Editing Sources Every developer can take fresh PBLs generated by PowerGen after build. Before change, perform Update command on existing object. Import this object from CVS sandbox into your work PBL (replacing the existing one). Perform any required changes. Export modified object from working PBL to the CVS sandbox. Execute Commit command on the exported object in CVS sandbox, provide proper comment and send it to the CVS source control. Benefits All sources are stored in plain text (including datawindows). All changes are simply trackable (from Power Builder 9 (?8?) this works much better, because in previous versions Power Builder changes order of methods on every save) - at least you know why and who made the change. You can simply resolve any conflicts (no more hell with sharing and synchronizing PBLs between developers). PBLs can't contain any old errors from rebuilding, etc. You can also connect additional actions to every source file commit/checkout/tag and automatically connect those into other company systems. You can also use tags and branches for tracking your builds. Links TortoiseCVS WinMerge Sybase Power Builder on Wiki PowerGen License This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL) About the Author voloda2 Software Developer Czech Republic I'm software developer since 1996. I started with assembler on Intel 8051 CPUs, during years I was interested in C, C++, Sybase PowerBuilder, PHP, Sybase Anywhere Database, MSSQL server and multiplatform development. Currently I'm developing in C++ and C# (this is my favorit and I spent some time with MCPD achievement). I'm also interested in design patterns. Article Top Comments and Discussions Add a Comment or Question Search this forum Profile popups Spacing RelaxedCompactTight Noise Very HighHighMediumLowVery Low Layout NormalOpen TopicsOpen AllThread View Per page 102550 -- There are no messages in this forum -- About Article A Technical Blog, originally posted at http://voloda.bazilisek.net/2010/06/using-cvs-as-source-control-with-sybase.html This article describes how to use CVS for PowerBuilder. We are using this solution for about 6 years and it works very well. Type Technical Blog Licence CPOL First Posted 25 Jun 2010 Views 5,282 Bookmarked 0 times All-Topics Top News Programmers without TDD will be unemployable by 2022 Get the Insider News free each morning. Related Videos Related Articles Sybase PowerBuilder Meets Microsoft .NET The Missing Link Introduction to Pocket PC Development Using SVN as source control for Sybase PowerBuilder Bye Bye Clip Window; Hello Snippets Peering Behind the PowerBuilder .NET Assembly Curtain ADO Connection Strings HOWTO: CVS with VS.NET Accessing CVS Repository with C# Getting started with a SourceForge project Visual Studio 2008 CVS Setup Case Study: Refactoring a PowerBuilder Classic Application Building the CVS Root File Changing Utility RESTful Web Services: A Quick-Start How-to Guide - Part 1 10 Steps to Creating a Windows Mobile Database Application Using .NET and UltraLite 10 Stored Procedure Class Wizard (SPCW) Packet Capture and Analayzer CResizeCtrl Call C# assembly and its method in PowerBuilder SvnRev: Extract Revision Numbers from Your Sources Related Research Fine-Tuning the Engines of SMB Growth: 4 strategies for growing your business Permalink | Advertise | Privacy | Mobile Web01 | 2.8.140120.2 | Last Updated 25 Jun 2010 Article Copyright 2010 by voloda2Everything else Copyright © CodeProject, 1999-2014 Terms of Use Layout: fixed | fluid