Get 20M+ Full-Text Papers For Less Than $1.50/day. Start a 14-Day Trial for You or Your Team.

Learn More →

A Programmer’s Introduction to C# 2.0Tips for Real-World Code

A Programmer’s Introduction to C# 2.0: Tips for Real-World Code CHAPTER 40 ■ ■ ■ This chapter discusses the techniques for writing code in a manner that reduces the chances of bugs and delivers high-performance, reliable assemblies suitable for production use. These techniques reflect our cumulative experience (as an original C# team member in Eric Gunnerson’s case and as a professional C# developer, consultant, and MVP in Nick Wienholt’s case). Some of the material in this chapter reinforces the advice presented in earlier chapters, and other sections cover new topics. Naming Conventions Chapter 38 listed the naming conventions you should use in C# applications. These recom- mendations are a subset of the full set of guidelines at http://msdn.microsoft.com/library/ default.asp?url=/library/en-us/cpgenref/html/cpconnamespacenamingguidelines.asp, which in turn are a subset of Microsoft’s own internal coding guidelines, which are currently (in early 2005) available at http://blogs.msdn.com/brada/articles/361363.aspx. ■Note The first sentence of the documentation starts with “First, read the .NET Framework Design Guidelines,” which may be helpful if you need to find the conventions using a Web search engine at some point in the future. Naming conventions are primarily designed to speed up coding and to reduce bugs by allowing a developer to differentiate items such as types, variables, enumerations, and other code constructs based on http://www.deepdyve.com/assets/images/DeepDyve-Logo-lg.png

A Programmer’s Introduction to C# 2.0Tips for Real-World Code

Editors: Gunnerson, Eric; Wienholt, Nick
A Programmer’s Introduction to C# 2.0 — Jan 1, 2005
Download PDF
6 pages

Loading next page...
 
/lp/springer-journals/a-programmer-s-introduction-to-c-2-0-tips-for-real-world-code-9v0gi05pgu
Publisher
Apress
Copyright
© Apress 2005
ISBN
978-1-59059-501-5
Pages
485 –491
DOI
10.1007/978-1-4302-0035-2_40
Publisher site
See Chapter on Publisher Site

Abstract

CHAPTER 40 ■ ■ ■ This chapter discusses the techniques for writing code in a manner that reduces the chances of bugs and delivers high-performance, reliable assemblies suitable for production use. These techniques reflect our cumulative experience (as an original C# team member in Eric Gunnerson’s case and as a professional C# developer, consultant, and MVP in Nick Wienholt’s case). Some of the material in this chapter reinforces the advice presented in earlier chapters, and other sections cover new topics. Naming Conventions Chapter 38 listed the naming conventions you should use in C# applications. These recom- mendations are a subset of the full set of guidelines at http://msdn.microsoft.com/library/ default.asp?url=/library/en-us/cpgenref/html/cpconnamespacenamingguidelines.asp, which in turn are a subset of Microsoft’s own internal coding guidelines, which are currently (in early 2005) available at http://blogs.msdn.com/brada/articles/361363.aspx. ■Note The first sentence of the documentation starts with “First, read the .NET Framework Design Guidelines,” which may be helpful if you need to find the conventions using a Web search engine at some point in the future. Naming conventions are primarily designed to speed up coding and to reduce bugs by allowing a developer to differentiate items such as types, variables, enumerations, and other code constructs based on

Published: Jan 1, 2005

Keywords: Unit Testing; Naming Convention; Visual Studio; Continuous Integration; Code Path

There are no references for this article.