Quote:
Originally posted by lEricPl
I still use Stored Procedures for all database transactions...
If you have written in asp, ASP.NET will blow your mind.
You can do SO much more.
Basically an ASP.NET Webpage can do anything a regular desktop application can do.
Since it's written in a real programming language like C# or Visual Basic .NET, you can either build a Web Page or Desktop application to do what you want. If you want to turn the functionality of your webpage into a desktop app. or vice versa, just copy the methods. It's that easy.
ASP.NET is something totally new. It makes asp look like childs play.
|
That's very interesting. I'm not sure if it'll help or hurt the web site, since I prefer to use my RAM on the database, where most of the serious work is done (my sites are the only things that I still program for). I wouldn't move code into dll's unless there was a serious performance improvement, since performance of cached ASP pages + cached DB results is pretty good now. Still, my bottleneck would be the DB, so I'm not sure if ASP.NET would help. Although, if I could do something on the fly that I currently do with an AT job and a VB .exe that I wrote, THAT would be cool... can't talk about it though, top secret.
I'll play with .Net on my own for a while. It's still much too new to put on my server. My server's rock solid, and I'd hate to fuck it up!