Problem with lazy loading implementation

Question

I have implemented lazy loading in my program. it's done through a proxy class like:

class Order
{
   public virtual IList<Item> Items {get; set;}
}

class OrderProxy
{
   public override IList<Item> Items 
   {
      get
      {
          if (base.Items == null)
              Items = GetItems(base.OrderID);
          return base.Items;
      }
      set { base.Items = value; }
   }
}

The problem is that whenever I instantiate proxy class, without even touching the Items property, it tries to load Items!
As you may know, I want to instantiate proxy class and return the instance to BLL instead of domain object itself.

What's the problem?
Does .NET CLR access(read) properties in a class, when it's instatiating the class?
Any other methods?

Thanks

Assuming no code is attempting to set into Items on construction, does the fact that Items in the base class is an auto-implemented property have anything to do with this behaviour? — Adam Houldsworth
– Adam Houldsworth, Commented Dec 23, 2010 at 16:57
Never mind, just tried this in my own sample project and my items doesn't get instantiated. However, whether you test its value or view it in the debugger, it will fetch. — Adam Houldsworth
– Adam Houldsworth, Commented Dec 23, 2010 at 17:01

k3b · Accepted Answer · 2010-12-23 16:55:14Z

4

Sometime it is the debugger-preview that triggers the loading

answered Dec 23, 2010 at 16:55

k3b

14.8k7 gold badges55 silver badges88 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Wim Coenen Over a year ago

+1 good point. This behavior can be controlled with Tools - Options - Debugging - General - "Enable property evaluation and other implicit function calls"

Mehran Over a year ago

Thanks,I think that's the answer

Wim Coenen · Accepted Answer · 2010-12-23 16:53:10Z

4

what's the problem? Does .NET CLR access(read) properties in a class, when it's instatiating the class?

No.

To see which code is accessing the property, simply put a breakpoint in there and look at the stack trace window (Debug menu - Windows - Call Stack).

answered Dec 23, 2010 at 16:53

Wim Coenen

67k14 gold badges162 silver badges253 bronze badges

Collectives™ on Stack Overflow

Problem with lazy loading implementation

2 Answers 2

2 Comments

Comments

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

Comments

Related