header image

ASP.NET – Single-Page Applications: Build Modern, Responsive Web Apps with ASP.NET

Posted by: | April 25, 2016 Comments Off on ASP.NET – Single-Page Applications: Build Modern, Responsive Web Apps with ASP.NET |



under: Uncategorized

Windows 8 Developer Preview

Posted by: | September 14, 2011 | 2 Comments |

Download the Windows Developer Preview


under: Uncategorized

.NET Framework 4.5 Developer Preview

Posted by: | September 14, 2011 | 1 Comment |

What’s New in the .NET Framework 4.5 Developer Preview


Download the NET Framework 4.5 Developer Preview


under: Uncategorized

Tutorial Microsoft SharePoint 2010

Posted by: | September 9, 2011 | No Comment |

SharePoint 2010 Reference: Software Development Kit

Conceptual overviews, programming tasks, code samples, and references to guide for developing solutions based on SharePoint 2010 products and technologies.


Installing and Using the SharePoint 2010 SDK Download


SharePoint Foundation 2010 SDK Documentation


SharePoint 2010: Professional Developer Evaluation Guide and Walkthroughs

Describes the SharePoint 2010 developer platform, including walkthroughs of some of the new capabilities for developers.


Developing Applications for SharePoint 2010

Provides technical information about key areas of SharePoint 2010 application development. It contains a written guide, reference implementations with source code and documentation, and a library of reusable source code components.


SharePoint 2010: Getting Started with Development on SharePoint 2010 Hands-on Labs in C# and Visual Basic

10 hands-on lab manuals for SharePoint 2010 to get started learning SharePoint 2010 development.


SharePoint 2010 Developer Training Kit

Provides developers with advanced guidance on how to develop for SharePoint.


Videos – Microsoft Office SharePoint Server


Webcast on-demand – Microsoft Office SharePoint Server


Virtual Lab – Microsoft Office SharePoint Server


Nice blog… which covers a lot…


under: Uncategorized

JustDecompile – Free .NET Decompiler

Posted by: | August 28, 2011 | 1 Comment |

JustDecompile is a free .NET Decompiler from Telerik.
Beta version is available from http://www.telerik.com/products/decompiling.aspx

