794
社区成员
发帖
与我相关
我的任务
分享（急）pb里自带的版本控制（source control）怎么用啊？？？
我在自己的机器上建立了一个pb native的source，而且把pbl加入了source里面，在本机上可以做check out/in，但是在别的机器上怎么设置，可以共用我的pbl进行check out/in操作啊？？？
我用的是pb9.0
我用的是pb9.0
...全文
请发表友善的回复…
发表回复
WorldMobile 2004-11-29
- 打赏
- 举报
10 steps to setup PowerBuilder and 3rd party source control tool
Steps on how to setup source control from PowerBuilder going against 3rd party source control tools.
Things to do in 3rd party source control administration tool:
1. The System Administrator creates a project if it does not already exist.
2. The System Administrator creates user ids for team members and assigns permissions
PowerBuilder 7 :
1. System Administrator will load app1.pbl (this PBL is what I would call a registered PBL. This PBL/s should reside locally on each developers machine) that is to be added to source control in PowerBuilder.
2. The administrator will then connect by Library painter > Source > Connect and create a new configuration file (cfg file) to connect to the newly created project (created earlier in the Source Control Tool)
3. On connecting to source control. The title on the Library Painter will now say "Library ?SCC" ?{Source Control Tool Name}
This will confirm that one is connected to Source Control
4. Now the administrator will select object/s in listview of the library painter , Source > Register. On successful registration one should see a cylinder on the left hand side of the object. Repeat this step for each PBL in the application.
5. Last of all the administrator will distribute all the registered PBLs to the developers in the team.
6. Developers will load the application given to them. They will then create a PBL say work.pbl, using Library > Create. This is the PBL where they will checkout/checkin objects to/from.
7. The developers will then edit the library search path such that the work.pbl is on the very top and other PBLs (app1.pbl, app2.pbl .....) after it.
8. Each developer will now connect to source control using Library painter > Source > Connect. They could either create their own cfg file or point to an existing one (if provided by administrator). They should make sure they are connecting to the same source control project and are using their userid.
9. Once successfully connected, the developer will select the object to be checked out in the library painter, right mouse click and select CheckOut from context menu or Source > Checkout. Destination PBL to checkout would be the work.pbl.
10. The developer will then update the object, save changes and check it back in by right mouse click Check In from the context menu or Source > Check In
PowerBuilder 8 :
1. The system administrator creates a new workspace file, wksp1.pbw, and connects to the new source control project. This is done by right mouse clicking on wksp1.pbw icon, selecting properties from the context menu, and selecting the Source Control tab dialog.
2. Select a source control provider from the dropdown listbox. Populate values for user id , project and local root directory. You can browse for the correct project specification by clicking on the ellipses. The local root directory property should be the directory where your workspace file is located. At this time, you should also carefully construct a meaningful sub-directory hierarchy (under the local root directory) that lets you group related objects together both on the local workstation and in the source control project. A new feature in PowerBuilder 8 is the ability to use folders (sometimes called sub-projects). One particularly useful technique is to create a sub-directory for each PBL in a target. By doing so, all of the objects belonging to that PBL will be grouped together in the source control repository.
3. Click Connect. The Output view should show
---------- Source Control
mm/dd/yyyy hr:min Source Management Initialization...
Connection to source control established
---------- Done Source Control
4. Add a target (this could be an existing PBL you want to add to source control or a new one). All targets that will be under source control must exist either in the local root directory or in a sub-directory under the local root directory.
5. Adding object to source control (registering objects) may be done either from the System Tree or the Library Painter.
System Tree ?Right mouse click the target, select "Add to Source Control ?. Select either all or a single object and click Ok. You should see a green dot on the left hand side of the object.
Library painter ?Select the object or *.pbt file in treeview or listview . Either do a right mouse click and select "Add to Source Control" from the context menu or choose Entry > Source Control > Add to Source Control from the Library Painter menu. Click Ok. You should see a green dot on the left hand side of the object.
Repeat this step for all the objects that comprise the target.
6. Copy the PBLs and PBT to a shared network drive that all the team members can access. This can easily be done with the XCOPY /S command from a DOS command. The /S option creates sub-directories and copies the necessary files.
7. Have each developer create their own workspace and copy the PBT file and PBLs from the shared network drive to their workspace directory. Team members should use the XCOPY /S command to accomplish this step. Using XCOPY /S insures that the exact same naming convention is used for all the sub-directories that appear under the local root directory. Also, each PBL will be placed in the correct sub-directory under the local root directory.
8. Have each developer use the exact same project property when setting up their source control connection from the workspace, properties tab dialog. This is required in order that relative path information, contained in the .PBT and .PBG files, is the same for each developer on the project.
9. Once connected to source control, developers may select the object they wish to checkout, right mouse click and select "Check Out?. They should now see a green check mark beside the object that has been checked out.
10. Developers then update the checked out object, save the changes and check it back into the repository. The symbol beside the object then reverts back to a green dot.
Steps on how to setup source control from PowerBuilder going against 3rd party source control tools.
Things to do in 3rd party source control administration tool:
1. The System Administrator creates a project if it does not already exist.
2. The System Administrator creates user ids for team members and assigns permissions
PowerBuilder 7 :
1. System Administrator will load app1.pbl (this PBL is what I would call a registered PBL. This PBL/s should reside locally on each developers machine) that is to be added to source control in PowerBuilder.
2. The administrator will then connect by Library painter > Source > Connect and create a new configuration file (cfg file) to connect to the newly created project (created earlier in the Source Control Tool)
3. On connecting to source control. The title on the Library Painter will now say "Library ?SCC" ?{Source Control Tool Name}
This will confirm that one is connected to Source Control
4. Now the administrator will select object/s in listview of the library painter , Source > Register. On successful registration one should see a cylinder on the left hand side of the object. Repeat this step for each PBL in the application.
5. Last of all the administrator will distribute all the registered PBLs to the developers in the team.
6. Developers will load the application given to them. They will then create a PBL say work.pbl, using Library > Create. This is the PBL where they will checkout/checkin objects to/from.
7. The developers will then edit the library search path such that the work.pbl is on the very top and other PBLs (app1.pbl, app2.pbl .....) after it.
8. Each developer will now connect to source control using Library painter > Source > Connect. They could either create their own cfg file or point to an existing one (if provided by administrator). They should make sure they are connecting to the same source control project and are using their userid.
9. Once successfully connected, the developer will select the object to be checked out in the library painter, right mouse click and select CheckOut from context menu or Source > Checkout. Destination PBL to checkout would be the work.pbl.
10. The developer will then update the object, save changes and check it back in by right mouse click Check In from the context menu or Source > Check In
PowerBuilder 8 :
1. The system administrator creates a new workspace file, wksp1.pbw, and connects to the new source control project. This is done by right mouse clicking on wksp1.pbw icon, selecting properties from the context menu, and selecting the Source Control tab dialog.
2. Select a source control provider from the dropdown listbox. Populate values for user id , project and local root directory. You can browse for the correct project specification by clicking on the ellipses. The local root directory property should be the directory where your workspace file is located. At this time, you should also carefully construct a meaningful sub-directory hierarchy (under the local root directory) that lets you group related objects together both on the local workstation and in the source control project. A new feature in PowerBuilder 8 is the ability to use folders (sometimes called sub-projects). One particularly useful technique is to create a sub-directory for each PBL in a target. By doing so, all of the objects belonging to that PBL will be grouped together in the source control repository.
3. Click Connect. The Output view should show
---------- Source Control
mm/dd/yyyy hr:min Source Management Initialization...
Connection to source control established
---------- Done Source Control
4. Add a target (this could be an existing PBL you want to add to source control or a new one). All targets that will be under source control must exist either in the local root directory or in a sub-directory under the local root directory.
5. Adding object to source control (registering objects) may be done either from the System Tree or the Library Painter.
System Tree ?Right mouse click the target, select "Add to Source Control ?. Select either all or a single object and click Ok. You should see a green dot on the left hand side of the object.
Library painter ?Select the object or *.pbt file in treeview or listview . Either do a right mouse click and select "Add to Source Control" from the context menu or choose Entry > Source Control > Add to Source Control from the Library Painter menu. Click Ok. You should see a green dot on the left hand side of the object.
Repeat this step for all the objects that comprise the target.
6. Copy the PBLs and PBT to a shared network drive that all the team members can access. This can easily be done with the XCOPY /S command from a DOS command. The /S option creates sub-directories and copies the necessary files.
7. Have each developer create their own workspace and copy the PBT file and PBLs from the shared network drive to their workspace directory. Team members should use the XCOPY /S command to accomplish this step. Using XCOPY /S insures that the exact same naming convention is used for all the sub-directories that appear under the local root directory. Also, each PBL will be placed in the correct sub-directory under the local root directory.
8. Have each developer use the exact same project property when setting up their source control connection from the workspace, properties tab dialog. This is required in order that relative path information, contained in the .PBT and .PBG files, is the same for each developer on the project.
9. Once connected to source control, developers may select the object they wish to checkout, right mouse click and select "Check Out?. They should now see a green check mark beside the object that has been checked out.
10. Developers then update the checked out object, save the changes and check it back into the repository. The symbol beside the object then reverts back to a green dot.
why_happy 2004-11-24
- 打赏
- 举报
自己搞定了，如果有人要学习，请参看
http://www3.ccw.com.cn/club/bbs/bbsView.asp?essenceID=8831
http://www3.ccw.com.cn/club/bbs/bbsView.asp?essenceID=8831
why_happy 2004-11-23
- 打赏
- 举报
兄弟姐妹们，帮帮忙啊！
hwh88888 2004-11-23
- 打赏
- 举报
没有用过，学习
why_happy 2004-11-22
- 打赏
- 举报
vss我也装了，但使用起来和pb native效果一样，不能共用同一个source
WorldMobile 2004-11-22
- 打赏
- 举报
Visual sourcesafe用起来方便，而且比较安全
Pb native用起来不太方便
Pb native用起来不太方便
WorldMobile 2004-11-22
- 打赏
- 举报
建议不要用pb native，最好用VSS即可Visual sourcesafe
