Hi Chaz,
As Karl has mentioned, the ASP.NET web application is a particularly
customized .net clr hoster, and its private assembly resolving path is a
fixed one (the physical sub "bin" dir under the web application's root
directory).
BTW, what are you going to do about the "bin" path? Are you going to let
the ASP.NET application use a shared location(folder) as the private
assembly's resolving path? Based on my experience, though it is not
supported at .net /ASP.NET level, we can consider using the windows NTFS's
symbolic links(hard link) feature to link one physical file directory to
another physical file directory. You can have a look at the "Symbolic
links" feature to see whether it helps you some:
#Symbolic links in Windows
http://www.thierryb.net/site/Symboli...n-Windows.html
There is also a tool from sysinternals site that can help create symbolic
links conveniently.
#Sysinternals Freeware - Junction
http://www.sysinternals.com/Utilities/Junction.html
Regards,
Steven Cheng
Microsoft MSDN Online Support Lead
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure!
www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)