我的工作在C＃.NET程序WinForms应用程序，对.NET 3.5框架运行。在这个程序，我设置了一个的DataColumn 在数据表，像这样的.EX pression成员

I am working with a .NET WinForms app in C#, running against the 3.5 .NET framework. In this app, I am setting the .Expression member of a DataColumn in a DataTable, like so:

DataColumn column = dtData.Columns["TestColumn"];
column.Expression = "some expression";

第二行，在那里我居然设置防爆pression ，有时会导致以下异常：

The 2nd line, where I actually set Expression, will sometimes result in the following exception:

FileName=
LineNumber=0
Source=System.Data
TargetSite=Int32 RBInsert(Int32, Int32, Int32, Int32, Boolean)
System.InvalidOperationException: DataTable internal index is corrupted: '5'.
   at System.Data.RBTree`1.RBInsert(Int32 root_id, Int32 x_id, Int32 mainTreeNodeID, Int32 position, Boolean append)
   at System.Data.RBTree`1.RBInsert(Int32 root_id, Int32 x_id, Int32 mainTreeNodeID, Int32 position, Boolean append)
   at System.Data.Index.InitRecords(IFilter filter)
   at System.Data.Index.Reset()
   at System.Data.DataTable.ResetInternalIndexes(DataColumn column)
   at System.Data.DataTable.EvaluateExpressions(DataColumn column)
   at System.Data.DataColumn.set_Expression(String value)

没有察觉没头没脑至于何时会发生的错误;在加载相同的数据集，它可能工作正常，但随后重新加载它会失败，反之亦然。这使我认为这是关系到一个竞争条件，在另一次写操作发生在数据表因为我试图修改其列。但是，与数据表 S中的code是的没有的多线程，运行仅在UI线程。

There is no perceptible rhyme or reason as to when the error will occur; in loading the same data set, it may work fine but then reloading it will fail, and vice versa. This leads me to think it is related to a race condition, where another write operation is occurring on the DataTable as I'm trying to modify one of its columns. However, the code relating to DataTables is not multi-threaded and runs only on the UI thread.

我已经在网上搜索和Microsoft论坛的，有很多讨论和混乱在这个问题上。回来时，这个问题在2006年首次报道时，想到的是，这是在.NET框架中的缺陷，并有发布了一些假想的修复程序是presumably滚入更高版本的.NET Framework。然而，人们报告好坏参半的结果在应用这些修补程序，这已经不再适用于目前的框架。

I have searched the web and Microsoft forums, and there is much discussion and confusion over this issue. Back when the issue was first reported in 2006, the thought was that it was an flaw in the .NET framework, and there were some supposed hotfixes released that were presumably rolled into later versions of the .NET framework. However, people have reported mixed results in applying those hotfixes, which are no longer applicable to the current framework.

另外prevailing理论是，有在数据表这虽然看似无害，其实是写操作操作。例如，创建一个新的数据视图一个基于数据表实际上是对表本身的写操作，因为它创建在数据表供以后参考的内部指标。这些写操作不是线程安全的，所以有时会发生竞争状态导致了无螺纹安全写入与我们的数据表的访问恰逢。这反过来，使数据表的内部索引被损坏，从而导致异常。

Another prevailing theory is that there are operations on the DataTable which, though seemingly innocuous, are actually write operations. For example, creating a new DataView based on a DataTable is actually a write operation on the table itself, because it creates an internal index in the DataTable for later reference. These write operations are not thread-safe, so it sometimes happens that a race condition leads to an unthread-safe write coinciding with our access of the DataTable. This, in turn, causes the internal index of the DataTable to become corrupted, leading to the exception.

我试图把周围每个数据视图创作中的code 锁定块，但正如我前面所提到的，code利用数据表没有螺纹，而锁定取值都没有效果，在任何案例。

I have tried putting lock blocks around each DataView creation in the code, but, as I mentioned before, code utilizing the DataTable is not threaded, and the locks had no effect, in any case.

有没有人看到了这一点，并成功地解决了/它周围的工作？

Has anyone seen this and successfully solved / worked around it?

没有，遗憾的是我不能。加载数据表已经发生的时候，我得到了保持它适用防爆pression到它的DataColumn的之一。我可以删除列，然后使用code您建议重新添加，但有一个特别的原因，将解决内部索引损坏问题？

No, unfortunately I can not. Loading the DataTable has already occurred by the time I get a hold of it to apply an Expression to one of its DataColumn's. I could remove the column and then re-add it using the code you suggested, but is there a particular reason why that would solve the internal index is corrupted problem?

推荐答案

我刚做了同样的问题，在导入行，因为它似乎，调用 DataTable.BeginLoadData 前加入固定为我。