Topic: Resolving References

[hermanm]

How are references to the AutoCAD .NET references resolved when moving between machines?

Explicit paths to acmgd.dll, acdgmgd.dll, etc. must be provided to VS during creation of the project.

But these paths may well be different on different machines.

How is this handled?

[kdub_nz]

See if these help
http://msdn.microsoft.com/en-us/library/yx7xezcf(v=VS.100).aspx

http://msdn.microsoft.com/en-us/library/15hyw9x3.aspx

[Jeff H]

A simple non-techincal explanation is
 
When AutoCAD is installed it installs acmgd.dll, acdgmgd.dll in the same location as the acad.exe
and when acad.exe starts up it demand loads acmgd.dll, acdgmgd.dll etc..
 
So you use the dll in the sdk which are stripped out version and provide the method names and return types etc...  to be able to compile your code, that is why you set Copy local false if not then you have two copies of acmgd.dll loaded which will cause problems.
 
When a dll in loaded it will look in its output path for the referenced dll's and having copy local to true copies them in the same location.
 
 
 

[hermanm]

A simple non-techincal explanation is
 
When AutoCAD is installed it installs acmgd.dll, acdgmgd.dll in the same location as the acad.exe
and when acad.exe starts up it demand loads acmgd.dll, acdgmgd.dll etc..
 
So you use the dll in the sdk which are stripped out version and provide the method names and return types etc...  to be able to compile your code, that is why you set Copy local false if not then you have two copies of acmgd.dll loaded which will cause problems.
 
When a dll in loaded it will look in its output path for the referenced dll's and having copy local to true copies them in the same location.

So, if  I understand correctly, the dlls in the SDK are more like a set of function prototypes, which do not contain the actual code, only the input/output specs., in order to validate the function references for compilation. Is that correct? I was confounded as to why they were so much smaller...

Makes sense not to have competing versions loaded.

But if I reference the actual assemblies in the ACAD install directory & set Copy Local to false, would that not accomplish the same thing? If that is the case, then the only advantage  I can see to referencing the SDK versions would be a) slightly faster compilation and b)  not having to repath references in the project in case you wish to modify existing code & have, for some reason, moved your AutoCAD installation. This seems like a very marginal advantage to me, but perhaps I am not grasping all implications.

@ kdub:

It will take me awhile to absorb this completely, but thanks very much for the references. I am sure others here will benefit as well. What I am getting right now is, the .NET runtime does most of this for you, but you can override its default protocol via your own configuration file.

Thanks, guys.

[kdub_nz]

You are essentially correct about using the SDK dll's ... their use is NOT mandatory.

However this post by Norman at the ADNG highlights a couple of points worth considering

http://forums.autodesk.com/t5/NET/Getting-Started/m-p/2898280#M22474

Regards,
Kerry

[Jeff H]

I do not remeber what it had to do with but I remeber Tony T saying that there are some things that will cause the VS IDE to crash if you use the ones installed with Acad

[kdub_nz]

Hi Jeff,
I recall the same statement, but can't place the details or timeframe ..
I also recall the same recommendation from several people associated with AutoDesk technical support.

I use the SDK as a matter of course and haven't 'tried' to break the IDE

As a side thought ... using the SDK (a particular build) may help with dependency issues for a previous class/method requirement.
ie. If you use an older SDK only the defined class/method definitions will be available in the IDE.
( This of course may be a 2 edged sword )

[hermanm]

.

However this post by Norman at the ADNG highlights a couple of points worth considering

http://forums.autodesk.com/t5/NET/Getting-Started/m-p/2898280#M22474

Regards,
Kerry

This in particular caught my eye:

Also, path to Autodesk.AutoCAD.Interop/Interop.Common being changed or not really does not matter, they are installed in GAC by AutoCAD. If you set reference to them from SDK folder (or anywhere in the disk), you do not copy them to output location (Copy Local =False) anyway, and AutoCAD (actually the .NET runtime) always look for it in GAC first.

Also, I agree with this, at least for a novice (raising hand):

So, I do recommend the start a blank class library project (VB.NET or C#), set references to acdbmgd/acmgd.dll(make sure "Copy Local to False), maybe add some boiler plate code in a class and then export it as your basic Acad .NET API development template

vs. using a "wizard."

I want control & knowledge of what I am doing.

[dgorsman]

For what its worth, I'm now compiling against the SDK DLLs which I'm keeping on the network rather than on the local drive.  The finished distributed DLLs are run from their own local drive with no issues, even though the users don't have access to that particular network location.  That, to me, would confirm the AutoCAD DLLs are being loaded from the GAC.