ASP / Code View Issues

Question

Good morning to all of you.
I have used Dreamweaver at work for many years to manage our extensive classic ASP applications.  I like the interface but I have found that programming with a darker background is much easier on my eyes.  I found some dark code view background profiles that covered HTML/PHP/CFM files and loved how they looked on those type of projects but they were lacking ASP support.  I took the time to create the profile for ASP Vbscript and then copied it to ASP Javascript so no matter what language I'm in they will be the same.  It looks great but I have to fake out Dreamweaver to force it to view the code in the right file type.  It seems Dreamweaver is pretty inconsistent with determining the ASP file/language type.
If I use:
<% @Language="vbscript" %>
It will load the correct profile and things seem well.  If I don't do that, I not only don't get the correct coding but the commenting doesn't look right either.  I have to end every line with that has a comment a single apostrophe as well to keep it from getting the code view appearance looking wrong.
This hackish attempt above works but it bad style.  You can't define this more than once in a document and would be problmenatic if you use include files (who doesn't really?)...
I almost exclusively code ASP-VB.  How can I make Dreamweaver read ALL ASP files in this the ASP-VB format by default?  As it sits right now, it's totally wrong.
Thanks in advance,
Joe Jenkins

Answer 1

It's not so much doing with the actual language. It's the fact that Dreamweaver doesn't recognize that the .asp file is indeed ASP so it applied the wrong code view coloring, rules for comments and no suggestive code.  If I am drop the language in the top of the file, this corrects THAT file but if you have multiple include files and you push it to your server like this (wish this language definition in each of those files) you will get an error from the server for multiple definitions.
Exmaple:
Top of main file:
<%@Language="vbscript" %>
<!--#include virtual="../aspinclude/dbconnect.asp"-->
<!--#include virtual="../aspinclude/utils.asp"-->
<!--#include virtual="../aspinclude/utils_workorders.asp"-->
Top of an included file:
<%@Language="vbscript" %>
<%
dim StartTime : StartTime = Timer()
Session.Timeout = 120
If you tried to fake out the code view by doing that to MAKE it view the file as an ASP-VB file, it's not only bad practice, it's redundant and the server will cough at it giving you an error that simply tells you that the declaration has to be on the first line.  This is true, in the main file, but the included file would then put it inline on whatever line it happens to be as part of the compiled page which is invalid.
The main problem is that I have to fake out the code view by defining the language on every page I edit to get text-coloring right and other features.  The question is can I make it always default to maybe ASP-VB unless explicitely defined something else like @Language="Javascript" ?
Joe Jenkins