Changes in dependend assemblies are not detected - by Aquariusquintini

Status : 


Sign in
to vote
ID 775789 Comments
Status Active Workarounds
Type Bug Repros 3
Opened 1/4/2013 5:24:37 AM
Access Restriction Public


VS2012 does not seem to detect changes to assemblies that are referenced by a project. If I rebuild one of the assemblies on which my project is dependend, the changes are not showing up in visual studio. For example if I add a new method to one of the dependend assemblies, and try to use it in visual studio, the compilation fails. So far the only workaround is to close all instances of visual studio and reopen them, which is simply unacceptable for any production development to restart all instances everytime I change something.
Sign in to post a comment.
Posted by Radhika [MSFT] on 7/18/2013 at 4:18 PM

Thank you for your feedback. We are resolving this as a duplicate becasue we already have an open workitem on our plate for thsi issue. Please check out connect bug #785752 for an update on the investigation/resolution.

Radhika Tadinada
Program Manager
Visual Studio Platform Team
Posted by Aquariusquintini on 5/10/2013 at 4:19 AM
Hi Dustin,

I would like to add that the structure with the symbolic link (directory junction) did work with the previous versions of VS.

Kind regards,
Posted by stratnl on 5/10/2013 at 1:57 AM
Hi Dustin, glad you could reproduce the problem. Hopefully you are able to fix this.
Posted by Dustin [MSFT] on 5/8/2013 at 7:35 AM

Thanks for the very helpful repro project and video! I was able to reproduce the problem and my *suspicion* (though I'm not sure) is that the change to the assembly on build is not detected through the symbolic link (i.e. NTFS junction) that you created. I've reactivated the bug for further consideration.

Kind Regards,
Dustin Campbell
Visual Studio Managed Languages
Posted by stratnl on 5/7/2013 at 2:25 AM
Hi, i've created two solutions that will explain the problem. I uploaded a zip file called: "". Also added a video 'bins\ReferenceBug2013-05-07_1114.swf'.
Please read the readme.txt file in the file i uploaded. This will explain how to reproduce the issue.

Kind regards,
Posted by Dustin [MSFT] on 5/2/2013 at 7:50 AM
The issue was closed because we didn't get a response for a couple of weeks after asking a question to clarify our findings on the only repro project that we've received. In other words, we assumed that the issue had been abandoned. If you have additional information, we'd love to get the bottom of this problem! Could you provide a sample project that reproduces the problem for us? If so, we can reactivate the issue and investigate.

Kind Regards,
Dustin Campbell
Visual Studio Managed Languages
Posted by stratnl on 5/2/2013 at 7:39 AM
Hi, No way this issue should be closed as it is now... Why is it closed? Because there is still no solution, and still we have the same problem...
Posted by Dustin [MSFT] on 4/2/2013 at 5:09 PM

Thanks for the sample project and movie. We're investigating this issue right now and have found that there is already a copy of the class library inside the bin\debug folder of your project. That old file can get picked as a reference instead of the one that gets built in C:\shared\current. When we unzipped the project, the relative path in the project pointing to that dll didn't have enough ..\'s so the incorrect library was resolved. Could open the solution on your machine, browse to the Properties window for the library reference isn't updated as you expect and verify that the correct path is shown for the reference?

Kind Regards,
Dustin Campbell
Visual Studio Managed Languages
Posted by Aquariusquintini on 1/24/2013 at 12:58 PM

I have added a file with some sample projects and a little movie that shows the issue. The files show that the intellisense fails and there are some errors in the error window in the scenario. However, in our production solutions we also have problems with building the solution at all, since the compiler is unable to find the newly added methods. I haven't been able to reproduce them in this small sample project, yet. But that is actually the most annoying issue, described in this bug.

Hopefully this will give you some more direction on how to fix the issue.
Posted by Damden on 1/21/2013 at 11:43 PM

I've got the exact same problem. I've one solution, that is in one instance of VS2012, the dll that i'm building is copied to a 'shared' dlls directory (c:\sharedll\). The second solution in another instance of VS2012 is referencing this dll in the shared directory. When I make a change to the firest solution, build it (thus creating a new dll in the shared directory), the second solution is not able to 'see' the new and/or changed methods.

Cleaning the second solution, closing and opening the solution does not work, only closing both VS2012 instances seem to work at all times.

Hopefully this is fixed asap.....
Posted by Hans Leeuw on 1/15/2013 at 12:08 AM

This problem occurs when you have two solutions opened at the same time in VS2012. When the first solution creates a dll with for example utility methods. The second solution is using these methods and thus is referencing the dll from the first solution. When a method is added to the first solution and the solution is build, the second solution does not see this new method. We first need to close both solutions and reopen them, before the new method is visible within the second solution.

Remark: the first solution has a post build event which copies the dll to a general directory, from which the second solution is referencing the assembly created by the first solution.

I hope this makes this problem more clear and reproducible.
Posted by Microsoft on 1/14/2013 at 9:47 PM

I am having trouble reproducing your issue. Do you have any addins installed? Can you share a sample project on which you are seeing this problem?

Posted by Microsoft on 1/7/2013 at 12:00 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 1/4/2013 at 5:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(