Re: Custom interop
- From: "xcal" <a@xxxxx>
- Date: Thu, 16 Oct 2008 18:41:41 -0300
Let's suppose you build a class using C++ 6.0, here you decide what is
private, public, this way you obtain a COM dll, now you reference it
within a C# app, where you again, decide wich methods shall be private or
public, etc. Finally, after compile and build your C# code, youll have an
exe or dll file
with bitmaps, icons, dlls, COM dlls, etc, etc. Here you apply
code hidding tools.
Well, I dont know, does someone can see your bitmaps ?
"khalprin" <khalprin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:12133EC5-BFB2-4ADF-8134-2FD9EC12D34E@xxxxxxxxxxxxxxxx
I've imported a reference to a COM type library, so all the interfaces,see
coclasses, event sink helpers are created by tlbimp - I don't have control
over that. I'm asking about the best way (or tools to provide a way) to
write/create the custom interop.
"xcal" wrote:
" the client .net applications just see the objects they can use"
why not to use public, private, etc?
public int SharedFunction( ... )
{
// call to COM parts
}
"khalprin" <khalprin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F5D432E7-847C-422A-A113-7B08BAE3B9B4@xxxxxxxxxxxxxxxx
I've got an exe that hosts COM objects and want to use them in .net
applications. I can do this by adding the exe's type library to the
references in the .net project and all works fine. However, I want to
customize the interop assembly so the client .net applications just
thethe
objects they can use, not the interface, object, coclass name and all
thereevent helper methods. What's the best way to go about this? Are
needany
tools (besides tlbimp/ildasm/ilasm) that simplify the process. Do I
to
edit the il code or is it better to create a project that defines the
available interfaces in C#? Are there good samples for this anywere?
Thanks
.
- References:
- Custom interop
- From: khalprin
- Re: Custom interop
- From: xcal
- Re: Custom interop
- From: khalprin
- Custom interop
- Prev by Date: Re: Custom interop
- Next by Date: Re: Declare the structure in c++ component
- Previous by thread: Re: Custom interop
- Index(es):
Relevant Pages
|
Loading