I'm seeing this too with a new install of Unity3.5. It's apparently a [documented bug][1] (fixed in the latest version of MonoDevelop)
Not sure what good that does us though, I'm not readily finding a way to manually update to the latest version of MonoDevelop so that it can still be used with Unity.
[1]: https://bugzilla.xamarin.com/show_bug.cgi?id=2182
↧