Previously I used to use .NET Reflector; one of the most essential tool for developing .NET application; especially for to make sure the difference between source code of a project and production version dll file[.NET assembly by comparing decompiled code.

.NET Reflector is no more Free.

Source code could see using JustDecompile but not main feature exporting code in the for of project from dll is not there. it’s missing which is the most useful and needful feature.

under: Uncategorized

Specify the communication mechanism – communicating a message to an endpoint

  • Protocol
    Determine the security, reliability, context flow settings

  • Transport channel
    Determine the underlying transport protocol
    E.g. http, https, namedpipe, MSMQ

  • Message encoding
    Determine the wire encoding to use for messages
    E.g. binary, text/xml, MTOM(Message Transmission Optimization Mechanism (MTOM)

Things to keep in mind when you think about WCF binding

  • Message Version
  • Transport Security
  • Message Security
  • request-reply(default),one-way (fire and forget), duplex (both way)
  • Reliability
  • Transaction
  • Streaming

For further you can refer


under: 9534

Sub-Domain Area

Architecture Pattern Name

Design Patterns

Solution Patterns

Related Patterns

Data Integration/SOA

ETL ( Data Extraction Transformation & Loading)

Change Data Capture

Error handling



Near Real-Time ETL

Job scheduling

Master Data Hub


Batch ETL

Data validation

Operational Data Store (ODS)


Data Discovery

Slowly Changing Dimensions Load
















Synchronous Request/Response



Message Exchange Patterns

Basic Callback




Claim Check







Data Architecture

Transaction Data Stores (TDS/OLTP)

Custom Applications Databases



Master Data Store

Packaged Application Databases



Operational Data Store

















Business Intelligence and Reporting

Transactional Reporting

Transactional Reporting Data Access

Real-Time Dashboards


Operational Reporting

Operational Reporting Data Access

In-Memory Analytics


Analytical Reporting

Analytical Reporting Data Access

Statistical Analysis



Analytical Dashboard Data Access

Predictive Analytics

Operational Data Store


Operational Dashboard Data Access




Data Mining








Master Data Management

Master Data Hub

Master Data Replication


Change Data Capture


Master Data Services




Master Data Synchronization







Data Architecture and Modeling

Dimensional Data Modeling

Modeling Standards




At a glance – List of Architecture Patterns, Design Patterns, and Solution Patterns in the Application and Information Architecture Domains nicely presented in WikiPedia

Source: http://en.wikipedia.org/wiki/Architectural_pattern_%28computer_science%29#Examples

under: Uncategorized

Database Trigger

Posted by: | October 15, 2010 | 11 Comments |

Trigger is a Program Unit generally a SQL statement or a set of SQL statements which executes automatically when an associated event of an object in a database occurs.

This has basically three components

  • Program unit is the automated predefined action item to be executed
  • Object on which the action item will be associated
  • Event is the condition/situation to be fired of an object

Before going into deep, I would like to mention that, the whole concepts of the trigger implementation are product specific. All the features of the trigger might not be available in a particular product; but it is true that the basic things are available in all the major products. Even when I came to know first time about the trigger, in 1995 then only DML type of triggers were available for manipulating transactional data; now it’s scope has been totally redefined by keeping same concept of trigger having three component mentioned above. Next phase, the concept of DDL triggers came into the picture.

Program Unit

This might be a set of related SQL of an object, any functionality implemented by an executable application.

For example: Different scenarios where possible action unit could be implemented.

For maintaining data integrity by cascading the changes to the related object, it could be maintaining some constrain. In this purpose single SQL or set of SQL could be used as a Program Unit.
For notification purpose by sending messages/alerts using email or other way.
For audit purpose by logging into event log, or some files, or into any table
For populating change history or Summarized data value
The object and event depends on the implementation of trigger. The trigger could be broadly categorized into two – DDL and DML Trigger.

DML trigger mainly used for maintaining transactional data where DDL trigger is used for administrative and auditing purpose. In earlier concept we used to see only DML trigger for INSERT/UPDATE/DELETE operations. The DML trigger could be associated to a Table or a View. Later we got the DDL trigger feature which could be associated to Database, Table, Index etc. Here the operation could be CREATE/ALTER/DROP. Same time there is another factor arises, that is, associated Program Unit will be executed BEFORE or AFTER of the triggering statement execution.


DML trigger – Data Manipulation Language Trigger; generally associated with Table or View when data values are inserted/updated/deleted

DDL trigger: Generally for object creation / alteration or deletion that mean the keywords CREATE, ALTER, and DROP associated with Transact SQL. It’s scope as follows:

  • Database level
  • Server level


The events depend on the object. If it a table it could be for each row or as whole of a SQL statement.


DML trigger

Statement: This occurs once for executing a SQL statement not depends on the number of rows affected by that statement. It is available in Oracle.
For each row: When a SQL executes, for every row the action will be fired. Again in granular level it could be BEFORE or AFTER
View: Instead of Trigger – Here only we can see only AFTER type operation is available. It has some other limitation too. When any modification or insertion or deletion has been done using instead of trigger, always it checks individuals object’s constrains.

DDL trigger

DDL triggers fire only after the DDL statements whether it’s scope is server level or database level.
Apart from above, there are other events related to Database/Server, user logon, server error causes to fire the trigger

Database Startup, Shutdown , Suspend
Logon, Logoff the session
Server Error

The possible usages of the different types of triggers.

DML trigger

It could be used in the following requirements::

  • For maintaining data integrity by cascading the changes to the related object, it could be maintaining some constrain. In this purpose single SQL or set of SQL could be used as a Program Unit.
  • For maintaining referential integrity  constraint, it is always good to use foreign key between parent and child table. [ Cascade deletion, nullifying foreign key’s data for the deletion of parent row. ]
  • For he case of data integrity, always good to use default constrains / check constraint, rules by using user defined data type.
    For the case of maintaining change history, I will prefer to have the trigger. The OLD/DELETED and NEW/INSERTED value could reference in a easy way using trigger to store change history.
  • For the case of populate summarized data, better to use stored procedure and call it explicitly.
  • For notification purpose by sending messages/alerts using email or other way.
  • Instead of trigger I will suggest to use notification service by developing triggering component. The business logic will be written in these component.

There some points to be keep into mind, where a group of people are responsible/involved to write/maintain the application.

Need to be well documented for each and every triggers; also it’s impacts to the related data, otherwise it will be difficult to know what are the data getting affected as a series of modification. It is always recommended not to use trigger for DML purposed mentioned above.
For the case of nested trigger / recursive trigger, it will very difficult to do the debugging the application. Therefore, I will be recommending to avoid using trigger for data manipulations. 
If we would like to keep change history in very limited and important table, trigger is a good choice.
DDL trigger

For audit purpose by logging into event log, or some files, or into any table DDL trigger. When any objects are creating, modifying, dropping all could be logged which could be auditable.

For auditing purpose logon, database startup/shutdown, server error trigger not a bad good choice. Maintaining these type logging are DBA related job. Generally in an organization there are very very limited number of DBAs are working; where good co-ordination is possible and risk factor is very less.

There are few restriction of trigger. For SELECT statement trigger is not applicable. Trigger fired implicitly not explicitly.

under: Uncategorized

Includes a comprehensive set of technical content including samples, demos, hands-on labs, and presentations for

  • Windows Azure
    Operating system as a service
  • Microsoft SQL Azure
    Fully relational database in the cloud
  • Windows Azure platform AppFabric
    Easy to connect cloud and on-premises applications

The links are…





Follow for the latest update http://twitter.com/azurecloudnet

under: 12606, 12607


  • Name  and Namespace – The name and namespace are the optional attibutes. Default name is same as the contract type and namespace is http://tempuri.org. It is always recommondable to use Namespace to specify proper namespace which remove the conflict of the datatype/contract.
  • CallbackContract – Return contract in a two-way (duplex) conversation.
  • HasProtectionLevel and ProtectionLevel – Specifies whether all messages supporting the contract have a explicit ProtectionLevel value.
    Default ProtectionLevel is ProtectionLevel.None.
  • ConfigurationName – The name of the service element in the configuration file to use.
  • SessionMode – This is to specify whether the contract requires a binding that supports sessions.


  • Name: The name of an operation is part of a service contract. Default is the method name.
  • Action: The send message dispatches to the method for the operation based on action.
  • ReplyAction: To specify the reply message
  • IsOneWay: Specifies whether the operation is one directional that an does not return a reply message. This is commonly used for notification service.
  • ProtectionLevel
  • IsInitiating: Specifies if the operation is the intial operation in a session. 
  • IsTerminating: Specifies if the session will be terminated after the operation
  • AsyncPattern: To asynchronously using a Begin/End method pair
under: 11143, 9534, 9536

Older Posts »