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. Create solution A, create library, build.
2. Close solution A.
3. Create solution B, create project, add reference to dll from A, Build.
4. Close solution B.
5. Open Solution A, add some API to the library, build.
6. Close solution A.
7. Open solution B. Try to use the new API. It's not in code completion, but it builds correctly, and it's visible in the assembly browser.
It looks like MD is caching the parsed dll too aggressively?
It looks like there is a check file call missing - I removed the background polling thread a while ago.
*** Bug 5731 has been marked as a duplicate of this bug. ***