1) stages. 2) Keeping the variable naming

1)    
Make a plan before you start writing your code

It’s a good idea to use a robust planning tool, to plan each class along with
its properties and methods before starting to work on coding. When planning
ahead, each component of the application, methods and properties have to be
identified in initial stages to avoid refactoring the code in later stages.

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!


order now

2)    
Keeping the variable naming schemes consistent  

While writing codes for clients, they might need the names of variables
in some particular manner. So it is better to keep the naming schemes
consistent and always procure coding standards documentation from clients.

3)  
Not forgetting the DATABASE

A dynamic web application with .NET framework needs a database. A poor
database design will cripple the application, the database layout is much
important than planning the code stage. Usually .NET developers work with
Microsoft SQL Server as it plugs into .NET code much easily. Also there are
some other solutions like MySQL, Oracle or NoSQL solutions available on web.

4)    
Separating the Coding Layers

A consistent coding requires layers. At the very least, one should create
a presentation and a data layer, but most software design requires a separate
presentation layer, business logic layer, and data layer. Layering helps in completely
overhauling one layer without affecting the other one. Using a dependency
injection for data layers will enable you to separate layers automatically.

5)  
 Maintaining an Error Log

A large application running on servers need a logging solution, to
identify the critical errors as it can be extremely tedious and time consuming
job to reproduce the error report. Interestingly, .NET has an internal Error
Logging system that compiles the log of errors to the Windows Event Viewer.

6)    
Checking that Configuration files are transferred correctly

It is advisable to have a process to manage the settings in the
application’s Web configuration file to ensure production Web site works
correctly.

 

7)    
Trimming the Working SET

Minimising the number of assemblies help in keeping the working set
small. While loading an entire assembly to use only one method, it incurs tremendous
cost with very little benefit. It would be advantageous if one can duplicate
the method’s functionality using code which is already loaded.

8)  
Using Loops for String iteration

The foreach keyword allows one
to perform operations on each item across the items in list or string. It is a
very powerful tool, as it acts a general purpose enumerator for many types. The
trade-off for this generalization is speed, instead use for loop if you rely
heavily on string iteration.

9)    
Using String Builder for Complex String Manipulation

While modifying the string, the run time creates a new string and leaves
the original string for trash. The String Builder code is much faster, as it
reduces the burden on performance when strings are to be modified multiple
times.

10) Batch Compiling

It is recommended to batch compile before deploying large pages into the
Web. This can be initiated by doing one request to a page per directory and
waiting until the CPU is idle again. This prevents the Web server from being crashed
down with compilations while trying to serve out pages.