I have an object properties page. In the parent class for Rhino.UI.ObjectPropertiesPage, there is a virtual (I think) item called PageControl. In V5, it returns a ‘Control’ object. In v6, it returns ‘object’.
In Rhino.UI.OptionsDialogPage, the same issue occurs. PageControl outputs ‘Control’ in V5, and ‘object’ in v6.
I think this is the bug track item associated with this problem and it looks like it was added to 6.x on 14 June 2018. I think that means it should be in the current 6.7 release candidate.
Ok! Does that mean that the Pachyderm version I compile from Rhinocommon V5 should run in V6 when service release 7 is deployed? If so, when will that be? (I have a client who really wants to use it in V6, which is sort of awesome, so I’d rather not disappoint them…)
I looked at the schedule and SR7 RC 4 is scheduled for 17 July so I think the public release will be the week after that. You should be able to test this in the current Rhino 6.0 SR7 release candidate.
The link said to use the installation stream in Rhino (so that’s what I did). I’m not sure if Rhino stores an installer on the hard drive, or where that would be. Do you have a link to the installer for download?
Testing C:\Users\Arthu\Desktop\DEV\PachydermAcoustic_Rhinoceros\bin\Debug\Pachyderm_Acoustic.rhp (and 9 other assemblies) for compatibility…
/|||/|||/-/||-/–|\/----|\||/–|-|/||-/|||\/-|/
Compatibility test succeeded in 10.68s
Thanks all, for the help from before on this topic. There is another issue, it seems. If you drag my Rhino 5 plugin to Rhino 6, it works. However, I have a VS deployment installer, and it adds the registry entries for my plugin for both Rhino 5 and Rhino 6. That part seems to work correctly, as the first time running Rhino 6 after installing, the plugin will try to load, but it ends with this:
When you click the ‘details’ button, it says that the plugin failed to initialize, but you can still drag the plugin from its installation folder to Rhino 6, and it loads fine after compatibility checks.
Is there something I can do to fix this, or is this in your court?
Thanks, Arthur. Unfortunately (fortunately?) I’m still unable to reproduce the behaviour that you’re seeing. Pachyderm loads just fine the first time when starting Rhino 6 (6.8.18219.371) after installing it. Verified on two machines running Windows 10.
Testing C:\Program Files\Pachyderm_Acoustic\Pachyderm_Acoustic.rhp (and 7 other assemblies) for compatibility...
-|\\/\-//\/--\-\
Compatibility test succeeded in 3.41s
Perhaps there’s something funny in the registry on your machine already. We could try cleaning it out. Can you try the following…
Open regedit.exe and navigate to HKEY_CURRENT_USER\Software\McNeel\Rhinoceros\6.0\Plug-Ins\25895777-97d3-4058-8753-503183d4bc01 (this is where the information about the currently installed version of your plug-in lives)
Export this key (just in case we need to dig into it later) and then delete it. Alternatively just rename it.
Uninstall “Pachyderm_Acoustic”
Open Rhino 6 and confirm that the plug-in is uninstalled