C# Best Coding Guidelines

Hello, when string comparing depends on casing, better use static String.Equals with right StringComparison parameter

An int can not be null in c#. It always zeroes so put int? if you want to make it nullable.

Check for 'null' Its not correct because parameter is not nullable

Nice article, thanks

It's good to say when and where use Pascal or Camel style

Nice article

Nice article

Thanks Prasanna M

Thanks Raja Ganapathy

Thanks Farhan Shariff

Thanks Anish kumar

Thanks Anu Vivin

Nice one

Nice Article...

useful articl

Nice article , very usefull...

Nice

Thanks Anand More

Thanks Prasham Sabadra

Thanks Rupali Shinde

Thanks Mohammed Ashraf

Thanks @Anand mor

Thanks for Sharing!!!

really useful tips for developer :) thanks for sharing ..

Really informative...

Thanks for sharing Bhuvanesh !!

Thanks Viipiin Tyagi

Thanks & its Just Microsoft Paint Prakash Tripathi

Thanks for that @Abhishek Sur

It's a great article.

Good one Bhuvanesh....Just curious which tool you used to draw the pictures for do/don't?

One small adjustment : Null can only be checked when it is nullable. If not it will already have default(type). Another thing string s = ""; and string s = string.Empty will have same meaning as because empty string is always interned in .NET. Also accountName.Equals("bhuvan", StringComparison.CurrentCultureIgnoreCase) will ignore the creation of extra Upper case string in memory.

Thanks Pratik BHAVSAR

nice article

Thanks Jeff Orris

Thanks Sabyasachi Mishra

I love your guys' site...anytime I need refreshed or to keep my coding in check I turn to you....you make it so easy for others to understand.

Good one

Thanks Pradeep Sahoo

Thanks Sonu Chaudhary

Thanks Rambabu Chintapanti

Thanks Rajeesh Menoth

Thanks Ipsita Sethi

Nice information .Thanks for sharing.

nice

Nice Article

Good Explanation..Thank you for sharing!! We can use enum for hard coding area's.

Nice sharing Bhuvan

Thanks, I have mentioned in early comments itself. " Yes of course its just for some sample, instead of a class mentioned as int".

Thanks @Paramjit Singh

Thanks @Jitendra Kumar

Nice Article..

Yes Right not necessary. But if you want to check null also then apply nullable, before check. in case of int.

Null test on "int value" is not necessary. Do you mean "int? value" ?

Awesome post,really helpfull

Good one

In null Check If we apply nullable like this public string GetDate(int? value) Then we can check it null. isn't it

Thanks for sharing

Nice one.

nice one

Very Nice article

Nice really helpful. Thanks

Nice article :)

nice article

Nice Sharing..

I liked the article! Good points, looking fwd for part 2

You should indicate when to use Camel or Pascal casing. It would be also helpful if you will add using underscore when naming global variables. Second, int a is value type and it requires a value so it doesn't make sense to check for nulls on int type not unless if you declare it as nullable type of int. Third, commenting isn't necessary for as long as you name your method properly. For example GetData() is not helpful and meaningful, GetCustomerOrderByID() is. Making your method name meaningful helps you easily understand what the code is all about and there's no need to put comments on it not unless if the logic within it has complex implementation.

Good Tips

String str = "" and string str = String.Empty. What difference does it make? Why is it better to use string.Empty

String Comparison -- We should instead use, String.Compare with ignorecase option.

Nice article

Great article! Every new employee should read and sign something like this :) p.s.:I don't believe that an int can be null

Thanks Nice Article

Good one

Good one, I just want to add that enum must be in separate file and must have a value for each such as public enum LoginType:byte{Admin = 1,Member=2 }

Good one Bhuvanesh.

Nice Efforts Sir......