Productivity

Unit testing LINQ to SQL repositories can be very challenging. Unit testing such requires faking hard to mock classes and requires simulation to return your custom data for a particular LINQ statement. In this post, i will show how you can mock your LINQ repositories easily without much digging in. As,  i was goggling [my start page is bing, its a matter of time when i will be bing-ing :-)] around, found a nice post by Ronnie Holm, where he shows how to unit test a  LINQ to SQL repository. I will follow his trail and use some of the codes...

Recently, Telerik released a new and improved version of the Telerik CAB Enabling Kit (TCEK). This latest version now provides support for using the RadDock control as a workspace in your Composite UI Application Block (CAB) applications. Previously, only the old DockingManager control had been supported. In this blog entry, I will show you how to begin using the RadDock as a workspace in your applications through the use of the newly updated RadDockableWorkspace. In case you are new to CAB/SCSF or the TCEK - I highly recommend reading through my older series of blogs. You can access the introduction ...

Disclaimer: this post is all about fun. It is not about: turning a bug into a feature; some new isolation/mocking practice; wow, look what I will do with pointers in my next project; It is all about fun :)

[Want to see JustMock in action? Register for the free webinar this Thursday, Jul 22, 11 am EST and check out What’s New in JustCode, JustMock, and OpenAccess ORM. During the live event attendees will also have the chance to win a Telerik Ultimate Collection (valued at $1999).]   In JustMock. The tale continues... (Part 1) we saw how we can inject prologue/epilogue code in .NET methods with JustMock. We covered the most simplest scenarios and some more complex ones as methods with ref/out parameters. Today I will show you how to do code injections in generic methods. Basically there is nothing new. We are already familiar with: AtStartOfAction AtStartOfFunc AtEndOfAction AtEndOfFunc etc. and last time...

One of the features that has inspired the TeamPulse team over the years is Static Code Analysis. In Visual Studio 2010 (Premium and higher) you have the ability to have Visual Studio perform a check on your code to see how well your code conforms to different coding best practices. You can have Visual Studio check for how to best declare error handlers, or even making sure that you dispose of your objects before they go out of scope - it’s like having a fully automated code review without the need for anyone to actually review your code. What’s ...