I am using MSTest and the corresponding code coverage tool since it's built into Visual Studio, and I'm not aware of any other code coverage solutions that allow for excluding of namespaces. However, all throughout log4net I've noticed other build directives for NETCF that configure different class signatures and attributes so I am concluding that this is the best course of action for this issue. If anyone has tested a better solution, I'd love to give it a shot.
From: Ron Grabowski [mailto:[email protected]] Sent: Thursday, June 23, 2011 12:17 AM To: Log4NET Dev Subject: Re: ExcludeFromCodeCoverage attribute Can you configure your code coverage tool to exclude certain namespaces? ________________________________ From: "Chadwick, Keenan" <[email protected]> To: "[email protected]" <[email protected]> Sent: Monday, June 20, 2011 11:20 AM Subject: ExcludeFromCodeCoverage attribute We are currently under stringent code coverage requirements here at Paychex, and one of the libraries I have created includes the log4net source so as to not require another .dll file. The library basically just contains the log4net code and a Log class with static methods for Info, InfoFormat and so on, while maintaining a Dictionary<string, ILog> of logger singletons which get created by reflecting up 3 stack frames to see who is invoking the log methods. I was wondering if it would be too much trouble to include the following (or some variation) on all non-nested classes in log4net for the next release. #if DEBUG [ExcludeFromCodeCoverage] #endif Thanks, Keenan Chadwick Enterprise Services Paychex, Inc. 585-216-2518 [email protected]<mailto:[email protected]> The information contained in this message may be privileged, confidential, and protected from disclosure. If the reader of this message is not the intended recipient, or any employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer.
