COM (VB6) interop with .NET assemblies
From: Raghu (rraghur_ng_at_yahoo.com)
Date: 12/24/04
- Next message: Paul Delcogliano: "problem with strong name CAS"
- Previous message: rox.scott: "GetProcessesByName() fails intermittantly with Access Denied"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 23 Dec 2004 23:25:11 -0800
Hi,
I need to build an offline client hosted in outlook. As we need to
support outlook 2000+, we will have to write COM add-ins in VB6 or VC++
ATL.
However for the framework that implements the offline functionality, we
would like to use .NET (the Smart Client application block as a
building block)
I would like to know if there are any security issues with
1. Using interop to call .NET managed assemblies.
- front end VB6 add-in forms calling .NET f/w assemblies
2. The VB6 add in DLLs will be signed and certified. But the .NET
assemblies referred to by the VB6 DLL - does it need to be signed AND
certified or does just signing work?
3. Are there any pointers/links/refs to security issues when calling
.NET assemblies from COM components (as the two security models are
different?)
Thanks!
Raghu
- Next message: Paul Delcogliano: "problem with strong name CAS"
- Previous message: rox.scott: "GetProcessesByName() fails intermittantly with Access Denied"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
