Convert PowerBuilder to C#

Convert PowerBuilder to C#

Delivering you a high-quality result in due time

Get started. Request a quote

Many companies have used our tools and provided excellent feedback on their performance

  • Capterra logo

    4.8

  • Clutch logo

    4.8


6 undeniable facts to choose conversion with Ispirer

  • Fact 1/6

    Same functionality, new application

    Migration does not require labor-intensive development of new functionality from scratch. Your application will be converted to a new technology while maintaining the original functionality

    Same functionality, new application -- card image
  • Fact 2/6

    Architecture preserved or modified

    Automated conversion implies preserving the initial architecture which is easier to maintain. The app architecture, can also be transformed, for example, from desktop to the web to improve accessibility and scalability

    Architecture preserved or modified -- card image
  • Fact 3/6

    The speed of conversion

    Migrating an application is much faster than creating a new one from scratch. Automated migration with Ispirer Toolkit minimizes manual effort and may speed up the delivery by 2-3 times

    The speed of conversion -- card image
  • Fact 4/6

    Legacy System Transformation

    Migrating PowerBuilder to modern architectures or platforms can upgrade your application, making it easier to maintain, update, and extend in the long term run

    Legacy System Transformation -- card image
  • Fact 5/6

    Performance and Scalability

    Through conversion, you can optimize the application's architecture and infrastructure, improving scalability and performance without the need to rebuild everything

    Performance and Scalability -- card image
  • Fact 6/6

    No need for documentation

    To perform the conversion, we go by your source code. There is no need to have detailed documentation in place to start the conversion as is the case with development

    No need for documentation -- card image

Сonversion opportunities with Ispirer

Ispirer Ecosystem automates your migration routine to enable quick and smart transformation of any application. Double the migration speed with our comprehensive solutions.

  • With CodeWays only

    • Free Metrics tool to analyze the migration complexity
    • Assistance in CodeWays configuration
    • Automated migration of the entire application including project files, business logic, GUI and database API
    • Prompt customization of the tool to maximize automation rate
    • Expert support
    With codeways -- card image
  • With CodeWays as a part of migration service

    • Tailored migration roadmap from assessment through migration and testing to cutover
    • Automated migration of the entire application, including project files, business logic, GUI and database API
    • Team of experts skilled in application conversion
    • Assistance in deployment, integration, performance optimization, and new feature development
    With Ispirer Codeways -- card image

Unleash the reinforced application
Save your time

Book a demo

Do it for 5 minutes

CodeWays for automated app conversion

CodeWays is a tool for automated application conversion that translates code from one programming language to another automatically, while preserving the initial functionality of an app. Using an intelligent proprietary algorithm, the tool analyzes the syntax, semantics, mapping data types, control structures, function calls, and code structures that do not have equivalents in a target technology.

Based on the analysis, CodeWays applies all the relevant conversion rules from its knowledge base core and translates PowerBuilder source code to C#.

It takes 5 min to start your application conversion journey!

App source code & App source code with embedded SQL*

  • Informix4GL
  • Delphi
  • Cobol
  • VisualBasic
  • Progress4GL
  • PowerBuilder
  • C/C++

Any files with SQL code

  • Informix
  • Teradata
  • SQLServer
  • Oracle
  • IBM DB2
  • SAP Sybase
  • PostgreeSQL
  • MySQL
  • Greenplum
  • MariaDB
  • Firebird
How Codeways work
  • App target code

    App target code
  • App target code with converted ESQL

    App target code with converted ESQL
  • Files with SQL code for the target DB

    Files with SQL code for the target DB

*Embedded SQL are SQL statements written inline with the program source code, of the host language.

Convert Smarter. Evolve Faster

Over 400+ ways to migrate

Give it a try now. Book a demo

Dive into the tool’s features

  • Delphi
  • Cobol
  • OracleForms
  • Progress 4GL
  • PowerBuilder
  • C\C++
  • IBM
  • RPG
  • Informix 4GL
  • Delphi
  • Cobol
  • OracleForms
  • Progress 4GL
  • PowerBuilder
  • C\C++
  • IBM
  • RPG
  • Informix 4GL
  • MSSQL
  • Oracle
  • OracleForms
  • Progress 4GL
  • C\C++
  • Delphi
  • Cobol
  • Informix 4GL
  • MSSQL
  • Oracle
  • OracleForms
  • Progress 4GL
  • C\C++
  • Delphi
  • Cobol
  • Informix 4GL

