[No Subject]

[No Subject]

Anonymous
Not applicable
1,040 Views
6 Replies
Message 1 of 7

[No Subject]

Anonymous
Not applicable
Gagan, If I add accui.dll and the *mgd.dll files all builds ok. No time to test but
I will tonight if you don't get it going.

From: "Gagan Gajabaharia"
Subject: Problems with AcRibbon.dll
Date: Wednesday, January 21, 2009 12:25 PM

In my Managed C++ project, I added a reference to AcRibbon.dll. After
having done that, in VS2005, the build is not successful; below are few
lines from the build Output. The build process seemingly goes on and on.
Any idea what is going on here? Thanks!

Gagan
-------------------------

1>------ Build started: Project: AppCore, Configuration: Debug Any CPU
------
1>AppCore -> C:\App\Starmaker\Output\Bin\debug\core\AppCore.dll
2>------ Build started: Project: ARXRunTime, Configuration: Debug Win32
------
2>Copying 'c:\Program Files\AutoCAD 2009\acdbmgd.dll' to target directory...
2>Copying 'c:\Program Files\AutoCAD 2009\acmgd.dll' to target directory...
2>Copying 'c:\Program Files\AutoCAD 2009\acmgdinternal.dll' to target
directory...
2>Copying 'c:\Program Files\AutoCAD 2009\AcWindows.dll' to target
directory...
2>Copying 'c:\Program Files\AutoCAD 2009\AcRibbon.dll' to target
directory...
2>Copying 'c:\Program Files\AutoCAD 2009\en-US\AcRibbon.resources.dll'
to target directory...
2>Compiling...
2>StdAfx.cpp
2>c:\program files\autocad 2009\acwindows.dll : error C2220: warning
treated as error - no 'object' file generated
2>c:\program files\autocad 2009\acwindows.dll : warning C4945:
'GeneratedInternalTypeHelper' : cannot import symbol from 'c:\program
files\autocad 2009\acwindows.dll': as
'XamlGeneratedNamespace::GeneratedInternalTypeHelper' has already been
imported from another assembly 'AdWindows'
2> c:\program files\autocad 2009\adwindows.dll : see declaration
of 'XamlGeneratedNamespace::GeneratedInternalTypeHelper'
2> first seen type is used; re-order imported assemblies to use
the current type
2> This diagnostic occurred while importing type
'XamlGeneratedNamespace.GeneratedInternalTypeHelper' from assembly
'AcWindows, Version=17.2.0.0, Culture=neutral, PublicKeyToken=null'.
2>c:\program files\autocad 2009\acribbon.dll : warning C4945:
'GeneratedInternalTypeHelper' : cannot import symbol from 'c:\program
files\autocad 2009\acribbon.dll': as
'XamlGeneratedNamespace::GeneratedInternalTypeHelper' has already been
imported from another assembly 'AdWindows'
2> c:\program files\autocad 2009\adwindows.dll : see declaration
of 'XamlGeneratedNamespace::GeneratedInternalTypeHelper'
2> first seen type is used; re-order imported assemblies to use
the current type
2> This diagnostic occurred while importing type
'XamlGeneratedNamespace.GeneratedInternalTypeHelper' from assembly
'AcRibbon, Version=17.2.0.0, Culture=neutral, PublicKeyToken=null'.
2>x:\output\bin\debug\core\acdbmgd.dll : warning C4945:
'LineWeightConverter' : cannot import symbol from
'x:\output\bin\debug\core\acdbmgd.dll': as
'Autodesk::AutoCAD::DatabaseServices::LineWeightConverter' has already
been imported from another assembly 'acdbmgd'
0 Likes
1,041 Views
6 Replies
Replies (6)
Message 2 of 7

Anonymous
Not applicable
Paul Richardson
> Gagan, If I add accui.dll and the *mgd.dll files all builds ok. No time to test but
> I will tonight if you don't get it going.
>
If I reference the ribbon related dlls in a new C++ project, they
compile/build fine. However, the same results in failed build in my
existing project. The existing project is part of a solution and there
is a lot of dependency across projects in the solution. I am beginning
to suspect this is more of VS2005 issue than ObjectARX.NET.

Thanks for the help.

Gagan
0 Likes
Message 3 of 7

