Click to See Complete Forum and Search --> : Migration .Net from ASP/VB
Bans.Net
09-17-2004, 12:37 AM
Hi,
We have to give a proposal for migrating a web-based application from classic ASP/VB to .Net.
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.
Major part of the code consists of SQL queries that access data from the Oracle database and display the result in the page?
kindly help me out as to what are the key points that need to be evaluated for this.
Thanks.
Bans
PeOfEo
09-17-2004, 08:26 AM
you mean you are migrating to asp classic? Asp.net performs great. It is compiled on application start similar to jsp so it runs pretty darned fast. It is also very easy to pick up programming with vb.net on the web because it very very similar to programming with vb.net for applications (or vb6). You have event handlers and elements, so you still do event oritned programming. The only new thing is the ql statement. I know nothing about oracle so I cannot comment on that.
Bans.Net
09-19-2004, 11:00 PM
Hi,
I am sorry about the original post... We have to migrate from classic VB/ASP to .Net. We have this web-based application in classic VB/ASP that we have to migrate to .Net. We need to evaluate this existing application on the parameter of performance. So, what points should be considered while migrating to find out how much performance improvement will happen.
Thanks for pointing out the mistake :)
PeOfEo
09-19-2004, 11:32 PM
well what is the existing application doing? If it is a whole lot of code and it gets data intensive (lots of loops and all), then asp.net can noticeably reduce strain on the server because of the fact that it gets compiled at application start. But for a small application, like one or two little pages that access some server variables, maybe send an email, that sort of junk, you would not notice a huge difference. I think the more code you have, the bigger the difference. You do not have to migrate your whole application to asp.net though, you can pass information between the two and run them side by side if you like.
Bans.Net
09-21-2004, 01:06 AM
This application is Internet based. It has huge amounts of data. About 200 ASP files. Uses some 17-18 VB components. Its a huge application, running on classic VB/ASP since atleast 5 years now. Recently we have had a tremendous increase in the users and hence a tremendous increase in the amount of data.
An interesting pointer I find in your reply is "partial migration". Now, I have further doubts regarding this -
How much complicated is it and is the end result (in terms of performance, primarily) worth all the time and effort put in for "partial migration"?
Is it that we will HAVE TO do a partial migration for migrating this completely to .Net?
Thanks.
Bans
PeOfEo
09-21-2004, 05:55 AM
well what do you use to pass data between your pages? I mean you can easily move data with query strings from page to page, asp and asp.net. I do not think the session or cookies survive... I have never tried it. I will play witht hat later. But if you wanted to keep the pages that receive a query string asp, there would be nothing preventing you from doing so, it would definatly save you some work. But all of the major pages that are used a lot could move to asp.net. What kind of data base are you using? MsSQL?
Bans.Net
09-21-2004, 11:14 PM
We are using querystring for passing data between the pages.
The database is Oracle.
PeOfEo
09-22-2004, 04:51 PM
Then you can easily migrate it little by little. Its not a big deal at all. Gradual migration should be rather painless actually. I am assumeing oracle is a rather fast data base (I mean you take the cost of it in the chin). Mssql server is what I use, and it is very fast, but its probably not as good as oracle. But yeah just move over some of the high traffic pages that access the data base a lot over first then you can go to the remaining ones if you want.