I'm currently trying to adapt our performance counter text string registration from being done in our own code (picked up from Jeff Richter's book "Programming Server-Side Applications for Windows") to use the LoadPerfCounterTextStrings API and, ultimately, the PerfCounter element in WiX. Something seemed to be corrupting the text strings on some systems, not definitively linked to our code but I thought it would be better to use the supported method.
I've just spent a day coding up LoadLibrary/GetProcAddress and falling back on CreateProcess to run lodctr.exe if LoadLibrary or GetProcAddress fail, then tested on NT 4.0 only to discover that the library, loadperf.dll, is actually present and implements the API! It does appear to work, but as it's not documented as being supported I thought I'd ask if anyone had seen any problems. Some of our customers are still running older versions of the product on NT 4.0 and would expect it to continue to work. Does anyone have any experience with the PerfCounter element, or the API that it uses, on NT 4.0? (I think this API may have been one of the internal ones disclosed for Windows 2000 in reaction to the anti-trust case, given that it basically requires the lodctr.exe command line to be passed.) ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