Anonymous
Not applicable
Gagan Gajabaharia wrote:
> Paul Richardson
>> Gagan, If I add accui.dll and the *mgd.dll files all builds ok. No time to test but
>> I will tonight if you don't get it going.
>>
> If I reference the ribbon related dlls in a new C++ project, they
> compile/build fine. However, the same results in failed build in my
> existing project. The existing project is part of a solution and there
> is a lot of dependency across projects in the solution. I am beginning
> to suspect this is more of VS2005 issue than ObjectARX.NET.
>
> Thanks for the help.
>
> Gagan

Hi Paul,

This was indeed issue with VS2005. Although MS claims this these errors
that I reported were fixed in VS2005 SP1, it is not actually. I was able
to fix the build by setting AcRibbon reference's "Use Dependencies In
Build" to false (in Project Properties->Common Properties->References).
That has fixed this issue for me.

Thanks!

Gagan
0 Likes
Message 4 of 7

Anonymous
Not applicable
Glad you got it working - sorry for the new thread - oops.
"Gagan Gajabaharia" wrote in message news:[email protected]...
Gagan Gajabaharia wrote:
> Paul Richardson
>> Gagan, If I add accui.dll and the *mgd.dll files all builds ok. No time to test but
>> I will tonight if you don't get it going.
>>
> If I reference the ribbon related dlls in a new C++ project, they
> compile/build fine. However, the same results in failed build in my
> existing project. The existing project is part of a solution and there
> is a lot of dependency across projects in the solution. I am beginning
> to suspect this is more of VS2005 issue than ObjectARX.NET.
>
> Thanks for the help.
>
> Gagan

Hi Paul,

This was indeed issue with VS2005. Although MS claims this these errors
that I reported were fixed in VS2005 SP1, it is not actually. I was able
to fix the build by setting AcRibbon reference's "Use Dependencies In
Build" to false (in Project Properties->Common Properties->References).
That has fixed this issue for me.

Thanks!

Gagan
0 Likes
Message 5 of 7

Anonymous
Not applicable
Paul Richardson
> Glad you got it working - sorry for the new thread - oops.

I think I replied too early. I still have problems when I reference
AdWindows.dll and AcRibbon.dll in a C++ project. It gives C4945 warning
as below:

Warning 1 warning C4945: 'GeneratedInternalTypeHelper' : cannot import
symbol from 'c:\program files\autocad 2009\acribbon.dll': as
'XamlGeneratedNamespace::GeneratedInternalTypeHelper' has already been
imported from another assembly 'AdWindows' c:\program files\autocad
2009\acribbon.dll 1


I was hoping I could ignore this warning using pragma, but can you
comment on this?

Thanks, Gagan
0 Likes
Message 6 of 7

Anonymous
Not applicable
I can add all the libraries here and build find. I did some digging and it seems cli doesn't do
xmal. Sorry hopefully someone else can help out. Came across a post by Kean while poking
might be useful for general ribbon help.

http://through-the-interface.typepad.com/through_the_interface/2008/04/the-new-ribbonb.html


"Gagan Gajabaharia" wrote in message news:[email protected]...
Paul Richardson
> Glad you got it working - sorry for the new thread - oops.

I think I replied too early. I still have problems when I reference
AdWindows.dll and AcRibbon.dll in a C++ project. It gives C4945 warning
as below:

Warning 1 warning C4945: 'GeneratedInternalTypeHelper' : cannot import
symbol from 'c:\program files\autocad 2009\acribbon.dll': as
'XamlGeneratedNamespace::GeneratedInternalTypeHelper' has already been
imported from another assembly 'AdWindows' c:\program files\autocad
2009\acribbon.dll 1


I was hoping I could ignore this warning using pragma, but can you
comment on this?

Thanks, Gagan
0 Likes
Message 7 of 7

Anonymous
Not applicable
Gagan, Seem since c++/cli doens't do xaml you can just ignore it...
"Gagan Gajabaharia" wrote in message news:[email protected]...
Paul Richardson
> Glad you got it working - sorry for the new thread - oops.

I think I replied too early. I still have problems when I reference
AdWindows.dll and AcRibbon.dll in a C++ project. It gives C4945 warning
as below:

Warning 1 warning C4945: 'GeneratedInternalTypeHelper' : cannot import
symbol from 'c:\program files\autocad 2009\acribbon.dll': as
'XamlGeneratedNamespace::GeneratedInternalTypeHelper' has already been
imported from another assembly 'AdWindows' c:\program files\autocad
2009\acribbon.dll 1


I was hoping I could ignore this warning using pragma, but can you
comment on this?

Thanks, Gagan
0 Likes