AppDomain.CurrentDomain.AssemblyResolve asking for a .resources assembly?

Answering on my own; Adding this line to AssemblyInfo.cs solves it and resolver will not get asked for resources any-more. [assembly: NeutralResourcesLanguageAttribute(“en-US”, UltimateResourceFallbackLocation.MainAssembly)] Though this is a work-around should be carefully considered multi-language applications. More Info: https://connect.microsoft.com/VisualStudio/feedback/details/526836/wpf-appdomain-assemblyresolve-being-called-when-it-shouldnt http://blogs.msdn.com/b/kimhamil/archive/2008/11/11/what-does-the-neutralresourceslanguageattribute-do.aspx http://forums.devshed.com/net-development-87/c-wpf-appdomain-assemblyresolve-being-called-when-it-shouldn-t-669567.html http://blogs.msdn.com/b/microsoft_press/archive/2010/02/03/jeffrey-richter-excerpt-2-from-clr-via-c-third-edition.aspx This approach fails for machines with non en-US cultures. A better approach is ignoring resources … Read more

C#: Custom assembly directory

You can add additional search paths to your app.config that it looks in to load assemblies. For example <runtime> <assemblyBinding xmlns=”urn:schemas-microsoft-com:asm.v1″> <probing privatePath=”lib;thirdParty” /> </assemblyBinding> </runtime> You can see more details here.