我们遇到了，我们遇到了问题，调试一个奇怪的错误。

We have run into a strange bug that we're having problems debugging.

我们有一个使用微软CAB，DevEx preSS组件和.Net 3.5 MDI工作区。

We have a MDI workspace that uses Microsoft CAB, DevExpress components, and .Net 3.5.

如果在工作区中的用户打开两个窗口，每个包含用户控件绑定到两个不同的数据模型，然后最小化他们两个，第一个窗口最小化是得到它的当第二个最小化绑定字段清除。

If users open two windows in the workspace that each contain a UserControl bound to two separate data models, then minimize both of them, the first window to minimize is getting it's bound fields cleared when the second one minimizes.

在 .Equals 和 .GetHash code 数据模型的方法已经这样既覆盖数据模型被认为是相等的。如果我们改变所以他们是独一无二的，我们没有得到这种行为。

The .Equals and .GetHashCode methods of the data model have been overridden so that both data models are considered equal. If we change that so they are unique, we do not get this behavior.

下面是一些例子伪code显示问题

Here's some example pseudocode showing the problem

var a = new MyWindow();
a.DataModel = new SomeClass(123);
a.ShowInMdiWorkspace();

var b = new MyWindow();
b.DataModel = new SomeClass(123);
b.ShowInMdiWorksace();

a.Minimize();

// If SomeClass.GetHashCode() is overwritten to consider two objects  
// as equal based on the value passed in, then the data bindings for A
// get cleared on this call. If SomeClass.GetHashCode is unique, then 
// this problem does not happen.
b.Minimize();

下面的调用堆栈时，第二个窗口被最小化的：

Here's the Call Stack when the second window gets minimized:

在上面的堆栈跟踪的 EndEditSession（）调用，它调用 EndEditSession 的第二个的窗口最小化，而由当时的堆栈跟踪获取过去 [外部code] 到的OnChange断点我已经设置，它被烧成在变革方法的第一的窗口。

At the EndEditSession() call in the stack trace above, it is calling EndEditSession for the second window minimized, while by the time the Stack Trace gets past the [External Code] to the OnChange breakpoint I have set, it is firing the change method in the first window.

EndEditSession（）是自定义的东西，我们已经实现了它看起来像这样

EndEditSession() is something custom we have implemented which looks something like this

protected void EndEditSession()
{
    IBindingValue bv = null;

    if (_bindingValues == null)
        return;

    if (_data != null)
    {
        foreach (KeyValuePair<string, IBindingValue> kvp in _bindingValues)
        {
            bv = kvp.Value;
            if (bv.IsBindable)
                ((PropertyManager)bv.Component.BindingContext[_data]).EndCurrentEdit();
        }
    }

}

_bindingValues​​ 被填充当用户控件初始化其数据绑定。密钥字段绑定控件的名称，值字段是存储有控制本身，它的名称，绑定值和默认值的定义对象。 bv.Component 返回控件的绑定设置，这在我的测试的情况下是一个定制的DevEx preSS LookupEdit

_bindingValues gets populated when the UserControl initializes its data bindings. The key fields are the name of the bound control, and the value fields are a custom object which stores the control itself, its name, its bound value, and default value. bv.Component returns the control that the binding is set on, which in the case of my testing is a customized DevExpress LookupEdit

_data 包含了数据模型中的用户控件，我可以验证它被设置为实例第二个窗口。