I think this release is the one that has officially driven me insane. I'm not sure how to best describe my frustration in the hopes of finding a solution, so I'll start at the beginning. If I bore you, or put you to sleep, I apologize now. Working on a fairly large VS2010 Solution, comprised of 5 separate projects all linked to together. These all work perfectly well in C3D2010-C3D2012 in both x64 & x86 flavors (one dll per Acad version), some using strictly .NET managed code, others have COM mixed in. Enter C3D2013 and notice that MOST of the old COM Interops has been ported to .NET wrappers. So we decide to update our code base to utilize the new offerings. First thing to do, make a full copy of the solution and change all of the references. With a few minor tweaks to satisfy the new Acad2013 Core split, it builds and runs. I then spend the next few weeks going through and changing all the code previously using COM to it's .NET counterpart, going in steps (change/build/debug) so as to ease the debug process. There are a few lingering issues, but most everything appears to have been ported nicely.
In the meantime, it's decided to create a 2013 version using the old COM based code. This builds and runs perfectly on my Win7x64 machine. I decide to test on a XPx86 as a precaution. Good thing! It doesn't work, failing at every attempt to access a C3D COM object. After asking many questions, and getting many varied answers, it was finally determined that separate builds must be made for x64 & x86, using the Interops from the installs of each of those 2 flavors. I found a way to do so (again after exhaustive searches and some trial & error) in the same VS Solution, and this route has worked well for the old project.
Since I now knew I needed these separate builds, I went ahead and made the same changes to the new .NET solution and projects. Test the builds, and all is smooth in both x86 & x64 installs. Great, now I can get back to those problem areas that didn't port quite right. Looks like I need to make a change to a form with user controls created in one of the other projects (MANY of the forms we have use this same process), so I click the form to open it, and am presented with an error screen, saying it can't load the form in the designer due to a missing file (AeccDbMgd.dll). The missing file is one that IS referenced, and the project would not build at all if it was unable to be found. So I know VS can find the file, but for some unknown reason the Designer is not finding it. And further inspection of the forms & controls is not giving any clues as to why, since none of them rely on the 'missing' file to construct the forms. I've spent literally days working on this now, and have found ONE web page that pretty much describes the issue I'm seeing (this one)
but after following the suggestions there, I am still stuck with projects that cannot use the controls previously created. Even trying to use it in a form in the same project throws this error. (By 'cannot use', I mean create a new form or edit an existing one in the Designer. The solution still builds and runs.)
All this, because MS & Autodesk decided to make things 'simpler' by removing the Interops from the GAC and Embedding them into the projects, thereby forcing the separate builds. So far, I'm at a loss on how to attempt correcting this. If you made it this far without snoring, thanks! If you have any suggestions, double thanks!