Mock Unit Testing with Dependency Injection

Get the complete article here

In software development, unit testing is performed to validate a small module or portion of functionality at a fundamental level. Test cases are written at the function or procedure level to validate inputs and outputs. Several test cases can be written to validate a given piece of functionality and then, when new functionality is added or changed, the existing test cases can be used to validate that existing functionality has not been affected.
 
In theory, unit testing sounds like an effective tool that can be used to improve application quality. The improved quality comes at a price however, because developers must take into account the additional effort required to develop useful and relevant test cases while still meeting deadlines.  To complicate matters, many application components rely upon other components and domain state to function properly, increasing the test effort.  An application component may require a database, a web service, or even the current outside temperature in order to work properly.

Get the complete article here

Use the .Net CodeDOM to compile C# On the Fly

Get the complete article here

Wouldn't it be nice if you could extend an existing application's functionality without re-compiling the entire application? There is a solution! The .Net CodeDOM provides a way to do just that. The CodeDOM provides a way to create a source code object graph by defining source code elements. Once these source code elements are defined, the CodeDOM can be used to compile the objects.

Get the complete article here

Enhancing the ASP.Net Validation Summary Control

The standard Validation Summary control in ASP.Net provides some useful functionality that enhances ASP.Net validation. However, there are instances when the standard functionality is not quite enough. For example, a client-side validator won’t suffice when input data must be validated against data in a database. Scott Juranek has provided a good way to add validation messages to a ValidationSummary control when server-side validation takes place. His project can be found on CodeProject. His project explains an instance where client-side validation is not practical when validating data from a database.

Scott’s example covers another scenario that I recently encountered. Say you have a DataGrid that has multiple editable columns and rows and each cell has its own validator. The validators each have the same values for the ErrorMessage and Text properties. When there are multiple failures in the DataGrid, the ValidationSummary control will display a message for each failed validator which could result in multiple messages listed, each with the same message. The result is a long list of repeated error messages in the ValidationSummary control.

Without violating the NDA, I thought I would provide some information about how I prepared for the Microsoft exam 70-300 Analyzing Requirements and Defining Microsoft .NET Solution Architectures.

First, I read the Microsoft Press book (twice!). As it turned out, that was overkill. The information in the book is useful and I don't regret reading it, however, there is no substitute for “real-life” experience. The book describes the Microsoft Solutions Framework development process in detail. It covers the entire process from defining the vision and scope of a project to developing, testing, and implementing a solution.

The second, and probably more valuable tool I utilized, was the Transcender practice exams. They not only covered all of the relevant material, but also mirrored the format of the exam, which is a bit different from the Microsoft exams I have taken. In addition, the Transcender exams highlighted areas that were not covered in detail in the book, which forced me to look to other sources for information. I would recommend extra study time on ORM and ER for data modeling. When I took the first Transcender exam, I failed it miserably. Because of this, I was a bit intimidated and reluctant to take the exam. All for nothing! I passed and it turned out to be a bit easier than I expected.

VAPr skin for .Text 0.95

This is my first .Text skin! It was interesting to try this. Configuring the .Text framework to add the skin was the easy part. I definately need some practice editing images. The skin is fairly heavy and can cause delays when viewing over slower connections. I will continue to optimize the images and content to improve the performance. Overall, I'm content with this, my first attempt at skinning my blog.

See Mark Wagner's blog for additional information on creating skins. This is a very good article that explains the basics of creating or editing skins for .Text.

Download the VAPr skin for .Text.  This has been written for .Text version 0.95.  Please report any problems or suggestions.  Your feedback is appreciated.

 Download  Get the skin here!

Notes:

• I found it much easier to use the style.css to apply styles than to try and add “custom“ attributes to individual HTML elements.
• The images definately need work! They are heavy and slow. I think I may have to change my “look“ in order to reduce the load time.

  Design Patterns in C#

   By Steven John Metsker

  Design patterns in programming seem to be gaining popularity. Every experienced programmer has used design patterns in one way or another without even knowing it. Finally, design patterns are being formally defined.

This book is a great primer to learning design patterns using C#. It is clear and concise. All of the samples are available for download and work well. I am becoming a big fan of design patterns in general and I really like this book!

Look for this book on