What is the recommended way to develop RhinoCommon plug-ins on a Win 10 computer? I failed to install Visual Studio 2013 and the free 2015 version doesn’t install the Rhino template.
Hi kjarke
I would like to know more. We briefly tested the Community edition and published an update to support it.
Which error are you getting?
See here a step-by-step guide (new page).
Thanks,
Giulio
Giulio Piacentino
for Robert McNeel & Associates
giulio@mcneel.com
Thanks for the quick response. I installed the Visual Studio express version and not the community version. Will try it tomorrow and give an update.
Which Express version did you install?
It is finally working! Here a summary of my experiences.
I installed Visual Studio Express for Windows 10 and couldn’t install the Rhino templates. So that didn’t work.
Installing Visual Studio Community 2015 allowed me to install the Rhino templates.
The VS installation was extremely painful and hung at the ‘creating a restore point’ step. After visiting some forums I deleted all the folders in C:\ProgramData\Package Cache and disabled AVG virus protection. I think then the installation worked. Previously the installation hung several times. It continued after pressing Restart (restarting the computer) and then cancelling the restart.
When I tried to compile my previous projects from VS 2013 I get the following error:
Cannot import the following key file: XYZ.pfx. The key file may be password protected. To correct this, try to import the certificate again or manually install the certificate to the Strong Name CSP with the following key container name: VS_KEY_D58AA…
What is the solution to that?
Starting a new project in VS 2015 and pasting the 2013 code into a new project worked.
That version is not designed to create the type of .dll that we need in Rhino. You need to use the ‘for Desktop’ Express version. That should work. That version creates the ‘metro’/‘Windows store app’ type of applications.
About the error that you are experiencing, a quick research found this.
Please note that this is not a Rhino or McNeel-specific problem. It is a development problem related to signed assemblies.
Thanks,
Giulio
Giulio Piacentino
for Robert McNeel & Associates
giulio@mcneel.com