Thoughts from the Wet Coast

The musings of an ASP.NET Developer from Canada's We(s)t Coast




Into the Matrix with Neo4j: 4 - The Neo4j Browser

Oct 29 2014

In my investigation of the Neo4j database I will now turn my attention to the Neo4j browser.  

Once Neo4j is installed there will be a small executable that can be used to start the Neo4j database server.


Into the Matrix with Neo4j: 3 - Why Graphs

Oct 28 2014

In this blog post I am going to return to my investigation of the graph database Neo4j.  So far I have done a brief introduction to Neo 4j and I have shown how easy it is to install Neo 4j in an Azure VM.

DNN Development Tips:10 - Using Action Filters in your Services Framework methods

Oct 23 2014

In an earlier blog I described the use of the DnnExceptionFilterAttribute which can be used to simplify the exception handling in Services Framework action methods.  In this blog I turn my attention to another, more generic attribute that you can apply to your action methods.

DNN Development Tips:9 - Using Moq, the “It” class

Oct 22 2014

In a previous article in this series of blog posts, I introduced Moq (Mock-you) – the mocking framework we are using in DNN to generate Mock objects for testing.

DNN Development Tips:7 - Using Moq

Oct 20 2014

In a previous article in this series of blog posts, I described the different Test Doubles that can be used when unit testing your application.

DNN Development Tips:6 - Dummies, Fakes, Stubs and Mocks

Oct 18 2014

One of the tenets of Unit Testing is that in order to test a piece of code we often need to create some alternate implementation of one or more of the Interfaces involved in a test.  This concept is generally called a Test Double.  However there are many types of Test Double, and there is some degree of confusion about the types of doubles used.

DNN Development Tips:5 - What Tests should I Write

Oct 17 2014

One of the biggest challenges in writing Unit Tests - at least when you write them after you have created the actual code, rather than in a Test Driven Development style, is determining what should be tested.