Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I need to add an assembly probing path at runtime, not through the element in app.config. Is there a way to do this?
The reason is so that my XOML-only workflow that resides in it’s own folder can know where to find it’s related DLLs (i.e. containing custom Activities). Currently I am getting fusion errors because the CLR is probing the wrong paths.
Basically what you are trying to do is something like what this question is about. Resolving assemblies that is not found by probing is done by hooking up with the AppDomain.AssemblyResolve event.
Whether you can use this approach to load activity assemblies requested by your workflow depends on whether a central event handler can figure out where to look for those assemblies given the workflow it tries to load.