Compiler errors in commented JavaScript code

[=?Utf-8?B?UmljaGFyZA==?=]

Hi,

I removed some functionality from an ASP.NET 2 webpage by deleting the input
ior textbox control from the page's code. Then I commented out the JavaScript
function on the same page that referenced the deleted control, so the
commented function looks like this:

/*
function MyFunction()
{
}
*/

I'm puzzled why the compiler gives me an error in a line of code that's
inside the commented function, and references the deleted control. It
complains b/c the control doesn't exist... But the code is commented out! Do
you know why does this happens?

Thanks in advance,

Rick

[Just Me]

You will probably find that you have missed out a semicolon or brace
somewhere else in the code, this is obviously bogus as an error message in
that respect.
"Richard" <Ri*****@discussions.microsoft.comwrote in message
news:22**********************************@microsof t.com...

Hi,

I removed some functionality from an ASP.NET 2 webpage by deleting the
input
ior textbox control from the page's code. Then I commented out the
JavaScript
function on the same page that referenced the deleted control, so the
commented function looks like this:

/*
function MyFunction()
{
}
*/

I'm puzzled why the compiler gives me an error in a line of code that's
inside the commented function, and references the deleted control. It
complains b/c the control doesn't exist... But the code is commented out!
Do
you know why does this happens?

Thanks in advance,

Rick

[=?Utf-8?B?UmljaGFyZA==?=]

But the coloring code of Visual Studio shows the function in commented-out
color, then whatever is inside the function should be dismissed by the
compiler.
Also, if some semicolon or brace was missing from other code, how comes
there was no error or warning before commenting the JS function?
I've seen the ASP.NET JS debugger stepping thru commented-out JS code, and I
wonder why? Have anyone else experimented this?

"Just Me" wrote:

>
You will probably find that you have missed out a semicolon or brace
somewhere else in the code, this is obviously bogus as an error message in
that respect.
"Richard" <Ri*****@discussions.microsoft.comwrote in message
news:22**********************************@microsof t.com...

Hi,

I removed some functionality from an ASP.NET 2 webpage by deleting the
input
ior textbox control from the page's code. Then I commented out the
JavaScript
function on the same page that referenced the deleted control, so the
commented function looks like this:

/*
function MyFunction()
{
}
*/

I'm puzzled why the compiler gives me an error in a line of code that's
inside the commented function, and references the deleted control. It
complains b/c the control doesn't exist... But the code is commented out!
Do
you know why does this happens?

Thanks in advance,

Rick

[Just Me]

I tried. I cant set a break point on the commented code, nor can I
replicated your problem. You may have some corruption in the symbols
datatbase. Delete the debug stuff and rebuild it.

"Richard" <Ri*****@discussions.microsoft.comwrote in message
news:17**********************************@microsof t.com...

But the coloring code of Visual Studio shows the function in commented-out
color, then whatever is inside the function should be dismissed by the
compiler.
Also, if some semicolon or brace was missing from other code, how comes
there was no error or warning before commenting the JS function?
I've seen the ASP.NET JS debugger stepping thru commented-out JS code, and
I
wonder why? Have anyone else experimented this?

"Just Me" wrote:

>>
You will probably find that you have missed out a semicolon or brace
somewhere else in the code, this is obviously bogus as an error message
in
that respect.
"Richard" <Ri*****@discussions.microsoft.comwrote in message
news:22**********************************@microso ft.com...

Hi,

I removed some functionality from an ASP.NET 2 webpage by deleting the
input
ior textbox control from the page's code. Then I commented out the
JavaScript
function on the same page that referenced the deleted control, so the
commented function looks like this:

/*
function MyFunction()
{
}
*/

I'm puzzled why the compiler gives me an error in a line of code that's
inside the commented function, and references the deleted control. It
complains b/c the control doesn't exist... But the code is commented
out!
Do
you know why does this happens?

Thanks in advance,

Rick