dotSoftwaredotDevelopmentdotCustomersdotAbout us
PushOk logoblank
fast linksFast Links
news&eventsnews and events

2012-12-21 
Major update of SVNCOM version 1.7.2 are finaly released

2012-12-21 
Major update of SVN SCC plug-in - versions 1.7.2 are finaly released

Lightweight embedded Node.js database with MongoDB API.

Pull from SCC

Search go
PushOk Logo blank
leftPull from SCCright

Before this operation make sure that SVN already contains previously added project. To get the project from the source control system, open your IDE without opening other projects in it. After this:
[VS .NET]
First of all select a user name for accessing to SVN: open the configuration window Tools\Options\Source Control\Scc provider and specify the name in the Login ID field. Then select File\Source Control\Open project from source control.
[VS]
First of all select a user name for accessing to SVN: open the configuration window Tools\Options\Source Control and specify the name in the login field. Then select File\Open Workspace. A standard workspace with a new button 'Source Control' in it will open. Press this button.
[VB]
Select Tool\Pushok SVN Proxy\Create project from Pushok SVN Proxy.
[PowerBuilder]
PowerBuilder is a specific system for this operation. See an article explaining Source Control and PowerBuilder. In contrast to other systems, in PB there is nothing similar to 'Open from source control' command. To our opinion that is so due to the fact that PB libraries (.pbl) are not connected to source control. But instead all objects exported from PB libraries are connected to source control. Probably, reassembling of .pbl file from its components is impossible, and hence it is not possible to recreate the project only from source control. Thus, to deploy the project from another PC you should copy the entire project from that PC (for example, from which it was added). You can copy either the entire folder or pbw/pbt/pbl files only. It is IMPORTANT that you should NOT copy 'SVN sandboxes' (.svn subfolders that exist in each original folder). You can delete them after copying.
As a result you will have a folder containing pbw/pbt/pfl files and not containing SVN subfolders. Now you have to bind workspace to SVN. Open copied workspace in PowerBuilder. Right-click on the workspace entry, choose 'Properties'. Open 'SourceControl' page. Choose 'Pushok SVN proxy' as the source control system. Please make sure that options are configured as described at IDE tips page. Then enter 'Local Root Directory' (you can use '..' button to choose it in the folder browser window). Normally, local root directory is the same folder where your workspace/targets/libraries are located. After that specify the user name in the User ID field. And at last press '..' button next to the 'Project' field.

After these operations you will see a dialog box already familiar to you.

To open the project you have to specify SVNURL again. Then select module in which the project file is located. Note that if the project file is located in a subfolder of the module root, you should select this subfolder, but not the module root itself. You can use the repository view window by pressing '...' next to the module input field instead of entering the module name manually. Mind that you do not have to create the module, since you open a project already added to SVN. However, press the button "CHECK" to make sure that the data are entered correctly.

Note that this time the field LOCAL PATH can be edited. This means that you have to specify the location where you want the source files from SVN to be placed. Two things are important:

  • The selected local folder should be empty, or it should not exist.
  • The module name is directly connected with the path. In other words, for the module DummyProject the local path must be 'C:\DummyProject' or 'C:\Work\DummyProject', but not 'C:\' or 'C:\Work'. You can replace some part of the path corresponding to the root module if necessary. For example, the local path for the module can be 'C:\MyDummyProject'. But to avoid mess, you should better avoid module names changing and their displaying on the local disk.

So, after selecting necessary data and pressing OK, IDE will get the list of files in this module, find project files there, and upload them to your local disk. Depending on the system the results can be the following:
[VS .NET]
If this module contains only one project file, the project will be get at once. Otherwise the system will ask you to specify the project in this module that you want to get.
[VS]
The system will get all project files at once and will return to the project workspace, having chosen the catalog containing the downloaded project files. You have to select a project file for opening, even if there is only one file in the catalog.
[VB]
If this module contains only one project file, the project will be get at once. Otherwise the system will ask you to specify the project in this module that you want to get.
[PowerBuilder]
Press 'OK' to close 'Bind to SVN' dialog. Then press 'Connect' button and 'Ok' to close workspace properties. After that PB will notify you that all files have "need update" status, that is, they are controlled but need updating. Right-click on them and select 'Get latest version'. After this you can work with the project.

After successful operation performance you can continue your work. Note that window 'Bind to SVN' can appear several times, if IDE does not know either 'LOCAL PATH' or 'Module'. Each time you have to specify these two parameters.

Note that to open this project next time you will simply have to open it as usual. That is, you do not have to repeat these operations again.




You are 8833638 visitor since 20 Jan 2003.
462 visitors today and 4 online right now.
blank left to top right blank

© Copyright by PushOk Software, 2003-2021, webmaster@pushok.com