First off I am not sure if you are referring to adding assemblies to managed C++ or you are trying to do interop from unmanaged code directly to managed code. So I'll talk a bit about both:
So real quick, adding .Net assemblies to managed C++ is much like adding them in C#, the syntax is different but both share the same notions
C#
using System.Xml
MC++
#using <mscorlib.dll
#using<System.Xml.dll
using namespace System::Xml
The environment variable LIBPATH is used to search for assembles referenced in the #using directive. You can specify the path in the #using directive as well. The .Net framework directory is also used to lookup assemblies as well.
Now to use from unmanaged code you have two choices
1) Use gcroot templates to define unmanaged objects with access to managed objects
2) Use TLBExp to make COM callable wrappers to use from unmanaged code
I only use the first option if I really have to. The code to do this can get a little tricky as it involves carefully sequestering of references to managed classes in your unamanaged code. So in general if I can get away with it, I use COM interop to access .Net objects. Now then, not all .Net objects are easy to use from COM land (basically you can create .Net objects from COM if they have default constructors, you can use them as long as they don't have vital static methods you need access to)
Hope this helped
Kevi
----- Kanaiya wrote: ----
hi how to add any dotnet component like we add in c#
and what path to set. by