Virtual Developer Workshop: Containerized Development with Docker
- Windows NT 4.0 [Workstation, Build 1381: Service Pack 4]
- Windows Sockets 1.1 Network Support [wsock32.dll, ws2_32.dll]
- Microsoft Visual C++ 6.0, ATL 3.0 [ole32.dll, oleaut32.dll], MFC 4.2 [mfc42.dll]
Install and ConfigureUnzip ping.zip retaining directory structure to any location with approx 40Mb of free space. You'll get a folder ./pingcomp
Ping componentOpen workspace ./pingcomp/pingcomp.dsw, select say 'Release MinSize' configuration (faster build), run build. If building a debug configuration, browse info will be available.
Ensure that component is registered properly, as indicated by output window: "Performing registration RegSvr32: DllRegisterServer in .\ReleaseMinSize\Pingcomp.dll succeeded."
If not try it manually: 'regsvr32 .\ReleaseMinSize\Pingcomp.dll'
Ping clientOpen workspace ./pingcomp/pingclient/pingclient.dsw, select 'Release' configuration (faster build), run build. If building a debug configuration, browse info will be available.
RunAfter a component and client are built, you're ready to run the program, but **you should login as administrator** to get valuable results, because of programs use of raw sockets, which can be opened only with admin privileges - that's an operation system limitation.
Program's DesignPing component (Pingcomp.dll) encapsulates ping implementation and exhibits corresponding COM interface - IPing.
CPingImpl class provides low level ping functionality, i.e. creates socket, form packets, sends, receives and decodes responses.
CProxyIPingEvents class implements IPingEvents interface, it's generated by classwizard.
Ping client (Pingclient.exe) provides user interface and interaction with the component.
CPingDlg class - initializes COM library, creates an instance of Ping component, advises connection for sinking events.
CPingEvents class - a bridge for transmitting events fired by component to dialog.