public class Class1
public interface IExecutable
public void ThisIsATest()
// This is not a good test of a mock but it shows how it works.
// The mock should be a Dependend Upon Component not the Subject Of Test
DynamicMock mockExecute = new DynamicMock(typeof(IExecutable));
Here is a useful wpf tutorial.
Here is an article on creating custom windows shapes in wpf.
Here is an example of how to create a markup extension to ease the addition of tooltips to a wpf application.
However this can be done just as easily via a resource entry!
I have recently moved to a new project.
This means that there is a large code-base that I need to learn quickly.
One of my starting points was to try and point a NDoc type tool at the application.
It was at this point that I found that the application was missing at least 5000 XML comments – the NDoc tools typically use the .
When I started to add them to the units that I was working on I was pointed to an article that describes javadoc style comments as now being considered evil for an internal project.
Agile projects these days use self describing names so “empty” xDoc comments don’t help.
I have suddenly realized that I can use reflection to create the “empty” xml stub file from an assembly. This would allow me to get the documentation (that will be at least partially useful) without polluting the code with javadoc comments.
One of the things that I like xDoc tools to generate is a class hierarchy diagram. This is great for finding the descendent’s of a class that you are modifying (this documentation is especially useful if you have code that currently does not compile).
Here is a sample of a grep equivalent in powershell
dir *.rdl | select-string “.Report_”
There is a slight problem when the database that you have set as the default for an account is dropped.
This means that logging in will fail.
Here is the fix.
The CSS world has Css Zen Garden as a showcase for what can be done with stylesheets.
I could not find an equivalent for wpf so I have set one up: