Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Created attachment 481 [details]
Image for the bug
Steps to Reproduce:
1. Launch the application.
2. Create a solution for single view iPad application.
3. Right Click on project name and select Rename.
4. Rename the project name.
5. Now double click on .xib file.
6. See system error.
System exception is occurring when user tried to launch xcode after changing the project name.Refer the screenshot.
Xcode should be launched successfully.
OS: Snow Leopard 10.6
MonoDevelop 2.8 beta 2
Mono Framework for MAC OS X Intel Runtime
*** This bug has been marked as a duplicate of bug 933 ***
Verified this issue,this is happening when user rename solution project name without space and special character and clicks on .xib file .Please view attached screenshot
Steps to reproduce:
1.Create project with name(e.g test)
2.Rename project (e.g tests)
3.Click on .xib file.
4.Look for validation error.
Created attachment 657 [details]
Validation Message after clicking on .xib file of a renamed project
The cause of this is that ProjectDomService.GetProjectDom(Project) relies on the filename in order to retrieve the DOM. If you rename a project the dom is not regenerated nor does the ProjectDomService track the change and fix it's cache. The workaround is simply to close and reopen the solution
Mike, what's the best way of handling this properly so we dont have to close/reopen the solution? Are there other places which might rely on this?
This issue is fixed for the latest installers, i.e.
Hence, closing this issue dated 22nd December, 2011.