DLL Dependencies

[doday]

When I run my plugins, it appears I need to have any dependent assemblies in the articy installation folder, instead of the plugin folder.

For example, I got the autocomplete control from the microsoft WPF toolkit so I needed to include a reference to DotNetProjects.Input.Toolkit.dll. This gets output with my plugin, but having it exist next to my plugin's DLL / manifest is insufficient. It needs to be a sibling of ArticyDraft.exe for the plugin to load properly.

Is this expected behavior, and if so is there any way I can make articy look in another folder for DLLs?

[[Articy] Peter Sabath]

Hi,

I have tried to reproduce this unintended behavior.

And can confirm that it arises if any access to a class in a dependent assembly comes from a static class member in the plugin or from an access in the "Initialized" method.

Using the current 3.1.1 versions fixes that shortcoming.

[doday]

Thanks for the rapid fix.

[doday]

Actually this update seems to have the same behavior. If I do not put DLLs next to the articy executable, some code that runs on ProjectLoaded fails because it cannot locate the requisite assemblies.

I am now running Articy version 3.1.1.31657

Do I need to update my Macro Devkit version?

[doday]

In case anyone else is running into this:

Via direct email correspondence we pinpointed the issue and improvements will be coming in future updates.

[doday]

3.1.3 fixed this.