Trying to get a custom Plug-in to work in 2017 that works in 2015

Trying to get a custom Plug-in to work in 2017 that works in 2015

Anonymous
Not applicable
413 Views
3 Replies
Message 1 of 4

Trying to get a custom Plug-in to work in 2017 that works in 2015

Anonymous
Not applicable

Hi Everybody,

 

So we have Autocad 2015 working with a "Company_plugin.bundle" which works in 2015, and I'm trying to get it to work with Acad Mechanical 2017. I have it located in the "ApplicationPlugins" folder under appdata. Do I need to move it elsewhere?  I have loaded the "vbaide" thing, whatever that does. I'm new to these types of lisp commands. Insde the "Company_plugin.bundle" folder there are bunch of ".dll" files.

 

Any help would be gladly appreciated. Thanks in advance.

Tim

0 Likes
414 Views
3 Replies
Replies (3)
Message 2 of 4

_gile
Consultant
Consultant

Hi,

 

You should contact the plugin publisher, only him can ensure the plugin is compatible with AutoCAD Mechanical 2017.

 

If you cannot, you can edit the PackageContents.xml file (within the .bundle folder) at your own risk.
You may have to change some attribute values in the RuntimeRequirements:

  • Platform="AutoCAD*" or, almost patform="AutoCAD|ACADM"
  • SerieMax="21.0"

More informations about the autoloader mechanism here.



Gilles Chanteau
Programmation AutoCAD LISP/.NET
GileCAD
GitHub

0 Likes
Message 3 of 4

Anonymous
Not applicable

Unfortunately, the publisher is no longer employed by the company, and left on bad terms.  I'll try adding that piece of script to the .xml file. Thanks.

 

Update: that didn't fix any of the problems.  Some information I forgot to include...

     - The CUIX file seems to be working since the Pull-down menu is visible at the top of the screen, just none of the .dll files are working.  None of the commands in the pull-down work.

 

Tim

0 Likes
Message 4 of 4

_gile
Consultant
Consultant

Changing Platform and SerieMax attribute values in the PackageContents.xml file may allow the application to load in ACADM 2017 but it doesn't ensure the app will run on this version, there may be some compatibility issue with ObjectARX and .NET applications.



Gilles Chanteau
Programmation AutoCAD LISP/.NET
GileCAD
GitHub

0 Likes