Why do ASP.NET resolve assembly references differently?
问题 I really tried hard to find a similar issue to get some leads, but no one seems to describe the case we are having, so here it goes. Background We have a product with the following general design: [Local installation folder] Contains a set of .NET assemblies, implementing the bulk of our product functionality. Example: Implementation1.dll , Implementation2.dll [GAC] ClientAPI.dll. Our client assembly, to be referenced from end user Visual Studio projects. Has strong references to the