Page Parser ERROR in ASP.NET

Question

0.00/5 (No votes)

See more:

Frequently i came accross a problem that is Page parse error....
to get out of this hell i used to remove inherit attribute in Page Directive.

After that it is showing compliation error???

How to solve it ???? what i have to do for the page compilation problem and page parser error tooo?????

And 1 more thing is i had written the code of a button1 click event k after after i had opened that project if i double click on that button i am going to inline coding.. How to solve it..Even though i took 1 button in that button events i doube clicked on a event still there is no use...I am redirecting to inline coding. How to solve the problem of that page. I should redirect to code behind file only

Posted 7-Apr-10 7:38am

Harish Thatha

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Gregory Gadow · Answer 1 · 2010-04-07T09:30:00

I have run into this problem when using separate code files, so I will assume that this is how you are writing your pages.

The HTML page's @Page directive uses CodeFile to tell the compiler where the file is located, and Inherits to tell the compiler what to do with it once it has been found.

You will note that the code-behind file is a partial class that, by default, inherits from System.Web.UI.Page. The class name is the same one used in the HTML page's Inherits attribute. If you are changing the page's class to something other than the default, you need to change it in the code-behind; there should be no need to change Inherits.

I expect the problem with the button is related. If you get rid of Inherits, the compiler can no longer merge the "class" of the HTML page with the partial class of the code-behind. So, the compiler will assume that all code is inline on the HTML page and act accordingly.