View Full Version : ASP v's ASP.Net
10-24-2003, 02:06 AM
We are building a site that runs its entire contents from a database backend which will be modified through an administration section on the website. There will also be a user logon area which will allow them to access certain parts of the website and to change the look and feel of the home page including what is displayed on the website. A primary focus on the website is the security of the logged in area. I have decided that it would be best developed in ASP.Net however I am having a little bit of a problem convincing the powers that be that ASP.net is better than straight out ASP to develop this solution (I picked it for the matrix which makes writing it alot easier).
Can anyone suggest some really strong arguements as to why ASP.net is better than ASP?? (In the absence of really strong arguements I will take weak ones!!)
Thanks for all your help.
10-24-2003, 02:21 AM
I been programming in ASP and .Net.
.Net is the way to go in developing applications if you have the choice. An ASP application is messy compared to a .Net application since the code is seperated from the html.
Most larger companies are moving to .Net. The company I am contracting for is redoing all of there ASP and Confusion pages into .Net. I am having an easier time developing my application in .Net then in ASP since it is easier to reuse code.
Now people might disagree with me. .Net costs more money up front. You are going to need Microsoft's Visual Studio to do this well. If you have multiple developers, it might get messy since you need multiple places to develop.
All I can say is start out in .Net if you can, in the future your applications will be going to it. So why start behind..
I do not have any great arguments.
10-24-2003, 02:25 AM
2. Much more modular (and reusable) code (since it's object oriented)
3. Stricter code, which means cleaner code (especially with C#, although there are some exceptions where they let some sloppiness creep in, i.e. VB syntax - which means different standards for code formatting!)
1. .NET learning curve
2. IDE generates proprietary code (unless you hack it) like all Microsoft products (for instance the generous use of JScript like "document.all" which only works in Internet Exploder).
3. The price of the IDE (although it's not _required_).
It's supposed to speed up development - see #1 and #2 for the drawback there, though - in order not to pay $1000 per head (or whatever), you have to learn it really well beforehand. If you're not concerned about cross-browser compliant code, then Visual Studio.NET is the tool for you, and you only have to learn whichever language(s) you want. I prefer to write compliant code, though, which means I'm going to have to learn how to write my own framework (which I've started doing, a little bit, thanks to angiras).
I still say if you're comfortable with .NET then go with it instead of classic ASP though. I definitely prefer OOP to linear programming personally, anyway. I get to do to little of it at this point. :)
10-24-2003, 02:26 AM
Wow I posted that while Alien51 was posting apparently. Looks like we agree on a lot of things. :D
10-24-2003, 02:33 AM
whammy, you brought up a good point on strictness....
Yeah with .Net, you will get murdered if you have a little mistake...Asp can be rough, but .net needs every variable accounted for and a lot of the build in functions need very strict. If it is not Int32 then it will not work.
All I can say is today, in 1 hour I built a scheduling Calendar that pulled information from a database. It would have taken me a full day to do it in ASP.
I been coding .Net for about a month, ASP over a year....I can do more in .Net then with ASP. Hardest part was to get the project started.
10-24-2003, 03:15 AM
I thought you were a PHP guy. :P
Most of the "little mistakes" in .NET can be figured out rather easily though, as long as it's a syntax error. :)
I know what you mean though, I have built a few console and windows apps that are pretty cool, although simple, in .NET (using C#).
I still have much to learn regarding the .NET framework - not the language syntax or logic (or even OOP). That stuff is pretty simple, it's Microsoft's implementation of it that throws me - and as you can see from the apps I've messed with, the web stuff is the worst. I'm still trying to figure out how to get .NET to generate code that is compliant, but I WILL figure it out... to me Visual Studio .NET is very similar to FrontPage when it comes to code. :mad:
10-24-2003, 03:27 AM
I am working on a php aim-bot that is a bartender......
Been to lazy to keep updating the database for it.......
Another Plus is that you can use many languages with .NET....VB,C#,etc..
10-24-2003, 03:30 AM
LOL, you sound like me... not enough time to learn everything you need to. :(
10-24-2003, 02:45 PM
Here is some info:
There is a learning curve but in the long run you would be a lot better with .net. It is a lot easier coding with objects then writing redundant procedural vbscript/asp code.
10-24-2003, 02:49 PM
this company xhtmlwebcontrols (http://www.xhtmlwebcontrols.net/) has tried to rewrite all ... for xhtml compatibility
10-24-2003, 04:53 PM
There is one extremely good reason to use ASP.NET instead of ASP that I haven't seen. ASP is obsolete, it's been replaced by ASP.NET and while ASP.NET will get new features and be supported well into the future the clock is now ticking on ASP support, expect bug fixes only from now on.
To give your application a longer future, you need to go with the current development tools. Also note that the .NET runtime environment has already had several releases and that the current development tools are in their second generation too. This isn't a new technology any more, it's a tried and proven development system with wide support.
10-24-2003, 08:27 PM
yes Net 2.0 Beta 1 is allready or very soon avalaible