Hi,
I know there is a performance issue in .NET 2.0, and it can be fixed by using BindingSource. Is this still necessary in .NET 3.5?
Hi Jason,
You are correct, we did that to work around the issue. You would only need to use a BindingSource in the case where you are using something other than the UltraDataSource.
In any case, like I said, if you were experiencing this problem, it would be obvious immediately. If you can run your application, select rows in the grid, and expand rows, then you don't have to worry about it.
Hi Mike,
I never have issue with the grid. The reason I am asking is because I see this in the doc.
http://help.infragistics.com/NetAdvantage/WinForms/2010.1/CLR2.0/?page=Win_Known_Issues.html
Since it's an issues in .NET 2.0, I am wordering does it get fixed in .NET 3.5? Also, in the source code. In the UltraDataSource.GetRelatedCurrencyManager(string dataMember) method, an UDSBindingSource instance is used, and this is inherited from BindingSource. It looks like the UltraDataSource is using BindingSource internally already. I think it may be redundant if I bind the UltraDataSource to BindingSource again, as suggested in the above link.
Regards,
Jason
The performance issue you are probably referring to is an issue with the BindingManager in DotNet. I'm not sure exactly what the issue is or under exactly what circumstances it occurs, though.So it's impossible to say if this was fixed.
But it's very easy to test. If you bind the grid to a data source and you can expand rows and select rows, then you are not having a problem. If you are experiencing this problem, you will know it, as the grid becomes almost completely unresponsive.