https://www.clipboardfusion.com/Discussions/RSS/?TopicID=a960fae0-128a-4164-8bfe-7780bce0f52b ClipboardFusion RSS: My own assemblies in ClipboardFusion Macros Wed, 17 Jun 2026 15:53:08 GMT en hourly 1 https://www.clipboardfusion.com/Discussions/RSS/?TopicID=a960fae0-128a-4164-8bfe-7780bce0f52b https://www.clipboardfusion.com/Discussions/View/my-own-assemblies-in-clipboardfusion-macros/?ID=a960fae0-128a-4164-8bfe-7780bce0f52b#6 Mon, 30 Oct 2017 23:04:40 GMT Binary Fortress Software https://www.clipboardfusion.com/Discussions/View/my-own-assemblies-in-clipboardfusion-macros/?ID=a960fae0-128a-4164-8bfe-7780bce0f52b#6 ClipboardFusion Thank you, Thomas!

Very helpful instruction, this "assembly to be sandboxed" error is indeed confusing and I used to get it sometimes, outside of CF macros ]]> https://www.clipboardfusion.com/Discussions/View/my-own-assemblies-in-clipboardfusion-macros/?ID=a960fae0-128a-4164-8bfe-7780bce0f52b#5 Mon, 30 Oct 2017 18:17:05 GMT Binary Fortress Software https://www.clipboardfusion.com/Discussions/View/my-own-assemblies-in-clipboardfusion-macros/?ID=a960fae0-128a-4164-8bfe-7780bce0f52b#5 ClipboardFusion The way I usually test it is to add the DLL to the references and compile to see if it throws an error. The error usually looks something like this if the assembly is using the wrong .NET framework:

"an attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed"

You can try a different version of the DLL, or you can right click on the file itself, click "Properties" and unblock the file. More details here:

https://stackoverflow.com/questions/15238714/net-local-assembly-load-failed-with-cas-policy ]]> https://www.clipboardfusion.com/Discussions/View/my-own-assemblies-in-clipboardfusion-macros/?ID=a960fae0-128a-4164-8bfe-7780bce0f52b#4 Mon, 23 Oct 2017 04:27:44 GMT Binary Fortress Software https://www.clipboardfusion.com/Discussions/View/my-own-assemblies-in-clipboardfusion-macros/?ID=a960fae0-128a-4164-8bfe-7780bce0f52b#4 ClipboardFusion Hi Thomas

By the way, your screenshot says you link Newtonsoft.Json.dll version 4.5 (and anyway no 4.6 version exists for that library in the download). So, is it OK to have 4.5 library and not necessarily 4.6 as you have suggested? Or you had to re-build Newtonsoft library from source to satisfy 4.6 requirement?

Thanks,
Dmitry ]]> https://www.clipboardfusion.com/Discussions/View/my-own-assemblies-in-clipboardfusion-macros/?ID=a960fae0-128a-4164-8bfe-7780bce0f52b#3 Thu, 19 Oct 2017 23:04:41 GMT Binary Fortress Software https://www.clipboardfusion.com/Discussions/View/my-own-assemblies-in-clipboardfusion-macros/?ID=a960fae0-128a-4164-8bfe-7780bce0f52b#3 ClipboardFusion Thank you, Thomas. Good example in your screenshot! ]]> https://www.clipboardfusion.com/Discussions/View/my-own-assemblies-in-clipboardfusion-macros/?ID=a960fae0-128a-4164-8bfe-7780bce0f52b#2 Thu, 19 Oct 2017 18:47:17 GMT Binary Fortress Software https://www.clipboardfusion.com/Discussions/View/my-own-assemblies-in-clipboardfusion-macros/?ID=a960fae0-128a-4164-8bfe-7780bce0f52b#2 ClipboardFusion Your assemblies can be anywhere you like. All you need to do is add the path to them in the "References" text box in the Macro Editor, and make sure your assemblies are compiled with the same version of the .NET framework (4.6).

I've attached a screenshot showing a Macro that I use with an external assembly.

I hope this helps! ]]> https://www.clipboardfusion.com/Discussions/View/my-own-assemblies-in-clipboardfusion-macros/?ID=a960fae0-128a-4164-8bfe-7780bce0f52b Thu, 19 Oct 2017 04:30:28 GMT Binary Fortress Software https://www.clipboardfusion.com/Discussions/View/my-own-assemblies-in-clipboardfusion-macros/?ID=a960fae0-128a-4164-8bfe-7780bce0f52b ClipboardFusion Change log for version 5.0 says:
"Change: You can now add your own assemblies to ClipboardFusion Macros"

Can you please elaborate on this feature? Where my own assembly's DLL file should be placed? Along with ClipboardFusion binaries or in the GAC? ]]>