前往Shuct.Net首页

Shudepb PB反编译专家长时间以来,为业内同类软件事实上的唯一选择.细节,彰显专业.态度,决定品质.

关于PowerBuilder的搜索

Subversion Plug-in for PowerBuilder - Agent SVN Agent SVN - SCC Subversion Plug-in Developed by Jussi Jumppanen "Seamlessly integrate the Subversion version control with your IDE...." Introduction Download Purchasing Technical Support Forum info@zeusedit.com Xidicone P/L Copyright (c) 2008-2014 Modified 21/1/2014 Latest Version: 2.35 Using PowerBuilder with Subversion Below is a video showing Agent SVN in action. Using PowerBuilder and Subversion with Agent SVN The Agent SVN plug-in allows you to seamlessly integrate PowerBuilder with Subversion. Features of the plug-in include: Easy to install, easy to configure, easy to use Add solutions, projects and files to Subversion, all from within PowerBuilder Check out, check in, get latest version all without leaving PowerBuilder Revert file changes from within PowerBuilder Provides the option of automatic file locking on check out and unlocking on check in View file differences, file status and file history from within PowerBuilder The power of Subversion with the feel of Visual Source Safe Can use an external difference tool to to view file differences (6 Megabytes) Using PowerBuilder .Net with Subversion Agent SVN will work with the PowerBuilder .Net IDE. For that IDE the configuration is very similar to the Microsoft Visual Studio configuration as described in the Agent SVN help file. Using PowerBuilder Classic with Subversion Agent SVN will work with the PowerBuilder Classic IDE. Below are the steps needed to get Agent SVN working with PowerBuilder Classic and Subversion. Step: 1 Configure Agent SVN Use the Agent SVN Configuration utility to do the once off configuration of the plug-in. For this initial testing, define a local Subversion repository that uses the file protocol as shown below: NOTE: It is highly recommended you start with this minimal configuration at first, since it is the easiest to work with. Once it has been confirmed that all is working, it is very easy to re-point Agent SVN to another repository type and location. IMPORTANT: Make sure the Mark files as read only when not checked out option is unticked since this is the method prefered by PowerBuilder. It is possible to run with the Mark files as read only when not checked out option enabled but this will result in the following PowerBuilder warning message each time PowerBuilder tries to get the latest copy of the files in the source control. For more details on how to use this configuration utility bring up the electronic User Manual using the Help button. Step: 2 Create a Test Workspace To see how Agent SVN works we need something to play with so the next step is to create a simple test project. From within the PowerBuilder IDE create a new MyWorkspace test workspace and application as shown below: Step: 3 Setup the Source Control for this Workspace From within the PowerBuilder IDE use the Properties menu to bring up the MyWorkspace, Properties dialog as shown below: Setup the Agent SVN as the Source Control System for this workspace by filling in the required details as shown below: IMPORTANT: For simplicity the User ID entered should match your Windows User ID but Agent SVN will work fine if this is not the case. Make sure the Project entered matches the workspace name used in Step 3. NOTE: If you want to bind the workspace to an existing project just leave the Project field blank but continue with the next step. Make sure the Local Root Directory entered matches folder location of the workspace that was created in Step 3. Use the button indicated to import the project into SVN Repository as shown below: If the project name is left blank this button will bring up the project binding dialog instead. Step: 4 Using the Source Control Inside PowerBuilder At this stage the workspace has been imported into the repository and the workspace has also been bound to the repository. To access the source control from inside PowerBuilder use the popup menu as shown below: To check the bindings use the Show History menu to check on the source control history for the workspace as shown below: With the workspace now fully configured, you can now use the check-out, check-in, file compare commands (or any of the other source control commands) to manage your workspace files. For more information, this link describes how to get the best out of source control from inside the PowerBuilder IDE.