I have developed a set of routines to compute certain statistics.
Because some of these computations are rather involved, I have
designed the relevant properties so that a statistic is computed the
first time it is encountered, that value is saved, and the previously
saved value is retrieved the next time the relevant property is
accessed.

A simple example: The Total property returns the total of a set of
numbers. The first time the Total property is evaluated, the numbers
are added together, and the result is stored. The next time the Total
property is accessed, the previously computed result is returned. Here
is the code --

        public double Total
        {
            get
            {
                if (!total.IsComputed)
                {
SET BREAKPOINT HERE =>            total.Value = 0.0d;
                    foreach(double d in dataList)
                    {
                        total.Value += d;
                    }
                    total.IsComputed = true;
                    return total.Value;
                }
                else return total.Value;
            }
            set
            {
                total.IsComputed = true;
                total.Value = value;
            }
        }

The problem is that if I set a breakpoint in the code where
total.Value is first computed and then run the debugger, the debugger
never reaches the breakpoint because Visual Studio has already
evaluated the property Total. When I step through the program, the
debugger always evaluates total.IsComputed as "true" and skips to the
"else return total.Value" statement.

Is there any way, by means of an attribute or otherwise, the prevent
Visual Studio from evaluating the Total property until the program is
running in the debugger?