Microsoft Development Services

.NET Frameworks & Best Practices

Silicus Microsoft .NET frameworks and best practices helps customers accelerate the design and development of applications, reduce project technical risk, and enable the product to take advantage of related Microsoft technologies.

Over the period Silicus has developed strong experience in Microsoft patterns & practices that can offer a combination of written documentation and re-usable source code. Our .NET architects and solution designers are familiar in the following categories of patterns & practices

Microsoft Application Blocks

Using Microsoft Application Blocks for commonly required functionalities, helps to achieve Consistency, Extensibility, Ease of use & Integration throughout the implementation of project, here are the set of Application Blocks that our developers are experienced in.

The Caching Application Block:

• Lets developers incorporate a local cache in their applications. It supports both an in-memory cache and, optionally, a backing store that can either be the database store or isolated storage.
• Provides all the functionality needed to retrieve, add, and remove cached data. Configurable expiration and scavenging policies are also part of the application block.

The Data Access Application Block:

• Reduces the need to write boilerplate code to perform standard tasks.
• Reduces difficulties in changing the database type.
• Relieves developers from learning different programming models for different types of databases.
• Reduces the amount of code that developers must write when they port applications to different types of databases.

The Exception Handling Application Block:

• Supports exception handling in all architectural layers of an application.
• Allows exception handling policies to be defined and maintained at the administrative level.
• Provides commonly used exception handling functions, e.g. logging exception information, hiding sensitive information and maintaining contextual information.
• Invokes exception handlers in a consistent manner. This means that the handlers can be used in multiple places within and across applications.

The Security Application Block:

• Implement common functionality of authorization & caching a user's authorization-related data.
• Helps maintain consistent security practices
• Eases the learning curve for developers.
• Extensible, Supports custom implementations of security providers.

The Validation Application Block:

• Using this, we can perform validation and create rule sets Using configuration, attributes or by writing code.
• includes adapters that allow you to use the application block with ASP.NET , Windows Forms and WCF

The Cryptography Application Block:

• Simplifies a variety of cryptography tasks, such as encrypting information, creating a hash from data, and comparing hash values to verify that data has not been altered.

Composite UI Application Block:

• Helps creating complex user interfaces made of loosely coupled components.
• Used exclusively for developing Windows Forms as well as Web Clients & mobile Clients.
• Encourages the developer to use either the Model-View-Controller or Model-View-Presenter architectural pattern, to encourage reuse of the individual User Controls (or 'SmartParts') by not coupling them with their underlying data elements or presentation code.