Topic: Custom Subassemblies from C3D 2009 in C3D 2010

[bdough15]

I have a number of custom subassembilies that I created and successfully installed in C3D 2009. I have tried to use the same .pkt files to import these subassemblies into 2010 with no success. On my home computer (learning version) the custom subassemblies import ok, but when I try insert them into an assembly I just get the circles and the error "Subassembly project, module or class not found". On my machine at work, when I try to import the .pkt file, AutoCad crashes everytime.

Any ideas on what has changed to make the subassemblies not work?

[mjfarrell]

Doc,

I have found these two(2) documents; I haven't tested them.

Did you attempt to use the process outlined in this document <ignore version ref>?
http://usa.autodesk.com/adsk/servlet/ps/item?siteID=123112&id=5590339&linkID=9240697
Does this process also not work?

http://usa.autodesk.com/adsk/servlet/ps/item?siteID=123112&id=9091860&linkID=9240697

[mjfarrell]

Although in this document :http://usa.autodesk.com/adsk/servlet/ps/item?siteID=123112&id=5590339&linkID=9240697

We are cautioned as follows:

Note: It is strongly recommended that you delete the subassemblies and recreate the assemblies in your drawings using the new subassemblies provided by Autodesk Civil 3D 2006, as enhancements have been made to how these new subassemblies process slope and grade values.

So it might seem that autodesk has STILL left this issue unaddressed, adding to the loss of productivity associated with upgrading.
Nice job there guys!

Propably NOT the answer you were looking for.

[sinc]

I have some custom subassemblies that I cannot get to compile in 2010.  Since we're actually using 2009 in production, I haven't poked around in them yet to try and figure out why they no longer compile.  But Autodesk changed something between 2009 and 2010 which appears to affect .NET subassemblies, and my code that works in C3D 2008 and C3D 2009 will not compile for C3D 2010.

I'm not sure if this is related to what you are seeing or not, since I haven't yet taken the time to track down this particular problem.

[Dinosaur]

Early on, the VBA codes within the assemblies seemed to cause a lot of the upward compatibility issues.  Have they changed how the assemblies are coded now or might this still be part of the problem?

[sinc]

"VBA codes"...?

[Dinosaur]

Weren't those assemblies written in VBA?  It seemed like something changed in the coding for them so they were not compatible with the new release - I'm talking about '05 thru '07 in particular.  I know I had to recreate the assembly in the new format for it to not crash the drawing on start up back then.

[sinc]

They switched to .NET subassemblies in 2008.  So all of the old VBA subassemblies were converted to (some rather nasty) VB.NET code.  At least for a while, they were shipping both the VBA and .NET versions (although I'm not sure if 2010 still has the VBA versions).

2010 seems to have introduced a change to the API.  My custom .NET subassemblies that compiled just fine in both C3D 2008 and C3D 2009 do not compile in C3D 2010, and I haven't yet taken the time to figure out why.  I think it might have something to do with the way they started adding more C3D access to the managed API in 2010 - they changed something in the process.

[mjfarrell]

I'm fair certain these assemblies, were created in 2008/2009 versions.