duplicating Multi Use COM like functionality in .NET

[Guest]

With a Multi-USe COM DLL object another applic. can get reference to it. -
And if that DLL's counter continue to have a least one reference, then
another application or reference to the DLL can exchange info with that DLL.
Could See the data in the DLL if the DLL exposed it ( like a list ).

What design pattern allows me similar functionality in .NET ?? - and is
there an ability to keep the "OBJECT" runnning if the reference count goes to
0 ??

 

[Guest]

In a similar idea, how would I duplicate the idea of an activeX.exe - where
another application can grab a shared object and read/write to it.

( By the way I need to do this without a service since I wont have
permissions to install a service - but I can register a DLL. )

 

[Nicholas Paldino [.NET/C# MVP]]

Andrew,

Do you need to expose this functionality to COM? If so, then you will
have to do this through COM+, setting the object pooling properties so that
you access the same shared object, and that the object doesn't die for a
very long time (you have to determine what the appropriate lifetime is).

If you only need .NET clients to attach to this, then I would recommend
you use remoting, creating a singleton server object.

You can not create an ActiveX EXE through COM interop in .NET.

Hope this helps.

 

[Guest]

Yes thanks for reminding me about the limitations of COM clients. I was
actually llooking for something even lighter weight than a remote - it only
needs to run on the client machine. ( one non .NET app calls an C# exe with
pass params - then this shell app just would pass on the information to the
viewable 'logger' and then terminate ). While not very elegant the speed is
fast enough.

Non .NET (makes external call ) -> .net Console + pass parameters=> new info
..netConsole -> visibleGrid + pass parameters, [ visible grid appends new info]
..netConsole terminates

Non .NET app continues on.....
....repeats some time later

--
Andrew

Andrew,

Do you need to expose this functionality to COM? If so, then you will
have to do this through COM+, setting the object pooling properties so that
you access the same shared object, and that the object doesn't die for a
very long time (you have to determine what the appropriate lifetime is).

If you only need .NET clients to attach to this, then I would recommend
you use remoting, creating a singleton server object.

You can not create an ActiveX EXE through COM interop in .NET.

Hope this helps.


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

With a Multi-USe COM DLL object another applic. can get reference to
it. -
And if that DLL's counter continue to have a least one reference, then
another application or reference to the DLL can exchange info with that
DLL.
Could See the data in the DLL if the DLL exposed it ( like a list ).

What design pattern allows me similar functionality in .NET ?? - and is
there an ability to keep the "OBJECT" runnning if the reference count goes
to
0 ??

 

[Guest]

Oh I see NET remoting can also be configured like a com client... THANKS