Assembly Binding Path Broken?
..NET Framework 1.1-SP1.
I created an ASP.NET project with Visual Studio, it automatically
created a bin directory. Then I modified web.config to add a new
binary assembly direcoty, moved the web application DLL to that
directory, and now ASP.NET cannot run the app. My web config looks
<publisherPolicy apply="yes" />
<probing privatePath="bin;bin2" />
Why is this broken?
RE: Assembly Binding Path Broken?
Thanks for your posting. As for the privatePath problem you mentioned, it
is a normal behavior because the asp.net web application is abit different
from the normal desktop or console application which will ignore the other
private bin path we set in the <probing privatePath="..." /> element. So
generally in asp.net application, as for nonstrong-named assembly, we
should put them in the private "bin" folder.
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
|All times are GMT. The time now is 06:51 AM.|
Powered by vBulletin®. Copyright ©2000 - 2014, vBulletin Solutions, Inc.
SEO by vBSEO ©2010, Crawlability, Inc.