if I add a reference to a type library in a *.tlb file to my project, I
don't get a extra interop dll. If I add a reference to a *.dll
containing the type library and the com object, I get a interop dll.
Is there a way to compile all my code in one single dll, even when

I am trying to open a file from VB.NET with ZwCreateFile, but I get
STATUS_DATATYPE_MISALIGNMENT returned. It's hard to know which bits to post,
so apologies for the dump below:
<header stuff>

I'm having a problem accessing a COM component made with VS.Net 2005 from
Excel, apparently because Excel uses .Net 1 rather than 2. I can see with the
debugger which mscorlib it loads:
'EXCEL.EXE': Loaded

I've written a .net component that should be callable from asp
It's worked on 3 computers, dev xp machine and 2 2003 web edition servers.
But deploying to one production machine (also 2003 web edition) I'm getting
some errors

Hello.  I am develop a console application that needs to interact with a 3rd
party API that I believe was written in VB6.  The program works fine and
executes as expected, but when my program exits, I get an error that memory
could not be read.  I've searched around for the past ...

When I monitor print jobs using FindFirstPrinterChangeNotification,
FindNextPrinterChangeNotification etc., then I get all detailed
information about print jobs, but not the "number of copies", so when I
launch a print job of 5 pages and tell the printer I want 2 copies,

I'm having problems with a COM+ Server Application written in C# .net 1.1. The Problem only occurs on Windows 2003.
I have implemented a COM+ Application containing a pooled COM+ Component. After accessing the COM+ Component using a ProgID the component isn't deactivated and stays ...

I need some help setting up a callback between C and C#.
Here is the C code:
typedef int (*iaxc_event_callback_t)(iaxc_event e);
EXPORT void iaxc_set_event_callback(iaxc_event_callback_t func);

I have a problem with VS not referencing ADODB as primary, but as
tlbimp in the project file. Suddenly I have Interop.ADODB instead of a
PIA. ADODB is referenced by a COM component included in the project. I
have the same adodbdll in assembly-cache as my colleague, but he get a

Hey all:
I'm having *exactly* the same problem that Torbjørn Vik described in
two of his posts titled "PInvoke failure" and "Obscure marshalling
problems (NullReferenceException)" (found them on Google Groups).  He

Ok, I know this is an old topic, but for me it's new. And with all
that's been written, I still have outstanding issues. I've been able to
get .NET controls to be hosted in IE and able to deal with the
dependent assembly and strong name issues. But I've not been able to

If a third party provides closed source CCW wrapper while installing
their software, then
can it be used by any kind of COM object to access the .NET dll APIs ?
Is it possible that the third party provides support for only VB6 COM

The next wall we're hitting...
We have defined a COM object in C# .Net. We instantiate it from our main
application and call a particular method on it. We try to pass a buffer of
data to it which should not be interpreted. We define that method like

I have a C# app, using the 1.1 framework, which is using the DSO API. We are
connecting to an Analysis Services 2000 database. Visual Studio was used to
create the InterOp assemblies to allow calls to the DSO API.
The app is creating 2 threads. In the start method of each thread, ...

From our main application we're creating a COM component, written in C#
under .Net, which in turn contains a web edit control. This control acts as
an editor, and we can enter text in it. If we run it as an in-process
component, all works as expected, but when running out-of ...