nlarson11 wrote:
The pool, connections, and transactions to the mainframe are all created/handled in the windows service
The Pool, Connection and Transaction are managed .NET classes? If yes, which clients will be using those classes? The static classes in there will be unique per AppDomain. You can't a static class to share resources among different applications - there's not a static class that's "global" across applications. A Windows-Service would only be usefull if there's an app that needs to run without user-supervision. It'd be comparable to writing a server-application, and yes, you could communicate with that. Is there an unmanaged resource that the Pool is protecting? What kind of connection is the user expecting? It "feels" like you're trying to limit database-connections - am I right?
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]