Blast from the Past

Tripped over an old Boston Computer Society (BCS) announcement for a special interest group (SIG) I used to run. “COMponent Software” – for OLE, OCX, COM, etc…
My future employer (Powersoft / Sybase) had two people come to one of my earlier SIG meetings to basically interview me without my realizing it…

BCS_Annc_Last

I was also active in the BCS Visual Basic group (and OS/2 group (oh well)…) and later in “NESoftDev” after the BCS fell apart in ’96.  Here’s an excerpt from the May-1998 meeting notice I found:

From:     JB
Subject: May 12 NESOFTDEV
Date:     Wed, 6 May 1998 21:14:19 -0400

Straight no mixing of the words talk about multiple vendors in
order to make an informed decision on the next generation of application
architectures - only at NESOFTDEV. Hope you can make it. Start thinking
about June too; we will have lots of fun.

NOTICE:     May 12       NESOFTDEV Monthly Meeting
TIME:	        7:00 -8:30 P.M.  NEW time just for this meeting
PLACE:       Cafeteria at Prospect Place **** 1st Floor ****
LOCATION: 9 Hillside Ave., Waltham exit 27a RT 128

**********************************************************************
MEETING:
7:00-8:30 P.M. Now That My Application Is Split Into Components, what do I do with it?

The one hour talk will cover "application level" concepts usable by the
typical Visual Basic, Java, or C++ programmer. Included will be:
* Application evolution from 1-tier to 2-tier to N-tier and under what circumstances
    you would want each level of separation.
* Scalability - does it affect me?
* Transactions - do I care?
* What are middleware application and transaction servers
* DCOM and CORBA - advantage and disadvantage of each
* Why UNIX machines and mainframes are not dead, in fact they're making
    more sales than ever
* Comparison of the two easily available middleware packages,
    Microsoft's Transaction Server (MTS) and
    Sybase's Jaguar Component  Transaction Server (Jaguar CTS)
* Time permitting, we will run through adding and using a Visual Basic
    component in Microsoft's Transaction Server

You will leave this evening discussion with the knowledge of  WHEN, WHY, and HOW to
use middleware with your applications.

Biography:
You may remember Reed Shilts from various Boston Computer Society
groups.  He is always on the bleeding edge of technology. Five years ago
Reed was excited about OCX's and component technology being more
important than C++.  Ten years ago he was pushing C++ being the
replacement for regular C.  Of course, he also once advocated OS/2
replacing Windows/16.... Reed is still in love with components, both COM
and Java Beans, but now running across a network of middleware
application servers. Reed is currently working in the PowerBuilder
internals group at Powersoft/Sybase and worked on the integration of
PowerBuilder with both Sybase Jaguar CTS and Microsoft Transaction Server.

Particulars: 2nd Tuesday of each month, September-June, 9 Hillside Ave,
Waltham, MA, Exit 27a, Route 128 (95), Third Ave, left after the Westin
Hotel, then go right, right, right to 1st Floor Cafeteria, 5:30 p.m.  

Sponsors: www.stingray.com, www.oi.com, www.aw.com, , www.ora.com,
www.symantec.com, www.tvobjects.com, www.bosoft.com,
www.englishwizard.com, www.powersoft.com, www.numega.com,
www.visualcomp.com, www.glbs.com, www.humanfactors.com, www.delorme.com,
www.ifmaboston.org/sodexho, www.csti.com,  www.blue-sky.com,
www.vigortech.com, www.SoftPro.com, www.ntxtras.com, www.vbxtras.com,
www.microsoft.com

(Originally published 27 February 2011)

File.New behavior with SCC in PowerBuilder.NET

Question:
What happens when the library (PBL) is not checked out, and I try “File → New” ? Or more generally, how does “File→ New” interact with Source Code Control systems…
Short Answer:
The “File → New” action may fail, depending on how “automatic checkout” is set.
The attached document (PB125_SCC_Note1.pdf) contains the three scenarios for how “Automatic Checkout” may be set along with screen shots of the (current) behavior in PowerBuilder.NET.
The test case is for Microsoft’s Team Foundation Server (TFS) but everything should be the same for other SCC providers.
(Originally published 17 February 2011)

PowerBuilder.NET – SCC with VSS and Perforce

PowerBuilder.NET (here the shipping 12.0) can easily use most (all?) Visual Studio compatible source code control (SCC) providers.  The attached document shows the steps to connect to either  my personal favorite, Perforce, or Microsoft’s Visual Source Safe (which I believe is being discontinued by Microsoft in favor of TFS).

These SCC packages are easier than Microsoft Team Foundation Server (TFS) both because they are just SIMPLER, but I also did not need any extra adapter installed. Especially Perforce, IT JUST WORKS.
So, grab this older document (PBNET120_SCC_Instructions_Public.pdf), written back in the 12.0 timeframe, and party-on!

And, since I just love pictures, here’s a pretty and informative (looks and smarts) screen capture showing some details when the user adds a new global function and a text file.  The “project” files for the target and library are automatically checked out also…

PB120_PendingCheckins

(Originally published 13 February 2011)

PowerBuilder.NET SCC with TFS

PowerBuilder.NET (here version 12.5) can easily use Microsoft’s “Team Foundation Server” (TFS) for all the expected Source Code Control (SCC) actions.  PowerBuilder.NET, like any non-Microsoft product will need an adapter layer, which is provided by Microsoft free of charge.  The “Microsoft Source Code Control Interface” (MSSCCI) provider is the adapter providing the actual connection to the Team Foundation Server.

The attached document outlines the installing and an overview of using PowerBuilder.NET (and a little TFS) for the basic SCC needs.

The end result, is that you can double-click a file (like a window object), the file (and the hidden XAML mate) will be automatically checked out, put into the pending check-ins list, and the world is sweet.  Check out this attached PDF document (PB125_SCC_Overview_TFS.pdf) for the details.

PBNET125_TFS2

 (Originally published 3-February 2011)