If I remove project A from the solution, then projects B and C revert to behaving correctly using the binary reference and compile fine.
But then, here is the catch, the code coverage metrics fail to report at all on project A since it has been removed from the solution even though the tests are passing.
In Visual Studio 2015, only the project version of Project A appears in the Object Browser.The dll is modified in the obj\debug folder before the Copy Files To Output Directory step is called.Like the So I would have expected that the Object Browser is always populated from Visual Studio's view of the project which would never reflect the metadata view of the world. @Pilchie, @dpoeschl, how did we change Editor Browsable Attribute in VS2015 here?Discussed this with @Anthony DGreen, and we agree that making this API accessible is desirable.Passing this bug to the compiler team to track the work of making the API accessible.Longer term we might need to something nicer here, but that should hopefully get you unblocked right away. The dll is modified in the obj\debug folder before the Copy Files To Output Directory step is called.We used the IL Support (2013 version) (original) extension to create the [email protected] Adding some quotes from the notes in internal bug 824590: When the set of symbols to be used for completion is filtered to visible and browsable members, that filtering only takes into account overrides relationships between symbols in that set (but not hiding relationships).This omission can be seen found in being made public or adding a reimplementation of it in the IDE. You mentioned you ran into this issue after a shutdown, which should indeed release all of those assemblies. Currently, those assemblies are not shadow copied, which leads to this locking behavior. I can confirm this occurred following a manual restart; however this was originally reported back in early May so things may have changed since then. Currently, those assemblies are not shadow copied, which leads to this locking behavior.