If you download a 2017 plugin, then you better be trying to load it on 2017.
I have the hardest time understanding why this would be the case since the references don’t change names, are set to non-version dependent within VS and they mostly just adding on to the existing API. Untested, but I am told that Navisworks plugins are extremely version specific.Navisworks Plugins are only intended to run in Simulate and Manage product versions.Navisworks is actually one of the most stable software’s I’ve seen, but an improper PlugIn build can destabilize the primary thread causing fatal errors.Correction: If you are referencing any support DLL’s in your project, then these DLL’s must be stored in the Navisworks Dependencies folder in order to be found and loaded at runtime.Navisworks will not load the plugin DLL if the folder doesn’t match the DLL name.The DLL and the containing folder names must match exactly.You can have multiple plugin types defined in a single Visual Studio solution.I’ve made always on/non initiated plugins using the EventWatcher type.There is actually quite a bit diversity and I don’t consider the entry points they’ve given us to be limiting you just have to know what’s available and when to use what.Navisworks plugins should derive from one of the predefined “Plugin” classes Autodesk gave us.Net together leveraging both without obvious ramifications However, to make this meaningful, I am going to expand on this topic a little bit by also providing some coverage of setting up Visual Studio to debug a Navisworks Plugin. So, here I am posting for the sake of having something to reference…. I was about to make a post involving a (somewhat) novelty Navisworks plugin and went looking for someone else’s rendition of manually installing a Navisworks Plugin and wasn’t real pleased with what I found.
0 kommentar(er)
