kevin.vandecar
2006-08-09, 03:08 PM
There is a problem with the ABS COM Interop assemblies working correctly with the .NET Framework due to a problem with registration. The ABS installer does not register the COM interop assemblies, but does correctly install them to the Global Assembly Cache (GAC). The results are that when the COM type libraries are referenced from within a .NET project (a.k.a using COM interop) the reference is incorrectly established. Visual Studio can not find the GAC assemblies and thus creates it's own "local copy" interop wrapper. This leads to further problems when trying to redistribute an application.
The solution is to register the COM interop assemblies correctly on each system where the application will reside. In the development project within Visual Studio, re-reference the type libraries to estblish the correct reference to the GAC assemblies.
Included with this communication are three registry files (one for each type library) that needs to be registered to resolve the problem. Please see attached ZIP file.
This is only a problem with the FCS ABS 2007 software. A future service pack release will resolve this problem.
Kevin Vandecar
Software Engineer
Autodesk Building Solutions Division
The solution is to register the COM interop assemblies correctly on each system where the application will reside. In the development project within Visual Studio, re-reference the type libraries to estblish the correct reference to the GAC assemblies.
Included with this communication are three registry files (one for each type library) that needs to be registered to resolve the problem. Please see attached ZIP file.
This is only a problem with the FCS ABS 2007 software. A future service pack release will resolve this problem.
Kevin Vandecar
Software Engineer
Autodesk Building Solutions Division