• .NET

    JustCode Code Style Settings for C# - Part 2

    December 11, 2012 Share
    In our previous blog posts on the JustCode Formatter ("Introducing the Formatter" and "Comparing the JustCode Formatter to the Visual Studio Formatter") we showed you what it is and how it works. Our latest post on the formatter detailed the first half of the settings for C#. In this post, we will show the rest of the code style settings for C#.
  • .NET

    Slides, Source Code and Video to the “Getting Started with JustMock” Webinar Now Available

    December 06, 2012 Share
    Chris and I wanted to thank you all for attending the “Getting Started with JustMock” webinar. The slides, source code and recorded video are now available for you to explore. If you have any questions, then feel free to leave a comment below or send us an email/tweet. I encourage you to go ahead and download your own copy of JustMock and start experiencing Fast, Fluid Unit Testing for yourself. WEBINAR MATERIALS Slides, Source Code and the Recorded Webinar Video is now available for you to enjoy.
  • .NET

    When Should You Profile Your Application?

    December 06, 2012 Share
    At Raleigh Code Camp, I had an unfortunately familiar conversation with another developer. Me: How often do you profile your application for performance or memory issues? Him: I don’t. Me: Really? How do you know if your app has any issues? Him: Because I write good code.
  • .NET

    The Changing Visuals of the Visual Aid

    December 05, 2012 Share
    Visual Studio received a facelift in 2012, and our tools changed to match its look and feel. It wasn't without some controversy, but there’s nearly universal agreement that the new theming support is cool. If you haven’t experienced it yet, install the Visual Studio 2012 Color Theme Editor. It’s from Microsoft, and it’s free. We modified JustCode well before the official release of Visual Studio 2012 to support the new theming capabilities. Since you use Visual Studio for your development environment, we want to ensure our tools integrate for a seamless experience.
  • .NET

    Future Mocking

    November 21, 2012 Share
    Mocking legacy code is hard. Especially, if it’s a third-party library and you have little control over how it’s written. It is even more difficult to unit test a type that is instantiated internally. One can argue that it should be refactored to accept dependencies via constructor injection.  However, constraints such as time, budget, experience with the offending code, or even access to the source often prevent paying down the technical debt accumulated in these legacy systems.   This post will show you how to mock an external library (concept) where it calls a login service class that cannot be sent...