FuturShoc
Active member
I have a theory on this, but since I'm still very much a newbie at VB, much less .NET, I figured I should ask you fine folks here before flat-out denying the development request I have for it.
We apparently need to somehow intercept an XP user's attempt to establish a second network connection. (ie. Ethernet and, say, wireless). The request asks that this theoretical application/service warn the user with a dialog of some kind, forcing them to either disconnect from one network method before connecting, say, wirelessly, or cancel the new attempt and stay on the existing connection - and vise versa.
Point being, we don't want a user to be able to have two connections going at once because this makes remote troubleshooting a bit trickier for us, the support group.
My theory here is that in order to actively intercept a user's attempt like this, the application we would deploy would need to be a service of some kind. By extension, that service would also have to do so much polling of the user's actions while it waits for that second connection attempt that the service would suck up WAY too much of the OS's resources - making the existence of said service a complete dog on the PC.
Am I out of line with this assumption? Is there some magic I don't know about which would allow a developer (.NET Dude, aka me) to "attach" some kind of action to a user's attempts to intitiate network connections?
We apparently need to somehow intercept an XP user's attempt to establish a second network connection. (ie. Ethernet and, say, wireless). The request asks that this theoretical application/service warn the user with a dialog of some kind, forcing them to either disconnect from one network method before connecting, say, wirelessly, or cancel the new attempt and stay on the existing connection - and vise versa.
Point being, we don't want a user to be able to have two connections going at once because this makes remote troubleshooting a bit trickier for us, the support group.
My theory here is that in order to actively intercept a user's attempt like this, the application we would deploy would need to be a service of some kind. By extension, that service would also have to do so much polling of the user's actions while it waits for that second connection attempt that the service would suck up WAY too much of the OS's resources - making the existence of said service a complete dog on the PC.
Am I out of line with this assumption? Is there some magic I don't know about which would allow a developer (.NET Dude, aka me) to "attach" some kind of action to a user's attempts to intitiate network connections?