471,321 Members | 1,860 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

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

private field is never 'assigned' ; force comiler to stop complaining?

Hello,

Not sure if this is exactly the right place to post this, so let me
know if there is a more relevant group.

I have a series of private members in my class, none of which are
'assigned to' as far as the compiler can tell. They *are* set, just by
reflection in a base class. Each member is tagged with an attribute
that tells the binder to do this, so I was hoping to use this as a
basis for supressing or eliminating the compiler warning.

I know that the ASP.Net controls, when you put them in something that
derives from Page, do not complain about this. Perhaps this is a
starting point?

The code currently looks like this :
[BindForMe] protected Textbox txtBox = null;

The null is required, or the error shows up.

Not even sure exactly what question to ask, so any help would be much
appreciated.

Thanks,
Andrew Backer

Jul 22 '05 #1
0 849

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Old Timer | last post: by
6 posts views Thread by Sahil Malik [MVP] | last post: by
10 posts views Thread by Gandalf | last post: by
3 posts views Thread by John Salmon | last post: by
6 posts views Thread by marktxx | last post: by
reply views Thread by rosydwin | 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.