In this blog post, we will go through step by step how to actualize DotNetNuke on Windows Azure Website from Gallery. For those who are not familiar with  DotNetNuke, we start by introducing what it is.

DotNetNuke is a web content management system based on Microsoft .NET. The Community Edition is open source, and source code and related information can be found on Codeplex.  The product is used to build professional looking and easy-to-use commercial websites, social intranets, community portals, or partner extranets.

In addition to robust content management, the free, open source DotNetNuke Community Edition includes the following built-in features:

  • A rich-text editor
  • File management
  • Cloud-ready with MS Azure compatibility
  • Mobile API and basic mobile device detection
  • Core written in C#
  • Single installation, multiple portals
  • Social API (in DNN 6.2 and above)
  • Modern client-side Web tools like CSS 3, HTML 5 and JQuery
  • Bulk email
  • Robust security
  • Administration features like: security roles, protected content and site log.

Windows Azure website from gallery makes available a wide range of popular web applications developed by Microsoft, third party companies, and open source software initiatives. Web applications created from the gallery do not require installation of any software other than the browser used to connect to the Windows Azure Management Portal.

So after a brief about DotNetnuke and Azure Websites, we are ready to go through step-by-step journey to set-up DotNetNuke on Azure.

NOTE:  For following steps you need a Windows Azure account that has the Windows Azure Web Sites feature enabled.  If you don’t have one, you can create trial for free at  following link:  Create a Windows Azure account and enable preview features.

1. Login to the Windows Azure Management Portal.

2. Click the New icon on the bottom left of the dashboard.


3. Click the Compute Icon, then click Web Site icon, and click From Gallery.

From Gallery

4. Locate and click the DotNetNuke Community Edition  icon in list, and then click  Next.


5. On the  Configure Your App  page, enter or select values for all fields:


    • Enter a URL name of your choice
    •  Leave Create a new SQL database selected in the Database field
    • Select the region closest to you.

6. Then click Next.

7.  On the ADD WEB APP page, you can specify a name for your new SQL database or use the default name. Select the region closest to you as the hosting location.  Then enter Server Login Name and Server Login Password.  Then click the check to complete the site creation.


NOTE: Please note down the Server login name and password, as this will be later required in setting up DotnetNuke installation.

8. Windows Azure will take a little time to deploy DotNetNuke Community Edition CMS to your site.


9. After successful setup, a new website with given name can be seen in Running status.


10. We are done at the part to be done at Windows Azure Management Portal, now open the deployed site by clicking website link.

11.  At the first time open of site will require some data from you.


    • Fill up Administrative Information

a) Fill up Username and enter Password.

Note:  Note down this username and password as it will be your admin username and password.

    • Enter Website Information

a)  Fill up website name and change language, if necessary.

    • Enter Database Information


a) Select Database Setup type Custom

b) Select Database Type as SQL Server/SQL Server Express Database

c) Enter Server Name and Datbase Name (You can check your server name at Windows Azure Management Portal)


d) Select  Security type User Defined.

e) Enter Database Username (this is also can be found at Windows Azure Management Portal).

f) Enter Database Password (that we saved in step 7).

    • Finally click on continue.

12. Installation will take for a while for verifying database connection.


13. Page is then redirected to installation page, which will take a little time to install.


14. After installation is complete, message is shown as Installation complete, Click Visit Website.


15. DotNetNuke is installed on Windows Azure with SQL azure database and is ready to use.


You can now enjoy the benefits of Azure Cloud Scalability and pay as you use model. You can monitor the traffic on website & database on Azure Dashboard.


In once a while, each developer goes through the term design pattern, analyze these patterns & eventually use in various code.  So question first arises in mind is what’s the design pattern,  what did they do and how did they do. We start with answering first question here.

Definition :

Design Pattern is is a general reusable solution to a commonly occurring problem within a given context.

What exactly this means ??? Lets understand.

