Wrox Programmer Forums
| Search | Today's Posts | Mark Forums Read
ASP.NET 1.x and 2.0 Application Design Application design with ASP.NET 1.0, 1.1, and 2.0.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the ASP.NET 1.x and 2.0 Application Design section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old September 17th, 2004, 01:32 AM
Registered User
 
Join Date: Sep 2004
Location: , , .
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default Migration .Net from ASP/VB

Hi,

  We have to give a proposal for migrating a web-based application to ASP/VB.
Before that we have to evaluate this application as to how migrating to .Net will benefit on the parameters of performance.

The back-end is Oracle.

kindly help me out as to what are the key points that need to be evaluated for this.

Thanks.
Bans

 
Old September 17th, 2004, 08:01 AM
Friend of Wrox
Points: 3,489, Level: 24
Points: 3,489, Level: 24 Points: 3,489, Level: 24 Points: 3,489, Level: 24
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Jun 2003
Location: Central, NJ, USA.
Posts: 1,101
Thanks: 0
Thanked 2 Times in 2 Posts
Default

If you have a web based application- I don't understand what migration is taking place.... Is it in ASP and you want to move it to ASP.NET? Is it a Client Server Application and you want to move it to the web?

Hal Levy
Web Developer, PDI Inc.

NOT a Wiley/Wrox Employee
 
Old September 19th, 2004, 11:16 PM
Registered User
 
Join Date: Sep 2004
Location: , , .
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hi Hal,

   I am sorry for the original posting. We have a web-based application in classic VB/ASP that we need to migrate to .Net.

Now, we need to evaluate the existing application as to how much difference it will make on the performance if we migrate to .Net.

For that, what are the points on which we should evaluate the application?

The back-end is Oracle. Major part of the code consists of SQL queries accessing data from the Oracle database and displaying the data on the pages. The VB components are used either for sending mails or updating the database on a regular basis. We are also using graphs in a couple of reports for which we are using a third party tool.

Hope this gives a clearer picture.

Thanks again.
Bans

 
Old September 20th, 2004, 09:01 AM
Friend of Wrox
Points: 3,489, Level: 24
Points: 3,489, Level: 24 Points: 3,489, Level: 24 Points: 3,489, Level: 24
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Jun 2003
Location: Central, NJ, USA.
Posts: 1,101
Thanks: 0
Thanked 2 Times in 2 Posts
Default

Why do you "need" to migrate it to .net? I would never just migrate from ASP to ASP.NET "because it's newer". If I had a working application that didn't require any major bug fixes or enhancements, I'd leave it alone in Classic ASP.

If performance is your issue, I'd be looking at your Oracle performance and if the SQL and Indexes are optimal.



Hal Levy
Web Developer, PDI Inc.

NOT a Wiley/Wrox Employee
 
Old September 20th, 2004, 02:46 PM
planoie's Avatar
Friend of Wrox
Points: 16,481, Level: 55
Points: 16,481, Level: 55 Points: 16,481, Level: 55 Points: 16,481, Level: 55
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Aug 2003
Location: Clifton Park, New York, USA.
Posts: 5,407
Thanks: 0
Thanked 16 Times in 16 Posts
Default

Hal makes a good point about the need to migrate. May I make the following points in response:

1) Performance: If your code is primarily performing lots of database interaction, there may be a lot of limitations in your current application due to the much simpler language that could be optimized by using the extensive ADO.NET classes and the true OOP environment of .NET. (This will have a much greater impact if and when you need to add features to the application.)

2) Education: Unfortunately, this point is often far too difficult to use to convince powers-that-be that you should dedicate time to an upgrade, depending on your organization. When I started learning .NET I worked with a team who was all new to .NET. We starting using it to build a whole new application. So we ended up having to think a lot about designing the application while also learning about the new technology. This proved less than fruitful. If I'd had the opportunity, I would have taken an existing application and migrated it. This would have yielded two major advantages:
A) You already know how the application works so you know when you have really busted it.
B) You can focus your energy on learning the technology and thinking about how to refactor what is already there to make it better using the new technology. You don't need to redesign the application from a business point of view, only a technical point of view.

