referencing an ATL project

[Manny Silva]

Hi,

I'm trying to create a simple managed C++ application that will be a test
UI around a couple of ATL COM DLL projects that I have created (all with
VS2003). What I am attempting to do is bring all three projects into the
same solution and use them together. Now, to the managed project that serves
as the test UI, I added project references to the other two ATL projects.
The IDE accepted that just fine and the properties of the references point
properly to the COM DLLs, but no proxy DLLs were created, nor can I find any
way to reference the datatypes from those DLLs. I have successfully done
this using non-project references, but I was really hoping that I could use
this project to debug the COM DLLs, in which case it would be really nice to
have all projects in the same solution and be able to step in and out of the
interactions between projects.

--
Thanks in advance for your help,
Manny

[Tarek Madkour [MSFT]]

"=?Utf-8?B?TWFubnkgU2l sdmE=?=" <Ma********@nos pam.nospam> wrote in
news:3A******** *************** ***********@mic rosoft.com:

I'm trying to create a simple managed C++ application that
will be a test
UI around a couple of ATL COM DLL projects that I have created
(all with VS2003). What I am attempting to do is bring all
three projects into the same solution and use them together. Now, to the managed project that serves as the test UI, I added
project references to the other two ATL projects. The IDE
accepted that just fine and the properties of the references
point properly to the COM DLLs, but no proxy DLLs were created,
nor can I find any way to reference the datatypes from those
DLLs.

When referencing projects, we can't tell with certainty the type
of output this project creates (it may be a COM object one day and
then you can change it to an MFC app the next day). Consequently,
we don't try to do the automatic "tlbimp" that we do for
referenced COM objects.

To get the setup you want to do the following:
1) add tlbimp as a post-build event on your COM object
2) add a dependency from the managed app on the COM object's
project
3) add a /FU relativepath\in teropdllname.dl l to the managed app's
project properties

You can also replace steps 2 and 3 by simply adding references to
both the project and the DLL created by tlbimp from your managed
app.

Thanks,
--
Tarek Madkour, Visual C++ Team
This posting is provided "AS IS" with no warranties, and confers
no rights.