"Volker Birk" <bumens@dingens.org> wrote in message
news:43394aaa@news.uni-ulm.de...
> Duane Arnold <notme@notme.com> wrote:
>> Yes a dll is not running by itself but the COM legacy applications (VB 6
>> exe's using COM) along with user applications that will be developed for
>> using .NET by LAN and remote user machines over the Internet will be
>> consumers of this dll and the .NET service that will running on the host
>> machine will consume that dll too.
>
> Hm... this sounds a little bit confusing. What do you mean with "remote
> user
> machines over the Internet will be consumers of this dll"?
Well, as I understand it a little more, all machines will have this dll
locally on the them and legacy servers and user workstations will use the
dll locally. The dll will not be on a COM + server to control database
access to SQL Server so it's really not a multi user application. I'll
assume these remote machines will have some kind of VPN connection.
>
>> But my main concern at this time is that this dll is not controlled by a
>> COM+ or Web server that can handle multiple instances of the dll running
>> on the host machine. The dll and the service will not be running on that
>> kind of a server.
>
The question is moot now that I see a little more as to how this dll will be
implemented in the company.
Thanks
Duane :)
Received on Thu Sep 29 20:11:06 2005