Chart control fails when databound to LINQ collection - by Lachlan01

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 507920 Comments
Status Resolved Workarounds
Type Bug Repros 1
Opened 11/3/2009 10:53:46 AM
Access Restriction Public


If the new chart control is databound to an IEnumerable(Of T) that is the result of a LINQ expression, it fails at the point when it attemps to call .Reset() on the enumerator.
Sign in to post a comment.
Posted by Lachlan01 on 11/16/2009 at 2:10 PM
I see this has been closed as "By Design". Yes, I always design my software to include random bugs too...

What do you think beginners will make of this "feature" when they come to bind a Linq collection to a chart control (presumably something many .Net beginners will try to do)?? I am guessing they will be flummoxed by the vague error message and probably give up and become PHP developers.

"Your feedback enables Microsoft to make software and services the best that they can be" - Yeah right.
Posted by Lachlan01 on 11/13/2009 at 4:50 PM
Eh what? That is the most ridiculous explanation I have ever heard!

How about calling getEnumerator for each pass???!!!

This MUST be fixed before .Net 4.0 final.
Posted by Microsoft on 11/13/2009 at 2:39 PM
Thank you for reporting this issue.

DataBindTable method requires multiple passes through the data. Reset method must be supported on the IENumerable for that. As such, this is currently by design.

Posted by Microsoft on 11/5/2009 at 10:19 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Thank you
Posted by Microsoft on 11/4/2009 at 2:42 AM
Thank you for your feedback, We are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(