Signing and Reflection with VS 2005

Question

Hello, I'm running into some difficulties with VS 2005 and signing. I have an application (that was writtin in C# 2 years ago) that uses reflection to call into Addon assemblies. It does this by referencing a config file that tells the application the new assemblies version, culture, publicKeyToken, and Type. When I build the Addon .dll using VS 2003, and specify the PublicKeyToken in the applications Config file, everything works fabulously. The application finds my assembly, and calls the methods inside of it using reflection. Our office is migrating to VS 2005 however, and when I build my AddOn using VS 2005, the BusyBeeBuilder service can no longer find the assembly. I am using the new Signing properties of VS 2005, and I have registered my .dll in the GAC (just in case), but the service still can’t seem to access my Addon assembly. Is there something additional that needs to be done in VS 2005 to correctly sign the Addon assembly? Or was there a change made in the underlying signing logic in VS 2005 that would cause this? Thank you in advance, -Ned Kost