Duplicate aecbaseMgd files in 2018 causing issues

Duplicate aecbaseMgd files in 2018 causing issues

MikeEvansUK
Advisor Advisor
3,016 Views
8 Replies
Message 1 of 9

Duplicate aecbaseMgd files in 2018 causing issues

MikeEvansUK
Advisor
Advisor

Hi all, hoping someone can help here, I am in the process of updating some code to 2018 and am having issues with the AecBaseMgd.dll version.

 

VS states, Error    The project currently contains references to more than one version of AecBaseMgd, a direct reference to version 8.0.44.0 and an indirect reference (through 'Autodesk.Aec.PropertyData.DatabaseServices.DictionaryPropertySetDefinitions') to version 8.0.44.27. Change the direct reference to use version 8.0.44.27 (or higher) of AecBaseMgd.

I have two versions of AecBaseMgd, one (v44.0) in Autocad root folder and one in the /ACA folder (v44.27).

I have renamed the files in turn. The /ACA version does not appear to reference the Aec.Civil paths.

If I import the v44.27 it defaults to the v44.0 file.

Looking in 2017, there are the same two files however they are both V 7.9.48.0

 

Any Ideas or assistance would be welcomed.

 

Mike

 

 

Mike Evans

Civil3D 2022 English
Windows 7 Professional 64-bit
Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz (8 CPUs), ~4.0GHz With 32768MB RAM, AMD FirePro V4900, Dedicated Memory: 984 MB, Shared Memory: 814 MB

0 Likes
Accepted solutions (1)
3,017 Views
8 Replies
Replies (8)
Message 2 of 9

augusto.goncalves
Alumni
Alumni

If I understood right, you should be using the reference from /ACA folder. I'm assuming you have a .NET code with direct reference to those DLLs, so make sure it's set to copy local false and specific version to false, which can help to late-bind the type definition. If the problem persists, maybe a clean install can resolve this conflicting issue.

Regards,



Augusto Goncalves
Twitter @augustomaia
Autodesk Developer Network
0 Likes
Message 3 of 9

MikeEvansUK
Advisor
Advisor

Thanks Augusto, I have tried the settings to no avail.

 

If I import the file from \ACA folder it just imports the version in the AutoCad Root folder instead.

I tried renaming the /root version and importing the \ACA version but the \ACA version does not seem to hold the same references that the other does. That is if I force the issue by renaming the /AutoCAD version it generates errors stating for example Autodesk.Civil: Civil is not a member of Autodesk. The only items listed are .Aec, .Aecc & .AutoCad.

 

I'd rather not have to get the IT involved for a full re-install unless necessary. Any other ideas before I face a re-install all. Can I manually force the location in Vb Express?

 

Thanks

 

Mike

 

Mike Evans

Civil3D 2022 English
Windows 7 Professional 64-bit
Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz (8 CPUs), ~4.0GHz With 32768MB RAM, AMD FirePro V4900, Dedicated Memory: 984 MB, Shared Memory: 814 MB

0 Likes
Message 4 of 9

Norman_Yuan
Mentor
Mentor

@MikeEvansUK, I am currently developing/supporting Civil3D2018 .NET plugins, using VS2017 (V15.7.4). Yes, the version of AecBaseMgd.dll in AutoCAD root folder and in \ACA folder are slightly different as you described (8.0.44.0 in \root, 8.0.44.27 in \ACA).

 

In my VS projects where AecBasMgd.dll is referenced, I use the one from root (8.0.44.0). In projects where I need to deal with PropertySet data, I add reference to AecPropDataMgd.dll in \ACA folder (of course both "Copy To Local" are set to False).

 

I do not run into any VS error, my code compiles as expected. See attached pictures of referenced DLLs in my VS project.

 

Norman Yuan

Drive CAD With Code

EESignature

0 Likes
Message 5 of 9

MikeEvansUK
Advisor
Advisor

@Norman_Yuan Thanks for the input.

Firstly from your post I note the following:

 

Your AecBaseMgd file is not being imported from the AutoCAD Root folder but instead the ObjectARX SDK. Looking at the version etc it all seems to match so I am not sure how much of a difference this makes?

 