Migration demo

Check out how Ispirer Toolkit automatically converts {PowerBuilder} application

PowerBuilder to C# conversion service overview

Assessment

  • Collecting info about an application
  • Analyzing the application and its components
  • Making migration plan
Start

More than 2K users use this way to
successfully convert their application code

Automated APP conversion

  • Entire APP conversion
  • APP changes (API, ESQL)
  • Tool configuration and customization for specific APP

Manual APP conversion

  • Manual code review and debugging
  • Replacing custom controls, libraries, methods, etc. with analogues
  • Developing remaining solutions using target technology

Functional testing

  • APP analysis and test documentation creation
  • Testing the application against test documentation
  • Fixing issues

Acceptance testing

  • Testing the APP against business requirements
  • Fixing issues

Cutover

  • Switching APP
  • System startup assisstance
  • Collecting info about an APP
  • Analyzing the APP and its components
  • Making migration plan
  • Entire APP conversion
  • APP changes (API, ESQL)
  • Manual code review and debugging
  • Replacing custom controls, libraries, methods, etc. with analogues
  • Developing remaining solutions using target technology
  • APP analysis and test documentation creation
  • Testing the application against test documentation
  • Fixing issues
  • Testing the APP against business requirements
  • Fixing issues
  • Switching APP
  • System startup assisstance

Conversion Samples of PowerBuilder to React and C# WPF

Ispirer Toolkit analyzes all object dependencies during the conversion process and provides not only line-by-line conversion, but resolves type conversions as well. The software understands and transforms the necessary inheritance dependencies. It parses the entire source code, builds an internal tree with all the information about the objects, and uses it in the migration process.

