01-21-2013 06:30 PM
Thanks for your tips, Len, it fixed mine too. after unblocking the dll and deleting the dependentdll.xml
01-30-2013 08:15 PM
We have a problem from time to time. When a plugin won't load and we delete dependentdlls.xml it still won't load, however if we change the dll name slightly and restart ACT! it all works. There must be some other record of the name other than dependentdlls.xml.
01-31-2013 05:56 AM
01-31-2013 09:30 AM
I'll put it another way. If a plugin refuses to load, as you would expect, it is found in dependentdlls.xml. Close ACT! delete dependentdlls.xml. Re-start ACT!, the same happens, the plugin doesn't load. However, close ACT! rename the plugin, start ACT! and it will load.
01-31-2013 10:16 AM
02-23-2013 09:01 AM
02-18-2016 08:03 AM
What do you exactly mean with "Right-click, click Unblock, click Apply and we’re back in business"?
Do you mean I Right-click on the Plugin-DLL, there is the Option "Unblock" and you can click on it?
And the tag <loadFromRemoteSources enabled="true" /> you place between the tags <switches>?
I ask because as an Act! partner we have a customer for whom we wrote a Plugin but it does not appear when Act is loaded?
We tried some other plugins which we wrote for ourselve but they also not appear? They are not disabled. They just not there.
We are using Act! 17 Premium on Windows 7.
Our Customer usesAct1 17 Pro on Windows 7.
06-14-2017 10:19 PM
Hi Len. Any chance of setting out the exact steps you took to resolve this? E.g. What do you mean by set the switch to 4? I have two addins I just can't get to load despite deleting the Dependent.dll file etc.