MBR IT/.NET 247 : Out-of-proc question on ASPFriends.com 'aspngbeta' list

Out-of-proc question

Messages

Related Types

This message was discovered on ASPFriends.com 'aspngbeta' list.
Responses highlighted in red are from those people who are likely to be able to contribute good, authoratitive information to this discussion. They include Microsoft employees, MVP's and others who IMHO contribute well to these kinds of discussions.

Goldfarb, Christopher

All,

We have a COM object wrapping a single-threaded dll. This worked fine for
individual clients; in the web world, it locks when more than one user tries
to hit it at the same time. For various reasons we cannot modify the dll.

We are thinking about rewriting the COM wrapper as an out-of-proc .exe
instead. I realize this breaks the ability to run tlbimp against it to
create a .NET assembly/dll. My question is, how can one go about
instantiating an instance of an out-of-proc .exe from within a web form?

Thanks,
// Chris

Reply to this message...

Willy Denoyette (VIP)

Tlbimp runs against any file containing a COM type library. This file can be
a .tlb, .dll, .odl, .ocx, .exe

Willy.

----- Original Message -----
From: "Goldfarb, Christopher" <Click here to reveal e-mail address>
To: "aspngbeta" <Click here to reveal e-mail address>
Sent: Wednesday, May 30, 2001 6:35 PM
Subject: [aspngbeta] Out-of-proc question

> ......
I realize this breaks the ability to run tlbimp against it to
> create a .NET assembly/dll. My question is, how can one go about

[Original message clipped]

Reply to this message...

Martin & Leah Lacey

per chance, are you using the same instance of objects from that
single-threaded dll for all clients? i.e. storing them in the IIS
Application space?

-----Original Message-----
From: Goldfarb, Christopher [mailto:Click here to reveal e-mail address]
Sent: May 30, 2001 9:36 AM
To: aspngbeta
Subject: [aspngbeta] Out-of-proc question

All,

We have a COM object wrapping a single-threaded dll. This worked fine for
individual clients; in the web world, it locks when more than one user tries
to hit it at the same time. For various reasons we cannot modify the dll.

We are thinking about rewriting the COM wrapper as an out-of-proc .exe
instead. I realize this breaks the ability to run tlbimp against it to
create a .NET assembly/dll. My question is, how can one go about
instantiating an instance of an out-of-proc .exe from within a web form?

Thanks,
// Chris

| [aspngbeta] member Click here to reveal e-mail address = YOUR ID
| http://www.asplists.com/asplists/aspngbeta.asp = JOIN/QUIT

Reply to this message...

Goldfarb, Christopher

I create unique instances of the multithreaded COM wrapper for each, but
they are all running within the IIS process. So the thread locks because of
the .dll (cvs2ntlib.dll), which is why we are looking into running it
out-of-proc. Since tlbimp works with COM .exe's it looks like it's ok.

The cvs2ntlib library allows Win32 machines to interface to CVS running on
Linux or Unix boxes. Interestingly enough, over concern about the
security/performance issues with running out-of-proc in a web environment, I
dug around the 'net last night and found there is a CVS server application
written for WinNT - called CVSNT, no less. I don't suppose anyone has heard
about this product? This would be an optimal solution as it eliminates the
need for two whole layers - the COM wrapper and cvs2ntlib.

Regards,
// Chris

[Original message clipped]

Reply to this message...

Goldfarb, Christopher

Fantastic. For some reason I thought it was limited to .dll's and .ocx's.

Thanks,
// Chris

[Original message clipped]

Reply to this message...

MBR BootFX
Best-of-breed application framework for .NET projects, developed by Matthew Baxter-Reynolds and MBR IT

	Copyright © Matthew Baxter-Reynolds 2001-2008. '.NET 247 Software Development Services' is a trading style of MBR IT Solutions Ltd.
	Contact Us - Terms of Use - Privacy Policy - www.dotnet247.com