Professional Documents
Culture Documents
C#CodeReviewAndBestSuggestedReviewGuidelines
In Focus
Umakanth
Ask a Question
ARTICLE
Contribute
READER LEVEL:
C#CodeReviewAndBestSuggestedReview
Guidelines
By Bhuvanesh Mohankumar on May 12, 2016
In this article you will learn about C# Code Review and best suggested Review
Guidelines.
7.8 k
19
1/9
18/05/2016
C#CodeReviewAndBestSuggestedReviewGuidelines
Code review has a large impact on consistent design and implementation. Peer review helps to
maintain a level of consistency in software design and implementation.It helps to have a higher
software security. Applications that require a high level of security benet from targeted security
reviews.It is also built on team cohesion. Review discussions save team members from isolation
and bring them closer to each other.
Code review gives the condence of stakeholders. You build condence of stakeholders about
the technical quality of the execution.
Source: javacodegeeks.com
TECHNOLOGIES
ANSWERStypes
BLOGS
VIDEOSreviews
INTERVIEWS
BOOKS NEWS
CHAPTERS
CAREER below,
JOBS CODE
There
are
basically three
of Code
recommended
and nd
the details
IDEAS C#CornerSearch
Peer review:
When one of your team members reviews the code to ensure that the code follows the coding
standards and meets requirements.
http://www.csharpcorner.com/article/CSharpcodereviewandbestsuggestedreviewguidelines/
2/9
18/05/2016
C#CodeReviewAndBestSuggestedReviewGuidelines
Peer level of review can include some unit testing also. Every le in the project must go through
this process.
Source: biomedcentral.com
Architect Review:
The Technical Architect of the team must review the core modules of the project to ensure that
they adhere to the design and there are no major mistakes that can aect the project in the long
run.
It is a kind of approval from the architect to check that the code has met the design
requirements.
http://www.csharpcorner.com/article/CSharpcodereviewandbestsuggestedreviewguidelines/
3/9
18/05/2016
C#CodeReviewAndBestSuggestedReviewGuidelines
Group Review:
This is a normally used review type where you randomly select one or more les and conduct a
group review once a week.
It is always strongly recommended to distribute a printed copy of the les to all team members
15 minutes before the meeting. All of them can read and come up with points for discussion. In
the group review meeting, use a projector to display the le content in the screen. Go through
every section of the code and let every member give their suggestions on how could that piece
of code could be written in a better way.
Best Suggested Review Guidelines:
I have explained the review guidelines that are mostly recommended in the software
development process.
1. Always check for 'null', this needs to be performed wherever applicable to avoid the Null
Reference Exception at runtime.
2. Check for the proper implementation of Exception Handling using the try, catch and nally
blocks of code.
3. Make sure the logging of exceptions and also proper ow of application is also logged [if
necessary] for better error xing in future.
4. Check that the developer has tested his codes along with the test cases by performing unit
test to make sure that basic level of testing is done.
5. Check that developer has reduced using nested if conditions as much as possible for better
code functionality use switch cases wherever required.
6. Conrm that the regular for loop are replaced with by using LINQ queries and Lambda
expressions to improve Readability.
http://www.csharpcorner.com/article/CSharpcodereviewandbestsuggestedreviewguidelines/
4/9
18/05/2016
C#CodeReviewAndBestSuggestedReviewGuidelines
7. Check that the class are marked as sealed or static or abstract as per its usage and your
need.
8. It is always recommended to hand write the code even though if you are referring to the
code from some sources, always its strongly recommended to avoid copy paste of code
from other resources.
9. In the Code analysis Rules and guidelines of Microsoft it is suggested to avoid using the
'out' and 'ref' keywords in the application as much as possible.
10. Check the developer has used "Stringbuilder" instead of "string", if multiple concatenations
are required in order to save heap memory.
Download 100% FREE Spire Oce APIs
Bhuvanesh Mohankumar
I am a Lead Technical programmer working in Microsoft Technologies not limited to
ASP.Net, MVC, SQL, AngularJS, Azure and social networking like Facebook, LinkedIn,
Google analytic.Specialties:Team Work, Coordinating, Bu... Read more
http://www.c-sharpcorner.com/members/bhuvanesh-mohankumar
155
Rank
296.1k
Read
Gold
Member
RELATED ARTICLES
What's New in Review Tab in Word 2013
Best Practices For Code Review
Increase Your Code Review Eciency With
http://www.csharpcorner.com/article/CSharpcodereviewandbestsuggestedreviewguidelines/
5/9
18/05/2016
C#CodeReviewAndBestSuggestedReviewGuidelines
C#
C# Code Review
Code Review
Developers
Guidelines
COMMENTS
10 of 19
Good one
Sonu Chaudhary
377 541 49.7k
Post Reply
Good one
Nitin Tyagi
152 1.6k 76.7k
Post Reply
Nice share
Bhavik Patel
551 223 43.6k
Post Reply
Nice Article
Rambabu Chintapanti
757 4 0
Post Reply
Nice
Vignesh Mani
118 1.9k 60.7k
Post Reply
http://www.csharpcorner.com/article/CSharpcodereviewandbestsuggestedreviewguidelines/
Post Reply
6/9
18/05/2016
C#CodeReviewAndBestSuggestedReviewGuidelines
Post Reply
Post Reply
Post Reply
Post Reply
Follow Comments
COMMENT USING
0Comments
Sortby Oldest
Addacomment...
FacebookCommentsPlugin
SPONSORED BY
http://www.csharpcorner.com/article/CSharpcodereviewandbestsuggestedreviewguidelines/
7/9
18/05/2016
C#CodeReviewAndBestSuggestedReviewGuidelines
TRENDING UP
01
02
03
04
05
06
07
08
09
10
Follow@csharpcorner
http://www.csharpcorner.com/article/CSharpcodereviewandbestsuggestedreviewguidelines/
61.3Kfollowers
8/9
18/05/2016
C#CodeReviewAndBestSuggestedReviewGuidelines
C#Corner
198,523likes
LikePage
BookNow
1friendlikesthis
MVPs
MOST VIEWED
LEGENDS
NOW
PRIZES
REVIEWS
SURVEY
CERTIFICATIONS
DOWNLOADS
ABOUT US
CONTACT US
FAQ
MEDIA KIT
PRIVACY POLICY
MEMBERS
STUDENTS
LINKS
SITEMAP
REPORT A BUG
http://www.csharpcorner.com/article/CSharpcodereviewandbestsuggestedreviewguidelines/
9/9