3) Scalability/Flexibility: ASP applications aren't easily scalable/flexible. If you needed to change the application so it work without cookies, you'd have to write a lot of code yourself. If you wanted to put the application on a web farm, you'd need to write a lot of code yourself. If you migrated the application to .NET, you could perform both of these tasks in minutes instead of weeks. (Granted, you would have had to spend time migrating the application to .NET anyway so it might not be a compelling point.)

4) 3rd Party Tools: .NET will allow you to get away from several 3rd party tools, which could save you licensing costs and also boost performance. .NET has built in mailing capability, and there are many charting tools for .NET that perform better than (not to mention eliminate the COM headache of) VB add-on components.

Hopefully this helps you.
 
Old September 21st, 2004, 12:41 AM
Registered User
 
Join Date: Sep 2004
Location: , , .
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Thanks for the pointers, Planoie.

Answering Hal's question (which is very valid and obvious), the need for migrating to .Net arose because of two major reasons:
  • We are facing performance related issues in some of the ASP pages since we are displaying data retrieved by huge SQL queries. Hal is correct in that this might be related to SQL tuning or perhaps the database tuning itself, but, we have been working on that since last 4-5 months and also have succeeded in improving the performance of the script to a large extent. However, we feel that we can further improve the performance by migrating to .Net. Moreover, the data is going to increase tremendously with time and the complexity is going to increase too due to further enhancements in the application.
  • We have a component that loads data in flat files to the Global Data Repository (GDR). Now, since there are a lot of flat files to be uploaded to the GDR at the same time, it consumes a lot of everything - time, system resources, etc - and the number of flat files to be processed each month is also increasing month by month
We are hoping that migrating to .Net will help us greatly in the above mentioned areas.

I hope this gives a clearer picture.

Bans.

 
Old September 21st, 2004, 08:22 AM
Friend of Wrox
Points: 3,489, Level: 24
Points: 3,489, Level: 24 Points: 3,489, Level: 24 Points: 3,489, Level: 24
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Jun 2003
Location: Central, NJ, USA.
Posts: 1,101
Thanks: 0
Thanked 2 Times in 2 Posts
Default

I, of course, bow to Peter when he gives an answer- He's much smarter than I am. I don't think, however, that the key to solving your problem is a migration to .NET but with dealing with the data issues. You need to look at how long the Queries take to run using a query tool and then compare it to the page response. If the time is the same, the issue isn't the ASP.

That said, depending on the quality of the ASP code (and for that matter, the VB code in your business objects) you could improve performance.

I'd test a Query time directly to the DB versus the query running through the application. If the response time is very different, you can justify re-writing the application.

I am sure you have done the obvious, like using stored proc's instead of using SQL embeded in code...


Hal Levy
Web Developer, PDI Inc.

NOT a Wiley/Wrox Employee
 
Old September 26th, 2004, 04:20 PM
planoie's Avatar
Friend of Wrox
Points: 16,481, Level: 55
Points: 16,481, Level: 55 Points: 16,481, Level: 55 Points: 16,481, Level: 55
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Aug 2003
Location: Clifton Park, New York, USA.
Posts: 5,407
Thanks: 0
Thanked 16 Times in 16 Posts
Default

Quote:
quote:Originally posted by Hal Levy
 I, of course, bow to Peter when he gives an answer- He's much smarter than I am.



Despites Hal's misconceived notion that I am smart, I whole-heartedly endorse his comments regarding database performance analysis.

Unless you are doing tremendously large amounts of processing in the application code itself, the #1 performance bottleneck will be the database calls. Unfortunately, even .NET can't make that better.




Similar Threads
Thread Thread Starter Forum Replies Last Post
Migration - Rendering ASP code silar ASP.NET 2.0 Basics 1 August 19th, 2008 08:07 AM
Tables migration from Access to SQL Server-VB.NET ayazhoda VB.NET 2002/2003 Basics 2 May 3rd, 2007 05:59 AM
Migration of treeview from VB6 to VB.NET karveajit General .NET 0 March 27th, 2007 01:34 AM
Migration of Treeview from VB6 to VB.NET karveajit ASP.NET 1.0 and 1.1 Professional 0 March 27th, 2007 01:25 AM
Urgent VB form Migration to VB.net form kvenkat_2k1 Pro VB.NET 2002/2003 1 December 7th, 2005 04:58 PM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.