Home Dashboard Directory Help

Referenced project assembly does not refresh by a_mikayil



Sign in
to vote
Type: Bug
ID: 777916
Opened: 1/30/2013 12:18:11 PM
Access Restriction: Public
User(s) can reproduce this bug


In a solution I have an ASP.NET website and a class library project for accessing database, which I've called DAL. The web site has a reference to the DAL.dll. When I add or update something in the DAL source code and build the solution, I expect to have the DAL.dll in the bin folder of the web site to be refreshed too. But this does not seem to work. Here's what I've noticed:
1. In the DAL project I have a public struct inside which are number of public const string fields. If I change the name of any of those fields and build solution, the change does not get reflected on the web site. However if I select that field name, right click on it and choose "Rename oldname to newname" and then build, it works.
2. When I add another public const string field and build the solution, that newly added field is not available, so again the dll file does not refresh.
Of course if I build the project separately and add the dll file manually then there's no problem. Note that I have the refresh file in the bin folder and it clearly shows the path to the original dll.
You wouldn't deny that this is a very big problem and needs immediate handling, because otherwise the time spent is going to dramatically increase
Sign in to post a comment.
Posted by Microsoft on 2/25/2013 at 8:58 AM

Thanks for contacting us about this issue. It appears that the problem that you described is a duplicate of the following Connect issue:


Kind Regards,
Dustin Campbell
Visual Studio Managed Languages
Posted by Microsoft on 1/30/2013 at 11:30 PM
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/30/2013 at 12:50 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.