Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » Component Development   (RSS)
Wednesday, September 17, 2008 9:57 PM

SqlExpressDatabaseInstaller

When unit testing data access components, I prefer to test against run-time components that match the target environment as closely as possible. In other words, if the data access component targets SQL Server 2008, I prefer to test against a SQL Server
Posted by ploeh | 0 Comments
Tuesday, December 11, 2007 11:01 PM

SqlScriptListInstaller

The last of a series of SQL Server-related database Installers is a little helper that simply makes it easier to bundle several SQL scripts together as part of a single Installer package. Instead of mixing several SqlScriptInstallers together with other
Posted by ploeh | 3 Comments
Saturday, December 01, 2007 9:23 AM

SqlScriptInstaller

In my previous post I described a general-purpose Installer that can be used to create a SQL Server database during installation (and delete it again during uninstallation). As promised, this post picks up where the other stopped to describe another Installer
Posted by ploeh | 2 Comments
Thursday, November 29, 2007 12:28 PM

SqlDatabaseInstaller

Installers provide a consistent way of implementing automated setup logic for an application, and as I previously wrote, they also work admirably well for setting up test fixtures . The BCL, however, only contains a limited amount of pre-built Installers,
Posted by ploeh | 4 Comments
Wednesday, May 30, 2007 12:22 PM

Reasons For Isolation

Object-oriented applications above some level of complexity are almost always modelled as a layered architecture. While the typical three-layer architecture remains the most widely known, n-layer architecture is also often utilized. Here's a typical design
Posted by ploeh | 5 Comments
Thursday, April 05, 2007 8:41 PM

Unit Testing Activity CodeDOM Serializers

Windows Workflow Foundation (WF) defines workflows as object graphs. To save or compile workflow definitions, these object graphs must be serialized, and WF supports serialization to both XAML and code. Similar to other components, WF utilizes the .NET
Posted by ploeh | 2 Comments
Sunday, April 01, 2007 4:10 PM

Validating Code Serialized by CodeDomDesignerLoaders

A while back I wrote about unit testing component serializers , but I left the task of validating the generated code against an expected result up to the reader. The approach outlined in that article was to retrieve the generated code as a string and
Posted by ploeh | 1 Comments
Thursday, August 10, 2006 11:22 AM

How To Dispose Members From Forms

When you create a new Form (or UserControl for that matter), Visual Studio creates it as a partial class, with the designer-generated code going into the *.Designer.cs file. One other piece of code that also goes into the designer code is an override
Posted by ploeh | 17 Comments
Monday, March 27, 2006 11:16 PM

A Faster TestTypeResolutionService

In February, I wrote about unit testing CodeDomSerializers , but although it was a good initial attempt, there was room for improvement (as I also described in the article). Back then, my main priority was just to get my unit tests working, so other issues
Posted by ploeh | 3 Comments
Attachment(s): TestTypeResolutionService.cs
Saturday, February 18, 2006 2:02 PM

Serializing Read-Only Collections to Code

In some cases, a Component or Control may have the need to contain a read-only collection of complex objects. Additionally, although you don't want to enable a developer to change the collection itself at design time, you still want to make it possible
Posted by ploeh | 0 Comments
Thursday, February 16, 2006 9:21 PM

Towards Unit Testing Component Serializers

When writing complex components or controls, it is sometimes necessary to implement custom CodeDOM serialization of the control. If the code serialization logic is complex, it would be nice if it was possible to unit test this logic. It's not quite as
Posted by ploeh | 12 Comments
Monday, February 06, 2006 2:02 PM

Unit Testing Control Designers

One of the inherent problems of control development is that it doesn't lend itself easily to unit testing. After all, you are developing a user interface, and it's necessary to validate that it looks as expected. While that's true, more complex control
Posted by ploeh | 0 Comments
 
Page view tracker