Problem with proxied classes

Nissim · **Joined:** Sat Jul 09, 2005 1:17 pm **Posts:** 17

Hi

I have a weird problem. I've noticed that for some of my proxied objects the underlying private variables of the public virtual properties don't have values, and yet the properties return correct values.
How can this be explained? and the behavior is inconsistent and dependent on a particular sequence of steps that I can explain and provide a log file later upon request.

Thanks

KPixel · **Posted:** Sat Sep 03, 2005 9:24 am

This is how proxy objects works, virtual members calls are intercepted to return the right values.
So you should not use private members... (even in virtual members)

Nissim · **Joined:** Sat Jul 09, 2005 1:17 pm **Posts:** 17

Hi,

Do you mean that instead of using properties in my class I should be using public variables?

KPixel · **Posted:** Wed Sep 07, 2005 11:42 am

Nissim wrote:

Do you mean that instead of using properties in my class I should be using public variables?

You should use virtual members; I am not sure if they have to be public/protected...
By "members" I mean properties; but I think it should also work with fields.

Nissim · **Joined:** Sat Jul 09, 2005 1:17 pm **Posts:** 17

What do you mean? I don't understand. I have public virtual properties. Here is an example:

private string m_comment;

public virtual string comment
{

get {return m_comment;}
set {m_comment = value;}
}

Are you saying that the field m_comment should be public or are you saying that I should just use a public m_comment without tying it to a property?

luggage · **Posted:** Wed Sep 07, 2005 1:19 pm

In that example, you should access the public Comment property only, never the private member. This will ensure that the proxy does it's job.

example:

Code:

public void ClearComment()
{
   m_comment = string.Empty;  //Bad, this will not flow through the proxy properly
}

public void ClearComment()
{
   Comment = string.Empty;  //Good
}

By the way, capitalize your public properies:

Code:

public virtual string Comment { get { ... } set { ...} }