http://register.microsoft.com/contactus30/contactus.asp?domain=windefault
The contact us page on MS seems to be missing a closing quote 
Anyone at MS want to pass this onto the correct people?
-
Follow
Oops, something didn't work.
Sign In to be begin to follow this thread
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.Getting "follow" information
Start following this thread
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.Removing your "follow"
Setting up your "follow"
Did you know you can
sign up for email notifications?
-
MattShepherd
Ave It
-
Steve411
Me, all suited up!
Sent.
-
W3bbo
Work hard; increase production; prevent accidents, and be happy.
MattShepherd wrote:http://register.microsoft.com/contactus30/contactus.asp?domain=windefault
The contact us page on MS seems to be missing a closing quote
Anyone at MS want to pass this onto the correct people?
Why are they still using ASP3 anyway?
And more importantly... why is ASP Script Debugging enabled?
-
ZippyV
Fired Up
Looks like you don't know how big Microsoft.com really is.W3bbo wrote:Why are they still using ASP3 anyway?
And more importantly... why is ASP Script Debugging enabled?
-
Steve411
Me, all suited up!
Some guy or girl is too lazy to update the pages, or is fired by now. Who knows.
-
dnrfan
It's .NET
. wrote:And more importantly... why is ASP Script Debugging enabled?
Maybe they had it on during the 64Bit transition, and forgot to disable it, once everything worked.
-
Maurits
AKA Matthew van Eerde
W3bbo wrote:
Why are they still using ASP3 anyway?
If you use the Session object to hold user state, the transition from ASP3 to ASP.NET is a bear.
W3bbo wrote:
and more importantly... why is ASP Script Debugging enabled?
Actually "echo errors to client" is enabled - useful for troubleshooting errors in new code. Turning it off does seal a mild kind of "information disclosure" but sometimes the error troubleshooting is so valuable that it's almost worth leaving it on.
Ideally there'd be a way to specify some kind of authorization method to be able to show errors only to certain developers/testers, and not to the general public.
Thread Closed
This thread is kinda stale and has been closed but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.