Write COM Object in C#

[MR]

i am developing a client C# application that utilized a legacy COM object.
For development, I cannot use the object because it has specific hardware
requirements. Therefore i would like to write a stub or "emulator" for this
COM object, preferably i C# but C++ or VB.NET would work too.
The idea is to be able to use this object in development, then in production
(when the hardware is available) just regsvr32 the "real" object and use
that instead. this means that the emulator object probably needs the same
GUID and methods , etc as the "real" object
is there a document or other source that details the development steps that
i would need to take to accomplish this?
thanks
m

[Kevin Spencer]

Here's a good starting point:

http://msdn.microsoft.com/library/de...cominterop.asp

--
HTH,

Kevin Spencer
Microsoft MVP
Professional Numbskull

The man who questions opinions is wise.
The man who quarrels with facts is a fool.

"MR" <co******@newsgroup.nospam> wrote in message
news:eO**************@TK2MSFTNGP05.phx.gbl...

i am developing a client C# application that utilized a legacy COM object.
For development, I cannot use the object because it has specific hardware
requirements. Therefore i would like to write a stub or "emulator" for
this COM object, preferably i C# but C++ or VB.NET would work too.
The idea is to be able to use this object in development, then in
production (when the hardware is available) just regsvr32 the "real"
object and use that instead. this means that the emulator object probably
needs the same GUID and methods , etc as the "real" object
is there a document or other source that details the development steps
that i would need to take to accomplish this?
thanks
m

[John A. Bailo]

MR wrote:

i am developing a client C# application that utilized a legacy COM object.
For development, I cannot use the object because it has specific hardware
requirements. Therefore i would like to write a stub or "emulator" for this
COM object, preferably i C# but C++ or VB.NET would work too.
When you say "cannot use it" I assume that when it runs, it loads some
set of resources that are too large for your workstation.

Well, you can always just register the object on your development
machine, add a reference to your c# project -- but not run it -- OR,
comment out the code that accesses it and put in dummy results.

Then, when doing a full on test, set up the real code and test on your
deployment server.
The idea is to be able to use this object in development, then in production
(when the hardware is available) just regsvr32 the "real" object and use
that instead. this means that the emulator object probably needs the same
GUID and methods , etc as the "real" object
is there a document or other source that details the development steps that
i would need to take to accomplish this?
thanks
m