Article ID: 323487 - View products that this article applies to.
This article was previously published under Q323487
This article has been archived. It is offered "as is" and will no longer be updated.
When server-side code in an .aspx page contains an at sign (@) immediately after a comment statement, the JScript .NET compiler may generate unexpected errors.
The following code demonstrates this scenario:
This problem occurs in both scenarios because of the way that JScript .NET implements preprocessor directives. The .aspx page is transformed into a JScript class file with the preprocessor set to on so that JScript can remap line numbers. This means that the "//@" characters are significant.
To resolve this problem, make sure that you are aware of how JScript .NET implements preprocessor directives when you write code in an .aspx page.
To work around this problem, you can vary the commenting style a little. However, Microsoft recommends that you not start comment statements with the "//@" characters. Only use this format for preprocessor statements.
The code that follows demonstrates how to use a version of the code from the "Symptoms" section that does not cause any errors. Also, this code includes two forms of JScript .NET conditional compilation to illustrate how JScript .NET preprocessor statements can appear with different comment statement types.
Steps to Reproduce the Behavior
For more information about JScript .NET preprocessor directives, visit the following Microsoft Web site:
Contact us for more help
Connect with Answer Desk for expert help.