CODEWITHSUNDEEP
visual-studio-2017visual-studio-debuggingreportviewer
user2012469
user2012469

Reputation: 11

Computer changed names and AD. Can not debug app because ReportViewer can not be loaded when debugging in Visual Studio

My computer was recently renamed and migrated into a new domain. I can no longer debug my application because the ReportViewer assemblies can not be loaded. I receive the follow error when I try to debug in Visual Studio

"Could not load file or assembly 'Microsoft.ReportViewer.Design-' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)"

This was working fine beforehand. I tried uninstalling and reinstalling the ReportViewer packages using NuGet.
I ran Clean and Rebuild to try to clean any issues in the build. I have checked the various methods (outdated GAC suggestions, various changes using Nuget between Updates and Uninstall\reinstall). I have searched my machine for any files that may be cached and causing the issues.

StackTrace

Upvotes: -3

Views: 30

Answers (1)

user2012469
user2012469

Reputation: 11

I found that my Bin directory in my web project had duplicate files that were appended with my computer name. Removing them corrected the issue.

Upvotes: 1

Related Questions