R
Richard Mahn
The "TCP/IP Netstat Command" component pulls in the "Simple Network
Management Protocol" (by something not visible in TD) component. This
depends on the "SNMP snapin" and somehow MMC (it comes in even if the
snap-in resource is disabled).
Can anyone explain why the snmp protocol should be pulling in a GUI
components ?
Are the GUI pieces really required to allow the protocol to work properly ?
Lmited test indicates that if I disable the snap-in and very manually
inhibit MMC and its dependents from being pulled in, netstat seems to work
fine.
Shouldn't lower level components only pull in even lower components and not
pull in higher (GUI) components that will cause a cascade of GUIness to be
added to the project ? Shouldn't the GUI pull in SNMP protocol and not vice
versa ? Is there even a seperate GUI component for the SNMP snap-in et al ?
Management Protocol" (by something not visible in TD) component. This
depends on the "SNMP snapin" and somehow MMC (it comes in even if the
snap-in resource is disabled).
Can anyone explain why the snmp protocol should be pulling in a GUI
components ?
Are the GUI pieces really required to allow the protocol to work properly ?
Lmited test indicates that if I disable the snap-in and very manually
inhibit MMC and its dependents from being pulled in, netstat seems to work
fine.
Shouldn't lower level components only pull in even lower components and not
pull in higher (GUI) components that will cause a cascade of GUIness to be
added to the project ? Shouldn't the GUI pull in SNMP protocol and not vice
versa ? Is there even a seperate GUI component for the SNMP snap-in et al ?