Search

System.Windows.Forms.DataGridView.RefreshColumns() Inefficiency by thoshaw

Closed
as Won't Fix Help for as Won't Fix

1
0
Sign in
 to vote
Type: Bug
ID: 776261
Opened: 1/10/2013 9:07:56 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
The System.Windows.Forms.DataGridView.RefreshColumns() method calls boundColumns = this.dataConnection.GetCollectionOfBoundDataGridViewColumns() even when AutoGenerateColumns is false. This causes the instantiation of numerous DataGridViewColumn objects that simply fall out of scope. It would seem like this call should be moved inside the AutoGenerateColumns check.
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

.NET Framework 4.0

Steps to reproduce

Simply set an instance of DataGridView.DataSource equal to a valid data source when DataGridView.AutoGenerateColumns = false and walk the code into DataGridView.RefreshColumns().

Product Language

English

Operating System

Windows 7 SP1

Operating System Language

English

Actual results

The call to this.dataConnection.GetCollectionOfBoundDataGridViewColumns() is made even though this.AutoGenerateColumns = false.

Expected results

I would expect the call to this.dataConnection.GetCollectionOfBoundDataGridViewColumns() to be bypassed if this.AutoGenerateColumns = false.
File Attachments
File Name Submitted By Submitted On File Size  
DataGridViewPerf.zip thoshaw 1/11/2013 46 KB
Sign in to post a comment.
Posted by Microsoft on 1/21/2013 at 10:40 AM
Thank you for reporting this issue. Customer feedback is a critical part of a successful, impactful software product. Unfortunately another part is the reality of schedules and the need to prioritize investments according to the objectives of the product. We have evaluated the issue that you have reported and at this point in the product's lifecycle, it does not meet the criteria to be addressed. This evaluation is carefully done and considers many aspects including the cost of the fix, implications of the change, and the number of reported instances of the issue.
Many customers have found it useful to discuss issues like this in the forums (http://www.microsoft.com/communities/forums/default.mspx) where Microsoft and other members of the community can recommend ways of achieving the behavior you are interested in.

Thank you,
The Windows Forms Product Team
Posted by Microsoft on 1/16/2013 at 2:06 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by thoshaw on 1/11/2013 at 9:57 AM
I've attached a demo project. If you profile this application, you'll see that 50 DataGridViewTextBoxColumns are being instantiated in the bowels of the framework only to be discarded since DataGridView.AutoGenerateColumns is false. This looks to simply be an inefficiency in the framework. There's nothing erroneous displayed to the end user.
Posted by Microsoft on 1/10/2013 at 6:00 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting a demo project. Please submit this information to us within 4 business days. We look forward to hearing from you with this information.
Posted by Microsoft on 1/10/2013 at 9:51 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.
© 2013 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement