Way off the beaten path...

A number of months ago my wife and I finally decided to build a new house.  If you have ever gone through the process of building or buying a new home, you know there is an unlimited amount of factors which ultimately affect the purchase and more so your monthly payment.  When we started this process I hit the ole Internet in search of a mortgage calculator.  I landed on the Office template section where I found a basic mortgage calculator workbook.  That workbook has since been revamped to closer depict a holistic purchase process.

The numbers represented in this spreadsheet are just for demonstrative purposes. MortgageCalc-2003.zip (36.04 KB)

I hope you find it as useful as I have. Enjoy!

Yesterday ( Friday ) the official TFS Release Candidate was cut.  Today I received my copy and tomorrow I upgrade.  I'm stoked!

The bits are on their way to the MSDN download center and you should see them sometime on the 7th.

Check out this post from Jeff Beehler for all the details.

I received my Toshiba Tecra M4 around 7 months ago.  Like any, there are pro's and con's; overall not a bad machine.  One thing that just drives me crazy it's the random mouse lag.

Does anyone know a fix for this?  If so, please comment!

Based on some conversations I had today, here is a simple NMock example.

NMockExample.zip (17.19 KB)

Code Snippets just rock.  I thought I would post my testing code snippets.

CSTestSnippets.zip (2.2 KB)

VBTestSnippets.zip (2.13 KB)

Just add them to the appropriate place under "My Documents\Visual Studio 2005\Code Snippets\"

Short answer.

It's as simple as adding one line to your csproj which in turn tells the IDE to treat that project like a test project.  Add the following line to your main PropertyGroup:

<ProjectGuid>{04082EBA-C85C-4336-B3FD-9891096BAA0F}</ProjectGuid>

Then just reference Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll and you are on your way.  Be sure to verify that Guid between releases. 

Long Answer.

When I start a project I create the base set of known assemblies that project will need.  I also add an additional test project which will contain any Scenario, Load and Stored Procedure tests.  Then I convert all assemblies to test projects.  I am a firm believer in Test Driven Development.  IMHO it is the only way to properly write code.  Having said that over the years I have developed my own set of TDD practices; one of which is the physical placement of your unit test classes in the assembly their testing.  Why? Well I will explain that in a future post call Unit Testing with Partial Classes.

With any decision there are of course trade-offs. In this case the trade-off is around the IDE interaction with hosting type projects, ie exe or web.  After you convert an exe to a test project, when you decide to run ( F5 ) it will actually fire off Test Manager rather than the launch app.  If you are a TDD bigot like me this is actually the correct action; if your not, I know your already complaining.  BUT all is not lost!  There is a little tool us TDD bigots keep in our back pocket at all times, TestDriven.Net.  This is an Visual Studio add-in and it allows you to execute your unit tests with just a right click.  If you choose to use this tool it isn't necessary to convert your project to a test project but rather just reference the Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll.  This will allow you to fire your app as intended and run your tests with the same project configuration.

Disclaimer: this is not a Microsoft recommend practice.  You can find more information about the Visual Studio Team System Testing Framework here.

Rob Caron has relaunched the VSTS User Education Team Blog.  If you are working with TFS then you need this on your blogroll.  Be sure to check out the following three posts: