AutoCAD Architecture 2009/10 - COM on x64

[bwinterscheidt]

I am running AutoCAD Architecture x64 on XPx64. I am trying to add the AEC Base Object Library (AecXBase##.tlb) and the AEC Base Application Library (AecXUIBase##.tlb) to VB2005 and/or VB2008 projects.

Neither component appears in the COM tab of the Add Reference dialog, but can be found by browsing. However, when they are selected, I get the following error:

"A reference to 'C:\Program Files\Common Files\Autodesk Shared\[ComponentName]' could not be added. Please make sure that the file is accessible, and that it is a valid assembly or COM component."

Is this an x64 glitch with the GAC, and is there a way around it? I didn't have trouble on my old 32-bit machine, but it's now gone... Edited by: [email protected] on Jun 2, 2009 11:19 AM

[Anonymous]

[email protected] wrote:
> Is this an x64 glitch with the GAC, and is there a way around it?

AutoCAD Architecture 2009/2010 apparently don't install all of the
necessary registry keys...

ACA registry entries at:
HKCR\TypeLib\{ComponentGUID}\5.7\0\
HKCR\TypeLib\{ComponentGUID}\6.0\0\

only contain win64 keys. Creating new 'win32' keys with duplicate info,
fixes my problem, for now.



Now, my question is whether or not this will affect the deployed
applications' functionality, if client machines have not manually added
these keys?


--
Brian Winterscheidt
LWPB Architecture
Oklahoma City, Oklahoma

[Anonymous]

It would be best to test your code on a clean system like
the ones you're planning to deploy to.

--
http://www.caddzone.com

AcadXTabs: MDI Document Tabs for AutoCAD 2009
Supporting AutoCAD 2000 through 2009

http://www.acadxtabs.com

Introducing AcadXTabs 2010:
http://www.caddzone.com/acadxtabs/AcadXTabs2010.htm

Email: string.Format("{0}@{1}.com", "tonyt", "caddzone");


"Brian Winterscheidt" wrote in message
news:[email protected]...
[email protected] wrote:
> Is this an x64 glitch with the GAC, and is there a way around it?

AutoCAD Architecture 2009/2010 apparently don't install all of the
necessary registry keys...

ACA registry entries at:
HKCR\TypeLib\{ComponentGUID}\5.7\0\
HKCR\TypeLib\{ComponentGUID}\6.0\0\

only contain win64 keys. Creating new 'win32' keys with duplicate info,
fixes my problem, for now.



Now, my question is whether or not this will affect the deployed
applications' functionality, if client machines have not manually added
these keys?


--
Brian Winterscheidt
LWPB Architecture
Oklahoma City, Oklahoma

[Anonymous]

After some testing, I'm somewhat perplexed on how all of this is
working, since the GUIDs which VB uses to reference these components are
different between win32 and win64 platforms.

Referencing the correct win32 components on a win32 dev platform, then
moving to win64 for dev, VB can't find any of the win32 references
because of the different GUID, but the win32-built assembly runs fine on
win64 once loaded into AutoCAD. (I haven't tested the other way yet, to
see if win64-built assembly will run on win32)

Since VB can't find the right COM components, how is AutoCAD managing to
do it? It must not be using the GUID in the compiled assembly?



--
Brian Winterscheidt
LWPB Architecture
Oklahoma City, Oklahoma

[Anonymous]

AutoCAD is looking for them in the registry.

--
http://www.caddzone.com

AcadXTabs: MDI Document Tabs for AutoCAD 2009
Supporting AutoCAD 2000 through 2009

http://www.acadxtabs.com

Introducing AcadXTabs 2010:
http://www.caddzone.com/acadxtabs/AcadXTabs2010.htm

Email: string.Format("{0}@{1}.com", "tonyt", "caddzone");


"Brian Winterscheidt" wrote in message
news:[email protected]...
After some testing, I'm somewhat perplexed on how all of this is
working, since the GUIDs which VB uses to reference these components are
different between win32 and win64 platforms.

Referencing the correct win32 components on a win32 dev platform, then
moving to win64 for dev, VB can't find any of the win32 references
because of the different GUID, but the win32-built assembly runs fine on
win64 once loaded into AutoCAD. (I haven't tested the other way yet, to
see if win64-built assembly will run on win32)

Since VB can't find the right COM components, how is AutoCAD managing to
do it? It must not be using the GUID in the compiled assembly?



--
Brian Winterscheidt
LWPB Architecture
Oklahoma City, Oklahoma