Intelligent, Custom and Highly Automated Cross Platform Database and Application Migration

PowerBuilder to ASP.NET Migration

From now on Ispirer Migration and Modernization Toolkit is capable of converting PowerBuilder applications to ASP.NET!


PowerBuilder to ASP.NET Migration Overview

While migrating PowerBuilder to ASP.NET, Ispirer MnMTK allows to convert::

  • Application source files (.SRA files)
  • Window objects (.SRW files)
  • Menu (.SRM)
  • DataWindow (.SRD)

This demo illustrates the whole process of conversion from PowerBuilder to ASP.NET with the help of our migration tool.




Why Ispirer MnMTK 2015 for PowerBuilder to ASP.NET Conversion?

The main purpose of Ispirer Systems is to carry out a high-grade and top-of-the-line application migration. We personalize our migration tool Ispirer MnMTK in such a way that a customized version can fully satisfy a client's business requirements.

Our main benefits:

  • High quality and experiences technical support: our technical team has a tremendous experience in migration projects of different levels of complexity.
  • Customer-oriented approach and Fast Customization: we personalize our migration tool in such a way that a customized version can fully satisfy our client’s business needs, custom conversions and optimizations are made within 1-2 business days;
  • Pre-Sales Engagement: we demonstrate a full conversion during the evaluation before you make a decision.
  • Flexible pricing: we can offer you a wide range of options, among which you will definitely find the one which suits you;
  • Optimized Conversion: after the conversion you get an intelligent and maintainable code, without using any Ispirer's middleware.

Assessment Process

The assessment of your migration project could definitely help to weigh up efforts and the approximate cost of your migration. In order to facilitate the process, you're welcome to download our:

Otherwise don't hesitate to complete the questionnaire and to send it to us so that we could initiate the discussion of your project:

Live Presentation

Ispirer Migration Solution

PowerBuilder to ASP.NET

Request

Request a Quote

Ispirer Migration Solution

PowerBuilder to ASP.NET

Service Toolkit

Conversion Features

