AutoCAD plugins

Hey Ewen,

Has anyone had, or heard of, success stories using LimeLM in an AutoCAD plugin DLL?

A number of our customers use TurboActivate successfully in plugins to other apps. I don't know if any are using it in AutoCAD plugins, but I wouldn't be surprised if that were the case.

AutoCAD comes in x86 & x64 flavors - should I make specific versions of these instead of "any CPU"? I saw the post on "any CPU" at https://wyday.com/forum/t/1893/any-cpu-question/ - I am thinking mainly of the deployment size, as well as complexity in the code.

Well you have a couple of options. You could build specific versions of your plugins or you can include either the x86 or x64 versions of TurboActivate. Or you could create a general "AnyCPU" plugin and include both x86 & x64 versions of TurboActivate with your plugin (rename the x64 version TurboActivate64.dll to avoid conflict).

The next release of TurboActivate includes a version of TurboActivate.cs and TurboActivate.vb that allows you to specify whether you want to just use TurboActivate.dll or use TurboActivate.dll and TurboActivate64.dll and choose the correct one at runtime. Email me if you want it now.

Hi Wyatt

Thanks for the response - and sorry I'm a bit slow following up, I'm still working on the app but it's getting there.

Just a follow-up on my ILmerge idea - is it feasible to merge your TurboActivate.dll into my main plugin dll? Mine is in .NET with versions in 3.5, 4.0 and 4.5, depending on the AutoCAD version. Or am I just asking for trouble?

cheersEwen

Just a follow-up on my ILmerge idea - is it feasible to merge your TurboActivate.dll into my main plugin dll?

No. TurboActivate is a "native" library (it doesn't use .NET at all). Even if you could do ilmerge it wouldn't make your app "more secure".

okey dokey, thanks. The Ilmerge thing was just to keep everything in one place, not so much for security.

cheersEwen