You are using VS2018, I am currently using VSE2013, again not sure this really makes a difference.

 

I have tried removing both and re-inserting the reference's one by one ensuring they are False... and I note the following.

 

When I insert AecBaseMdg the only errors I receive are relating to the Property Data:

Error    47    Type 'Autodesk.AEC.PropertyData.DatabaseServices.DictionaryPropertySetDefinitions' is not defined.  

 

When I insert the AecPropData reference I receive the following error.

 

Error    32    The project currently contains references to more than one version of AecBaseMgd, a direct reference to version 8.0.44.0 and an indirect reference (through 'Autodesk.Aec.PropertyData.DatabaseServices.DictionaryPropertySetDefinitions') to version 8.0.44.27. Change the direct reference to use version 8.0.44.27 (or higher) of AecBaseMgd.  

 

I remember having this issue in the past but how I corrected this I have no Idea now. I thought it was through copy local & specific version but neither of these seem to help.

 

Not really sure other than a Full re-install what to do next. As I'd rather not do that @augusto.goncalves if there is another way to correct I would appreciate the help.

 

 

Mike Evans

Civil3D 2022 English
Windows 7 Professional 64-bit
Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz (8 CPUs), ~4.0GHz With 32768MB RAM, AMD FirePro V4900, Dedicated Memory: 984 MB, Shared Memory: 814 MB

0 Likes
Message 6 of 9

Norman_Yuan
Mentor
Mentor

The reason of my referenced AecBaseMgd.dll located in folders other than AutoCAD/Civil3D install folder is that I place all AutoCAD/Map/Civil3D reference DLLs in a single folder, so that whenever I start a new VS projects (I do this a lot, as primarily focus on CAd development currently), I only go to this  location to add all needed references to AutoCAD/Map/Civil3D. Since all this reference DLLs should be set "Copy Local" to false, where they are do not matter. the AecBaseMgd.dll was grabbed from AutoCAD/Civil install folder, not the one from "...\ACA\" folder.

 

I do not have VS2013 available from all my development computers any more, thus, not able to reproduce the error you ran into. But you did see that the version of AecBaseMgd.dll I use is 8.0.44.0 and the AecPropDataMgd.dll version is 8.0.44.27 (in turn it references AecBaseMgd.dll 8.0.44.27). Since I did not have the issue as you did with VS2017, maybe it is VS2013 issue (even you had made sure "Specific Version" being set to false)? 

 

You may want to download VS2017 Community version and give it a try.

 

Norman Yuan

Drive CAD With Code

EESignature

0 Likes
Message 7 of 9

Jeff_M
Consultant
Consultant
Accepted solution

Mike, you show that you are using VS2013. This may sort of the problem. See the required versions here: https://knowledge.autodesk.com/search-result/caas/CloudHelp/cloudhelp/2018/ENU/OARX-DevGuide-Managed...

Jeff_M, also a frequent Swamper
EESignature
0 Likes
Message 8 of 9

MikeEvansUK
Advisor
Advisor

Thanks Jeff, that's a good catch and simple workaround.

 

I didn't know you needed certain versions for the programs, I've used 2012 & 2013 right up to 2017 without issues.

 

Before I sign this off I'll make sure this is the fix (which I believe it will be).

 

Mike

 

Mike Evans

Civil3D 2022 English
Windows 7 Professional 64-bit
Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz (8 CPUs), ~4.0GHz With 32768MB RAM, AMD FirePro V4900, Dedicated Memory: 984 MB, Shared Memory: 814 MB

0 Likes
Message 9 of 9

MikeEvansUK
Advisor
Advisor

Yes, updating to VSE2015 resolved the issue.

 

Almost everything working as it should again.

 

Thanks Jeff.

 

Mike

Mike Evans

Civil3D 2022 English
Windows 7 Professional 64-bit
Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz (8 CPUs), ~4.0GHz With 32768MB RAM, AMD FirePro V4900, Dedicated Memory: 984 MB, Shared Memory: 814 MB

0 Likes