Wednesday, July 20, 2005

Be sure to visit all the options under "Configuration" in the Admin Menu Bar above. There are 16 themes to choose from, and you can also create your own.

 

posted on Wednesday, July 20, 2005 1:00:00 AM (Central Standard Time, UTC-06:00)  #    Comments [0] Trackback
 Tuesday, July 05, 2005

A quick breakdown of the Team Test attributes compared to NUnit attributes with a few examples.

All Team Test attributes are found in the following namespace:
Microsoft.VisualStudio.QualityTools.UnitTesting.Framework

Attribute Quick List

Team Test NUnit
TestClass TestFixture
AssemblyInitialize N/A
AssemblyCleanup N/A
ClassInitialize TestFixtureSetUp
ClassCleanup TestFixtureTearDown
TestInitialize SetUp
TestCleanup TearDown
TestMethod Test

AssemblyInitalize and AssemblyCleanup are new. There are no equivalent attributes in NUnit. These attributes run at AppDomain load and dispose.

[ AssemblyInitialize ]
public static void AssemblyInitialize()
{ }


[ AssemblyCleanup ]
public static void AssemblyCleanup()
{ }

Acting just like the NUnit TestFixtureSetUp and TestFixtureTearDown with the only one minor difference. Both methods have to be static and the ClassInitialize takes in one parameter. ClassInitialize will execute before any TestInitialize and TestMethod after the AssemblyInitialize while ClassCleanup executes after the TestMethod and TestCleanup but before the AssemblyCleanup.

[ ClassInitialize ]
public static void ClassInitialize(TestContext t)
{ }


[ ClassCleanup ]
public static void ClassCleanup()
{ }

TestInitialize executes before each test and TestCleanup executes after each test for every TestMethod.

[ TestInitialize ]
public void TestInitalize()
{ }


[ TestCleanup ]
public void TestCleanup()
{ }


 

posted on Tuesday, July 05, 2005 9:05:35 AM (Central Standard Time, UTC-06:00)  #    Comments [0] Trackback
 Wednesday, June 29, 2005
First I would like to thank everyone involved with the Springfield IL .Net Developer day for asking me to speak.

Springfield.NetDay.ppt (1.61 MB)
posted on Wednesday, June 29, 2005 9:04:13 AM (Central Standard Time, UTC-06:00)  #    Comments [0] Trackback

Since Google’s purchase of Keyhole, they’ve recently released a program called Google Earth. Its free and will no doubt suck up some of your time.

So far my favorite place is the Grand Canyon National Park.

posted on Wednesday, June 29, 2005 9:01:53 AM (Central Standard Time, UTC-06:00)  #    Comments [0] Trackback
 Tuesday, June 28, 2005

I have been without TestDriven.Net for a while and it’ s been killing me. I can’t explain why the following change works but it works.

  • Copied the version of Microsoft.VisualStudio.QualityTools.Tips.UnitTest.ObjectModel.dll that was installed with the version of the IDE into the root of “C:\Program Files\TestDriven.NET 1.0” and “C:\Program Files\TestDriven.NET 1.0\QualityTools”
  • Updated the TestDriven.Config AssemblyPath to remove “QualityTools\”.

    Original:

    testrunner Name=”QualityTools” AssemblyPath=“QualityTools\TestDriven.QualityTools.dll” TypeName=”TestDriven.QualityTools.QualityToolsTestRunner”
    targetframework AssemblyName=”Microsoft.VisualStudio.QualityTools.UnitTestFramework”
    testrunner

    Modified:

    testrunner Name=”QualityTools” AssemblyPath=“TestDriven.QualityTools.dll” TypeName=”TestDriven.QualityTools.QualityToolsTestRunner”
    targetframework AssemblyName=”Microsoft.VisualStudio.QualityTools.UnitTestFramework”
    testrunner

  • posted on Tuesday, June 28, 2005 8:51:52 AM (Central Standard Time, UTC-06:00)  #    Comments [0] Trackback
     Friday, June 24, 2005

    It’s always nice to share your tools of the trade with fellow colleagues. I was going to compile my own list when I was passed Scott Hanselman’s. I think I shall pass, he did a great job of covering things.

    Thanks to Mike Becker for sharing it with me.

    posted on Friday, June 24, 2005 8:50:32 AM (Central Standard Time, UTC-06:00)  #    Comments [0] Trackback
    posted on Friday, June 24, 2005 8:49:57 AM (Central Standard Time, UTC-06:00)  #    Comments [0] Trackback
     Thursday, June 09, 2005

    Let me start by saying I just love Subversion ( SVN ). When it comes to source control there are many different products to choose from, VSS, CVS, Sourcegear Vault, Perforce, Microsoft VSTS just to name a few. They all have their pros and cons and until last night I swore by SVN. Like I said before, I love SVN. These guys really deserve a great deal of credit. SVN is free and it functionality meets the needs of a great SCC repo. When I looked to pick my personal SCC repo, I looked for the obvious things like commit, update, delete, etc and on top of that I look for things like :

  • Easy of maintenance
  • Fast
  • Simple interface ( example : TortoiseSVN or TortoiseCVS )
  • Reliable
  • Secure
  • Access from anywhere
  • Built on a DB rather than a filesystem

    I setup a small repo with SVN and was in awe. I don’t think I spent more that 30 minutes starting from scratch to committing files. I used it for a few months and decided I better move the DB to a RAID I had sitting on another sever. This would give me the reliability of a raid yet run SVN on a separate machine.

    WRONG!! I was able to mount a directory to a share on another server with the RAID. svnadmin created the DB just fine, but things puked when I tried to use it.

    It logged the following:

    (20014)Error string not specified yet: Berkeley DB error while opening environment for filesystem /PATH/To/Repos/ db:\nInvalid argument

    [error] [client XXX.XXX.XXX.XXX] Could not fetch resource information. [500, #0]

    [error] [client XXX.XXX.XXX.XXX] Could not open the requested SVN filesystem [500, #160029]

    [error] [client XXX.XXX.XXX.XXX] Could not open the requested SVN filesystem [500, #160029]

    I hit the SVN book to see what I had done wrong only to find this.

    Warning

    Do not create your repository on a network share—it cannot exist on a remote filesystem such
    as NFS, AFS, or Windows SMB. Berkeley DB requires that the underlying filesystem implement
    strict POSIX locking semantics, and more importantly, the ability to map files directly
    into process memory. Almost no network filesystems provide these features. If you attempt to
    use Berkeley DB on a network share, the results are unpredictable—you may see mysterious
    errors right away, or it may be months before you discover that your repository database is subtly
    corrupted.

    As stated on page 83 of Version Control with Subversion

    and so the boat sailed off into the distance with all the n-tier SCC users as SVN stood there watching.

    BUT there is good news…..

    The SVN team stated as a long term product goal they were going to add a SQL repository back-end. You can stay informed about it here.

  • posted on Thursday, June 09, 2005 8:49:06 AM (Central Standard Time, UTC-06:00)  #    Comments [0] Trackback