grasshopper identified as a .net plug in but .net support not found on this computer

Replies to This Discussion

Permalink Reply by Nino Chang on May 2, 2010 at 12:57pm

have the same problem here. looking for solutions.

Permalink Reply by David Rutten on May 3, 2010 at 5:43am

Apologies for the late response, I've been on the road.

I don't know what's causing this (does it happen with 0.7 or with 0.6.0059?). If you're trying to run Grasshopper 0.7 (the most recent release), you'll need Rhino4 SR8.

--
David Rutten
david@mcneel.com
London, UK

Permalink Reply by brian on May 25, 2010 at 9:46am

This happens with versions 0.6.0059 and v 0.6.0017 for me...

Permalink Reply by Polly Sjobon on July 9, 2010 at 10:05am

I am having the same problem using Windows on a Mac by boot camp, Rhinoceros version 4 and grasshopper 0.6.0059

Permalink Reply by Polly Sjobon on July 9, 2010 at 4:42pm

It s solved!! It s everything okay using Rhino 4 SR8 and grasshopper 0.7...

Permalink Reply by Daniel Palma on March 8, 2012 at 3:13pm

I know it's been a while but is there any chance you remember how you solved this?

Can't seem to get past this error. I'm using Rhino 4.0 SR8 on parallels Windows 7. Downloaded latest version of grasshopper and still didn't work. Help please.

Thanks-

DP.

Permalink Reply by Daniel Palma on March 8, 2012 at 3:11pm

Can't seem to get past this error. I'm using Rhino 4.0 SR8 on parallels Windows 7. Downloaded latest version of grasshopper and still didn't work. Help please.

Thanks-

DP.

Permalink Reply by Hannes Löschke on March 8, 2012 at 3:38pm

This thread is pretty old, as is your Rhino. Current SR is 9.

Permalink Reply by Mario Guttman on June 13, 2012 at 7:46pm

I have Rhino 4.0 SR9 and just downloaded Grasshopper WIP 20120122.  It worked fine for a while while I was fooling around with C#.  Then it stopped working with the message that started this thread.  Has anyone found a solution?

Permalink Reply by Mario Guttman on June 13, 2012 at 8:54pm

Reinstalling Grasshopper failed to fix the problem. However, a complete uninstall of Rhino, restart Windows, reinstall Rhino, reinstall Grasshopper seems to have done the trick. I hope I don't have to do that too many times. If someone has any idea where Rhino is storing its opinion on the availablity of .NET that would be userful information.

By the way, what I was doing was trying to connect to a .dll library. In my first try it had been built with .NET 4.0 which caused an error as others have said is to be expected. It appears that this error had some bad effects because rebuilding the .dll with .NET didn't fix the problem but after my complete reinstall of Rhino it is now working.