Home Dashboard Directory Help
Search

Lightswich, VS 2012 PRO: add item with same name crash VS by Ragoran


Status: 

Closed
 as Fixed Help for as Fixed


1
0
Sign in
to vote
Type: Bug
ID: 778887
Opened: 2/9/2013 9:17:44 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

I added a new Modal window in an existing form.
By error, I changed the nameif thie new item to the same name as another item. I received an error message saying it is not correct, but then name has been changed.

I now have two items with the same key.

When I then tried to change teh name of either the new item or the existing one, I received an error message saying "property can' tbe change outside a transaction".

I closed VS and restarted it. Now when I try to change the name, I get a duplicate key error.
If I try to delete one of the item with duplicate key, VS crashes.
Details
Sign in to post a comment.
Posted by Microsoft on 4/29/2014 at 12:30 PM
Thank you for reporting this issue. This issue has been fixed in Visual Studio 2013. You can install a trial version of Visual Studio 2013 with the fix from: http://go.microsoft.com/?linkid=9832436
Posted by Microsoft on 5/4/2013 at 2:54 PM
Thanks again for reporting this! We have fixed the issue and is planned to be available in a future release of Visual Studio. If you have any questions or concerns, don't hesitate to get in touch.

Thanks,
Pete (Lightswitch Test Team)
peter.hauge@microsoft.com
Posted by RStanton on 3/14/2013 at 6:23 PM
Thank you, we have been able to reproduce the bug and are investigating a fix.
Posted by Microsoft on 2/10/2013 at 11:23 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.
Posted by Microsoft on 2/9/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.