A significant chunk of web based applications are built on .Net framework. The overall framework is consistent, scalable and capable of creating powerful applications online. Dot Net Application Development then keeps gaining increased importance today. Here are some of the best Practices for Dot Net Application Development in 2016

2.  A novel consistent software framework by Microsoft
 As rightly depicted by Microsoft –
› “Any developer, any app, any platform”
 Scalable and capable of creating powerful
applications online

3.  Enhanced security for web based
applications
 Development output is typically “WYSIWYG”
 Framework helps reduce code quantity
 Significant collection of supporting tools
 Drag & drop capabilities, server controls

5.  Simplistic code writing
 Consistency can be set up while avoiding
exceptions and errors.
 Commonly recognized standards for code
layout, naming, appearance.

6.  A recommended technique by
experts.
 To measure the code
performance, so as to tune the
application better.
 Use analyzers to monitor
application performance, and
identify bottlenecks.

7.  Use SQL parameters instead
of concatenating strings while
building SQL queries.
 Any values that are pulled
from the application should be
populated as SQL parameters.
 Users should not have rights
to write or inject SQL code.

8.  Try and check if the
string length is set to 0.
 Variable checks for
measuring string length
 Use “string.format”
method instead of
appending or
concatenating strings
manually.

9.  A good practice to catch specific exceptions,
rather than generic exceptions.
 Recommended to use an appropriate
architecture or patter (such as MVC) while
using the .Net framework.

10.  Must advocate the use of inheritance
features, although this best practice is not
just limited to the .Net framework.
 Developers should try and incorporate client
side validation / client side scripts.
 Wherever feasible, Ajax UI can be
implemented using dot net development.

11.  Developers need to ensure that if an object
is provisioned, the Close or Dispose method
needs to be called.
 Connections should be opened just before
the requirement, and closed out as
applicable.

12.  If data caching is not required, it makes
sense to use DataReader for efficient data
binding.

13. Visit www.valueedgesolutions.com and
request a Quote/Proposal for any of your .Net
Development Needs