Rules to Healthier Code Presented by Adam Cogan (Chief Architect for

About Chief Architect for doing: –internal corporate development and –generic off-the-shelf databases –Clients: Royal & Sun Alliance, Westbus, Microsoft… President.NET User Group, Sydney Speaker for Microsoft TechEd and Roadshows, Dev Conn, VSLive…. Microsoft Regional Director, Australia …Australia…

Agenda Unit Testing –NUnit –Test Driven –Other Unit Tests Code Analysis –Microsoft FxCop –SSW Code Auditor Code Profiling –JetBrains dotTrace Profiler Build Server –Cruise Control The Future –Other Tools –Visual Studio Team System

What is Healthy code? What is Healthy Code anyway? Why is it Important? What about Documentation? Is your spec in bite-sized pieces? Does your spec have the 3 important things?

NUnit How many unit tests do you write…?

When do you write Unit Tests? 100% unit tests is 100% impractical Unit tests should be written for: –Dependencies – e.g. DLLs Run time errors (JIT) –Dependencies – e.g. Database Schema, Datasets, Web Services –Fragile Code – e.g. Regular Expressions –When errors can be difficult to spot – e.g. Rounding, arithmetic, calculations –Performance – e.g. Slow forms Don’t: –When the unit tests are bigger than the original (Insert) –Generated Code like Insert, Update, Delete Rules to Better Unit Testing

Do you have ‘Run Unit Tests’ on your Help Menu? UnitTests.aspx#MenuUnitTestshttp:// UnitTests.aspx#MenuUnitTests A user should be able to run unit tests through an application. This aids the developers quickly identify any problems with the application by running the unit tests.

Test Driven.NET Do you run Unit Tests with the right click of your mouse? Run unit tests from your right click menu

What about other things? Access Unit Tests –SSW Performance PRO ( –FMS Total Access Analyzer ( SQL Reporting Services Unit Tests –SSW Report Validator Performance Unit Tests –MBUnit ( Javascript Unit Tests –JsUnit ( ) And The Backend?

SSW Performance Pro

SSW Report Validator

MBUnit

JsUnit

FxCop What is FxCop? Code analysis tool for.NET managed code assemblies Checks: Library design Naming conventions Performance Security Don’t: Globalization

SSW Code Auditor What is Code Auditor? 1.Maintains coding standards 2.Checks C# and VB.NET code 3.Prevents bad coding practices 4.Integration into Visual Studio

SSW Code Auditor Extensive rule set that is customizable – ult.aspx#Ruleshttp:// ult.aspx#Rules

SSW Code Auditor Produces an XML Report

JetBrains dotTrace Profiler Measures the performance of ASP.NET or Windows Form Application Quickly identify bottle necks through Hot Spots

Test Driven Process Q: What is VSS? A: It is not a file share Check Out Compile Run Unit Tests If it is OK then Start Develop… Develop… Develop… Run Unit Tests If OK Check In Get Latest Run Unit Tests Again to confirm venProcesshttp:// venProcess Want to poison the system – I smell a rat

Cruise Control What is Cruise Control? –Automated Continuous Integration server –Integration with a variety of Source Control systems –Integration with other external tools, such as NAnt and Visual Studio –Can build multiple projects on one server –Remote management and reporting –There is always oneThere is always one +to+CruiseControl.NET

Cruise Control Features: –Web Portal for build info –Tray icon notification

Visual Studio Team System Key Features: –Integration of: Unit Testing –Code Coverage Source Control Code Analysis (FxCop) Code Profiling

Overview Team Communication Quality Early & Often Platform For Innovation Design for Operations Project Manager Solution Architect Developer Tester Infrastructure Architect

Visual Studio Team System Integrated Unit Testing Code coverage –See what code has been executed Static code analysis –FxCop in the task list Code profiling –Based on two internal profilers: Sampling (Light weight) Instrumented (Heavy duty) –Sequence view examines running threads –Caller-callee, callstack, and function views (there today) Why was it built? To avoid the cat problem

Integrated Unit Testing

Code Coverage

Static Code Analyzer

Code Profiling

Perf Counter integration and monitoring Load Testing

Integrated Reporting

Integrated Build Server

Conclusion To achieve healthy code: –Unit Testing - NUnit –Code Analysis – FxCop and SSW Code Auditor –Build Server – Cruise Control.NET –Visual Studio Team System (everything is integrated) The resources don’t hurt either! – perGeneral/netTools.aspxhttp:// perGeneral/netTools.aspx

Resources SSW.NET Toolkit SSW Code Auditor SSW Performance PRO FMS Total Access Analyzer NUnit MBUnit Test Driven

Resources JetBrains dotTrace Profiler JsUnit FxCop Cruise Control.NET Welcome+to+CruiseControl.NET Welcome+to+CruiseControl.NET Visual Studio Team System

2 things