Re: VC6 ATL DLL interop with VB.NET
- From: v-phuang@xxxxxxxxxxxxxxxxxxxx ("Peter Huang" [MSFT])
- Date: Mon, 17 Apr 2006 02:47:40 GMT
Hi Dave,
As I said before, the IDE did not generate Symbol file and source file for
the Interop Assembly so the any debugger did not know that the code is.
If you do need to behavior, you have to create the Interop Assembly
manually so that it is a common class library coded by yourself.
How to: Create Wrappers Manually
http://msdn2.microsoft.com/en-us/library/x8fbsf00(VS.80).aspx
But we may still need the symbols for the CLR itself.
Commonly the IDE will generate correct Wrap assembly for us, if you did not
want the generated Assembly, we have to create one ourselves per the link
above.
Anyway, there is a detailed COM Interop Referece Book, you may have a check.
..NET and COM: The Complete Interoperability Guide (Paperback)
by Adam Nathan
http://www.amazon.com/gp/product/067232170X/103-1572468-9548663?v=glance&n=2
83155
If you still have any concern, please feel free to post here.
Best regards,
Peter Huang
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
.
- References:
- VC6 ATL DLL interop with VB.NET
- From: Dave
- RE: VC6 ATL DLL interop with VB.NET
- From: "Peter Huang" [MSFT]
- Re: VC6 ATL DLL interop with VB.NET
- From: Dave
- Re: VC6 ATL DLL interop with VB.NET
- From: "Peter Huang" [MSFT]
- Re: VC6 ATL DLL interop with VB.NET
- From: Dave
- VC6 ATL DLL interop with VB.NET
- Prev by Date: Rich text limiting text
- Next by Date: Reading application settings
- Previous by thread: Re: VC6 ATL DLL interop with VB.NET
- Next by thread: Determine if a File exists
- Index(es):
Relevant Pages
|