Known Issues with COM Interop/GAC?

 

We are a software company with a fairly large vb6 codebase who recently started to migrate to visual studio .net 2005.  We are attempting to release the next iteration of our software using several COM interop assemblies written in VB.NET.  We have a central build machine which checks out of source control and builds the software nightly.

Although the build seems to run successfully, we are having several application runtime issues.  These include: automation errors, more specifically a "cannot find specified file" error.   We have found that some of our assemblies have been building with versions we would not expect.

Has anyone had similar behavior when working with COM Interop AND/OR using the Global Assembly Cache.   Or is there any way we can see example projects of proper implementation of a COM/GAC setup?  Are we approaching this incorrectly.

 

We've attached a couple examples of our build scripts for our .NET assemblies.

 

Thank you in advance for any help or suggestions.

 

Walter L. Diethorn III

Software Developer

Applied Systems Associates, Inc.

 

 

aSa.Utilities.fbz4 (5.923 KB)aSaFramework.NET.fbz4 (9.15 KB)aSaShared.NET.fbz4 (21.041 KB)

Hi Walter,

This doesn't sound like a FinalBuilder issue, although I guess it may be FinalBuilder related.

I actually blogged about something similar yesterday, here: https://www.finalbuilder.com/blogs.aspx?EntryID=239

Basically, you can sometimes see FileNotFoundExceptions when working with assemblies which are only built against a certain architectures. This is because on .NET Framework 2.0 and above, there are actually 4 possible GACs. See the blog post for the details. :-).

Regards,

Angus