Escolar Documentos
Profissional Documentos
Cultura Documentos
Hanu Software
Hanu Software
Hanu Software
Event-Driven Programming: ASP .NET is an object oriented technology that supports event
driven programming unlike ASP. Objects on a Web page can expose events that can be processed by ASP .NET code. Load, Click and Change events handled by code makes coding much simpler and better organized.
Improved Scalability: ASP.NET has removed the bottlenecks created by ASP sessions, which
used to work well only on the server where they were created. They used to store the session data "in-process" on the web server, which was a cause of scalability bottlenecks on high-volume sites. ASP.NET stores session's data on a dedicated state server that can be easily shared by multiple web servers and on an SQL Server database too, providing a better scalability and availability of sessions. This has improved the server to server communication, making it possible to scale an application over several servers. One example of this is the ability to run XML parsers, XSL transformations and even resource hungry session objects on other servers.
Hanu Software
Improved Performance: ASP.NET highly improves the performance of your code because it
uses caching in code with automatic content expiration. This feature automatically expires and refreshes data from the cache. This automatically solves the problems of memory leaks from your application and improves the performance of your application. ASP.NET performs dynamic compiled execution of code, which allows fast retrieval of pages as compared to ASP, which requires each page to be interpreted when it is requested by the client. The dynamic compilation automatically detects changes in the code and stores the compiled code in memory to serve the future requests by the web server.
Easier Configuration and Deployment: ASP.NET use XML (extensible markup language) file
within the application to store application configurations. The configuration files used by ASP.NET applications can be changed and uploaded while the application is running without restarting the server. The web applications are simply copied to the server without the need to run regsvr32 to register any application components and configuration settings.
Easier Code Maintenance: ASP.NET enables easy code maintenance because it separates
presentation layer from business logic layer. Developers with relevant expertise in front end and back end programming can easily maintain code as compared to ASP, where a single file is used to write HTML, VB script, Java script, and ASP code.
Hanu Software
Core API Changes: These changes refer to the changes made to the API method calls while
migration. For example the changes that would occur when you make the calls related to Request, Response, and Server objects. Usually the method of making calls is same but if there are multiple values for a given key for collection objects different method to return the collection of values is used.
Structural Changes: These changes refer to the changes that affect the layout and coding style
of an application. For example ASP.NET pages only support one language on a single page where as ASP allowed multiple languages to be used on a single page. ASP.NET page functions must be declared in <script runat=server> blocks where as in ASP, page functions are declared within <% %> blocks. In ASP.NET, page functions must be declared in <script runat=server> blocks whereas ASP.NET does not support page-render functions.
COM-Related Changes:
VB.NET code migration does not force you to incorporate any COM-related changes in your code. Most of these changes are back stage changes and are done automatically. Some changes include the change in threading model, early binding and late binding changes, and changes in OnStartPage and OnEndPage methods in the code.
Application Configuration Changes: ASP.NET requires you to store all your configuration
settings in Web.config file, which is available in the main application directory.
State Management Issues: ASP.NET does not require you to change your Session or Application
objects. On the other hand it provides State Management Options for Inproc, StateServer, SqlServer for improved control on your applications. If your application is partially migrated to .NET platform then you cannot share state variables stored in the intrinsic Session or Application objects in your application with .NET pages. You need to duplicate this information in both systems, till the complete migration takes place.
Hanu Software
authentication, including cookie management and automatic redirecting of unauthorized logins. All these authentication methods were also available in ASP but Passport based authentication in a new feature added to ASP.NET. Unlike ASP, ASP.NET does not do per-request impersonation. It does not allow your code to run on behalf of authenticated user. You can still use your old authentication methods and perform custom user and login checking using other authentication methods.
Data Access: ASP .NET uses ADO .NET, which offers an enormous range of features as compared
to ADO to improve your data access methods. It offers powerful new features to get you data from database. Though you need not make any code changes for migration but you can make use of all ADO.NET features in your code.
Hanu Software
Hanu Software
We Accept Challenges
At Hanu Software, we accept challenges to migrate any ASP application successfully to .NET platform. The application may be simple or complex, after migration, you receive all the benefits of migration of your application. Although the complete migration of a site in one go is possible but Hanu Software believes in modular approach. The decision to go for a modular migration or full fledged migration is based on the size and complexity of the application. The simple and small web sites can be migrated to .NET platform in one go but big, complex, and mission critical business applications must be migrated using modular approach. At the time of suggesting a migration solution we also consider other factors that affect a migration strategy such as the migration goals of a company, complexity and architecture of existing system, budget, and other available resources. Hanu Software believes that a company willing to migrate its application from ASP to ASP.NET must not suffer losses due to the downtime of the business website. The migration process should be smooth and easy going without affecting the business of a company. Hanu Software offers a solution based on planned phases of migrations and enhancements and possesses strong product release management experience to manage old as well as new product versions. Hanu Software simultaneously supports: - Bug fixes for existing ASP system - Development of the new .NET version - Implementation of new features in ASP as well as ASP.NET based system.
Hanu Software
We believe that if a company is looking for long-term benefits from the migration then the company can follow the approaches given below:
Co-Existence - In this approach, you can have the ASP and ASP.NET modules existing together.
You can perform migration for a specific functionality of an application and ensure that the migrated module would still interoperate with the existing application. At Hanu, we follow the following co-existence strategies: Migrating Shared Pages: In this approach we select only those pages first that share their code with other pages. These pages are common pages having intensive code processing and the potential for caching. This enables the important and complete sections of the applications to be migrated first. After this migration both ASP and ASP.NET would be running simultaneously and ASP pages will be using ASP.NET code. Migrating New Pages: In this approach we select only those pages, which need to be added to the application for additional functionality. These pages can be entirely new pages or existing pages that require major code changes. This is the most comfortable approach without affecting the existing functionality. This also restricts new bugs to the new pages only. Migrating Entire Tier or Entire Module: In this approach, we either select an entire module for migration or migrate the application tier by tier. This can be done using Horizontal and Vertical migration strategies. Both these migration strategies will be discussed in the next section of this paper.
Build the Roadmap - In this approach, to get long term benefits of migration, you decide to
invest in re-architecting a system so that you can make the best use of .NET framework. The primary objective of this approach is to provide a comprehensive and detailed design for future project developments.
Full Fledged: In this approach you may want a full fledged migration of your system with the
plans for change in application design, development, and deployment. This may be due to some strategic business needs. The two co-existence migration strategies that Hanu Software offers are Vertical and Horizontal Migration. Both these strategies offer a modular approach for migration.
Hanu Software
Vertical Migration
Vertical migration refers to migrating an application one tier at a time, as shown in the Figure given below. For example, consider you have a three tier HR application, which consist of three modules, Recruitment, Leaves Management, and Salary Management. The three tiers used by the application include the user interface, business components, and database. Vertical migration approach would proceed through all the pages of the user interface tier for each module, followed by the business component and data interface tiers, as shown in the figure given below:
The vertical migration is most appropriate when the application's modules are tightly coupled and minimal changes are required to the interfaces between application tiers. The initial architectural review in this case could yield opportunities for shared code across all three tiers rather than result in separating the modules into distinct applications:
Hanu Software
Horizontal Migration
Horizontal migration refers to migration of an application module by module, completing the migration for all three tiers of one module before moving on to the next. As shown in the Figure given below. For example Horizontal migration would proceed through entire Recruitment Module first with all the three tiers (user interface, business components, and database) migrating together for that module. After the recruitment module is completely migrated the other two modules Leaves Management, and Salary Management will be migrated. A horizontal migration is most appropriate when application modules are loosely coupled and when interfacing between different application tiers is a tedious task. An architectural review all of the application's modules should be conducted before any module migration begins. This review should uncover opportunities for creating reusable code, and may lead to separating the modules into independent applications.
The vertical migration is most appropriate when the application's modules are tightly coupled and minimal changes are required to the interfaces between application tiers. The initial architectural review in this case could yield opportunities for shared code across all three tiers rather than result in separating the modules into distinct applications:
Hanu Software
Analysis: At this stage, we analyze the existing code, and create a migration strategy. We
consider the scope of migration, the processes required for migration such as code modification and testing plans. At this stage we also identify the .NET specific functionality that can be added to the application or can be replaced with ASP.NET functionality.
Conversion: At this stage, we perform the actual code conversion. We start developing and
modifying modules for migration. At this stage we perform unit testing and peer reviews for the converted code.
Re-factoring - At this stage, we perform code optimization and design improvement. This stage
can actually enables you to get long terms gains from the migration and can be helpful in drastically improving the performance of the application.
Testing: At this stage we conduct functional and non-functional testing for the modules that
have been successfully migrated. The complete life cycle of the migration process ensures a smooth migration of your system from ASP to ASP.NET
Hanu Software
Hanu Software
Acknowledgments
The following Hanu Software Employees contributed to the development of this white paper
For more information about Hanu Software Solutions Technology migration services, call our US Sales Information Center at (732) 668-3691 or email asingh@hanusoftware.com. In India, call the Hanu Software Solutions offshore delivery center at (732) 823-4153 or email msrivastava@hanusoftware.com. To access information using the World Wide Web, go to: http://www.hanusoftware.com/