Re: Digest for pbscc@googlegroups.com - 2 updates in 1 topic

22 views
Skip to first unread message

Chris Tillman

unread,
Jul 11, 2015, 12:55:16 PM7/11/15
to pb...@googlegroups.com
Second the sentiments on PBSCC with SVN being the best current solution for Powerbuilder source control. I'm not aware of any git Powerbuilder glue like PBSCC provides for SVN. It might not be too hard a hack using the git-svn commands. 

As for Powerbuilder viability, SAP has committed to it publicly and there is a deal in the works with Appeon to outsource sales/support from SAP, so I don't think it's quite dead yet. There's such a strong lock-in factor; nothing does so much so quickly as Powerbuilder in client-server I think. Everybody wants to get away, but many get sticker shock when they see the Java/.NET equivalent web app price.


On Fri, Jul 10, 2015 at 8:29 PM, <pb...@googlegroups.com> wrote:
Timmy Chong <laker...@gmail.com>: Jul 09 08:42AM -0700

Hi,
 
 
Our company has been around since 1995, and the Owner and main developer
has never used any version control software.
 
 
To cut the story short, he doesn't think researching and deciding on a
version control software is a good use of our time. But its literally
impeding on our existent workflow (if you can call it that), coding is
getting overwritten, (USA developers work during day time here, and
Overseas developers work during night time in USA (daytime there).
 
 
I was looking at GIT and couple others, does anyone else have some
experience with version control software? And does it work well with
Powerbuilder? I read some limitations that the migration isn't perfect for
power builder when using GIT, but i've also read that others had no
problems.
 
 
We also try to keep most of the logic in the backend (SQL), is there any
version control software that can keep track of both?
 
 
I've looked at red-gate for SQL Script managing, because this also gets
overwritten as well.
 
 
http://www.red-gate.com
 
 
 
RedGate also manages for .NET as well. This might be our solution, if we
convert our whole System from PowerBuilder to .NET. Which i want to avoid
until absolutely necessary (EX: PowerBuilder is no longer supported)
 
 
 
Also if someone can advise, should we stick to PowerBuilder? Since SAP
bought PowerBuilder, there hasn't been too many improvements and there are
bugs here and there and I'm afraid they might discontinue it.
In which we would have to slowly Migrate to .NET or Swift (if it gets
adopted universally)
 
 
Just wanted some advice and thoughts.
 
Thank you
"Chandrasekar (Chan) Ponnusamy" <mnste...@gmail.com>: Jul 09 06:41PM -0400

Timmy Chong,
 
Let me put it in perspective here. You are looking for 2 things - 1. You
want to find the best source control for your Powerbuilder source code and
your SQL source code. 2. You want to know if its time to get out of
PowerBuilder.
 
For #1 I would say I have had better luck using PBSCC and Tortoise SVN for
maintaining PB code. I have been a PB developer for 20 years now and I can
say that so far PBSCC is the best solution I have come across for PB. As
for SQL code, we store them in Tortoise SVN. Just before releasing the code
we update the SVN copy with the latest changes.
 
For #2 I would say, if you have a choice get out of PB now. I know people
have predicted PB's death even 10 years ago, but I tell you its been a slow
death march this past decade and PB is in life support. Get out while you
can. Just my 2 cents!
 
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to pbscc+un...@googlegroups.com.



--
Chris Tillman
Developer
Reply all
Reply to author
Forward
0 new messages