COM object problem

  • Thread starter Thread starter Pete Davis
  • Start date Start date
P

Pete Davis

I have some stuff I'm exporting as COM interfaces. The problem is this:

I have two libraries. Let's call them Library A and Library B

Library A defines some interfaces and a single exception class that is also
exported.

Library B implements the interfaces from Library A.

When I build Library B, it complains that it can't find the type library for
Library A and fails to build. If I go into the bin\debug or bin\release
directory for Library A, the type library file is there. If I manually copy
it to the Library B bin\debug or bin\release directory, it builds fine, but
I have to do this EVERY time I rebuild.

Is there a way to do this automatically?

Thanks.

Pete
 
Pete,

I would define a post build step which would generate your type library,
and copy it over to the appropriate directory. This will have to be placed
in a batch file (to be run as the post-build step in VS.NET), but it should
be a trivial matter.

Hope this helps.
 
Nicholas,

Thanks. It already builds the type library, so I guess I just need to
copy it. I would expect VS.NET to handle that for me. Oh well, I can live
with that. Thanks.

Pete

--
http://www.petedavis.net
Nicholas Paldino said:
Pete,

I would define a post build step which would generate your type library,
and copy it over to the appropriate directory. This will have to be placed
in a batch file (to be run as the post-build step in VS.NET), but it should
be a trivial matter.

Hope this helps.
Click to expand...
 
Back
Top