[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 232
  • Last Modified:

ASP_DEBUG_INFO metafile

When I view the source on any asp page in one particular application I'm working on I see that the first several lines have this metafile inserted first which includes the term ASP_DEBUG_INFO followed by may lines of numbers.  All of this is surrounded by regular html comment tags.  

I didn't put this in on purpose but I'm thinking VI's debug tools did.  It seems that when an error occurs in my asp pages the typical error page (the one which indicates what type of error and what line, etc.) doesn't show up.  This "bugs" me since I rely heavily on the hack and detect method of debugging alot more than the debugging tools that come with VI.  Probably because I am still learning those tools and am not too comfortable with them.

I want to learn how to get rid of these lines.  Any help out there?
0
beaudetious
Asked:
beaudetious
  • 4
1 Solution
 
DreamMasterCommented:
Following is an excerpt of a Microsoft page that holds the solution to this very problem... ;-)

SYMPTOMS
When you view or debug an Active Server Pages (ASP) page, you may notice that the following tag is inserted into the resultant HTML at the top of your page:

<!-- METADATA TYPE="ASP_DEBUG_INFO" -->
When this tag is inserted into the resultant HTML, it may cause problems in the following scenarios:
When you generate XML in your ASP page and send the XML to the client rather than HTML.


When you use the Response.BinaryWrite method to stream binary data to the client (for example, a Microsoft Excel document).





CAUSE
ASP sends down this tag when the following two conditions are met:

The Enable ASP client-side script debugging flag is enabled for the Web application.


An ASPCLIENTDEBUG cookie is present on the client that makes the request.


Typically, when you use automatic debugging with Visual InterDev 6.0, both of these conditions are met. The Visual InterDev debugger requires this tag at run time to automatically map breakpoints in the client script.



RESOLUTION
To resolve this problem, use one of the following methods.

Method 1
Disable the Enable ASP client-side script debugging flag as follows:
In the Internet Services Manager, right-click the Web application with which you are currently working, and then click Properties.


Click Configuration.


On the App Debugging tab, clear the Enable ASP client-side script debugging check box.


Method 2
Delete the ASPCLIENTDEBUG cookie from your client computer as follows:
On your computer, search for a file named username@applicationname*. For example, if the user name is "johndoe" and the application is named "myapplication," search for the johndoe@myapplication* file.


After you locate the file, delete it.


NOTE: If you need to debug in the above-mentioned scenarios, you must manually debug the application.

Cheers,
Max.
0
 
DreamMasterCommented:
This should help you beaudetious... if you need any more help please let me know...

Max.
0
 
beaudetiousAuthor Commented:
Max:

Excellent work!!!  Thanks for the info.  I previously searched Microsoft Knowledge Base but came up empty.  Would you please send me the article #?

Brian
0
 
DreamMasterCommented:
I'll have a look at that again tomorrow...am now home and ready to go to sleep...thanks for the grade A...

Max.
0
 
DreamMasterCommented:
See...I knew I had forgotten something and when I looked into my email when I came home I noticed this Good Answer email and remembered what I promissed...

Well..here it is...

http://support.microsoft.com/support/kb/articles/Q297/9/95.ASP

Cheers,
Max.
0

Featured Post

Take Control of Web Hosting For Your Clients

As a web developer or IT admin, successfully managing multiple client accounts can be challenging. In this webinar we will look at the tools provided by Media Temple and Plesk to make managing your clients’ hosting easier.

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now