Microsoft Naming Conventions

Microsoft recommends following naming conventions

Variables : use came case e.g. someName

Method: use Pascal case e.g. SomeMethod. Also name the method by the action they perform e.g. WriteLine. Microsoft does not recommends Hungarian notation e.g. iSomeInteger or underscore e.g. Some_Integer.

Coding standard:

Always use this to refer to the members of current class.
Never make a member field as public. Always create properties or methods to allow access to member fields.

Comments

Why there is semicolon at the start of a JavaScript function?

Very often while reviewing the code for my team, I will come across a semicolon at the start of JavaScript function as show below ; (function () { 'use strict'; ...and I often wondered what purpose it served. Guess what. It is an insurance to make sure your script works fine when all other scripts are merged together; The leading ; in front of immediately-invoked function expressions (iffe) is there to prevent errors when appending the file during concatenation to a file containing an expression not properly terminated with a ;. So there you go. Now you know what that little semicolon is doing there in your code.

unable to download wsdl file while adding web reference

If you get this error while adding web reference, simply delete the reference, close and reopen the project. Now add the web reference again but this time stick ?wsdl at the end of url. This reolves the problem.

C# Performance Improvement - The Power of StringBuilder

Often when we are wring code we don't think about performance and go with the default options available to achieve a task. String concatenation is one such scenario. If you are doing simple and few string catenations, then you can use the following result = string1 + string2; string1+= string2; result = String.Concat(string1,string2); String.Format and string interpolation are few other options. However when you are performing large and repetitive operation, string catenation can be expensive. Here is an example to prove the point. As you can see it took 41 seconds to perform 100k string catenation. Now lets replace this with StringBuilder and see. 8 ms!!!!!! That is a massive performance difference. Hope you get the point. More info on StringBuilder can be found here https://learn.microsoft.com/en-us/dotnet/api/system.text.stringbuilder?view=net-7.0

Developing modern applications in cloud

Search This Blog