What did we do when we get a problem to solve which is new to us?  Google it and check if somebody already solved our problem. Exactly like this case,  each design pattern is already available solution to solve some particular problems that we encounter while designing logic or writing code for our applications.

Now let’s explore various types of Design Patterns. Design patterns are mainly categorized into three types:

1. Creational Patterns : Creational patterns are used to construct objects such that they can be decoupled from their implementing system.

Example of creational patterns are :

  • Abstract Factory: Create instances of classes belonging to different families.
  • Builder : Separate representation and object construction.
  • Factory:  Create instances of derived classes.
  • Prototype : Clone or copy initialized instances.
  • Singleton: Class with only one single possible instance.

2. Structural Patterns : Structural Patterns are used to form large object structures between many disparate objects.

Example of structural patterns are :

  • Adapter: Match interfaces of classes with different interfaces.
  • Bridge: Separate implementation and object interfaces.
  • Composite: Simple and composite objects tree.
  • Decorator: Dynamically add responsibilities to objects.
  • Facade: Class that represents subclasses and subsystems.
  • Flyweight: Minimize memory usage by sharing as much data as possible with similar objects.
  • Proxy: Object that represents another object.

3. Behavioral Patterns:  Behavioral Patterns are used to manage algorithms, relationships, and responsibilities between objects.

Example of behavioral patterns are:

  • Chain of Responsibility: Pass requests between command and processing objects within a chain of objects.
  • Command: Encapsulate a method call as an object containing all necessary information.
  • Interpreter: Include language elements and evaluate sentences in a given language.
  • Iterator: Give sequential access to elements in a collection.
  • Mediator: Encapsulates and simplifies communication between objects.
  • Memento:  Undo modifications and restore an object to its initial state.
  • Observer: Notify dependent objects of state changes.
  • State: Change object behavior depending on its state.
  • Strategy: Encapsulate algorithms within a class and make them interchangeable.
  • Template: Define an algorithm skeleton and delegate algorithm steps to subclasses so that they may be overridden.
  • Visitor: Add new operations to classes without modifying them.

In design pattern we often listen the term Gang of Four, GOF, or GO4. Gang of four is nothing to do with technical sense, it’s name of four authors(Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides) of book Design Patterns: Elements of Reusable Object-Oriented Software.

In next posts, I will pick each one of original 23 GOF design patterns, discuss pros, cons & need, UML diagrams for patterns and simple code illustration in C#.

When the project in which I was working was going through performance analysis, we found our project has a lot of warning generated by code analysis and also code coverage is not up to mark. We analyze warning & methods that was not under test coverage. What we found was that we were mostly following best practices but still code analysis left us with a lot of warnings. Same goes with code-coverage, all new methods were having proper test cases for all scenarios. What’s wrong was happening???

Actual problem was :

1. Some code components (commonly used components and third-party code) developed earlier was considered tested and free from warnings, but that wasn’t the case.

2. Also we can’t change that code for warnings & test coverage (because nor time-constraint allows that neither we want to do so for ample many other reasons like copyright with change etc.)

So what can be solution.

Solution was nevertheless easier then we thought. Microsoft has provision for disabling code-analysis warnings & excluding code-coverage for such a scenarios only in System.Diagnostics.CodeAnalysis namespace.

NOTE: Although it’s not recommended to disable code-analysis warnings and also disabling code-coverage. Doing this can project wrong code-analysis data, but our scenario was just perfect for what Microsoft has provisioned disabling.

The System.Diagnostics.CodeAnalysis namespace contains classes for interaction with code analysis tools :

1. ExcludeFromCodeCoverageAttribute: Specifies that the attributed code should be excluded from code coverage information.

Actual working example

 public static OperationControl GetInstance()
   //Your code goes here

In above code, ExcludeFromCodeCoverage attribute will prevent the method from being covered in test coverage & thus increases code coverage percentage. Please note only third-party tested code, test methods and such cases are recommended for using the attribute & it must not be applied to all/most of methods that will defeat purpose of code-coverage check.

