Hi

I am having trouble getting the assembly execute working now. This is not a visualcron error, but happened due to an upgrade of another software we are using. Anyway, what happens is that VIsualCron suddenly looks in C:\Program Files (x86)\VisualCron for all my assemblies. See the attached file from fuslogvw.exe (Fusion).   Microsoft_Practices_Unity_Configuration.txt (5kb) downloaded 53 time(s).

My question is, can I force VisualCron in someway to use something else as working directory? What does 'Local execution' mean in assembly execute. Is it my local pc, or is it the bin folder of the executed dll? I get 'no binding' when I try to run it. Can I use the 'Load app.config if existing' to solve this problem? Any suggestions are highly appreciated as this is slightly urgent


Thomas

Yes, you should use "Load app.config" and set dll path there:

http://stackoverflow.com...-path-to-referenced-dlls 

---

Hi Henrik

Thanks for your help. It looks like <probing privatePath="blabla" /> is a path relative to the visualcron folder, not my assembly folder. Do you know if it should be name app.config, or assemblyname.config?

thomas

assemblyname.config - the term app.config just relates to any assembly name the executable might have.

---

Thanks

I couldn't make it work, but when I changed the NETExecute40.exe.config file and added the following configuration, it worked:

<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<probing privatePath="assemblies/visualcron/" />
</assemblyBinding>
</runtime>

So basically it works when vi put all our custom assemblies, and all the quantifi assemblies in a folder under the visualcron program (C:\Program Files (x86)\VisualCron). The runtime then apparently checks the NETExecute40.exe.config file and finds the assemblies using the probing path. It does not work when I add a config file called VisualCronLib.dll.config. Pretty dirty. Do you know if this could make other things fail?

Thomas

Thanks

I couldn't make it work, but when I changed the NETExecute40.exe.config file and added the following configuration, it worked:

<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<probing privatePath="assemblies/visualcron/" />
</assemblyBinding>
</runtime>

So basically it works when vi put all our custom assemblies, and all the quantifi assemblies in a folder under the visualcron program (C:\Program Files (x86)\VisualCron). The runtime then apparently checks the NETExecute40.exe.config file and finds the assemblies using the probing path. It does not work when I add a config file called VisualCronLib.dll.config. Pretty dirty. Do you know if this could make other things fail?

Thomas

Most probably not as it just adds another folder to look at. Just remember to update this file whenever you install a new version.

---