The code samples below provide you with more details.

  • Variables declarations conversion:

    PowerBuilder

    1.  
    2. long var1
    3. long var2[]
    4. string var3
    5. datetime var4
    6. boolean var5
    7. decimal var6
    8. integer var7
    9. any var8
    10.  

    → C# WPF

    1.  
    2. int? var1 = 0;
    3. UnboundedArray < int? > var2 = new UnboundedArray < int? >();
    4. string var3 = string.Empty;
    5. DateTime? var4 = new DateTime(1900, 1, 1);
    6. bool? var5 = false;
    7. decimal? var6 = null;
    8. int? var7 = 0;
    9. object var8 = new object();
    10.  
  • Function conversion:

    PowerBuilder

    1.  
    2. public function string sample_function();
    3. return "end"
    4. //do logic
    5. end function
    6.  

    → C# WPF

    1.  
    2. public string sample_function()
    3. {
    4. return "end";
    5. //do logic
    6. }
    7.  
  • Subroutine conversion:

    PowerBuilder

    1.  
    2. protected subroutine sample_sub (string v_app);
    3. v_app = ""
    4. //do logic
    5. end subroutine
    6.  

    → C# WPF

    1.  
    2. public void sample_sub(string v_app)
    3. {
    4. v_app = "";
    5. //do logic
    6. }
    7.  
  • If statement conversion:

    PowerBuilder

    1.  
    2. integer i
    3.  
    4. if true then i = 1 else i = 2
    5.  
    6. if true then
    7. i = 3
    8. end if
    9.  

    → C# WPF

    1.  
    2. int? i = 0;
    3.  
    4. if (true)
    5. {
    6. i = 1;
    7. }
    8. else
    9. {
    10. i = 2;
    11. }
    12.  
    13. if (true)
    14. {
    15. i = 3;
    16. }
    17.  
  • For statement conversion:

    PowerBuilder

    1.  
    2. For lv_count = 1 to 10
    3. lb_units[lv_count].Visible = TRUE
    4. Next
    5.  

    → C# WPF

    1.  
    2. for (lv_count = 1; lv_count <= 10; lv_count ++)
    3. {
    4. lb_units[lv_count - 1].Visibility = Visibility.Visible;
    5. }
    6.  
  • While statement conversion:

    PowerBuilder

    1.  
    2. IDX = 0
    3. do while true
    4. if IDX = 10 then exit
    5. IDX = IDX + 1
    6. loop
    7.  

    → C# WPF

    1.  
    2. idx = 0;
    3.  
    4. while (true)
    5. {
    6. if (idx == 10)
    7. {
    8. break;
    9. }
    10.  
    11. idx = idx + 1;
    12. }
    13.  
  • Try catch statement conversion:

    PowerBuilder

    1.  
    2. try
    3. IDX = 1 / 0
    4. catch (Exception ex )
    5. IDX = 100
    6. FINALLY
    7. IDX = IDX * 2
    8. end try
    9.  

    → C# WPF

    1.  
    2. try
    3. {
    4. idx = 1 / 0;
    5. }
    6. catch (Exception ex)
    7. {
    8. idx = 100;
    9. }
    10. finally
    11. {
    12. idx = idx * 2;
    13. }
    14.  
  • Try choose statement conversion:

    PowerBuilder

    1.  
    2. integer some_id
    3. boolean cond
    4.  
    5. CHOOSE CASE some_id
    6. Case IS < 0
    7. cond = False
    8. CASE 0 TO 2
    9. cond = True
    10. some_id = 200
    11. Case IS > 0
    12. cond = True
    13. CASE ELSE
    14. cond = False
    15. some_id = 0
    16. END CHOOSE
    17.  

    → C# WPF

    1.  
    2. int? some_id = 0;
    3. bool? cond = false;
    4.  
    5. if (some_id < 0)
    6. {
    7. cond = false;
    8. }
    9. else if (some_id >= 0 && some_id <= 2)
    10. {
    11. cond = true;
    12. some_id = 200;
    13. }
    14. else if (some_id > 0)
    15. {
    16. cond = true;
    17. }
    18. else
    19. {
    20. cond = false;
    21. some_id = 0;
    22. }
    23.  
  • Inline query conversion:

    PowerBuilder

    1.  
    2. global type s_2 from structure
    3. long field_1
    4. end type
    5. s_2 param1[]
    6.  
    7. INSERT INTO TAB1
    8. (
    9. COL1 , COL2
    10. )
    11. VALUES
    12. (
    13. :param1[1].field_1,
    14. :param1[2].field_1
    15. );
    16.  

    → C# WPF

    1.  
    2. public class s_2
    3. {
    4. public int? field_1 = 0;
    5. }
    6.  
    7. UnboundedArray< s_2 > param1 = new UnboundedArray< s_2 >();
    8. var dbCmd_ = new SACommand();
    9. dbCmd_.CommandText = "INSERT INTO TAB1 " +
    10. " ( " +
    11. " COL1 , COL2 " +
    12. " ) " +
    13. " VALUES " +
    14. " ( " +
    15. " :field_1, " +
    16. " :field_1 " +
    17. " )";
    18. dbCmd_.Parameters.AddWithValue("field_1", param1[0].field_1 ?? (object) DBNull.Value);
    19. dbCmd_.Parameters.AddWithValue("field_1", param1[1].field_1 ?? (object) DBNull.Value);
    20. dbCmd_.CommandType = CommandType.Text;
    21. AppGlobalVariables.sqlca.ExecuteNonQuery(dbCmd_);
    22.  
  • CURSOR conversion:

    PowerBuilder

    1.  
    2. String v_uname[]
    3. Long v_unum[]
    4. Int v_count = 1
    5.  
    6. DECLARE c_unit CURSOR FOR
    7. SELECT U_NAME, U_NUM
    8. FROM UNT
    9. WHERE A_NUM = 10;
    10.  
    11. OPEN c_unit;
    12. FETCH c_unit INTO :v_uname[v_count],:v_unum[v_count];
    13. v_count ++
    14. Do While SQLCA.SQLCode = 0
    15. FETCH c_unit INTO :v_uname[v_count],:v_unum[v_count];
    16. v_count ++
    17. Loop
    18. CLOSE c_unit;
    19.  

    → C# WPF

    1.  
    2. UnboundedArray< string > v_uname = new UnboundedArray< string >();
    3. UnboundedArray < int? > v_unum = new UnboundedArray < int? >();
    4. int? v_count = 1;
    5. var dbCmd_c_unit = new SACommand();
    6. dbCmd_c_unit.CommandText = "SELECT U_NAME, U_NUM " +
    7. " FROM UNT " +
    8. " WHERE A_NUM = 10";
    9. dbCmd_c_unit.CommandType = CommandType.Text;
    10. var c_unit = sqlca.ExecuteReader(dbCmd_c_unit);
    11.  
    12. if (c_unit.Read())
    13. {
    14. v_uname[v_count] = c_unit?.GetString(0);
    15. v_unum[v_count] = c_unit?.GetInt32(1);
    16. }
    17. else
    18. {
    19. sqlca.SqlCode = 100;
    20. }
    21.  
    22. v_count ++;
    23.  
    24. while (sqlca.SqlCode == 0)
    25. {
    26. if (c_unit.Read())
    27. {
    28. v_uname[v_count] = c_unit?.GetString(0);
    29. v_unum[v_count] = c_unit?.GetInt32(1);
    30. }
    31. else
    32. {
    33. sqlca.SqlCode = 100;
    34. }
    35.  
    36. v_count ++;
    37. }
    38.  
    39. c_unit.Close();
    40. c_unit.Dispose();
    41.  

