Printable View
I've been searching alot for this and not sure how to scour this forum for this answer...
What is the difference between ASP 3.0 and ASP.NET 1.x?
Does the IIS web server have to be upgraded? I assume that has to be true as the code is interpreted by the server...
I just read an article about ASP.NET 2.0 and it has things I am looking for but it sounds like it won't be ready till 2006. I'd like to start toying with ASP.NET if it has anything good to offer.
Thanks,
Dave
ASP.NET is leaps and bounds better than ASP. The only thing different on the server side is you need the .Net framework on the server.
Waiting for ASP.Net 2.0 isn't what I would do. The coding is easier in some places in 2.0 compared to 1.1, but that doesn't make any work you do until then worthless. Your code is still .Net code.
That is saying alot without saying alot ;)Quote:
Originally posted by hellswraith
ASP.NET is leaps and bounds better than ASP.
Could you extrapolate on this?
Dave
What do you want specifically? It would take too long to talk about all the differences.
You can use datagrids to display data quickly and easily. True seperation of code and html. Inheritance, OOP, all the rest of the buzz words. A library that is just huge that you can take advantage of. Event driven model without having to write all the plumbing...
SOOOO MUCH.
What I want specifically is to stop working with klunky old ASP 3.0 and start using something that is closer in functionality to Visual Basic (if you catch my drift).
Of course I am writing alot of web apps in ASP 3.0 now but I have outgrown the scope of ASP 3.0 and am looking to evolve into something better but I know little about ASP.NET 1.x - not enough to know if it can satisfy my thirst for usefulness.
I guess I am wondering if ASP.NET 1.x is an evolutionary step above ASP 3.0 or if it is truly a revolutionary step above like ASP.NET 2.0 sounds to be...
What I read about ASP.NET 2.0 says that ASP.NET 2.0 is a revolutionary step above ASP 3.0 and I will see about beta testing it when it comes out in June. I guess I am wondering if I should skip messing with ASP.NET 1.x altogether or if I would greatly benefit from using it first and then gradually migrate into ASP.NET 2.0.
Thanks for advice so far - looking for more...
There's an ASP.Net forum, you could ask there.
I think it doesn't matter. Just matters when you want to start deploying apps. If you want to wait till sometime in 2005 before you can get anything officially supported for asp.net 2.0, then ok, wait for 2.0. If you think you want to create and deploy something before this "Unknown" release date of 2.0, then use 1.1. Anything you learn by using 1.1 won't be worthless when you move to 2.0. The only thing 2.0 will do is let you write less code for common tasks. I am excited about 2.0, but not as much as I was that asp.net 1 took over classic asp. Classic ASP is like the stone age to me when you compare it to what is currently out in asp.net.Quote:
Originally posted by Dave Sell
What I want specifically is to stop working with klunky old ASP 3.0 and start using something that is closer in functionality to Visual Basic (if you catch my drift).
Of course I am writing alot of web apps in ASP 3.0 now but I have outgrown the scope of ASP 3.0 and am looking to evolve into something better but I know little about ASP.NET 1.x - not enough to know if it can satisfy my thirst for usefulness.
I guess I am wondering if ASP.NET 1.x is an evolutionary step above ASP 3.0 or if it is truly a revolutionary step above like ASP.NET 2.0 sounds to be...
What I read about ASP.NET 2.0 says that ASP.NET 2.0 is a revolutionary step above ASP 3.0 and I will see about beta testing it when it comes out in June. I guess I am wondering if I should skip messing with ASP.NET 1.x altogether or if I would greatly benefit from using it first and then gradually migrate into ASP.NET 2.0.
Thanks for advice so far - looking for more...
Switch to either, and you will be greatly appreciative. You just need to let go of the classic asp ways, it seems too many classic asp devs want to still use the same old things they always have done. .Net radically changes things, take advantage of it. Get a good book.