2. SuppressMessageAttribute: Suppresses reporting of a specific static analysis tool rule violation, allowing multiple suppressions on a single code artifact.

The SuppressMessage attribute has the following format:

[Scope:SuppressMessage("Rule Category", "Rule Id", Justification = "Justification", MessageId = "MessageId", Scope = "Scope", Target = "Target")]


  • Rule Category – The category in which the rule is defined. More information on categories can be found on msdn.
  • Rule Id – The identifier of the rule. Support includes both a short and long name for the rule identifier. The short name is CAXXXX; the long name is CAXXXX:FriendlyTypeName.
  • Justification – The text that is used to document the reason for suppressing the message.
  • Message Id – Unique identifier of a problem for each message.
  • Scope – The target on which the warning is being suppressed. If the target is not specified, it is set to the target of the attribute. Supported scopes include the following:
    • Module
    • Namespace
    • Resource
    • Type
    • Member
  • Target – An identifier that is used to specify the target on which the warning is being suppressed. It must contain a fully-qualified item name.

Actual working example

 public static OperationControl GetInstance()
   //Your code goes here

In above code SuppressMessage attribute will prevent Microsoft.Design warning”CA1024″.

For more detailed information you can refer following links on msdn:

In day to day work we often need data to displayed in Grid that needs sorting, paging and filtering on User Interface whether web or windows. I often struggle to find a unified solution. I found that best way is to have fetch data  in required  format from stored procedure and just have presentation logic on UI  rather than mixing a lot of logic for Sorting, Paging and Filtering.  Here I am presenting a simple approach to have data from Stored procedure in required format based on given parameters.

        /* Optional Filters for Dynamic Search*/
       @ContactID INT = NULL,
       @FirstName NVARCHAR(50) = NULL,
       @LastName NVARCHAR(50) = NULL,
       @EmailAddress NVARCHAR(50) = NULL,
       @EmailPromotion INT = NULL,
       @Phone NVARCHAR(25) = NULL,
       /*– Pagination Parameters */
       @PageNo INT = 1,
       @PageSize INT = 10,
      /*– Sorting Parameters */
     @SortColumn NVARCHAR(20) = ‘Title’,
    @SortOrder NVARCHAR(4)=‘ASC’
         /*–Declaring Local Variables corresponding to parameters for modification */
        @lContactID INT,
        @lFirstName NVARCHAR(50),
        @lLastName NVARCHAR(50),
        @lEmailAddress NVARCHAR(50),
        @lEmailPromotion INT,
        @lPhone NVARCHAR(25),
         @lPageNbr INT,
         @lPageSize INT,
         @lSortCol NVARCHAR(20),
         @lFirstRec INT,
         @lLastRec INT,
         @lTotalRows INT
        /*Setting Local Variables*/
        SET @lContactID = @ContactID
        SET @lFirstName = LTRIM(RTRIM(@FirstName))
        SET @lLastName = LTRIM(RTRIM(@LastName))
        SET @lEmailAddress = LTRIM(RTRIM(@EmailAddress))
        SET @lEmailPromotion = @EmailPromotion
        SET @lPhone = LTRIM(RTRIM(@Phone))
        SET @lPageNbr = @PageNo
        SET @lPageSize = @PageSize
        SET @lSortCol = LTRIM(RTRIM(@SortColumn))
         SET @lFirstRec = ( @lPageNbr – 1 ) * @lPageSize
         SET @lLastRec = ( @lPageNbr * @lPageSize + 1 )
         SET @lTotalRows = @lFirstRec – @lLastRec + 1
         ; WITH CTE_Results
         AS (
                   CASE WHEN (@lSortCol = ‘ContactID’ AND @SortOrder=‘ASC’)
                            THEN ContactID
                  END ASC,
                  CASE WHEN (@lSortCol = ‘ContactID’ AND @SortOrder=‘DESC’)
                           THEN ContactID
                  END DESC,
                 CASE WHEN (@lSortCol = ‘Title’ AND @SortOrder=‘ASC’)
                          THEN Title
                 END ASC,
                 CASE WHEN @lSortCol = ‘Title’ AND @SortOrder=‘DESC’
                         THEN Title
                 END DESC,
                CASE WHEN @lSortCol = ‘FirstName’ AND @SortOrder=‘ASC’
                        THEN FirstName
                END ASC,
                CASE WHEN @lSortCol = ‘FirstName’ AND @SortOrder=‘DESC’
                        THEN FirstName
                END DESC,
                CASE WHEN @lSortCol = ‘MiddleName’ AND @SortOrder=‘ASC’
                        THEN MiddleName
                END ASC,
                CASE WHEN @lSortCol = ‘MiddleName’ AND @SortOrder=‘DESC’
                       THEN MiddleName
                END DESC,
                CASE WHEN @lSortCol = ‘LastName’ AND @SortOrder=‘ASC’
                      THEN LastName
                END ASC,
                CASE WHEN @lSortCol = ‘LastName’ AND @SortOrder=‘DESC’
                      THEN LastName
                END DESC,
               CASE WHEN @lSortCol = ‘Suffix’ AND @SortOrder=‘ASC’
                     THEN Suffix
               END ASC,
               CASE WHEN @lSortCol = ‘Suffix’ AND @SortOrder=‘DESC’
                     THEN Suffix
               END DESC,
                CASE WHEN @lSortCol = ‘EmailAddress’ AND @SortOrder=‘ASC’
                      THEN EmailAddress
                END ASC,
                CASE WHEN @lSortCol = ‘EmailAddress’ AND @SortOrder=‘DESC’
                      THEN EmailAddress
                END DESC,
                 CASE WHEN @lSortCol = ‘EmailPromotion’ AND @SortOrder=‘ASC’
                      THEN EmailPromotion
                END ASC,
                CASE WHEN @lSortCol = ‘EmailPromotion‘ AND @SortOrder=‘DESC’
                     THEN EmailPromotion
                END DESC,
                 CASE WHEN @lSortCol = ‘Phone’ AND @SortOrder=’ASC’
                    THEN Phone
                 END ASC,
                 CASE WHEN @lSortCol = ‘Phone’ AND @SortOrder=’DESC’
                     THEN Phone
                 END DESC
       ) AS ROWNUM,
       Count(*) over () AS TotalCount,
   FROM Contact
         (@lContactID IS NULL OR ContactID = @lContactID)
         AND(@lFirstName IS NULL OR FirstName LIKE ‘%’ + @lFirstName + ‘%’)
         AND(@lLastName IS NULL OR LastName LIKE ‘%’ + @lLastName + ‘%’)
        AND (@lEmailAddress IS NULL OR EmailAddress LIKE ‘%’ + @lEmailAddress + ‘%’)
        AND (@lEmailPromotion IS NULL OR EmailPromotion = @lEmailPromotion)
        AND (@lPhone IS NULL OR Phone  LIKE ‘%’ +@lPhone+ ‘%’)
         ROWNUM > @lFirstRec
               AND ROWNUM < @lLastRec


