Re: VC6 ATL DLL interop with VB.NET
- From: v-phuang@xxxxxxxxxxxxxxxxxxxx ("Peter Huang" [MSFT])
- Date: Fri, 14 Apr 2006 08:01:30 GMT
Hi Dave,
From your description, you have resolved the issue, if I have anymisunderstanding please feel free to post here.
I know that your solution worked in VB6, because we can upgrade VB6 Project
into VB.NET project, so I suggest you have a try.
To debug an application, we need the symbols otherwisse we will only see if
the assembly code. Unfortunately , the IDE generated Interop Assembly
neither generated Symbols(commonly it is pdb file) nor source code. So we
can not debug into it.
But if you have both .NET client source code and C++ source code, we can
debug into the C++ code when we try to call into C++ aproach from .NET.
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.
.
- Follow-Ups:
- Re: VC6 ATL DLL interop with VB.NET
- From: Dave
- Re: VC6 ATL DLL interop with VB.NET
- 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
- VC6 ATL DLL interop with VB.NET
- Prev by Date: Re: String Tokenizing - Help!
- Next by Date: Re: Email Issue due to Antivirus (posting again)
- Previous by thread: Re: VC6 ATL DLL interop with VB.NET
- Next by thread: Re: VC6 ATL DLL interop with VB.NET
- Index(es):
Relevant Pages
|