Hi, > I build-tested with all of these patches using the openvpn-build VM in > Vagrant[1]. After the build libopenvpnmsica.dll and tapctl.exe show up > under tmp/installer/<arch>. So the build part is definitely working > correctly. > > How would I test that both of the above are operating as intended?
For the libopenvpnmsica.dll, testing could have been introduced using some unit test suite. Unfortunately, it so tightly integrates with Microsoft Installer, I see no feasible way of mocking it. The way I test is to use debug version inside MSI package. The debug version raises MessageBox() on each custom action function invocation. This allows me to use elevated Visual Studio, locate the msiexec.exe process, attach on it using remote debugging, set breakpoints, then click "Ok" in the MessageBox() pop-up to let it run up to the first breakpoint. If somebody knows of a better way to test and debug MSI custom actions I would be most happy to learn it. As for the tapctl.exe: this utility is already usable with existing TAP-Windows 9.21.2. Just open an elevated command line and play with it on a Windows computer that has TAP drivers installed. Best regards, Simon
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
