Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Migrating a ASP Web App

Status
Not open for further replies.

MattWoberts

Programmer
Oct 12, 2001
156
GB
Hi,

I am trying to work out how to migrate a typical ASP web app. to ASP.NET. The web app was built around the DNA architecture, so has the ASP's, Business components (VB), and Data components.

I am unsure how to approach this in .NET. Should I keep the business/data layers and write them as .NET components (classes). Also, many of the data comps return recordsets, should they return DataSets in .NET?

Any help would be very welcome!

MattWoberrs
 
On the microsoft Developer days i got the booklet "migrating from asp to .net" its got loads of articles on how to com-->.net and the other way around. Edward@de-leau.com
 
Thanks - is there any way I can get hold of the booklet, maybe download it from MS's site?
 
I hate to say this, but the architecture of .NET is completely different than it ever was in ASP Classic, even if you went by MS' DNA guidelines.

If you start migrating it piece by piece, then you're going to wind up with a .NET application written with a legacy architecture.

True, there are lots of articles out there that talk about migration, but you'll also find lots (and I'm one of these) that tell you that true migration is more trouble than it's worth. My suggestion is to just start from scratch.

It sounds harsh, but take your current app, lay it out, and approach it from an OO standpoint. I'll guarantee you that you'll like what you come up with there much more than you would like the end result of a migration project.

Just my two cents. Worth somewhere in the neighborhood of what you paid for them. ;-)
penny1.gif
penny1.gif
 
Thanks. I think I was coming to the same conmclusion myself. The architecture of a DNA app does not seem to fully expoilt the power of .NET if you attempt to map it accross.

Having said that, I suppose there could be some sort of similiarities...the data comps would nicely map to a set of .NET classes that deal with the data work, likewise the bus. comps would also map to another set of classes - but the actual "migrating" from A to B would be pretty worthless.



 
Sounds like you have a handle on it. That's pretty much it, exactly.

And I'm glad to see that you don't sound terribly discouraged. You'll love this stuff. Really. :)
penny1.gif
penny1.gif
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top