SP can be used to filter data as per given parameters as:

No parameters provided, fetch first 10 default records with title in ascending Order :

 On providing @SortCol = ‘FirstName’ and @SortOrder=’Asc’, will fetch 10 records sorted by First Name in ascending order:
EXEC USP_SEL_Contacts @SortColumn = ‘FirstName’, @SortOrder=‘Asc’

 On providing @SortCol = ‘LastName’, will fetch 10 records sorted by Last Name in descending order:
EXEC USP_SEL_Contacts @SortColumn = ‘FirstName’, @SortOrder=‘Desc’

 Following query will pull out 20 records in a page having Email Address ‘’ sorted by Last Name in Descending order:
EXEC USP_SEL_Contacts @EmailAddress = ‘’, @PageSize = 20, @PageNo=1, @SortColumn = ‘LastName’ , @SortOrder=‘Desc’

NOTE: Please note that while publishing blog single quotes ‘ & minus sign – are converted to some unrecognizable characters, if you have error like

Msg 102, Level 15, State 1, Procedure USP_SEL_Contacts, Line 14
Incorrect syntax near ‘‘’.
Msg 137, Level 15, State 2, Procedure USP_SEL_Contacts, Line 42
Must declare the scalar variable “@SortColumn”.
Msg 102, Level 15, State 1, Procedure USP_SEL_Contacts, Line 43
Incorrect syntax near ‘–’.
Msg 102, Level 15, State 1, Procedure USP_SEL_Contacts, Line 45
Incorrect syntax near ‘–’.
Msg 102, Level 15, State 1, Procedure USP_SEL_Contacts, Line 49
Incorrect syntax near ‘‘’.

