MSDN Magazine - January 2008 - (Page 12)

of the external dependency. Moreover, you also get the ability to test the interaction between your code and the external dependencies. Instead of just testing that your business layer can successfully return an object, you can test that it will cess layer to retrieve that object. There are a number of different mocking frameworks available for .NET, and ing what a mock should expect and return a little bit differently. Rhino.Mocks, an open-source framework developed by Oren Eini (also known as Ayende Rahien), stands out because of its ability to provide strongly typed mocked objects. Most of the available mocking frameworks require the use of hardand parameters, which means you won’t know about potential issues until you actually try to run your tests at run time. By allowing for strongly typed mock objects, of compilation—helping you catch errors earlier. types of mocking allowed. A normal mock object will throw an exception if an unexpected method is called. But Rhino.Mocks offers a dynamic mock object that, instead of throwing an exception, will return null or 0 for any unexcepted method calls. Finally, Rhino.Mocks allows a partial mock, which also avoids throwing an exception stead of returning 0 or null, it will call the original method on the object and return that value. This lets you mock only the methods needed on an object. Rhino.Mocks also offers a number of other useful features, including support for generic types, callbacks, and the ability to mock delegates and events. Price: Free; source code available. www.rhinomocks.com slow, followed by a guessing game on the developer’s part as to what is causing the performance issues. What developers really need is a way to quantify how an application is performing and quickly identify bottlenecks. dotTrace JetBrains that makes accomplishing both tasks quick and easy. Windows® applications, Web applications (using either IIS or the Visual Studio® Development Server), and Windows services. dotTrace offers both you to view the amount of time each of your methods and lines of code takes which shows the amount of memory currently being used and by what objects. applications built on the 1.1 and 2.0 versions of the .NET Framework; memory built using version 2.0. shows you how many times each of your methods was called, how much total time was spent in those methods, and what percentage of the overall time a particular method consumes. These the parts of your application that aren’t performing well. An even easier way is to use the Hot Spots feature, which shows you the 100 worst-performing parts of your application. dotTrace includes two modes for of the memory, which lets you view the objects currently in memory and the amount of space they occupy. Or you can use the Differences mode, which lets you capture memory during a particular interval and then shows you both new objects and dead objects and the difference between the two during a procan be very valuable when trying to track down a memory leak. One feature that makes dotTrace stand out is its integration with Visual Studio, which lets you easily start promouse clicks. With dotTrace, the next time you need to speed up all or part of Quantifying App Performance One of the main goals when writing any application is performance, yet most developers work on a daily basis with almost no way to quantify this goal. Typically, it is left to users to identify which screens or pages are running too msdnmagazine http://www.dynamicpdf.com http://www.rhinomocks.com http://www.dynamicpdf.com http://www.cete.com http://www.cete.com

Table of Contents Feed for the Digital Edition of MSDN Magazine - January 2008

MSDN Magazine - January 2008 Contents Toolbox CLR Inside Out Data Points Advanced Basics Cutting Edge IIS 7.0 - Enhance Your Apps with the Integrated ASP.NET Pipeline World Ready - Around the World with ASP.NET AJAX Applications WCF Syndication - HTTP Programming with WCF and the .NET Framework 3.5 Wicked Code Foundations Extreme ASP.NET {End Bracket}

MSDN Magazine - January 2008

For optimal viewing of this digital publication, please enable JavaScript and then refresh the page. If you would like to try to load the digital publication without using Flash Player detection, please click here.