Pretty soon after starting to write unit tests you will find yourself in a situation where you want to access a private or protected member of the class being tested. This can either happen if you need to check a private field or property or if you’re planning on testing a private method.

This is part 2 of my series about unit testing. The first part covered the different assertion methods and can be found here. This part will cover additional test attributes.

Ever stumbled across a unit test that was encapsulated into code like this?

With the release of version 2.2 of Profile Migrator not only covers all current migration scenarios, it also is the only application that migrates Microsoft Office and Internet Explorer between versions. One of the most important settings that makes the migration seamless for the user are stored passwords. Everybody knows the hassle of having to retype passwords. Many times the user doesn't remember them, doesn't know where to find them again or didn't even know that he needed one, because it was entered by his system administrator.

A colleague recently asked me how he could calculate the calendar week from a given date using PowerShell. He did not know that I wrote a simple PowerShell function doing exactly that while I was learning PowerShell. I did not know that the function could be useful besides my learning experience. I stand corrected and I've decided to share it for those of you who are looking for this.