Get a free sample code of our PowerBuilder to C# WPF code conversion

Ispirer Toolkit automatically converts not only a single piece of code, but an entire application. Complex code will require customization of the toolkit

  • Explore how Ispirer Toolkit migrates the source code to the target technology without downloading it.
  • Analyze and compare the source sample with your code to understand which components of your application can be automatically converted using Ispirer Toolkit.
  • Test an application containing nearly 1,500 lines of code.
  • Our experts can add new conversion rules within 3-5 business days.
Enter your name.

Enter a valid e-mail address.

Select your country.

Invalid input.

PowerBuilder to C# WPF conversion overview

PowerBuilder programs consist of Workspaces (starting from PB 8.0 and higher, these are .pbw files). Conceptually, they are similar to Solution. These are text files consisting of paths to the Target files (.pbt files) that correspond to the concept of Project. The Target files are in text format, and each contains paths to the PowerBuilder libraries (.pbl files that store source code files in binary format). Typically a library with the same name as the Target file has a .sra entry point file.

To convert a PowerBuilder application, you need to extract all source files from the appropriate Workspace libraries (or Target, if PB version is less than 8). You can download Ispirer PowerBuilder Metrics to get a statistical report on PB sources, as well as extract source files from PowerBuilder libraries using Workspace, or a set of Target files, or a set of particular PB libraries (.pbl files) that need to be converted.

Once the source code is extracted, for each PowerBuilder library file, a corresponding folder named library will be created with all the source code extracted. The folders will contain source files with the following file extensions:

  • .SRD - DataWindow source files
  • .SRW - Window source files
  • .SRM - Menu source files
  • .SRS - Structure source files
  • .SRP - Data pipeline source files
  • .SRF - Function source files
  • .SRQ - Query source files
  • .SRA - Application source files
  • .SRU - Custom user object source files

Now you can use Ispirer CodeWays to convert it to your chosen target technology. Basic source type conversion by extension:

  • .SRD - converted to 3 files in a folder named datawindow_object_name_srd. The files are named datawindow_object_name_srdView.xaml and datawindow_object_name_srdView.xaml.cs – the UI and code of the DataWindow object and file datawindow_object_name_srdViewModel.cs with view model of the DataWindow object.
  • .SRW - converted to 3 files in a folder named window_object_name_srw. The files are named window_object_name_srwView.xaml and window_object_name_srwView.xaml.cs – the UI and code of the Window object and file window_object_name_srwViewModel.cs with view model of the Window object.
  • .SRM - converted to 3 files in a folder named menu_object_name_srm. The files are named menu_object_name_srmView.xaml and menu_object_name_srmView.xaml.cs – the UI and code of the Menu object and file menu_object_name_srmViewModel.cs with view model of the Menu object.
  • .SRS - converted to 1 file named structure_object_name_srs.cs. The file contains a class with variable declarations from the PowerBuilder structure.
  • .SRP - not used for conversion.
  • .SRF - converted to 1 file named function_object_name_srf.cs. The file has a public static partial class AppGlobalFunctions with a converted function.
  • .SRQ - not used for conversion.
  • .SRA - converted to 1 file named application_object_name_sra.cs. The contents of this file are used to copy into the project's entry point file in the same way as in the conversion sample.
  • .SRU - converted to 1 file named user_object_name_sru.cs for nonvisualobject and to 3 files in folder named user_object_name_sru. The files are named user_object_name_sruView.xaml and user_object_name_sruView.xaml.cs – the UI and code of the User object and file user_object_name_sruViewModel.cs with view model of the User object.

