Expert One-on-One™ C# Design and Development

Chapter 12. Coding the Application

After the initial design phase, many developers head directly to their editors and start typing. If you're working alone on a simple project, you can probably take this approach without experiencing any problems. However, when working on a complex team project, the immediate typing approach seldom works because you must consider some code writing issues such as the naming convention the team will use and determining how certain features will appear in the application.

This chapter begins by addressing the mundane sounding, yet politically charged, issue of using a consistent naming convention. In the end, it doesn't matter which naming convention you use—they all work. What matters is that all coders on your team use the same naming convention so they can read each other's code. This chapter doesn't espouse a particular naming convention—it simply tells you what's available so you can make your own decision.

How an application begins and exits has always been important. However, in an age when Microsoft has introduced Windows Server 2008 Server Core — a special version of Windows that lacks a GUI — the manner in which an application begins and ends has taken on special significance. This chapter provides you with techniques you can use to begin and end a .NET application at the command line or simply use the command line as an intermediary to standard GUI use. Having command line functionality gives you a big advantage when it comes to making the ...