loadFromRemoteSources issues with custom components

Hi all,

I'd been getting several reports of people unable to load kangaroo in recent versions, and from what I gather some other plugins had experienced similar issues.

From to]'s comment on the geco forum, I found that the problem can be fixed by right-clicking the .gha in windows explorer and unblocking it in properties (thanks Thomas).

However, if it is possible I'd like to find a way to fix the problem without having to get users to do this.

I did some searching related to the error messages and found my way to this:

http://blogs.msdn.com/b/shawnfa/archive/2009/06/08/more-implicit-us...

Which sounds like the cause of the problem, but I'm not quite sure how to apply the solution at the end with the config file to a custom .gha

So my question is - What exactly do we need to do to our custom components to get them to work in whichever .net framework people have without this error ?

thanks,

Daniel

Replies to This Discussion

Permalink Reply by Giulio Piacentino on March 18, 2011 at 7:39am

As far as I know, there's nothing really a third-party developer can do programmatically from within a .dll file after the browser has set NTFS extended file attributes with group policy to it, because the behaviour is defined in the .Net framework 4.

Only the loader (officially Rhino) might circumvent it. What you can do is remind the user that he has to unblock the file after downloading (this is what the button says in this strange Windows user interface). To make the loader circumvent this, you could add the sample XML from the msdn link above into a text file called rhino4.exe.config that resides in the same folder as rhino4.exe.

- Giulio
______________
giulio@mcneel.com
McNeel Europe

Permalink Reply by Daniel Piker on March 18, 2011 at 7:59am

Thanks Giulio,

Thomas suggested having people download a zip instead of the .gha directly, so that the file is created on the users computer, and it then doesn't treat it as a remote source. Do you think this would be enough to get around it ?

Daniel

Permalink Reply by Giulio Piacentino on March 18, 2011 at 8:01am

It depends on what people use to decompress... if they use Windows Explorer (the default in Vista and 7) that's not enough.

Permalink Reply by Danny Boyes on March 18, 2011 at 7:58am

If you had a Kangaroo Windows Installation File that put the gha file in the right place would this circumvent it? Then all the user has to do is allow the installation file to run, similar to GH

Permalink Reply by Giulio Piacentino on March 18, 2011 at 8:01am

Yes that of course would do.

- Giulio
______________
giulio@mcneel.com
McNeel Europe

RSS