I would like to use the shell function SHGetDesktopFolder
from within VB.NET, but I don't know how I can use it
without an implementation of the IShellFolder interface,
and was wondering if anyone could point out an answer, or

I have several problems with COM Callable Wrappers implementation. Please
answer any of the ones you know:
1. Can't get the ProgIdAttribute("Name") to work. I use
ComClassAttribute(guid,guid,guid) for all my exposed classes so I was

Reeading the MSDN page:
http://msdn.microsoft.com/library/en-us/cpguide/html/cpcondeployingapplicationfo
rcomaccess.asp?frame=true
makes me really skeptic.
I thought that using regasm /tlb:blabla.tlb blabla.dll will register the

The following snippet of code:
class Class1
{
 [DllImport("kernel32")]

I'm having a problem with CCW and method parameters. Some of the parameters
are classes.
It seems that these classes (or at least the properties inside the class)
are not seen from my VB client

Hi everybody,
 I have a customer using Win2K, MQSeries 5.2 and MQAX200.DLL from
VB.NET using interop.
 I could get some crash dumps and see that MQAX200.DLL is raising

I am writing an application that gets data from excel worksheets, it works
fine for most workbooks but when I open some by using the following line of
code:
   _xlApp = new Excel.ApplicationClass();

I am try to access a remote com server from my c# app. The server has no
dispatch interfaces. Is this possible?

I have a .exe application which exposes several COM
In VB 6.0 I can instantiate a class by using Set myClass = GetObject(path,
progid) where path is the path on harddisk to a file (actually a .INI file
in this case) and progid is the progid in registry.

I try to call c function in C#,What is the syntax of
DllImport's EntryPoint field?
Why some of extern method need to point out this field
while some of them do not need?

I've developed a MFC based ActiveX control using VC++ 6.
In the last days I've tested the control compatibility with the various
language of Visual Studio.NET and it seemed to work correctly.
Today I was forced to change the control version stored inside the .odl file

I wrote a C# wrapper for the ReadConsole Win32API as following:
(Original unmanaged signature)
BOOL ReadConsole(
 HANDLE hConsoleInput,

I am trying to Marshal an Array consisting of custom Objects from VB.NET to
VB6. The function signature in VB.NET is like the following:
Public Function GetItemArrary (Byval ItemCode as String)  as
<MarshalAsAttribute(UnmanagedType.LPArray)> Array

I am trying to get a reference to an ATL COM singleton object running on a
Windows CE 4.1 (w/DCOM) device from a C# client. I have no problem accessing
it from a Win32 client. The code that I am using to instanciate the object
is:

How can I expose VB.NET modules (shared classes) through a COM callable
wrapper? This works with classes but not with modules:
   <ProgId("Loconet_caca"),
ComClass("383F5F0D-ABFE-414C-B71C-E2369AA8BCCD",