I'm just starting to learn ASP, I already know PHP and Java fairly well, so I am already familiar with basic programming concepts. I used the W3 schools tutorial as a starting point, but what other tutorials are good for a beginner who doesn't need programming 101 explained?
Also, what's the difference between ASP and ASP.NET?
I know these questions are fairly simple, but I'd appreciate any help that can be provided.
__________________
$guiness &= new sixpack();
$guiness->chug();
Honestly, unless you really need ASP for legacy apps, there is little reason to learn it. .NET is utterly and completely different. Plus, as a PHP coder, you are bound to prefer C# to VB, and Classic ASP only supports VBScript (jscript doesn't count, no one used it and there are very few examples, much less tutorials, on it).
__________________
If this post contains any code, I may or may not have tested it. It's probably just example code, so no getting knickers in a bunch over a typo, OK? If it doesn't have basic error checking in it, such as object detection or checking if objects are null before using them, put that in there. I'm giving examples, not typing up your whole app for you. You run code at your own risk.
Bored? Visit http://www.kaelisspace.com/
Thanks for your reply, I've only started with this stuff in the last few days and it's blowing my mind with what you can do. Why is ASP.net less popular than PHP, or is it? How is the server load vs. with PHP and how available is hosting and so forth?
__________________
$guiness &= new sixpack();
$guiness->chug();
Well, I do code intranet web applications, so I might be a bit biased towards enterprise level tools. I have Visual Studio and ajax.net and a ton of other tools (both official and unofficial), plus a really nice web server.
PHP is more popular because it's free, among other things. .NET is expensive to develop well (you really do need Studio to leverage the power), hosts cost more, and it is more server intensive. PHP has a huge community and lots of free and open source apps, so you rarely have to completely re-invent the wheel.
However, I would still never choose Classic ASP. If I want an app that is not .NET, non-enterprise, I'd choose, well, PHP.
__________________
If this post contains any code, I may or may not have tested it. It's probably just example code, so no getting knickers in a bunch over a typo, OK? If it doesn't have basic error checking in it, such as object detection or checking if objects are null before using them, put that in there. I'm giving examples, not typing up your whole app for you. You run code at your own risk.
Bored? Visit http://www.kaelisspace.com/
Well, I do code intranet web applications, so I might be a bit biased towards enterprise level tools. I have Visual Studio and ajax.net and a ton of other tools (both official and unofficial), plus a really nice web server.
I cannot do these things in Classic ASP (at least not without hassle or 3rd party tools):
* Multiple file uploads
* Automatic form validation
* SQL parameters (not dynamically generated sql, which is open to injection attacks)
* pretty much anything I want to do is easier and faster, since 99% of what I do deals with database actions, either query, insert, update, or delete
PHP is more popular because it's free, among other things. .NET is expensive to develop well (you really do need Studio to leverage the power), hosts cost more, and it is more server intensive. PHP has a huge community and lots of free and open source apps, so you rarely have to completely re-invent the wheel.
However, I would still never choose Classic ASP. If I want an app that is not .NET, non-enterprise, I'd choose, well, PHP.
__________________
If this post contains any code, I may or may not have tested it. It's probably just example code, so no getting knickers in a bunch over a typo, OK? If it doesn't have basic error checking in it, such as object detection or checking if objects are null before using them, put that in there. I'm giving examples, not typing up your whole app for you. You run code at your own risk.
Bored? Visit http://www.kaelisspace.com/
Since this is NOT a flame war, simply a discussion...
I also code some pretty intensive Classic ASP web applications, which do include AJAX, web-based WYSIWYG text editors, CMS, etc.
They are all encrypted and secured both on the web server and the database server using 256 AES encryption (http://www.truecrypt.org).
I can do multiple file uploads using ASP (minus the 3rd party stuff), I have coded my own Auto-form validation (NO FP-bots), and do have SQL-Injection safe dynamic SQL syntax based on forms and search fields.
The web server that I have is a Quad Xeon, so power is not an issue. I just find that Classic ASP has the same tools that .NET does IF YOU KNOW HOW TO MANIPULATE THE SYSTEM...
Now, that being said ---
Does .NET provide a better platform for some systems and groups - YES.
Does .NET allow for more robust applications - YES.
Does .NET work for everyone - NO.
PHP won't work for me in this situation either, as I am not a good PHP coder.
Just another $0.02 from another coding perspective...
Interesting.
Perhaps .NET is simply better out of the box than Classic ASP. Meaning both have good power and whatnot, but you have to do more hand-coding with classic.
Out of curiosity, how do you handle mail with classic? I'm stuck with classic for an older app I maintain, and I have tried both cdonts and cdosys, and I still am not getting errors when mail addresses bounce, yet if even one is invalid, the whole darn mail fails and nothing is sent.
__________________
If this post contains any code, I may or may not have tested it. It's probably just example code, so no getting knickers in a bunch over a typo, OK? If it doesn't have basic error checking in it, such as object detection or checking if objects are null before using them, put that in there. I'm giving examples, not typing up your whole app for you. You run code at your own risk.
Bored? Visit http://www.kaelisspace.com/
CDONTS and CDOSYS are both NT 4.0 and ASP2.0 based, both are long "gone".
I use a free emailer called ASPEmail. You can download it from http://www.aspemail.com. Supports Reply-To, Security (inc. SMTP-AUTH), CC, BCC, Encryption (but only for the paid version), Subject, Body, HTML / Text, etc.
Be happy to help you configure if you need it, but it's pretty easy.
Lastly, I learned how to use computers in DOS/UNIX, so I am used to CLIs and hand-coding everything. I still code HTML by hand. Only use FP for the color-coding.
Thanks for the tip!
What does it do if one address in the list is invalid? Return false, but still send to valid addresses, or throw an error and not send at all?
__________________
If this post contains any code, I may or may not have tested it. It's probably just example code, so no getting knickers in a bunch over a typo, OK? If it doesn't have basic error checking in it, such as object detection or checking if objects are null before using them, put that in there. I'm giving examples, not typing up your whole app for you. You run code at your own risk.
Bored? Visit http://www.kaelisspace.com/
If the address is invalid, it will throw a 550 error, on which you can tell it to either On Error Resume Next OR tell it to record the error somewhere and move on.
It's a simple DLL that gets loaded into the IIS of the box, then it's up to you to add the methods as necessary.
Depending on the reason for the mailer, I use 2 loops.
Loop 1) Pull email address. IF IsNull(email) = false THEN... Continue on to Loop 2. ELSE Movenext
Loop 2) If Valid Email, send, ELSE ON ERROR RESUME NEXT; EXIT FOR. Exits the second loop and goes to the next Email address.
But, I am also a data NaughtZ and I routinely go through and doublecheck all my entries. My forms also have an email check routine that makes sure that you are using a valid top-level domain before it lets you submit the form.
A quick little test it actually sent the mail to the valid address and sent an Undeliverable to the From address. Which is PERFECT.
Thanks so much for the link!
__________________
If this post contains any code, I may or may not have tested it. It's probably just example code, so no getting knickers in a bunch over a typo, OK? If it doesn't have basic error checking in it, such as object detection or checking if objects are null before using them, put that in there. I'm giving examples, not typing up your whole app for you. You run code at your own risk.
Bored? Visit http://www.kaelisspace.com/
Before you post, read our: 
