Can you convince me?

[mendhak]

I've been going through a bit of ASP.NET, and I don't like the fact that there's a postback to the server for everything. (I'm aware that there's an option to disable this postback-feature).

The second thing I didn't like, is the extensive use of JavaScript.

Can you, the reader, give me some good articles, links, or arguments for ASP.NET, I would like to believe that it's better than using ASP 3.0.

Thanks.

[MarkusJ_NZ]

Well, here is a start; You can build real 3 tier applications without having to go through dll hell. If you use code behind you can reference your dlls (Business layer) in any .net program. Example was that I created a vb.net application that my clients loved. they then wanted a web version of the same thing. I just made some HTML forms and then referenced the dll's that were built in the original vb.net program and they had a web version, total time taken, 4 hours!

I like it because I can easily resue objects that I have created before. Easier to maintain because your code is in a seperate file (Code behind). User controls are similiar to include files but can raise events and do a bunch more..

When I first started using .net it was if Microsoft looked at all the crap parts of ASP and addressed them. Like I previously mentioned, no more dll hell, seperation of coding into 3 tiers and OOP (inheritance, events etc)

Basically, after spending the last 2 years doing asp.net I would never ever go back to classic ASP (which I did for over 2 years as well).

Have a play and see if it's for you

Good luck
Cheers
MarkusJ

[Memnoch1207]

I don't use any javascript on my asp.net applications. For form validation I use .NET built in required field validators.

Postback is a great feature, especially when needing to hide or show more controls depending on what the user selects.

I still like ASP (the way I did it was similar to ASP.NET's code and html separation), but I wouldn't use anything but ASP.NET to create full featured, enterprise quality web based applications. After learning ASP.NET you'll see just how lacking ASP really is.

[hellswraith]

Same thoughts as above. Just playing around with it won't help, you got to dive in. Once you do, and you learn the asp.net way to do the same things you did in asp, you won't want to go back as mentioned above.

There is no way, after using asp.net, anyone can say they would rather build a enterprise app in asp 3.0. If they did, they need to be taken out back and beaten to a pulp!

Another benefit? How bout speed! Fully compiled, not interpreted. You can cache items. Better control over security, true config file, that when you edit it, the asp.net worker process restarts by itself without disrupting users (unless you rely on session state, but now we are talking about some coding issues) and takes the changes immediately. Hmmm, tracing... Datagrids? DataSets, DataReaders, DataViews, etc...etc...etc... Validators... There is even a table object you can work with in code. Create your own controls, inherit from existing controls...
There is many options available to you now...don't know where to start or end.

[mendhak]

Thanks for the inputs everyone.

Appreciate it.