Organizational Advantages of ASP.NET

I was wondering if anyone could help me. Up until now, I've been using ASP/VBScript to connect my company's webpages to our access databases, and it has worked quite well for us. Lately, I've been reading about asp.net and how it makes it simple to segregate code from html, and all of the technical advantages of what asp.net has to offer.

Since I'm not a programmer by trade, this shift from asp to asp.net is leaving me a bit more than perplexed. I'm not used to object-oriented programming for the web. So, I've been checking into formal training on the subject. The only problem is that my director won't justify spending the money on a formal training unless I can prove that it will benefit the company. Since asp/VBScript will do everything we currently need, I'm having trouble justifying this training.Can anyone list any "organizational benefits" (rather than "technical benefits" -- which is all I've really found) of asp.net over classic asp.

Thanks for all the help

One good advantage is the use of code behind and user controls. It eliminates spaghetti code. You truly seperate html from programming logic. If you have several people working on a project (html coder and a programmer), both can work on their parts of the project without breaking something. However, if you do everything, there really is no advantage in this type of organization.

Unfortunatly, I'm currently the only person doing any kind of web programming or design at my place of work. But the way you state that, I think I can turn it into something useful. We house multiple projects, each needing its own web presence. I can give more design responsibility to project coordinators and concentrate solely on application development.

Besides that, here is actually what I've come up with so far:

1. Modular development & code seperation lead to fewer code revisions. This aspect also leads to less time to initial completion.

2. What time that is spent on code revision is negligable, as I don't have to sift through design elements in my scripting.

3. Design and code revisions are both easier to accomplish, as (again) design and code are seperated. Also, server controls are very customizable, both at design and run-time.

That's pretty much all I can come up with. If anyone can think of anything I'm missing, I'd appreciate hearing about it.