Skip to Content
author's profile photo Former Member
Former Member

how secure the pbls on network for developers

my question is how to secure the application on network when more than 2 developers are working on same application.

regards,

Sarfaraz

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

5 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jan 03, 2014 at 02:25 PM

    What you should be doing is each developer have a copy of the PBL files on their local C drive and use a Source Control system to keep everyone in sync.

    In PB 8 and higher there is a very simple source control system called "PB Native" that comes with it. It doesn't maintain object history but it will prevent multiple developers from working on the same object. The developer does a "Check Out" before they can start changing an object. It will only allow you to change objects checked out to you. Then when the change is ready to go into production, you do a "Check In". After that, all other developers do a "Get Latest Version" which will pull in the updated version of the checked in objects.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 03, 2014 at 03:22 PM

    Hi Muhammed,

    Just to add to what everyone else has said you might want to check out the PowerBuilder documentation on source control at SyBooks Online. It's Chapter 3 of the User's Guide.

    Ted

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jan 03, 2014 at 01:20 PM

    Hi,

    What do you mean by "securing"? Can you detail us what you want to achieve?

    If you want that many developpers work on same app, then using a Source Control is your solution.

    HTH,

    Jacob

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jan 03, 2014 at 01:31 PM

    The way you've describes it, I would recommend not doing it. Besides performance problems, running the app from the IDE against PBLs locks the PBLs, so if one developer is running and the other tries to save... Hopefully you get the picture, and can start projecting other types of sharing conflicts.

    I'd recommend looking into source control using PB Native. It lets you store your "repository" up in the network, yet allows copies down on the local developers workstations. It also allows you to pull the other developer's checked in changes at a time that makes more sense to you (say, instead of getting hit with a change to an ancestor while you're in the middle of testing).

    Good luck,

    Terry

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 03, 2014 at 02:05 PM

    Hi Muhammad;

    I think what you need to do is utilize PB's native "Source Code Management" (SCM) feature. This allows two developers to share code from a centralized network PBL but check-out the code to local PBL's for editing and unit testing. Once the changes are completed locally, any developer can then check-in the changed code to the centralized (networked) PBL where other developers can perform a "Get Latest" operation to pull down the updated & shared code into their local PBL's.

    You can also take this SCM feature one step further and incorporate a commercial (or open source😉) SCM package into the picture. This will allow you to capitalize on more advanced features like code history, code merging, branching, etc.

    HTH

    Regards ... Chris

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      At most companies users have a personal network share. For example, at my company the I: drive is the personal network share and the K: drive is the primary shared network share. With this setup, I would have developers put the PB workspace in I:\PBSource\<workspacename>. Then I would use a source control system to keep them in sync. Having the workspace on the network avoids problems if their computer dies or in the case of a laptop - stolen.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.