Class Libraries Output to Same Directory

  • Thread starter Thread starter Brian Reed
  • Start date Start date
B

Brian Reed

I have three projects in the same solution that are all class library
projects. The projects are COM interop objects that will be used within my
COM framework. It is important to me to have all three projects building to
the bin directory of my COM framework so that I don't have to use the
/codebase option when registering the objects.

Here is my problem, all three projects reference the same COM typelib, which
will generate an interop.TYPELIB.dll file. Only one of the projects will
successfully build to the target directory and any code in the other two
projects that references the COM typelib fails to build as if the reference
wasn't even there.

Since one project works successfully, this appears to be a Visual Studio
..NET problem. It looks to me like the first project opens the
interop.TYPELIB with no sharing allowed, so the other projects can't
reference it.

Is there any solution to this problem? Can I make VS not hold open (not
sharing) the referenced interop dll?

Thanks
 
Thanks. That did hte trick. I just let one unique reference be copied to
the local area. It seems like a strange error that can be misleading. It
took me awhile to figure out that the proplem was with sharing the same
file.
 
Back
Top