Whats the Difference - ASP & ASP.NET
Printed From: Web Wiz Forums
Category: General Discussion
Forum Name: General Discussion
Forum Description: General discussion and chat on any topic.
URL: https://forums.webwiz.net/forum_posts.asp?TID=16853
Printed Date: 31 March 2026 at 6:31am
Software Version: Web Wiz Forums 12.08 - https://www.webwizforums.com
Topic: Whats the Difference - ASP & ASP.NET
Posted By: Cannylad
Subject: Whats the Difference - ASP & ASP.NET
Date Posted: 09 October 2005 at 12:14pm
| Whats the Difference - ASP & ASP.NET I am a bit thick on the uptake and new to this ASP Stuff and do not want to start on one when I perhaps should have used the other????? |
Replies:
Posted By: dpyers
Date Posted: 09 October 2005 at 12:31pm
|
Go with .net. Classic asp will be around for a long time but it will not be developed any further as a language. ------------- 
Lead me not into temptation... I know the short cut, follow me. |
Posted By: Cannylad
Date Posted: 09 October 2005 at 1:25pm
|
OK thanks for the advice. So wheres best to start with Net???
Ive just spent the last 4 days trying to get the demo guest book from Web Wiz working........................does this mean I have to start all over again
 |
Posted By: dpyers
Date Posted: 09 October 2005 at 5:01pm
|
Nope. Classic asp is a very functional scripting language. I, and many
others, still build new sites with it. The only problem is that all
other main stream web languages - php, .net, java, etc., all have
migration strategies to develop the languages further. ASP doesn't.
What you see is what you get forever. At some point, MS will pull the
plug on it and stop releasing new versions of IIS that support it
although I'd expect to see some thrd parties or open source solutions
to run it. It just makes more sense for someone just strating out to go with a language that has more of a future. For inexpensive web hosting platforms, asp.net will give you more bang for your buck than either asp or php. - IMHO. www.asp.net is a real good place to start. -------------
Lead me not into temptation... I know the short cut, follow me. |
Posted By: michael
Date Posted: 09 October 2005 at 11:33pm
|
On another note, at this time you might want to think about what
version of ASP.net you start with. 2.0 will be released in about a
month and I am sure it will take you that long at least to get a
publishable site working. Therefore you can start with the Visual Web
Developer Express which you can currently download for free from
asp.net. There are many advantages in 2.0 over 1.1 and as there will an Express Version of Visual Studio it shall give more students and beginners the chance to code in .net. Sure they are not supposed to be free but from what I heard, if you buy a microsoft press .net book on 2.0 they will include a CD with the relevant Express product so you get it free if you buy the book kinda deal. They are still free for now in the beta version. ------------- http://baumannphoto.com" rel="nofollow - Blog | http://mpgtracker.com" rel="nofollow - MPG Tracker |
Posted By: Bluefrog
Date Posted: 11 October 2005 at 5:21am
|
ASP has a smaller learning curve than ASP.NET, but you'll get a lot more done a lot faster with ASP.NET. If you need to get something fast done NOW, then go with ASP. But, if you're a strategic planner, go with ASP.NET. The extra time and effort you put into it will pay off. Dpyers' advice on going with ASP.NET is bang on the money - go with the future. You do NOT want to have to deal with porting old applications to new platforms. It is NOT fun. ------------- http://renegademinds.com/" rel="nofollow - Renegade Minds - Guitar Software http://renegademinds.com/Default.aspx?tabid=65" rel="nofollow - Slow Down Music |
Posted By: Muskan
Date Posted: 20 October 2005 at 10:46am
|
Hi all the experts here,
We have got a very big site ..nearly 5 yrs old .. all coded in asp, with thousands and thousands of pages of content, forums, dozens of services, shopping malls etc and nearly 100,000 visitors a month - all pure asp with access and sql server. What could be the future of sites such as ours? I have though about migrating to php or .net many times ..but have never been able to sort out how this can be done. Any ideas? There are so many issues in migration ..database migration is the most error prone if we move to php/mysql, recoding all the scripts and applications, renaming all the asp content files, updaing the includes... Is there any other way to it? |
Posted By: michael
Date Posted: 20 October 2005 at 12:54pm
|
Well whatever technology you decide for, the migration path will not be easy.
One important thing to consider is that you probably have quite a few links from search engines that you want to be directed appropriately, that means you'd need a handler.
If you are already running SQL Server, there is no real reason to switch to mySQL, just stick with SQL Server so you do not necessarily have to upgrade all databases.
Nonetheless, upgrading 1000's of pages will be undertaking that you have to plan wisely, and might have to be done gradually by application/service ------------- http://baumannphoto.com" rel="nofollow - Blog | http://mpgtracker.com" rel="nofollow - MPG Tracker |
Posted By: snowgoose
Date Posted: 24 October 2005 at 6:45am
|
Hi
I've got a big ASP site too, and am wondering whether/how to move over to ASP.NET.
The point is ASP will be around for many years, but it will be unsupported. However, my website will (I hope) be around for many MORE years.
So at some point I will have to migrate. Though it's not hugely urgent...
My thought is to start changing a few key pages sooner rather than later, and at some point (once I've got a much better handle on it) start doing all new development on the site in ASP.NET.
In summary, I think eventually we will have to migrate. We should start slowly though.
|
Posted By: Gullanian
Date Posted: 24 October 2005 at 12:32pm
| Doing bits at a time can get you in quite a mess, it might be better to re-write and release fresh when it's completed. |
Posted By: michael
Date Posted: 24 October 2005 at 5:11pm
|
Well you sure have to be careful but depending on the size of the site, it may not be possible to do a one-process upgrade. By the time he is ready converting he will be ready to add stuff again and change. I would take a small application not too important and try an upgrade. ------------- http://baumannphoto.com" rel="nofollow - Blog | http://mpgtracker.com" rel="nofollow - MPG Tracker |
Posted By: dpyers
Date Posted: 24 October 2005 at 6:53pm
|
I've seen people take an engine aproach to upgrading by first redoing
common functions into their own application api - e.g. a .net data base
engine that you can convert all your existing db ACID stuff to and
later a display engine to handle .net output from the db using web
controls. etc. The nice thing about starting with db and display engines is that you can convert scripts at your lesiure - don't have to do them all in one release, or at least you can bundle the conversion to an engine in several releases. As michael noted, some sort of url handler/rewriter is probably the most important thing in your situation if you plan on reorganizing your site or renaming pages. You don't want to screw up years of search engne placement. I wouldn't do the url handler as my first .net app though... it's to important to the site. -------------
Lead me not into temptation... I know the short cut, follow me. |