Ispirer MnMTK allows to:

  • Convert Application source files (.SRA files)

    SRA file is an application source file that contains basic information about the application and an entry point to it:

    forward
            global TYPE simple_demo FROM application
            END TYPE
    END forward
     
            global TYPE simple_demo FROM application
            string appname = "simple_demo"
            END TYPE
    global simple_demo simple_demo
     
    ON simple_demo.CREATE
    END ON
     
    event OPEN;
            OPEN ( simple_demo_main )
    END event
     

    SRA file is converted to Class with Transfer Method which is used to open the application:

    public partial class _simple_demo : System.Web.UI.Page
    {
            protected void Page_Load(object sender, EventArgs e)
            {
            Server.Transfer("simple_demo_main.aspx");
            }
    }
  • Convert Window objects (.SRW files) to ASPX

    SRW file is a window source file. It has the description of Form and Component items and also Events and Methods. SRW file is converted to ASPX.

    Consider an example of simple Form with one Control element:

    $PBExportHeader$simple_demo_main.srw
    forward
            global TYPE simple_demo_main FROM window
            END TYPE
            TYPE b_button FROM commandbutton WITHIN simple_demo_main
            END TYPE
    END forward
     
    global TYPE simple_demo_main FROM window
            INTEGER width = 800
            INTEGER height = 1200
            BOOLEAN titlebar = TRUE
            string title = "simple_demo"
            b_button b_button
    END TYPE
    global simple_demo_main simple_demo_main
    ON simple_demo_main.CREATE
            this.b_button =CREATE b_button
            this.Control[]={this.b_button}
    END ON
     
    ON simple_demo_main.destroy
            destroy(this.b_button)
    END ON
     
    TYPE b_button FROM commandbutton WITHIN simple_demo_main
            INTEGER x = 400
            INTEGER y = 400
            INTEGER width = 200
            INTEGER height = 120
            string text = "Show"
    END TYPE
     
    event clicked;
    END event

    Declare Control is converted to Class Designer:

    public partial class _simple_demo_main
    {
            protected System.Web.UI.HtmlControls.HtmlForm simple_demo_main;
            protected System.Web.UI.WebControls.Button b_button;
    }

    Below is the description of Form and Component converted to an ASPX file:

    <%@ Page LANGUAGE="C#" AutoEventWireup="true"
    CodeBehind="simple_demo_main.aspx.cs"
    Inherits="simple_demo._simple_demo_main"%>
     
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
     
    <html xmlns="http://www.w3.org/1999/xhtml">
    <head id="Head1" runat="server">
    <title>simple_demo</title>
    </head>
    <body>
    <form id="simple_demo_main" runat="server">
            <div>
            <table>
            <tr>
            <td><asp:Button ID="b_button" runat="server" Text="Show"
    Width="44" Height="30" onclick="b_button_Click"></asp:Button></td>
            </tr>
            </table>
            </div>
    </form>
    </body>
    </html>

    Event is converted to Class Method:

    public partial class _simple_demo_main : System.Web.UI.Page
    {
            protected void Page_Load(object sender, EventArgs e)
            {
            }
            protected void b_button_Click(object sender, EventArgs e)
            {
            }
    }

    SQLWays saves size and location property of components like in a convertible PowerBuilder application:

    Convert PB Convert to ASP
    PowerBuilder Application Window ASP.NET Pages

  • Convert Menu (.SRM) to standard User Control

    SRM file is a menu source file. It contains the description of Menu Elements and Events. Here is an example of a simple Menu with one Element for your consideration:

    $PBExportHeader$simple_menu.srm
    forward
            global TYPE simple_menu FROM menu
            END TYPE
            TYPE m_about FROM menu WITHIN simple_menu
            END TYPE
    END forward
     
    global TYPE simple_menu FROM menu
    END TYPE
    global simple_menu simple_menu
     
    ON simple_menu.CREATE
            simple_menu=this
            CALL super::CREATE
            this.m_about=CREATE m_about
            this.Item[UpperBound(this.Item)+1]=this.m_about
    END ON
     
    TYPE m_about FROM menu WITHIN simple_menu
    END TYPE
     
    ON m_about.CREATE
            CALL super::CREATE
            this.text = "&About"
    END ON
     
    event clicked;OPEN(simple_about)
    END event

    SRM File is converted to System.WEB.UI.UserControl Class.

    public partial class _simple_menu : System.Web.UI.UserControl
    {
            protected void Page_Load(object sender, EventArgs e)
            {
            }
    }

    Menu Elements are converted to asp:Menu and asp:MenuItem Controls. They are added to ASPX:

     
    <div>
            <asp:Menu ID="simple_menu" runat="server" 
    Orientation="Horizontal">
            <Items>
            <asp:MenuItem Text="About" VALUE="About" 
    navigateurl="simple_about.aspx">
            </asp:MenuItem>
            </Items>
            </asp:Menu>
    </div>

    Event calls Method to open simple_about page:

    event clicked;OPEN(simple_about)
    END event

    Method is converted to navigateurl="simple_about.aspx".

  • Convert DataWindow (.SRD) to ASPX

    SRD file is a DataWindow source file. It contains information about DataWindow Object:

    release 10.5;
    datawindow()TABLE(COLUMN=(TYPE=CHAR(200) updatewhereclause=yes 
     name=name dbname="simple_demo.name" )
            COLUMN=(TYPE=long updatewhereclause=yes 
     name=age dbname="simple_demo.age" )
     retrieve="PBSELECT( VERSION(400) TABLE(NAME=~"simple_demo~" )
    COLUMN(NAME=~"simple_demo.name~") 
    COLUMN(NAME=~"simple_demo.age~")) " )

    SRD file is converted to an ASPX file with GridView Control:

    <asp:GridView ID="dw_1" runat="server" AutoGenerateColumns="False"
          DataSourceID="d_simple_demo" Width="201px">
            <Columns>
            <asp:BoundField DataField="name" HeaderText="Name"
                SortExpression="name" />
            <asp:BoundField DataField="age" HeaderText="Age"
                SortExpression="age" />
            </Columns>
    </asp:GridView>
    <asp:SqlDataSource ID="d_simple_demo" runat="server"
           SelectCommand="SELECT [name], [age] FROM [simple_demo]">
    </asp:SqlDataSource>

    Control Declare is converted to Designer Class:

    public partial class _simple_demo_main
    {
            protected System.Web.UI.WebControls.GridView dw_1;
            protected System.Web.UI.WebControls.SqlDataSource d_simple_demo;
    }

You can also reach us via Contacts page.

 
ASP.NET Versions

ASP.NET 4.6 and earlier

.NET Versions

Microsoft .NET 4.6.1 and earlier

PowerBuilder Versions

PowerBuilder 12.5.2 and earlier

Case Studies
July 20, 2014PowerBuilder to С# Conversion, United States

Our Baltimore, Maryland-based client has been providing documentation and billing solutions for hospitals for more than fifteen years. The migration task was to be performed for one of its...

...

May 27, 2014PowerBuilder to Java Migration, United States

Ispirer was engaged by an ISV company that develops and provides advanced maintenance software solutions and services in the airline software market. The company, founded in 1997, has its main...

...

Testimonials
December 3, 2012Epicor Software Corporation, United States
Progress 4GL to C# .Net Migration

"Epicor has engaged with the Ispirer team to create and refine prototype techniques for migrating certain parts of the Epicor Progress ABL code to well...

...

Feedback

Your software was critical to the success of our task of migrating 80 databases from the AS/400 to SQL Server. I would highly recommend your company and products to anyone who has the type of challenge we had. Your tool turned out to be the best and most reasonably priced product I researched and your customer support is excellent.

Read more
Industry Events