Strange Error after installing ssiStructdraw

I installed the ssiStructDraw plugin and am having some problems getting some of my Library objects to load that were loading previously without any problems.

I uninstalled the plugin, searched around my drive and got rid of any remnants hoping that would fix my problem, but I am still getting the following error when loading Objects that were loading without a problem.

An exception occured during GHA assembly loading:
Path: C:\Users\ryan\AppData\Roaming\Grasshopper\Libraries\LocalCode.gha
Exception System.IO.FileLoadException:
Message: Could not load file or assembly 'file:///C:\Users\ryan\AppData\Roaming\Grasshopper\Libraries\LocalCode.gha' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515)
Exception System.NotSupportedException:
Message: An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See http://go.microsoft.com/fwlink/?LinkId=155569 for more information.

I even reinstalled Grasshopper and am still getting it.
Thanks in advance.

Replies to This Discussion

Permalink Reply by Giulio Piacentino on December 2, 2010 at 1:44pm

Right click the assembly, then in Properties choose "Unblock".
Is this helpful?

- Giulio
______________
giulio@mcneel.com
McNeel Europe, Barcelona

Permalink Reply by kleerkoat on December 2, 2010 at 2:01pm

That worked! Thank you.

Any reason why they got blocked all the sudden?

Thanks again.

Permalink Reply by Giulio Piacentino on December 2, 2010 at 2:45pm

I think it happens when you download a file.
A somewhat hidden feature in Windows.

- Giulio
______________
giulio@mcneel.com
McNeel Europe, Barcelona

Permalink Reply by Jon Mirtschin on December 4, 2010 at 1:34pm

Hi Giulio,

Any suggestions of what might cause this from the installer (as something similar has been reported a couple of times) and how to avoid it (MSI created by WIX)?

This happens on very few occasions and not even consistently on the same computer (I believe).

Cheers,

Jon

Permalink Reply by Giulio Piacentino on December 5, 2010 at 5:19am