Skip to main content

C# Naming Conventions

Variable names are something you will use a lot, so it's worth spending a bit of time learning the sort of names you should use. Developers have realized that it is far better to name variables appropriately for their purpose.

Currently, two naming conventions are used in the .NET Framework namespaces: PascalCase and camelCase. The case used in the names indicated their usage. They both apply to names that comprise multiple words and they both specify that each word in a name should be in lowercase except for its first letter, which should be uppercase. For camelCase terms, there is an additional rule: The first world should start with a lowercase letter.

The following are camelCase variable names:

These are PascalCase:

For your simple variables, stick to camelCase. Use PacalCase fo certain more advanced naming, which is the Microsoft recommendation. Finally, note that many past name systems involved frequent use of of the underscore character, usually as a separator between words in variable names, such as yet_another_variable. This usage is now discouraged(which is just as well; it looks ugly!).

By convention, namespaces are usally written in PascalCase.


Popular posts from this blog

Stretch a row if data overflows in jasper reports

It is very common that some columns of the report need to stretch to show all the content in that column. But  if you just specify the property " stretch with overflow' to that column(we called text field in jasper report world) , it will just stretch that column and won't change other columns, so the row could be ridiculous. Haven't find the solution from internet yet. So I just review the properties in iReport one by one and find two useful properties(the bold highlighted in example below) which resolve the problems.   example:
<band height="20" splitType="Stretch"> <textField isStretchWithOverflow="true" pattern="" isBlankWhenNull="true"> <reportElement stretchType="RelativeToTallestObject" mode="Opaque" x="192" y="0" width="183" height="20"/> <box leftPadding="2"> <pen lineWidth="0.25"/> …

JasperReports - Configuration Reference

Spring - Operations with jdbcTemplate

This class manages all the database communication and exception handling using a java.sql.Connection that is obtained from the provided DataSource. JdbcTemplate is a stateless and threadsafe class and you can safely instantiate a single instance to be used for each DAO.

Use of Callback Methods
JdbcTemplate is based on a template style of programming common to many other parts of Spring. Some method calls are handled entirely by the JdbcTemplate, while others require the calling class to provide callback methods that contain the implementation for parts of the JDBC workflow. This is another form of Inversion of Control. Your application code hands over the responsibility of managing the database access to the template class. The template class in turn calls back to your application code when it needs some detail processing filled in. These callback methods are allowed to throw a java.sql.SQLException, since the framework will be able to catch this exception and use its built-in excepti…