471,082 Members | 727 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,082 software developers and data experts.

Build Error in Inherited Forms

I have a Studio issue where I have a base Form - FormA. FormB inherits from
FormA. I have a property or a control in FormB called Prop1 that was NOT
inherited from formA.

Sometimes, when I edit a completely unrelated class, I get the following
build error:

Name Prop1 is not declared.

The file name is the file for FormB.

If I close the solution and open the solution back up, everything compiles.
This occurs even without ever touching the source for FormA or FormB.

Recreating the formB doesn't fix the issue either.

Does inheritance just not work that reliably in .Net 2003?
Jul 21 '05 #1
2 1217
Sean,
Does inheritance just not work that reliably in .Net 2003?


I think I can understand your question, however this addition to your
question makes that I do not understand what you are really asking.

Do you want a solution for your problem or an answer on the last question?

As an answer on that, until now I have not seen any problem.

Cor
Jul 21 '05 #2
I have had the same thing happen for quite a while. Got used to closing and
reopening the solution whenever the build failed. Typically there are several
forms with "undeclared" controls. On at least one occasion I opened one of
those forms in the designer and found the "undeclared" control had in fact
disappeared. However, after closing and reopening the solution the control
reappeared.

Have you found out any more about this issue since your original post?

"Sean" wrote:
I have a Studio issue where I have a base Form - FormA. FormB inherits from
FormA. I have a property or a control in FormB called Prop1 that was NOT
inherited from formA.

Sometimes, when I edit a completely unrelated class, I get the following
build error:

Name Prop1 is not declared.

The file name is the file for FormB.

If I close the solution and open the solution back up, everything compiles.
This occurs even without ever touching the source for FormA or FormB.

Recreating the formB doesn't fix the issue either.

Does inheritance just not work that reliably in .Net 2003?

Jul 21 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

10 posts views Thread by Douglas Buchanan | last post: by
1 post views Thread by Boniek | last post: by
reply views Thread by Robert Smith | last post: by
2 posts views Thread by Sean | last post: by
4 posts views Thread by asad.naeem | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.