Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more ➡
Download
Standard view
Full view
of .
Add note
Save to My Library
Sync to mobile
Look up keyword
Like this
1Activity
×
0 of .
Results for:
No results containing your search query
P. 1
Coding Standards

Coding Standards

Ratings: (0)|Views: 289|Likes:
Published by api-3740209

More info:

Published by: api-3740209 on Oct 15, 2008
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, DOC, TXT or read online from Scribd
See More
See less

03/18/2014

pdf

text

original

c# coding standards and best programming practices
by
http://www.dotnetspider.com
http://www.dotnetspider.com/tutorials/bestpractices.aspx

1. author...........................................................................................................................3 2. license, copyrights and disclaimer...............................................................................3 3. revision history............................................................................................................3 4. introduction..................................................................................................................3 5. purpose of coding standards and best practices...........................................................3 6. how to follow the standards across the team...............................................................4 7. naming conventions and standards..............................................................................4 8. indentation and spacing...............................................................................................7 9. good programming practices.....................................................................................10 10. architecture................................................................................................................15 11. asp.net........................................................................................................................16 12. comments...................................................................................................................16 13. exception handling.....................................................................................................17

1. author

this document is prepared by thedotnetspid er team. latest version of this document can be downloaded fromhttp://w ww.dotn etspider.com /tutorials/bestprac tices.as px. please post your comments and feedback about this document in the above url.

most of the information in this document is compiled from the coding standards and best
practices published in various articles in dotnetspider.com. also, we referred to theguidelines
published by microsoft and various other sources.
2. license, copyrights and disclaimer
you are permitted to use and distribute this document for any non commercial purpose as long as
you retain this license & copyrights information.
this document is provided on \u201cas-is\u201d basis. the author of this document will not be responsible for
any kind of loss for you due to any inaccurate information provided in this document.
3. revision history
if you are editing this document, you are required to fill the revision history with your name and
time stamp so that anybody can easily distinguish your updates from the original author.
sl#
date
changed by
description
1
4. introduction

anybody can write code. with a few months of programming experience, you can write 'working
applications'. making it work is easy, but doing it the right way requires more work, than just
making it work.

believe it, majority of the programmers write 'working code', but not \u2018good code'. writing 'good
code' is an art and you must learn and practice it.
everyone may have different definitions for the term \u2018good code\u2019. in my definition, the following
are the characteristics of good code.
\u2022
reliable
\u2022
maintainable
\u2022
efficient

most of the developers are inclined towards writing code for higher performance, compromising
reliability and maintainability. but considering the long term roi (return on investment), efficiency
and performance comes below reliability and maintainability. if your code is not reliable and
maintainable, you (and your company) will be spending lot of time to identify issues, trying to
understand code etc throughout the life of your application.

5. purpose of coding standards and best practices
http://www.dotnetspider.com/tutorials/bestpractices.aspx

You're Reading a Free Preview

Download
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->