Book a demo

Pitney Bowes Tier 3: VB6 to C# .NET Core on AWS

How TSRI and Accenture modernized more than 443,000 lines of VB6 and 450,000 lines of XML metadata to C# .NET Core, with 100% functional equivalence, ahead of schedule and within budget.

100% functional equivalence
Ahead of schedule
Within budget
CLIENTPitney Bowes
SOFTWARETier 3 / Comet Server
LANGUAGE PAIRINGVB6 → C# .NET Core
TIME TO COMPLETION5 months

Executive summary

Over 440K lines of VB6 modernized to C# .NET Core on AWS

TSRI adapted its modernization capabilities to Pitney Bowes’ unique Visual Basic 6 code constructs, automatically modernizing more than 443,000 lines of VB6 and more than 450,000 lines of XML metadata to C# .NET Core, within budget and earlier than scheduled.

Unusually, TSRI’s partner Accenture manually rewrote the user interfaces for a modern, user-friendly experience while TSRI completed the automated transformation of the application code and database with Janus Studio®. The application achieved total functional equivalence, with a greatly improved front end.

01 · Background

A 100-year innovator, moving to the cloud

Pitney Bowes has been an American innovator in mail metering and payment systems for more than 100 years. When it became clear that digital operations were moving to the cloud, it turned to Accenture and TSRI to modernize its VB6 code to C# .NET Core. The team had already worked together to modernize another Pitney Bowes application, the Postage Payment system, from COBOL to C# .NET Core.

02 · Process

From blueprints to refactoring

Through a unique, iterative process using Janus Studio®, TSRI transformed Pitney Bowes’ VB6 to C# .NET Core with 100% functional equivalence.

How the project ran

  1. 01 · PHASE 1

    Application Blueprint®

    Code, interfaces and databases documented

  2. 02 · PHASE 2

    Architecture workshop

    Target C# .NET Core architecture defined

  3. 03 · PHASE 3

    Transformation Blueprint®

    Side-by-side view of old and new

  4. 04 · PHASE 4

    Transformation

    VB6 to C# .NET Core, 100% equivalent

  5. 05 · PHASE 5

    Refactoring

    Readability, security, performance

Application documentation

In the first phase, TSRI delivered an Application Blueprint® of the current system and a preliminary Transformation Blueprint® of the target, covering code, user interfaces and databases.

Source code & design metricsNavigation indicesControl-flow diagramsStructure chartsData element tablesState machine modelsState transition tablesCause-effect graphsHyperlinked web docs
01

Architecture design workshop

TSRI worked with Pitney Bowes and Accenture architects, subject matter experts and analysts to define the final C# .NET Core architecture, code standards and system requirements, and to fine-tune Janus Studio® for the best possible result.

02

Iterative refactoring

TSRI’s refactoring technology automatically re-engineered the application in iterations, improving readability, security and performance, and producing automated rules that can be reused.

03 · Challenges

VB6 behaviors, translated with confidence

Runtime polymorphism

VB6 can override the behavior of a base type at runtime rather than at compile time, implicitly converting to the type it thinks you want. Useful in VB6, but a pain point when moving to a language without it, like C# .NET Core.

Implicit default fields

A VB6 structure can have a default field, so referring to an employee record might return only “Name.” Combined with implicit type conversion, this invites confusion in translation. TSRI built a type-behavior model so the code could be translated confidently without introducing errors.

Country-specific DLLs

Pitney Bowes operates in many countries, each with its own same-named DLL files, distinguished only by GUIDs and version numbers. TSRI automatically serialized the DLL information and linked each to a VB6 project file, so users see the right information in the right language, a capability now reusable for other VB6 clients.

Testing without a GUI

With Accenture redesigning the GUI, TSRI built stub test controllers that mimic front-end functions, so the business logic could be compiled and tested before the new front end and the transformed back end were merged.

TSRI created a type-behavior model, which allowed the code to be translated confidently without introducing errors.

Runtime polymorphismImplicit default fieldsImplicit type conversionLegacy exception handling

04 · AWS

From the Comet server to a multi-tier architecture on AWS

Beyond transforming the code and metadata, Accenture and TSRI migrated the Tier 3 application off the Comet server to a multi-tier, distributed, cloud-native architecture on AWS, using a more modern Microsoft SQL Server database.

TARGET ARCHITECTURE · AWSSIMPLIFIED
USERS & INTERFACE
End usersUser interfaceTSRI UI/Client Framework Library
LOAD BALANCING
Elastic Load Balancing (ALB)
API TIER · EC2
TSRI API servers.NET Core on Red HatTSRI Data Access Objects frameworkExternal library
DATA
Microsoft SQL Server on EC2Encrypted volumeSecurity group
INTEGRATION & OPS
Pitney Bowes data centerAmazon CloudWatch
Simplified from the original AWS target architecture diagram; connections are not shown.
443K+lines

VB6 to C# .NET Core

Plus 450,000+ lines of XML metadata.

100%equivalent

Functional equivalence

Delivered while the UI was redesigned in parallel.

Ready to run it themselves

TSRI provided ongoing training so Pitney Bowes’ technical resources could continue code maintenance and application support, another example of the seamless partnership between Pitney Bowes, Accenture and TSRI.

Get modern fast.
Stay modern forever.

See Juno in action!