Login

license downloads forums

Summary

Title:	Couldn't resolve assembly message "spam"
Category:	Workflow
Status:	Open
Posted By:	rodcloutier ( Rodrigue Cloutier )
Date Created:	5 October 2009

Problem

Description:	We are using the AppDomain.CurrentDomain.AssemblyResolve delegate to load dependent assemblies from a custom path since we do not want to put all the dll in Max's directory. Doing so results in the following message being outputted in MaxScript listener: Couldn't resolve assembly ... Could we optionally disable the message?
Steps to Reproduce:	Create a plugin Add a dependency that will not be found in Max's directory Use the AppDomain.CurrentDomain.AssemblyResolve delegate to resolve the dependency and load the assembly Load your plugin Open MaxScript listener See "Couldn't resolve assembly <your dependent assembly" message in the listener

5 October 2009 #716
EPHERE	Right, the wrapper does exactly the same thing for child assemblies that it loads. I will remove the listener messages in the next build. Marsel Marsel Khadiyev (Software Developer, EPHERE Inc.)
6 October 2009 #722
rodcloutier	Thanks! Rod