We have a web application that calls a bunch of VB.NET objects. We have intgerated with a 3rd party's software which includes one of our objects referencing one of their dlls.
When we build our app we get a copy of all required dlls in the bin directory of the web app. On a system where the users do not have the 3rd party app I would like to be able to remove the 3rd party dll. If I do that then I get an error message about it (or a dependency) not being accessible. Is there any way to tell .Net not to resolve dependencies of specific components ? Thanks Steve =================================== This list is hosted by DevelopMentor� http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