please replace those characters by single quotes & minus sign respectively.

All of us have daily routine to create back up of databases on daily or weekly basis. I am here presenting a simple script that can create backup all databases except the system databases. Backup files will be saved in the format NameOfDatabase_YYYYMMDDHHMMSS.bak, where name of database will be appended with date at which back up is created in format NameOfDatabase_YYYYMMDDHHMMSS where YYYY is Year, MM is month in numeric, DD Date, HHMMSS is hours, minutes & seconds.

– 1. Backup all databases except the system databases.
– 2. Backup files will be saved in the format NameOfDatabase_YYYYMMDDHHMMSS.bak.

– Name of database
DECLARE @DatabaseName VARCHAR(50)
– Path of backup folder.
DECLARE @BackupPath VARCHAR(256)
– Name of Backup file
DECLARE @BackUpFileName VARCHAR(256)
– Get current date used for suffixing with file name.

– Specify path for database backup directory. Make sure directory exists before executing script, else script will give error.
SET @BackupPath = ‘C:\Backup\’

– Get current date used for suffixing with file name.

–Declaring cursor for storing Database Names
FROM master.dbo.sysdatabases
– Excluding system databases
WHERE name NOT IN (‘master’,‘model’,‘msdb’,‘tempdb’)
–For Specific Database, replace TestDB with required database name in below line & uncomment it
–AND name IN (‘TestDB’)

–Fetching database names from cursor to local variable
OPEN db_cursor
FETCH NEXT FROM db_cursor INTO @DatabaseName

–Loop for all databases
          –Setting file name in format NameOfDatabase_YYYYMMDDHHMMSS
          SET @BackUpFileName = @BackupPath + @DatabaseName + ‘_’ + @Date + ‘.bak’
         –Creating back up
         BACKUP DATABASE @DatabaseName TO DISK = @BackUpFileName

        –Fetching Next Database Name
         FETCH NEXT FROM db_cursor INTO @DatabaseName

–Close & deallocate cursor
CLOSE db_cursor
DEALLOCATE db_cursor

While analyzing performance of application, many a times we find that indexes are broken, not rebuild from a long time and that is hampering performance. We need to quickly re-index all the tables in a SQL server. This is a script for rebuilding all indexes in given database.
DECLARE @TableName varchar(255)
                 SELECT table_name
                          FROM information_schema.tables
                                  WHERE table_type = ‘base table’
              OPEN TableCursor
              FETCH NEXT FROM TableCursor
              INTO @TableName
              WHILE @@FETCH_STATUS = 0
                     DBCC DBREINDEX(@TableName,,90)
                     FETCH NEXT FROM TableCursor
                     INTO @TableName
            CLOSE TableCursor
Please note that  DBREINDEX is not supported for use on the following objects:
  • System tables
  • Spatial indexes
  • xVelocity memory optimized columnstore indexes