Bug 52455 - Cut and paste control and ID disappears
Summary: Cut and paste control and ID disappears
Status: RESOLVED DUPLICATE of bug 39470
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS Designer ()
Version: 4.4.0 (15.1)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2017-02-10 21:17 UTC by servicerequest
Modified: 2017-04-27 18:43 UTC (History)
5 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description servicerequest 2017-02-10 21:17:23 UTC
If I cut a control and paste from one view to another the ID/name that I gave it gets lost.  This would be fine if I were just copying but cutting I would expect every property to be associated with it.

A good example of this happening is I start with a TableView and then realize I need to add a ScrollView after my table and cells have been set up.  If I add the scroll view to the existing controller and then open the document outline.  If I cut the tableView and paste it into the ScrollView I lose all ID/names that I previously set.
Comment 1 Alex Corrado [MSFT] 2017-04-27 18:43:49 UTC

*** This bug has been marked as a duplicate of bug 39470 ***