List of Figures

 < Day Day Up > 



Chapter 1: Planning Your Project

Figure 1.1: Mind map for Download Tracker
Figure 1.2: Scheduling a new project using Task Tracker
Figure 1.3: Tracking hours with A to Z Project Billing
Figure 1.4: Schematic diagram of the Microsoft Solutions Framework

Chapter 2: Organizing Your Project

Figure 2.1: Architectural diagram for Download Tracker
Figure 2.2: Trade-offs in software development

Chapter 3: Using Source Code Control Effectively

Figure 3.1: Viewing a file’s history using SourceGear Vault
Figure 3.2: Creating a branch for a release
Figure 3.3: Merging changes from a branch back to the trunk
Figure 3.4: Source code control in the Visual Studio .NET IDE
Figure 3.5: Source code control tree for Download Tracker

Chapter 4: Coding Defensively

Figure 4.1: Assertion at runtime
Figure 4.2: Defining build constants
Figure 4.3: Defining comment tokens
Figure 4.4: The Visual Studio .NET Task List

Chapter 5: Preventing Bugs with Unit Testing

Figure 5.1: First test run with NUnit
Figure 5.2: Test run with a failing test
Figure 5.3: Attaching to a process to debug
Figure 5.4: A failing test for new functionality

Chapter 6: Pumping Up the IDE

Figure 6.1: Selecting a profile
Figure 6.2: The Options dialog box
Figure 6.3: Comparing 10-point Courier with 8-point ProFont
Figure 6.4: The Recorder toolbar lets you start, pause, finish, or cancel macro recording.
Figure 6.5: The Macro IDE
Figure 6.6: Project Line Counter
Figure 6.7: QuickJump.NET
Figure 6.8: Total .NET XRef
Figure 6.9: Total .NET Analyzer
Figure 6.10: CodeSMART Code Explorer
Figure 6.11: UML model generated by Rational XDE
Figure 6.12: Analyzing memory usage with DevPartner Studio

Chapter 7: Digging Into Source Code

Figure 7.1: A .NET file in Ildasm
Figure 7.2: Disassembling a method with Ildasm
Figure 7.3: Exploring with Reflector
Figure 7.4: Reflecting into the .NET Framework
Figure 7.5: Using nogoop .NET Component Inspector
Figure 7.6: Testing a control
Figure 7.7: Snippet Compiler
Figure 7.8: Information on a Logidex SDA
Figure 7.9: FxCop in action
Figure 7.10: FxCop rule details
Figure 7.11: FxCop and the FCL

Chapter 8: Generating Code

Figure 8.1: CodeSmith template properties
Figure 8.2: CodeSmith output
Figure 8.3: Building a strongly typed DataSet

Chapter 9: Tracking and Squashing Bugs

Figure 9.1: A sample bug report

Chapter 10: Logging Application Activity

Figure 10.1: An event log message from Download Tracker
Figure 10.2: EIF architecture
Figure 10.3: The System Information utility

Chapter 11: Working with Small Teams

Figure 11.1: A SourceForge project home page
Figure 11.2: A GotDotNet Workspaces home page
Figure 11.3: A page from a wiki
Figure 11.4: Groove Workspace

Chapter 12: Creating Documentation

Figure 12.1: A task-oriented help topic
Figure 12.2: Help topic with a feedback link
Figure 12.3: HTML Help Workshop
Figure 12.4: RoboHelp 4.1
Figure 12.5: Activating XML documentation in VS .NET
Figure 12.6: Using NDoc to build a help file
Figure 12.7: Developer-style help for a class library

Chapter 13: Mastering the Build Process

Figure 13.1: Daily Build
Figure 13.2: FinalBuilder
Figure 13.3: Visual Build Professional

Chapter 14: Protecting Your Intellectual Property

Figure 14.1: Looking at an unobfuscated assembly
Figure 14.2: The Dotfuscator project in the Visual Studio .NET IDE
Figure 14.3: Looking at an obfuscated assembly

Chapter 15: Delivering the Application

Figure 15.1: InstallShield DevStudio in Action
Figure 15.2: Choosing the pieces of Office 2003 to install
Figure 15.3: Choosing a project type
Figure 15.4: Dialog boxes for setup projects
Figure 15.5: Properties for a setup project
Figure 15.6: The completed installer



 < Day Day Up > 



Coder to Developer. Tools and Strategies for Delivering Your Software
Coder to Developer: Tools and Strategies for Delivering Your Software
ISBN: 078214327X
EAN: 2147483647
Year: 2003
Pages: 118

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net