davguyonlinemicrosoftcom 01 Apr 2004 There is a known bug (in both VS 2002 and VS 2003) where Regasm fails to register properly if you are trying to register an assembly and the dependency can't be found. If you run RegAsm in the bin dir, usually the dependencies are copied locally. However, setup projects run regasm from the obj dir (for other important reasons), where the dependency is not available. In this case, setup projects will fail to register correctly. The workaround is to add the assembly to your project as a "file", right click in the File System Editor, and select Add File, and navigate to the assembly in the bin dir. Usually that gets regasm to work and we get the proper registration information.