Bug 43485 - renaming outlets does not remove the previously named ones
Summary: renaming outlets does not remove the previously named ones
Status: RESOLVED DUPLICATE of bug 43101
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS Designer ()
Version: 4.1.2 (C7SR1)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-08-17 19:14 UTC by reemfz
Modified: 2016-08-18 16:21 UTC (History)
4 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 reemfz 2016-08-17 19:14:27 UTC
steps to reproduce

1. from the designer , drag and drop controls into a view controller
2. provide names for each control.
3. build the project
4. rename the outlet using the properties window. A new outlet will be added, rather than renamed.

expected behavior:
when I change the outlet name from the properties window , under widget, I expect the outlet field to be RENAMED.  

actual behavior:

renaming an outlet causes VS to add a new outlet to the designer file. The old outlet remains in the designer file and needs to be manually removed. not a good user experience. 

Comment 1 Alan McGovern 2016-08-18 13:17:41 UTC

*** This bug has been marked as a duplicate of bug 43101 ***
Comment 2 Alan McGovern 2016-08-18 13:19:08 UTC
Bug #43101 is internal, but to update you: This is a known issue and we've patched it and the fix should be availabke in the next C8 preview release
Comment 3 reemfz 2016-08-18 16:06:28 UTC
Thank you Alan,

it appears that 95% of the bugs reported were fixed in c8.
is it safe to update to c8 at this point? what is the time line for c8?

Comment 4 Alan McGovern 2016-08-18 16:21:48 UTC
It's already in the beta channel, so it's approaching the final stage before it hits stable.

My recommendation would be to grab the latest C8 builds (beta channel) and test it out on a copy of your project. If you encounter any new issues, or if existing issues aren't completely fixed, do let us know!

This secific bug isn't entrely fixed in the current beta. One workaround, when using the current beta, is to hit `save all` and then make a change to the storyboard. That shoukd cause the actions/outlets to properly regenerate.