Search

VS.NET 2010 and VS.NET 2012 crash when copying/altering BindingSource with System.Type as DataSource by Frans Bouma - Solutions Design bv

Active

1
0
Sign in
to vote
Type: Bug
ID: 777877
Opened: 1/30/2013 5:19:20 AM
Access Restriction: Public
0
Workaround(s)
1
User(s) can reproduce this bug
When copying or altering a BindingSource control on a Windows Forms user control or form in a .NET 4.0 Windows Forms project which has System.Type set as DataSource, it will crash VS.NET 2012 (StackOverflow exception). VS.NET 2010 will also crash with the same code if .NET 4.5 is installed.

On a system with .NET 4.0 installed and not .NET 4.5 installed, this works OK in VS.NET 2010.

Debugging the crash suggested a System.StackOverFlowException. It's likely this is caused by the fact in .NET 4.5 System.Type has new subtypes, while it's an in-place install over .NET 4.0, so it will likely affect code which expects .NET 4.0 class hierarchies but gets .NET 4.5 class hierarchies, but that's a wild guess.
Details (expand)

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

Visual Studio 2012

What category (if any) best represents this feedback?

 

Steps to reproduce

Create Windows Forms project (e.g. C#) for .NET 4.0
Add Project Data Source to Object -> System.Type
Add BindingSource to the Windows Forms project's windows form (or add new user control and add it to that)
Set BindingSource's DataSource property to the Project Data Source we created earlier, namely the System.Type one.
Select BindingSource control and press cntrl-C
Alternatively, it might very well be VS.NET already crashed when setting the DataSource property or when you try to save the form.

Reproducible every time.

Product Language

English

Operating System

Windows 8

Operating System Language

English

Actual results

Crashing VS.NET 2012

Expected results

The BindingSource definition being copied to the clipboard or its BindingSource property being set.

Locale

 
File Attachments
File Name Submitted By Submitted On File Size  
634953278200190152.zip (restricted) 2/1/2013 -
Sign in to post a comment.
Posted by Frans Bouma - Solutions Design bv on 2/1/2013 at 6:23 AM
I found the location, and have attached a zip file with the one which walks you through all the steps to reproduce it. Not visible to others outside MS. If you don't see the file, please let me know.
Posted by Frans Bouma - Solutions Design bv on 2/1/2013 at 6:16 AM
I tried the extension, recorded a repro twice, but it fails to upload it, it complains about some error, not saying what error, nor does it allow me to re-upload the recorded files (I have no clue where they are, there's no indication where they're located).

Could someone tell me where these files are located, and update the extension to allow one to re-upload the files and at least show more info about the error? If I know where the files are located I can manually attach them.

Anyway, anyone following the simple steps I described will immediately run into the crash when he tries to save the form.
Posted by Microsoft on 1/31/2013 at 12:00 AM
Hi Frans,

Thanks for your feedback. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please use Visual Studio 11 Feedback Tool to collect steps while you're repro'ing the issue?

Visual Studio now has an extension called Visual Studio 11 Feedback Tool , available on the VS gallery(http://visualstudiogallery.msdn.microsoft.com/f8a5aac8-0418-4f88-9d34-bdbe2c4cfe72).

The extension allows you to
1.    upload files,
2.    collect trace and dump files
3.    collect steps while you're repro'ing the issue, as well as
4.    SQM logs about VS extensions installed
5.    System details (in DxDiag output)

We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 1/30/2013 at 5:49 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.