RPGDevNet

A Paradigm Shift in ASP.NET Application Architecture

By Tim Daniels

ASP.NET application development is undergoing a paradigm shift that will alter the architectural foundation of application design. Moving application processing from the server to the client is the simplest way to describe this change. More specifically, this means moving user interface centric processes, from the web server to the browser. This change not only affects system architects and website designers, it also changes the way developers design and create browser-based applications. Developers will have to give more consideration to architectural concerns than ever before.

At a technology level, this paradigm shift means that the current ASP.NET application model, based on postbacks and view state, is being replaced with an alternative architectural model. The new model is a combination of technologies focused on enhancing the end user experience in the browser. These technologies include; AJAX, JavaScript, jQuery and Service Oriented Architecture. For the developer, this means that server side controls will give way to AJAX and JavaScript based components running in the browser. Silverlight will also play a major role in this model. The ASP.NET Model View Controller (MVC) design pattern, which eliminates server side controls, also figures prominently in future web-based development.

What is driving such a dramatic shift in ASP.NET application architecture? End users are becoming more and more sophisticated; demanding more from web based applications in terms of content, work flow, graphics, animation, data access and rich interactive experiences. They are also becoming more intolerant of poor response to their requests. Regardless of network latency, architectural limitations and technological limitations, end users are demanding a more responsive web. The solution is to exploit the processing power and data caching capacity of the client, and drive as much processing and data manipulation as possible into the browser, along with reducing the payload size and number of round trips to the server.

The content for this article is based on two books I’ve been studying. Microsoft ASP.NET and AJAX: Architecting Web Applications by Dino Esposito and Developing Service-Oriented AJAX Applications on the Microsoft Platform by Daniel Larson. You will find these to be excellent references as you explore the future of ASP.NET application development. Also, although the spec isn’t yet completely feature-complete, read about what Microsoft has on tap for the upcoming ASP.NET 4.

The Migration Engineer’s Tool Box

by Tim Daniels

You can’t do the job right without the right tools. Over the past three years, I have been supporting ASNA BluePhoenix sales and services efforts by migrating and modernizing, IBM Systemi based applications, to the Microsoft .NET framework. In this timeframe, the size and complexity of these projects have grown as BluePhoenix expands its professional services offering in the Midrange market space. Looking back on this timeframe, the early projects were simple proof of concepts, in support of sales. These were small one man projects that could be turned around in a matter of days. I have also been participating in projects as part of the services team. These are much larger projects requiring the efforts and expertise of multiple team members who can be spread across multiple locations in America and offshore regions. As the size and complexity of projects has grown, so has the number and sophistication of technical tools used to deliver a migrated and modernized application.

From time to time, it is necessary to take inventory of what’s in the migration engineer’s tool box and see how effectively these tools are being used in the migration process. I find it helpful to list the tools within the following functional categories

• Analysis
• Automation
• Development
• Communications
• Project management

Some tools are used in multiple categories throughout the life cycle of a migration project. Following is a brief description of each tool by functional category and how it’s used within each function of a migration and modernization project.

Analysis Tools

• Monarch – fast in-depth analysis of the legacy Systemi application. Monarch exposes all of the objects supporting the application and how they relate to each other.
• DataGate – middleware between DB2/400, OS/400 and client applications like Monarch and AVR.Net programs

Automation Tools

• Monarch – automates most of the legacy application analysis and source code migration to .Net
• Visual Studio – Provides a complete project solution structure automatically populated by Monarch
• DataGate – middleware conduit facilitating automated migration from System i to .Net

Development Tools

• Visual Studio – integrated development environment supporting further development and modernization of the migrated application
• AVR.Net – Object oriented language providing RPG like syntax in .Net
• DataGate – middleware between DB2/400, OS/400 and client applications like Monarch and AVR.Net objects
• Vault by Sourcegear – provides source code management and version control

Communication Tools

• Webex – Online meetings to share desk top environment and results with customers and remote team members in real time
• Skype – provides high quality voice over IP, and instant messaging communication with local and offshore team members
• Instant messaging
• E-mail

Project Management Tools

• Journyx – time entry and time management systems
• Monarch – very useful for distributing and managing workloads across team members. Also very useful in forming strategic and tactical elements of the project
• Vault by Sourcegear – check in and checkout source code feature facilitates collaboration of team members
• MS Excel, MS Project

This inventory of tools also gives you some idea of the scope and magnitude of a migration and modernization project. Keeping the toolbox up to date with the latest technologies is absolutely necessary for delivering a quality product in a timely and cost effective manner. Modern tools coupled with sound methodologies, make the delivery process smooth and predictable without heroics.

[photo credit: SXC]

Free Microsoft graphing controls for Windows and ASP.NET

by Tim Daniels

Microsoft recently announced a new suite of free chart and graph user interface controls for ASP.NET web pages and Windows forms. These new controls are available as a free download and snap into the Visual Studio 2008 tool box. Note that these controls do not work with previous versions of .NET. They do require .NET 3.5 and Visual Studio .NET 2008.

I recently used the pie chart controls in a previously migrated Monarch app. In this example, the data for the chart is retrieved from an inventory file residing on the System i through DataGate. Learning how to fully exploit the chart suite will take some time, but after just a little exposure to MS’s examples and documentation, I got results pretty quickly. The graphics for the chart are provided in the properties and images that come with the free download. A wide variety of charts and graphs are supported with these new controls.

Follow these four steps to get all you need to use this new chart suite (the first two are mandatory, the second two are optional but recommended):

1. Download and install the controls

2. Download and install the graph control add-in for Visual Studio 2008

3. Install the documentation

4. Install the Microsoft-provided examples

Watch this blog and our DevNet site for more info on using these controls with ASNA Visual RPG (AVR).