Windows Forms Designer CodeGen issue with SplitContainer - by Greg D

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<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 375805 Comments
Status Closed Workarounds
Type Bug Repros 3
Opened 10/15/2008 10:21:06 AM
Access Restriction Public


The designer-generated code for a SplitContainer may order the property assignments incorrectly, resulting in a failure to execute the code (An InvalidOperationException is thrown on component initialization).
Sign in to post a comment.
Posted by Greg D on 6/30/2009 at 6:23 AM
Thanks for addressing this. :)
Posted by Microsoft on 3/25/2009 at 10:15 PM
Thanks for your feedback on the .NET Framework!

We are able to reproduce the bug that you reported and consider rolling in a fix to this issue in next release if resources/schedule allow us.

Many customers have found it useful to discuss issues like this in the forums ( where Microsoft and other members of the community can suggest workarounds.

Please keep the feedback comming.

UIFx Team
Posted by Greg D on 12/1/2008 at 6:27 AM
What does "Closed (External)" mean? This has been repro'd and is a problem that exists in Microsoft code, isn't it? Is this something that just isn't going to ever be fixed?
Posted by Be the ball Danny on 11/12/2008 at 3:44 PM
Whoa this is a long-standing issue! I found posts about it going way back to March 2006 that acknowledge this as a bug! It is now Nov 2008!

This also seems like it would be a simple fix.
C'mon folks, this doesn't do a lot for the credibility of your products eg. Visual Studio and .NET frameworks, your Engineering practices, eg. Microsoft has the most resources of any software company in the world and this simple bug is not fixed for at least 2.5 years! and overall this reflects badly on Microsoft as a whole.
How many person hours to fix this bug? 1 day? 1 week? I reckon one person working a week on this is worth it. Put someone on it. Hire me if you must!
Posted by Microsoft on 10/27/2008 at 10:08 PM
Thanks for reporting the issue.

We are able to reproduce this issue in our environment.

Given the tight schedule/resources the team has for the next milestone of Visual Studio 2010, we'll look into this issue in more details later on. Shall update you when there is progress. Thank you for your patience.

UIFx Team
Posted by Microsoft on 10/22/2008 at 3:04 AM
Thanks for your feedback. We are escalating this bug to the product unit who works on that specific feature area. The team will review this issue and make a decision on whether they will fix it or not for the next release.

Thank you,
Visual Studio Product Team