Bug 7298 - *.designer.cs files cannot be deleted (MonoTouch integration)
Summary: *.designer.cs files cannot be deleted (MonoTouch integration)
Status: RESOLVED DUPLICATE of bug 1433
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: 3.0.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
Depends on:
Reported: 2012-09-19 09:38 UTC by Yvan Rodrigues
Modified: 2012-10-31 16:23 UTC (History)
1 user (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 or GitHub 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 Yvan Rodrigues 2012-09-19 09:38:34 UTC
Designer files created by the interface to the XCode Interface Builder cannot be deleted without deleting the parent file in the group.

Similar, but different from #671, #1433, #4965, #6210.

1. Close MonoDevelop
2. Delete the designer file from the filesystem
3. Use an editor to remove the reference to the file in *.csproj
4. Restart MonoDevelop

MonoTouch 5.4.1
XCode 4.4.1
OS X 10.8.1
Comment 1 Jeffrey Stedfast 2012-10-31 16:23:06 UTC
technically this is the same bug as bug #1433, it's just that the naming convention changed.

I'll cook up a patch

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