So you want to produce a coverage report for your .Net project, preferably from the command line? If you use dotCover and NUnit then this:
<?xml version="1.0" encoding="utf-8"?>
<Executable><!-- Path to your NUnit bin directory e.g. -->C:\Program Files\NUnit 2.5.10\bin\net-2.0\nunit-console.exe</Executable>
<WorkingDir><!-- This path works for running dotCover with a config file in the project directory-->bin\Debug\</WorkingDir>
<Arguments><!-- The dlls containing NUnit tests. Space delimited if more than one-->My.Tests.dll My.MoreTests.dll</Arguments>
<Output><!-- Path to where I want the report. Can be relative or absolute -->My.Tests.Coverage.html</Output>
<FilterEntry><!-- _ "Module" means project _ --><ModuleMask>*</ModuleMask></FilterEntry>
<FilterEntry><!-- _ "Module" means project _ --><ModuleMask>My.Tests</ModuleMask></FilterEntry>
<FilterEntry><!-- namespaces can be filter with a ClassMask with * wildcard --><ClassMask>Namespaces.For.AutogeneratedCode.*</ClassMask></FilterEntry>
will allow you, from the command line, to type:
dotCover analyse MyConfigFileName.xml
and generate coverage reports. Assuming that dotCover is in your path of course.
I like to set the filters to exclude coverge report on the test project itself as well as autogenerated code.
Covering Multiple Test Projects In One Run
- Set your working directory to be a parent of all the test projects, e.g. the solution directory.
- List the full relative paths to each Test dll, space limited:
Filtering and more advanced coverage configs
- Look down the right hand side of the page here : http://www.jetbrains.com/dotcover/documentation/index.html for documentation, such as it is.
- Filtering is covered here: http://blogs.jetbrains.com/dotnet/2010/07/filtering-with-dotcover/
- More complex stuff is touched on here: http://blogs.jetbrains.com/dotnet/tag/code-coverage/
Update: See Vladimir’s comment below for the built in one-liner.
So there you in your code or possible your debugger and immediate window and you have a mock object and realise you want to change the setup but you didn’t keep a reference to the Mock<> …
So your first though is, no problem, you can cast your object to one of type Castle.Proxies.MyStronglyTypedProxyClass and voila you have access to the Mock property. Except that the compiler doesn’t recognise Castle.Proxies.MyStronglyTypedProxyClass as real class.
So then you try reflection to get hold of the Mock property. Which nearly works, but you get a System.Reflection.AmbiguousMatchException : Ambiguous match found. because there’s more than one property called Mock (one with and one without a generic parameter).
But this worked for me:
public static Mock<T> GetMockFromObject<T>(T mockedObject) where T : class
PropertyInfo pis = mockedObject.GetType().GetProperties()
p => p.PropertyType.Name == "Mock`1"
return pis.First().GetGetMethod().Invoke(mockedObject, null) as Mock<T>;
hope that helps.
You have something like this:
Server Error in ‘/Vendorapplication’ Application.
Could not load file or assembly ‘Oracle.DataAccess’ or one of its dependencies. An attempt was made to load a program with an incorrect format.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.BadImageFormatException: Could not load file or assembly ‘Oracle.DataAccess’ or one of its dependencies. An attempt was made to load a program with an incorrect format.
|An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
It’s because you are trying to run 32 bit dlls on a 64 bit system.
Fix it in IIS manager by changing the advanced settings on you application pool to enable 32 bit applications. Or create a new app pool specifically for them.
Alex James Brown has a nice picture: change app pool to 32 bit
You’ve been working with no problems probably in VS2008 on web app written on .net 2 or .net 3.5 or .net 3.5 sp1 and then you try running on a machine with windows 7 or vista running IIS7 and you get this error message…
Simples. It’s comes of running your .Net 2 (you did know that a .Net 3.5 app actually runs on .Net 2 didn’t you?) app under .Net 4. Fix it by changing the app pool for your web app to the pre-defined “Classic .Net App Pool”, which runs .Net framework 3
I don’t always agree with Bob Martin’s Clean Code Tip #12: Eliminate Boolean Arguments – probably because the mathematician in me believes that there are such things as functions of a boolean value – but I came across an example in a WinForms app today where I’d apply it.
void FindApplicant(int id)
turned out to mean:
void ProcessUI(bool processing)
... do a whole load of stuff
which would have been easier to read as:
void FindApplicant(int id)
...do a whole load of stuff