Mike Swanson

July, 2004

  • Mike Swanson's Blog

    DVD ISO for Visual Studio .NET 2005 Beta 1 Now Available on MSDN


    The DVD ISO file (3.50 GB) for Visual Studio .NET 2005 Enterprise Architect Beta 1 is now available for download at MSDN Subscriber Downloads. Similar to the CD ISO releases last week, the download is available for the following subscriber levels: MSDN Universal, MSDN Enterprise, MSDN Professional, MSDN Academic Alliance, and Microsoft Certified Partner. If you’ve been waiting to get the Beta 1 release in a single file, this is the download you want.

  • Mike Swanson's Blog

    MSDN TV: Build a VS.NET-Hosted Tool Window for Reading Blogs


    In this episode of MSDN TV, Craig Skibo uses the Visual Studio .NET 2003 automation model to build a tool window hosted within Visual Studio that allows you to read blog postings. Even if you’re not interested in reading blogs within VS.NET, this is a good foundation for building any kind of managed tool window. Runs for about 10 minutes.

    While I'm at it, I'll plug Craig's book called Inside Microsoft Visual Studio .NET 2003. It covers the Visual Studio .NET 2003 add-in architecture, the automation model, wizards, macros, and much more. If you'd like to extend the capabilities of the IDE or automate a lot of your repetitive tasks, this is the best book I've seen.

  • Mike Swanson's Blog

    Visual Studio .NET 2005 Beta 1 Available for Download


    Visual Studio .NET 2005 Beta 1 and related tools have been posted for download at MSDN Subscriber Downloads. The downloads are available for the following subscriber levels: MSDN Universal, MSDN Enterprise, MSDN Professional, MSDN Academic Alliance, Microsoft Certified Partner.

  • Mike Swanson's Blog

    Summary of James Newkirk on Unit Testing


    James Newkirk (of NUnit fame) gave a presentation at Tech·Ed Europe about the integration of unit testing into the software development lifecycle. Benjamin Mitchell took some good notes and posted them to his blog for those of us who couldn’t attend (thanks, Benjamin). Here are some of the highlights:

    “He favors testing the public interface because it decouples the test from the implementation which will discourage refactoring.”
    Not only do I agree with him, but I would add that your private behavior is likely exposed through a public interface anyway, and that’s where you should test.

    “James said that he believes that testing has to be seen as a primary part of development. We have to incorporate test inside development.”
    Amen! Using a tool like NUnit is most effective if it is used during development. Although I consider test-first the ideal, this is a radical idea for many people new to test-driven development, so writing any test is better than nothing.

    “James mentioned that studies have show that Test First is 16% longer, but the quality was much higher.”

    “James believed that if you are interacting with something complex, building the simulation of something that is complex is a worthless activity - you spend more time writing the simulator than the test and it doesn't tell you anything.”
    Remember, we aren’t writing tests for testing’s sake. We’re writing tests to help us with design, development, refactoring, and confidence.

    “James thinks looking at the implementation to drive the tests is looking at it the wrong way.”

Page 3 of 3 (14 items) 123