cancel
Showing results for 
Search instead for 
Did you mean: 
Subscribe

I am working on a prototype that I started in PB.NET  and with the aid of intellisense the learning curve was near zero. Talking with Appeon they recommend that I use PB Classic for the moment and when they get the C# versions there will be tools to port easily from Classic to C#.

Issue is I started up Classic and started looking at the porting my .NET scripts to Classic scripts and without intellisense I start to get lost quickly.

Any suggestions on how to minimize the pain here?

Thanks

TPS

0 Likes
View Entire Topic
Former Member
0 Likes

With powerbuilder classic when you do builds does it really force all painters to be closed?

Thanks

TPS

Former Member
0 Likes

Hi Tom;

Yes, almost all ... for example, you could have the DataBase Painter still open. Its just any painter that manages a PB Object Class (ie: Menu, User Object, Window, etc). Closing the Painter forces a save - which performs the incremental compile of that object at this time.

  Note: you do not need to compile each time in PB Classic like you have to do in PB.Net. PB Classic's modus operandi is compile & go on the Save of any Painter (or its closure). You just need to click the blue jogger on the PB Classic's main toolbar at anytime to force a save/close & run the application almost instantaneously.

HTH

Regards ... Chris

Former Member
0 Likes

I think most people refer to it as "The Runman". I'm sure you remember in early versions it was a hatchet as in 'execute' the program.