TLB losing its reference in VBA

Hello,

I have written a C# assembly that I am using through COM interop. I need
to use it through an application that supports VBA. In the VBA
environment, I add the tlb through the references dialog, and all works
great.

But when I have to re-build the C# assembly, to fix bugs and such, next
time I enter the VBA, the reference is lost. It looks like the VBA
environment looks for the tlb using its GUID, and every time I compile
with VS..NET, the tlb gets a new GUID.

Is there a way to cause VS.NET to use the same GUID, something like binary
compatibility on the dll/tlb?

Thanks,

Noam

You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.