Com+ vs. DotNet Objects

[Gregg Maggioli]

I have a dll that we wrote using VB 6 and the Winsock object. We use
the dll as a COM+ object on our .Net server. The COM+ seams to handle
the mutli-threading even though the dll is single threaded (we have
done extensive testing and it works very well). Initially when we
created the dll we did not register it as a COM+ object and if
multiple simultaneous call were made to it the return data would be
passed back to the wrong calling application. Once we registered this
dll as a COM+ object it worked great.

Question:
Now we are looking to rewrite the VB 6 single threaded winsock
communication dll using VB.net. Does .Net offer the same
functionality of writing a single threaded object and registering it
as COM+ equivalent service in DotNet?

 

[Adrian Forbes [ASP MVP]]

You could write this dll in .net and not bother with com+ at all as .net is
multi-threaded. It could sit as a regular dll on your machine. You could
also look into remoting if you want the equivalent of dcom where one
machine/process accesses a dll on another machine/process.

 

[IndyKid]

Maybe a little more clarification - the dll or DotNet Object will be
called from multiple web applications so the dll or DotNet object will
be loaded on the WebServer running the DotNet framework. So, many
requests will need to be processed as indepentent requests keeping the
returned data isolated from other calls.

I hope this helps...