Could not load file or assembly Microsoft.Practices.EnterpriseLibrary.Configuration.Design

Introduction

I am providing my best solution as following. I am much assure, you will fix your issue after going through given below steps.



1.    You have to check your private assembly “Bin” folder whether it is already place in right folder or not. If you found desired assembly put it in “Bin” folder. Hope it will work fine & know problem will remove permanently.

2.    You have to check missing assembly in public location in “GAC”, check it carefully whether it is generated on right place or not.
3.    You have to clear all stuff from the web space, now put all fresh stuff into production server, then now compile all source files on server in “Release” mode. Hope it will work for you & known issues would be removed permanently.
4.    It is a very important workaround to work with Fuslogvw.exe (Assembly Binding Log Viewer) for assembly binding. It will help you why the .net framework can’t locate assembly at run time.
4.1    To run this tool you have to open “Visual studio Tools” then right click on “Visual Studio Command Prompt” and runt it as an “administrator”.
4.2    Now at the administrator command prompt, now type “fuslogw”.
5.    We can provide another precious workaround with assembly bind feature fired from web.config.  I have provide web.config sample as following:

 <configuration>
   <runtime>
      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
         <dependentAssembly>
            <assemblyIdentity name="YourAssemblyName"
                              publicKeyToken="99abcb445e2a69a1"
                              culture="neutral" />
            <bindingRedirect oldVersion="7.1.0.0"
                             newVersion="7.2.0.0"/>
            <codeBase version="7.2.0.0"
                      href="http://www.technologycrowds.com/myAssembly.dll"/>
         </dependentAssembly>
      </assemblyBinding>
   </runtime>
</configuration>

 6.    I have faced relevant issue then I start one by one all assembly in “Bin” folder, and then replicate the issue that an assembly found that unnecessary located in “Bin” folder named with “Microsoft.Practices.EnterpriseLibrary.Configuration.Design”, I removed it permanently from “Bin” folder then it worked fine me seamlessly.

Suggested Reading

• The underlying provider failed on open
• MVC ASP.Net Interview Questions And Answers
• Validation failed for one or more entities
• Email Validation using Jquery