I am using a custom page base class (BasePage), derived from System.Web.UI.Page.
The class has some public properties which should be accessible from the .aspx @Page directive once I have added the CodeFileBaseClass attribute to set the base class to BasePage.
R# marks up the all (valid) BasePage public property references in the @Page directive as errors.
E.G. BasePage has a public string property called Foo. I should be able to do the following:
R# incorrectly marks the Foo attribute as invalid.
See attached solution for full example.
Description
I am using a custom page base class (BasePage), derived from System.Web.UI.Page.
The class has some public properties which should be accessible from the .aspx @Page directive once I have added the CodeFileBaseClass attribute to set the base class to BasePage.
R# marks up the all (valid) BasePage public property references in the @Page directive as errors.
E.G. BasePage has a public string property called Foo. I should be able to do the following:
Re: #23909- Incorrect error highlighting in asp when using CodeFileBaseClass
It is a VS, who highlights Foo as unresolved. R# highlights the file as valid, for we do not support custom page attributes.
You may covert the request to a feature request to support them, though.
Sergey Coox - 09 Aug 06 12:07 Re: #23909- Incorrect error highlighting in asp when using CodeFileBaseClass
It is a VS, who highlights Foo as unresolved. R# highlights the file as valid, for we do not support custom page attributes.
You may covert the request to a feature request to support them, though.
It is a VS, who highlights Foo as unresolved. R# highlights the file as valid, for we do not support custom page attributes.
You may covert the request to a feature request to support them, though.