Hello again Chris,
I am working with this new drop again to build it against .NET4 and I have to go through a whole slew of test failures to make everything work as expected. The good news is that there ARE solutions to most problems.
I DO understand that you are not YET targeting the new Framework. But I wonder if it isn't the right time to be thinking ahead about how EL can be released with a full battery of passing tests and usable QuickStarts straight out of the box.
I made a few comments about this on another thread and I'll include those here because I think you are probably the guy to whom they should be addressed:
I am having similar issues with Instrumentation in the 5.0 drops as I attempt to migrate EL5 to .NET4 (see
It seems like it would be useful to add to the Enterprise Library suite a GUI utility specifically designed to handle EL WMI configuration. It is really a tedious process to ensure that all counters, configuration settings,
and events, are properly set up for the tests and the QuickStarts. I think it has to be one of the primary issues when developers decide to give up on EL because of the relative complexity involved. I think a lot of people must throw up their
hands before they even make it through the "Quick"-Starts, much less the full suite of tests.
I have not had any success with the script provided. Instead I have had to individually work directly with InstallUtil.exe and then check WMI repeatedly to resolve problems. I don't know if this has anything to do with using the
newer operating systems (server 2008 r2, vista, win7) or what.
Am I missing something or does anyone know of an existing utility that makes this process easier and faster to manage?
It also seems like a good idea to dedicate a specific document with more detailed guidance for instrumentation and configuration required to
run all tests successfully. I've encountered significant numbers of tests that fail invariably because of the assumptions made by the tests themselves and NOT because there's anything wrong with the
library itself. Obviously the P&P team has all of this configured properly on an ongoing basis. But those of us who migrate across development environments are subject to a severe penalty when it comes to such issues.