Problem loading ARX

[Anonymous]

I am having trouble loading my arx. It has been suggested here that the
manifest tool should be disabled for ARX applications. When I do this, all
of my arx and dbx modules load correctly except for two of them. When those
two modules load, I get the following error message:

"Microsoft Visual C++ Runtime Library
R6034
An application has made an attempt to load ATL80.DLL incorrectly. Please
contact the application's support team for more information"

At this point, the arx will not load because AutoCAD (2007) considers it to
be invalid.

These two modules both have in common the fact that they both define their
own type libraries via IDL files. It seems to load okay with the manifest
enabled, but I'm not sure if this is setting me up for trouble down the
road. Can anybody help me understand why I'm getting this message?


Jon Rizzo
Langan Engineering and Environmental Services, Inc.

[Anonymous]

Hi Jon;

I use the manifest tool on my arx apps, for example that's the way I can
tell my program to load an specific dll version.

i.e.




version="1.0.0.0"
processorArchitecture="X86"
name="LESQ.LE.GBPoly"
type="win32"
/>
GBPoly -- Polyline Generator Engine



type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
processorArchitecture="X86"
publicKeyToken="6595b64144ccf1df"
language="*"
/>




If you turn that ability on, it will work properly?

HTH


>I am having trouble loading my arx. It has been suggested here that the
manifest tool should be disabled for ARX applications. When I do this, all
of my arx and dbx modules load correctly except for two of them. When those
two modules load, I get the following error message:

[Anonymous]

Yes, if I turn on the manifest, the dll loads properly. I guess I will
enable it, but I was under the impression that using a manifest in arx
applications could result in version-related problems with core microsoft
components (ie: MFC).



"Luis Esquivel" wrote in message
news:5445592@discussion.autodesk.com...
Hi Jon;

I use the manifest tool on my arx apps, for example that's the way I can
tell my program to load an specific dll version.

i.e.




version="1.0.0.0"
processorArchitecture="X86"
name="LESQ.LE.GBPoly"
type="win32"
/>
GBPoly -- Polyline Generator Engine



type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
processorArchitecture="X86"
publicKeyToken="6595b64144ccf1df"
language="*"
/>




If you turn that ability on, it will work properly?

HTH


>I am having trouble loading my arx. It has been suggested here that the
manifest tool should be disabled for ARX applications. When I do this, all
of my arx and dbx modules load correctly except for two of them. When those
two modules load, I get the following error message:

[Anonymous]

Jon:

It's a bad idea to specify a specific MFC or ATL version in an ObjectARX
app, because your app needs to use the same DLL that AutoCAD is using
(unless you really know what you're doing, and understand how to ensure that
a separate instance will work). You should figure out why your .arx wasn't
loading without the manifest and fix that problem. BTW, there's nothing
wrong with using a manifest per se -- you just can't include any of the DLLs
that need to be shared with AutoCAD. 🙂
--
Owen Wengerd
President, ManuSoft ==> http://www.manusoft.com
VP Americas, CADLock, Inc. ==> http://www.cadlock.com

[Anonymous]

Any idea what I could do to fix it? When I googled that error message
(R6034), I got a Microsoft document that says that the "application has made
an attempt to load the C runtime library without using a manifest. This is
an unsupported way to load Visual C++ DLLs. You need to modify your
application to build with a manifest."

This says to me that I must use a manifest w/my arx if I want to use ATL.
Do you know of a way to make it work?


Jon





"Owen Wengerd" wrote in message
news:5447551@discussion.autodesk.com...
Jon:

It's a bad idea to specify a specific MFC or ATL version in an ObjectARX
app, because your app needs to use the same DLL that AutoCAD is using
(unless you really know what you're doing, and understand how to ensure that
a separate instance will work). You should figure out why your .arx wasn't
loading without the manifest and fix that problem. BTW, there's nothing
wrong with using a manifest per se -- you just can't include any of the DLLs
that need to be shared with AutoCAD. 🙂
--
Owen Wengerd
President, ManuSoft ==> http://www.manusoft.com
VP Americas, CADLock, Inc. ==> http://www.cadlock.com

[Anonymous]

Hi Owen & Jon;

I read the C++ At Work magazine, and there are some recommendations by the author Paul DiLascia about the usage of manifests here:

http://msdn.microsoft.com/msdnmag/issues/06/07/CAtWork/

I introduce to one of my application in the dialog for the edit boxes the BannerCue's and the BallonTips, and that's why I use it since then and in other routines I have done. 🙂

"Balloon tips and banner cues require Common Controls version 6.0"

[Anonymous]

Jon and Luis:

Please have a look at my manifest manifesto for more about this topic:
http://otb.manusoft.com/2007/01/my-manusoft-manifest-manifesto.htm
--
Owen Wengerd
President, ManuSoft ==> http://www.manusoft.com
VP Americas, CADLock, Inc. ==> http://www.cadlock.com

[Anonymous]

Good, I'll go there and read it... thank you Owen.

by the way, I knew about your blog place in a link posted in the swamp..

http://www.theswamp.org/index.php?topic=14076.0

[Anonymous]

Thanks, Owen. That is helpful. I have 2 ATL modules & decided to go the
static linking route. It increased the size of my dll by < 5% and all
appears to be well.


Jon



"Owen Wengerd" wrote in message
news:5448775@discussion.autodesk.com...
Jon and Luis:

Please have a look at my manifest manifesto for more about this topic:
http://otb.manusoft.com/2007/01/my-manusoft-manifest-manifesto.htm
--
Owen Wengerd
President, ManuSoft ==> http://www.manusoft.com
VP Americas, CADLock, Inc. ==> http://www.cadlock.com

[Anonymous]

I quite not follow your approaches... (I'm soooo limited! )


a.