ASP Development
 
Forums: » Register « |  User CP |  Games |  Calendar |  Members |  FAQs |  Sitemap |  Support | 
 
User Name:
Password:
Remember me
 
Go Back   Dev Articles Community ForumsProgrammingASP Development

Reply
Add This Thread To:
  Del.icio.us   Digg   Google   Spurl   Blink   Furl   Simpy   Y! MyWeb 
Thread Tools Search this Thread Display Modes
 
Unread Dev Articles Community Forums Sponsor:
  #1  
Old May 27th, 2003, 12:14 PM
mark0 mark0 is offline
Junior Member
Dev Articles Newbie (0 - 499 posts)
 
Join Date: Feb 2003
Posts: 9 mark0 User rank is Just a Lowly Private (1 - 20 Reputation Level) 
Time spent in forums: < 1 sec
Reputation Power: 0
Converting standard ASP to ASP.NET

Not knowing much about .NET, can anyone tell me that if I wanted to move away from my standard (classic) ASP site how much effort would be involved to convert my existing site to use .NET?

At the moment I am guessing I would have to do a complete re-coding exercise, however, I am hoping that Microsoft built .NET with this issue in mind.

Thanks in advance.

Reply With Quote
  #2  
Old May 27th, 2003, 09:17 PM
DeadManWalking DeadManWalking is offline
Junior Member
Dev Articles Newbie (0 - 499 posts)
 
Join Date: May 2003
Location: Shimonoseki
Posts: 12 DeadManWalking User rank is Just a Lowly Private (1 - 20 Reputation Level) 
Time spent in forums: < 1 sec
Reputation Power: 0
Send a message via ICQ to DeadManWalking
I don't know much about .NET either but AFAIK, ASP and ASP.NET are two different languages.
If you want to learn ASP.NET you have begin from zero, even if you have a good knowledge of classic ASP.
Thats what I heard

Reply With Quote
  #3  
Old May 27th, 2003, 10:05 PM
stumpy's Avatar
stumpy stumpy is offline
May contain nuts.
Dev Articles Regular (2000 - 2499 posts)
 
Join Date: Aug 2002
Location: Sydney, AU
Posts: 2,058 stumpy User rank is Just a Lowly Private (1 - 20 Reputation Level) 
Time spent in forums: 5 h 8 m 57 sec
Reputation Power: 9
Send a message via ICQ to stumpy Send a message via MSN to stumpy
ASP.NET isn't a language... it's the "web-interface" of either C# or VB.NET.

Both these languages are OO (object oriented), whereas ASP is far from it... essentially meaning you'll have to learn OO, and do a complete re-write....

And lemme tell ya, i'm in (was) in the process of learning, and it's a whole new world... some very difficult paradigms to get your head around.
__________________
DevArticles Moderator
BlueSix - Web Development and Consulting

Reply With Quote
  #4  
Old June 2nd, 2003, 12:42 PM
James Yang James Yang is offline
Contributing User
Dev Articles Newbie (0 - 499 posts)
 
Join Date: Apr 2002
Location: Atlanta, Georgia
Posts: 284 James Yang User rank is Just a Lowly Private (1 - 20 Reputation Level) 
Time spent in forums: 2 m 45 sec
Reputation Power: 7
Send a message via ICQ to James Yang
Well there are two options. One is to re do the whole site or 2nd is just do the portions of the site.

if u re do it then your site is most likely to have ASP.NET pages and Web Services as your front end, .NET Components as mid tier and SQL and ADO.NET as your back end. This is probably the best option because you can do alot if all three tiers have FULL compatibility. Like being able to pass DataSet between tiers including web services.

the other choice is only upgrade one or two of the tiers. this might involve developing COM+ using .NET, (not a good choice) or developing ASP.NET front end and using existing COM+ coponents( more likely option) OR just changing the COM+ in just the backend (the data tier code to access DB...this is good cuz .NET provides faster access to ORACLE and sQL servers ...also a good choice)

now choosing between them really depends on the size of your website. Is it a personal site? if yes then the 1st choice is viable and is probably the best thing to do at the moment...It will be a good chance to upgrade your site to become OO making it easier to upgrade in the future

but if ur site is HUGE..then the first choice is hard to achieve. and sometimes its unnecessary. The time and effort spent in replacing com+ would be better spent else where.

But having said that...is it even necessary for you to upgrade to .NET. I think this is a misconception everyone has. just cuz .NEt is good, it doesn't mean you need to upgrade to it. It should be IF you are going to upgrade, upgrade to .NEt not upgrade to .NET because .NET is good

I hope this helped you out a bit
__________________
Regards,

James Yang
.NET Developer / Network Engineer
MCSE, MCDBA, MCSA, CCNA

http://www.yellowpin.com/
http://www.opentechsupport.com/

Reply With Quote
Reply

Viewing: Dev Articles Community ForumsProgrammingASP Development > Converting standard ASP to ASP.NET


Thread Tools  Search this Thread 
Search this Thread:

Advanced Search
Display Modes  Rate This Thread 
Rate This Thread:


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
View Your Warnings | New Posts | Latest News | Latest Threads | Shoutbox
Forum Jump


Forums: » Register « |  User CP |  Games |  Calendar |  Members |  FAQs |  Sitemap |  Support | 
  
 





© 2003-2008 by Developer Shed. All rights reserved. DS Cluster 3 hosted by Hostway
Stay green...Green IT