After the conversion, you need to create a WPF application desktop project in Visual Studio and add the converted files from the results folder to it. There is the Ispirer framework for converting PowerBuilder to C# WPF (IspirerFramework*) in the results folder. It contains 4 or more projects that should be added to the solution and used in the main project with the conversion results as references. The events are converted to the corresponding events of the target technology.

Note: this is a special framework provided by Ispirer. It extends the target technology to enable specific source code features.

They succeeded using Ispirer Toolkit

Transportation Firm Expands Software with Ispirer Solution

Delphi -> C# WPF

Target: C#

Transportation and defense corporation case card

Project Scope

600 000 LOC

Project Duration

11 Months

Industry

Transportation and defense corporation

Customization allowed to speed up migration 3 times

Delphi -> C# WPF

Target: C#

Transportation and defense corporation case card

Project Scope

2 000 000 LOC

Project Duration

4 Months

Industry

Financial Services Company

Trust us with your conversion project

  • Seasoned team

    Ensuring high security and performance standards is what we do best, thanks to our impressive expertise in building reliable and scalable solutions.

  • Technology expertise with 25+ years of experience

    Our team has gained a wide pool of expertise in various programming languages, from the rarest to the most popular ones.

  • We comply with ISO 27001 security

    We comply with ISO 27001 security management requirements with comprehensive policies and processes, advanced security technology, and skilled professionals.

  • Proprietary tools

    We employ Ispirer proprietary tools, underscoring our dedication to delivering the utmost reliability and performance solutions.

    The toolkit is compiled daily and continually integrates dozens of new conversion rules, enhancing the automation capabilities.

They chose Ispirer to revamp their application

Epicor, University of Maryland, Splice Machine and more have adopted CodeWays to boost their innovation life-cycle accelerate and manage their end-to-end innovation lifecycle

Epicor logo
University of Maryland logo
High Availability Systems Co. Ltd., Japan
Splice Machine, United States logo
NedGraphics, The Netherlands logo
Kellenberger, Switzerland logo

Progress ABL to C#

Migration project

50%

Migration time reduction

2 MLN

Lines of code

75%

Аutomation achieved

Enterprise software

"We have found the Ispirer team to be knowledgeable and responsive, and we have found the tooling to be flexible enough to be easily adapted to our coding conventions."

COBOL to Java

Migration project

6-month

Migration time reduction

100K+

Lines of code

200+

COBOL programs

Education

"Ispirer Toolkit enabled us to efficiently convert 200 COBOL programs with over 100,000 lines of code to Java. The tool produced high-quality, maintainable code, allowing our team to focus on infrastructure rather than conversion. Ispirer’s support was exceptional, often resolving issues within one business day."

Informix 4GL to Oracle PL/SQL

Migration project

95%

Аutomation achieved

200K+

Lines of code

75%

Migration time reduction

IT Services

"Ispirer provided a full-cycle migration service, converting over 200,000 lines of Informix 4GL to Oracle PL/SQL with 95% automation. Their expertise, customizations, and commitment to quality ensured a seamless transition. We highly recommend Ispirer for complex migration projects."

Oracle PL/SQL to Java

Migration project

80%

Аutomation achieved

400K+

Lines of code

50%

Migration time reduction

Database technology

"At the onset of the engagement, the Ispirer MnMTK was expanded to meet the specific requirements of our migration prior to being delivered for our use. Once this phase of the project was complete, we were provided with the expanded toolkit."

C/C++, AutoLISP to C#.NET

Migration project

70%

Аutomation achieved

250K+

Lines of code

50%

Migration cost reduction

Civil engineering and infrastructure

"We were impressed with the knowledge, professionalism, hard work, and enthusiasm of the Ispirer team. Through this Migration Project, we have a solid base for further expanding our application."

Borland Delphi 7.0 modernization

Migration project

75%

Аutomation achieved

20K

Lines of code

50%

Migration time reduction

Automation Equipment

"We had an old Borland Delphi 7.0 project, which was brought back to life. Ispirer had offered us a timely and financially attractive conversion of the application. The work was performed promptly."


Are you still here? And wow, that's quite a lot you had to scroll through! 😄

Сonsult with our expert to better organize for you migration flow

Take control of your application
сonversion now

Book a demo

Do it for 5 minutes

THIS SITE USES COOKIES: By continuing to browse this site, you give your consent for cookies to be used. For more details, please read our Privacy Policy and Cookies Policy.
I Got it