R
Rashad Rivera
Hi gang,
I have somewhat of a complicated question. I will try my best to
explain. I have .NET assemblies that run in IIS's memory space. But I want
to be able to interface with those running instances from a user's logon
session on the host server. Basically I want to write a UI that allow a
server administrator to see what is happening at runtime and be able to
control the assemblies. I know of three basic ways to get this done:
1) write a web UI and allow him to interface via an administrative web page
that accesses the app via the "Application" variables in .ASPX forms
2) bridge the gap via a database like a local .MDB
3) bridge the gap via TCP connections to the local loopback address
127.0.0.1 with TcpClient and TcpListener.
But I want to do it through and API or memory space. No offence but these
way seem to be workarounds for this type of controlling/interfacing. Does
..NET facilitate this functionality or am I going to have to settle for the
three mentioned options? Is there a way to share the memory space in a .NET
dll so I can change settings at run time? I mean in how do MSExcnahge and
IIS admin tools do it anyway? Lots of good questions here, I sincerely hope
someone can answer them.
- Rashad Rivera
Department of State/NCC
I have somewhat of a complicated question. I will try my best to
explain. I have .NET assemblies that run in IIS's memory space. But I want
to be able to interface with those running instances from a user's logon
session on the host server. Basically I want to write a UI that allow a
server administrator to see what is happening at runtime and be able to
control the assemblies. I know of three basic ways to get this done:
1) write a web UI and allow him to interface via an administrative web page
that accesses the app via the "Application" variables in .ASPX forms
2) bridge the gap via a database like a local .MDB
3) bridge the gap via TCP connections to the local loopback address
127.0.0.1 with TcpClient and TcpListener.
But I want to do it through and API or memory space. No offence but these
way seem to be workarounds for this type of controlling/interfacing. Does
..NET facilitate this functionality or am I going to have to settle for the
three mentioned options? Is there a way to share the memory space in a .NET
dll so I can change settings at run time? I mean in how do MSExcnahge and
IIS admin tools do it anyway? Lots of good questions here, I sincerely hope
someone can answer them.
- Rashad Rivera
Department of State/NCC