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.
1. Open a project and open a layout file and switch to source view
2. Switch to another file, say an activity
3. Switch back to the Layout and you will get the following crash.
I have tried this on two machines.
Windows 7 64bit and Windows 8.
I have tried upgrading to 4.08 and now to 4.09 in the beta channel and they all do it.
This is a crippling bug and makes it almost impossible to keep working.
System.ArgumentNullException: Value cannot be null.
Parameter name: fileName
at MonoDevelop.Ide.TypeSystem.TypeSystemService.ParseFile(Project project, String fileName, String mimeType, TextReader content)
at MonoDevelop.Ide.TypeSystem.TypeSystemService.ParseFile(Project project, String fileName, String mimeType, String content)
at MonoDevelop.Ide.Gui.Document.<>c__DisplayClass1c.<>c__DisplayClass1e.<StartReparseThread>b__1a(Object )
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
Mike, is this already fixed?
*** Bug 12607 has been marked as a duplicate of this bug. ***
Fixed a while ago
*** This bug has been marked as a duplicate of bug 12773 ***