Sealed Vs Private Class

Sealed Class:
Sealed keyword is used to avoid the inheritance of that class. it cannot be inherited.
In inherited hierarchy Sealed class is the leaf node.
Even a public class is declared as Sealed it will be ban to inherit.
No instance of a Sealed class is possible because we cannot create constructor of it.

Private Class:
Private keyword is used to limit the scope. if we declare a class private within a class means it will not be visible out of base class.
Private classes cannot be used directly as this will throw compilation error.
We have must nest a private class within another public class.
We can create constructor for a private class so instance of private class is possible.
Private class is only visible to that class it is defined and within it.
Private class can be inherited but a private class cannot be inherited from a public class. because a child class can not be more accessible than base class. Either parent should be more accessible or equal.
Comments and Suggestions are always Welcome!

Ado.Net Components, DataSet or DataReader

ADO.Net:
There are two main components of ado.net which are .Net framework Data provider and DataSet.

1. .Net frameword Data provider are very lightweight, used to connect with database, run the command/query by using Command object and get the results. then it depends upon us how to treat that Result set either we directly process the data or we place in DataSet as per requirements. there are different types of Data Providers in .Net Framework like:
a. .NET Framework Data Provider for SQL Server
it gives data access for Microsoft SQL Server. Uses namespace System.Data.SqlClient.
b. .NET Framework Data Provider for OLE DB
Used for data sources discovered by using OLE DB. Uses namespace System.Data.OleDb.
c. .NET Framework Data Provider for ODBC
It is used for data sources discovered by using ODBC. Uses namespace System.Data.Odbc.
d. .NET Framework Data Provider for Oracle
It provides supports for Oracle data sources. namespace System.Data.OracleClient
e. EntityClient Provider
give data access to Entity Data Model (EDM) applications. System.Data.EntityClient
f. .NET Framework Data Provider for SQL Server Compact 4.0.
It is for Microsoft SQL Server Compact 4.0. using System.Data.SqlServerCe.

Mainly .Net Framework Data Providers uses few core Objects which are give below:
a. Connection: Used to establish connection. its base class is DbConnection
b. Command: used to execute a database command. this object base class is DbCommand
c. DataReader: it reads a forward-only(DataReader reads one row at a time then move forward to next row then next, it will not move back thats why it's called Forward only), read-only(it will just read records from data source does not allow any editing). base class for DataReader objects is DbDataReader class.
d. DataAdapter: it is used to populates the DataSet. basically it provides communication between data source and DataSet to enable data access and manipulation of data.

There are some additional Objects also names as Transaction, CommandBuilder, ConnectionStringBuilder, Parameter, Exception, Error and ClientPermission.

2. The DataSet: it is second component of ado.net. it is mainly designed to data access from any data source or we can say independent of data source, it can be used with different data source like XML data or to manage data local. DataSet can have one or more than one DataTable objects which have rows, columns even primary and foreign keys contraints. we can perform within application qurieson DataSet to manipulate the data.

Choose DataReader or DataSet: when you think you want only to read data and there is no requirements to perform editing then DataReader is preferable and fast also but when you require data to cache it locally in application and do some manipulation and perform some other operations then DataSet is best.

SqlDataSource and ObjectDataSource Differences

why we should use SqlDataSource and why ObjectDataSource.
why we do not directly use SqlDatasource and prefer ObjectDataSource even SqlDatasource is less code and fast also.

> Basically ObjectDatasource is business object that calls the stored procedure to get records from database whereas we can do directly this one by using Sqldatasource in very less code.

> Objectdatasource provide a perfect abstraction of our design and code.

> While using objectdatasource our pages does not depend upon the database information used in code behind.

> SqlDataSource is typically two-tier in nature but ObjectDataSource is based on three-tier architecture.

> SqlDataSource requires very less line of code to connect with database and ObjectDataSource needs more coding to build data access classes to communicate with database.

> SqlDataSource does not support data encapsulation whereas ObjectDataSource is fully designed for encapsulation.

> For SqlDataSource we write complete connection string for database connection. ObjectDataSource exposes TypeName attribute as a middle layer class mainly used to perform database operations.

> Sqldatasource uses ADO.NET mainly. we have to write all database queries, connections and commands on the page which looks very raw data.

> Objectdatasource behave like a wrapper which control all crud operations.

> Normally if we have to do same thing for a short time span and for a limited time perioed then it's okay to use SqlDatasource but when we talk about a big application and for long run we prefer to use Objectdatasource because direcltly use sqldatasource in your code behind is very quick but dirty habbit which is not preferable always.

> When we face frequent changes in our system then we have to go for page by page and change all sections of code which are directly accessing that change. so by using objectdatasource it is very professional and pretty to have such changes in practice.

Reference: https://forums.asp.net/t/1876836.aspx?When+do+I+use+SqlDataSource+vs+EntityDataSource+vs+ObjectDataSource

Disadvantage of Session or Requests stuck in IIS due to RequestAcquireState

Some of the clients were complaining about website speed so Last month I was monitoring web server and found out that there is a request queue and server is not efficiently handling the entire request rather stuck on the event called RequestAcquireState due to which a queue is built on server. After searching I’ve come to the conclusion that it was happening due to session used in the website and there are pages where we are using sessions. So whenever user request the page where session is used it locks down other requests from entering into that page which causes slowness in web application and our clients were complaining about speed.

I’ve read about session in details and came to know about concurrency issue of sessions. If you send two requests at the same time, ASP won't even start on the second request until the first one is finished. This can cause unexpected and poor performance on applications that use a lot of AJAX or other logic that is supposed to be asynchronous.

So finally I’ve removed session from website pages and rather use query string and other techniques to send data from one page to another which solves my problem.

Hope this tutorial will be helpful for you.

Difference between SingleOrDefault and FirstOrDefault in C# Linq

In this tutorial we will see the difference between SingleOrDefault () and FirstOrDefault ().

SingleOrDefault():-
When you are exactly sure that there is only 1 result/record you should use SingleOrDefault(). If there is no result/record returned or there is more than 1 result/record this function will throw exception.
Example:-

string[] fruits = { "orange" };

string singleFruit = fruits.SingleOrDefault();

Console.WriteLine(singleFruit);

/*
 This code produces the following output:

 orange
*/

FirstOrDefault():- It will not throw any exception in case when there is no result/record returned from database rather it returns null when there is no result. It is slightly better in performance than SingleOrDefault()that is why it is recommended to use when you need single value from database.
Example:-

int[] integers = { };
int first = integers.FirstOrDefault();
Console.WriteLine(first);

/*
 This code produces the following output:

 0
*/

Tracing in asp .net Application for Beginners

Today we will learn how to use Tracing in Asp.Net to check the performance of Web Application.
In Web Development the most concerned part is Performance. so how we can check which part of our application is slower either its Asp.Net code or our Database queries. you can check your SQL queries performance by using SQL Profiler, look the execution plan which part of query is taking more time than normal and then you can easily find alternative or some good way to resolve query slowness.
But if query is performing fast in database then it means there is something in our application which is making causing slowness. In production environment its not easy to check which line of code is making problem so by using Tracing we can easily check where is the problem actually. We can turn on Tracing by setting page directive Trace="true". once its set on page then we can check at the end of page or in trace.axd file. from trace log in the file we can easily check which piece of code is making problem.
Let's have look on code:
First in page directive you need to set:

<%@ Page Language="C#" AutoEventWireup="true" Trace="true" CodeFile="WebPage.aspx.cs" Inherits="WebPage" %>

Now we will create three Gridviews to check each gridview data load performance on Page load.

<div>
            <b>All Orders</b>
            <asp:GridView ID="GridView1" autogeneratecolumns="True" runat="server"></asp:GridView>    
            <br />
            <b>Delivered Order</b>
            <asp:GridView ID="GridView2" autogeneratecolumns="True" runat="server"></asp:GridView>    
            <br />
            <b>Cancelled Order</b>
            <asp:GridView ID="GridView3" autogeneratecolumns="True" runat="server"></asp:GridView>    
        </div>

And In code behind we will call our Stored Procedure on Page load, here i am not going to write full code for calling stored procedures, we will just understand how Tracing will work:

protected void Page_Load(object sender, EventArgs e)
    {
        Trace.Warn("GetAllOrders() Stored procedure started");
        GetAllOrder();
        Trace.Warn("GetAllOrders() Stored procedure End");

        Trace.Warn("GetDeliveredOrder() Stored procedure started");
        GetDeliveredOrder();
        Trace.Warn("GetDeliveredOrder() Stored procedure End");

        Trace.Warn("GetCancelledOrder() Stored procedure started");
        GetCancelledOrder();
        Trace.Warn("GetCancelledOrder() Stored procedure End");

    }

Above we discussed it was page level Tracing, We can also set Tracing on application level by using below web.config code. it save trace data for up to 40 requests.

<configuration>
  <system.web>
    <trace enabled="true" requestLimit="40" localOnly="false" />
  </system.web>
</configuration>

Comments and Suggestions are always Welcome!

Retrieving Selected Item Text, Value and Index of Dropdown

Today we will check in Asp.Net, how to get a value from dropdown, its item text and index also. so i think without discussing more on theory let's go to code and create a dropdown with some sample data.

<asp:DropDownList ID="ddlSampleData" runat="server">
    <asp:ListItem Text="Select Name" Value="-1"></asp:ListItem>
    <asp:ListItem Text="Pakistan" Value="1"></asp:ListItem>
    <asp:ListItem Text="England" Value="2"></asp:ListItem>
    <asp:ListItem Text="Ireland" Value="3"></asp:ListItem>
</asp:DropDownList>

<asp:Button ID="btnGetValddl" runat="server" Text="Button" onclick="btnGetValddl_Click" /> 

You can create a dropdown by using Asp.net toolbox, just drag and drop the dropdown control after that add some listitem to dropdown from proprty or by code. We created a asp button also to perform the operations.
On this button click event we will get the value, text and index of selected item with a very simple way and then we will write this to our page by using HttpResponse's Write method. here is the code for that button click event.

protected void btnGetValddl_Click(object sender, EventArgs e)
    {
        if (ddlSampleData.SelectedValue != "-1")
        {
            Response.Write("Selected Item's Text = " + ddlSampleData.SelectedItem.Text + "<br/>");
            Response.Write("Selected Item's Value = " + ddlSampleData.SelectedItem.Value + "<br/>");
            Response.Write("Selected Item's Index = " + ddlSampleData.SelectedIndex.ToString());
        }
        else
        {
            Response.Write("Select Countrt First!");
        }
    }

As on the first item of dropdown we set the value as -1, this value will tell us either a country is selected from the dropdown or not and if no country is selected then we will show message "select country first".
To get the select item Text we used:

ddlSampleData.SelectedItem.Text

To get the Select Item's Value we can:

ddlSampleData.SelectedItem.Value

or
ddlSampleData.SelectedValue
To get the index of Select Item's, we can do:

ddlSampleData.SelectedIndex

we can perform many other operation like if we want to set a value by default it should be select like if we want in our dropdown pakistan should come selected by default then we can set on page load event like:

 ddlSampleData.SelectedValue = "1";

or we can achieve this by using selectedIndex:

 ddlSampleData.SelectedIndex = 1;

if we want to bind our dropwdown directly data from data then we can do something like below, for example we have to bind a city dropdown:

<asp:DropDownList ID="slctCity" runat="server"></asp:DropDownList>

we are going to create a function so we can call this from different pages:

public void ddlbind(DropDownList ddl, string query, string text, string val)
    {
        DataSet ds = new DataSet();
        da = new SqlDataAdapter(query, con);
        da.Fill(ds);
        ddl.DataSource = ds.Tables[0];
        ddl.DataTextField = text;
        ddl.DataValueField = val;
        ddl.DataBind();
    }

in this you need to set con with your SQL Connection and after that pass just query and dropdown id.
we will call like this:

ddlbind(slctCity, "select ct_name,ct_charges from tbl_city", "ct_name", "ct_charges"); 

Comments and Suggestions are Always Welcome!

Web Application Life Cycle Event ASP.NET

Events in the life cycle of a web application:
Today we will discuss the events in the life cycle of a web application. As the name shows Application events are used across the application. these events are used to initialize some data which will be available to all current user of application. As we know Session are also used to initialize the data but that data will be available for individual session not for whole application. First let's have a look on Web application events available in Global.asax file:

void Application_Start(object sender, EventArgs e)
{
    //This Code will run on application start
}
void Application_End(object sender, EventArgs e)
{
    //This Code will run on application shutdown
}
void Application_Error(object sender, EventArgs e)
{
    //This Code will run when some unhandled error occured
}
void Session_Start(object sender, EventArgs e)
{
        //This Code will run when a new session starts
}
void Session_End(object sender, EventArgs e)
{
    //This Code will run on when a session ends
} 

1. Application_Start: This event runs when an application starts running first time if it was not running before. mostly this even is used to initialize data that needs to be available across all the application. we can set an application state variable to keep records that when an application starts and we can also count of application start event fired.

void Application_Start(object sender, EventArgs e)
{
    // Create Application state variables
    Application["AppStartDateTime"] = DateTime.Now;
}

This will available across the application if required on some pages.

2. Application_End: This event will be fired when application shutdown. we can use this event to keep records and also, we can generate some alert so we could be aware of application is running or shutdown. this event will be fired when IIS is restarted basically it is a once per application event.

void Application_End(object sender, EventArgs e) 
{
    //Code
}

3. Application_Error: This event is mostly used than above mentioned events because when ever and error occurred then this event will be fired and we can set redirect according to error status code so our used should be face some terrible error page and we present some user-friendly message to use and mention the reason why user come to this page.

void Application_Error(object sender, EventArgs e) 
    { 
        // Code runs when an unhandled error occurs
    Exception ex = Server.GetLastError();
    if (ex is HttpException && ((HttpException)ex).GetHttpCode() == 404)
    {
        Response.Redirect("~/404.aspx");
        //Server.Transfer("~/Error.aspx");
    }
    else
    {
        // your global error handling here!
    }
}

4. Session_Start: This event will be fired every time when a new user/browser visits the application with different session id. by using this Event we can keep record how many user visits our application and we can check how many users currently on our application.

void Session_Start(object sender, EventArgs e)
{
    //Application["TotalUser"],Application["CurrentUser"] will be initialize in application_start
    // Increment TotalUserSessions by 1
    Application["TotalUser"] = (int)Application["TotalUser"] + 1;
    Application["CurrentUser"] = (int)Application["CurrentUser"] + 1;
}

5. Session_End: This event is fired when a single user's session ends or timed out.

void Session_End(object sender, EventArgs e) 
    {
        // Code that runs when a session ends.  
    Application["CurrentUser"] = (int)Application["CurrentUser"] - 1;   
    }

Note: Session End event is fired only when we have set session state mode to "InProc". In other state mode, it will not fire Session End event.

Comments and Suggestions are Always Welcome!

Highlight Duplicate Records in GridView

How to highlight Duplicate Records in GridView.
Hi, today I will share my experience with you which I face long time ago. problem was how to identify if there is any duplicate record. so, after spending too much time on search and finding solution I reached to a solution. below is given a function which finds the duplicate rows in a Gridview without much effort, just we need to pass our Gridview ID and it will find and highlight the duplicate rows. we can find duplicate row depending upon a cell value within a row or for multiple cells also.
Here is the function:

public void HighlightDuplicate(GridView gridview)
    {
        for(int currentRow = 0; currentRow < gridview.Rows.Count - 1; currentRow++)
        {
            GridViewRow rowToCompare = gridview.Rows[currentRow];
            for (int otherRow = currentRow + 1; otherRow < gridview.Rows.Count; otherRow++)
            {
                GridViewRow row = gridview.Rows[otherRow];
                bool duplicateRow = true;
                //check Duplicate on Name Coloumn
                if ((rowToCompare.Cells[2].Text) != (row.Cells[2].Text))
                {
                    duplicateRow = false;
                }
                else if (duplicateRow)
                {
                    rowToCompare.BackColor =System.Drawing.Color.Yellow;
                    row.BackColor = System.Drawing.Color.Yellow;
                }
            }
        }
    }

we will call this function after DataBind() is done to the Gridview.
Call function

HighlightDuplicate(GridView1);

In current function i am checking value of Cell[2] you can set as per your requirements.
This function can also be used for some other operations on the Gridview because you have full control on rows and cell of Gridview even you can find a specific value or control in the Gridview row and do whatever you want.
Comments and Suggestions are Always Welcome!

Difference in ExecuteNonQuery ExecuterReader ExecuteScalar

ExecuteNonQuery() Vs ExecuterReader() Vs ExecuteScalar()
Today we will check the difference between ExecuteNonQuery, ExecuterReader and ExecuteScalar and we will try to understand which one should be used for which type of Database operations:
1. ExecuteNonQuery():
ExecuteNonQuery is always recommended for such operation in which you are not required to return anything from the query. it's used for INSERT,UPDATE and DELETE operations or other Action Queries like Alter, Drop,Create. it's function is same either we use direct SQL Query or Stored Procedure. so becarefull and do not use with SELECT Statements because it will always return total count of affected rows by query or stored procedure. we can not do much with its return because it is only returning int and its assigned to integer variable only.
Example:

        ExecuteNonQuery("DELETE FROM MYTABLE");
    ExecuteNonQuery("UPDATE TABLE SET COLUMNAL = 'Code'");

If we use ExecuteNonQuery with a Select Statement then it will do nothing. it will execute the Query but it's row affected will be negative -1 you can throw any error also.

2. ExecuterReader():
ExecuteReader is used to Read the Data from SQL Statement and its recommended to use with SELECT Operations. ExecuteReader returns IDataReader object when fetch the records from Database and we can perform other operation on this object as per our requirements like we can bind GridView etc. we use .Read() method of SqlDataReader which read the data one by one. it will also work for Action Queries but best to use for SELECT non action queries. it will return a collection of all data on which we can perform operation row by row or column by column also.

       IDataReader dr = ExecuteReader("SELECT * FROM MYTABLE"); 
     while(dr.Read())
     {
             Response.Write("Name: " + dr["ColumnName"]);
    } 

3. ExecuteScalar():
ExecuteScalar is always used for a single column value. it will return first column of first row of Query. it is used when we are required one column or a single value like we want to get SUM of a column,Average of Column or Count and also it's usable when we want to know ID of employee from employees table against a single employee. it will be usefull for Non Action quries. it will return the an object type.

       Int32 Value = Convert.ToInt32(ExecuteScalar("SELECT SUM(SALARY) FROM EMPLOYEES")); 
 Int32 Value = Convert.ToInt32(ExecuteScalar("SELECT AVG(INCENTIVE) FROM EMPLOYEES")); 

it's always used for single value but if we used with multiple column statement then it's behavior will also remain same it will return first row first column value.
Comments and Suggestions are Always Welcome!

Difference Between Abstract Class and an Interface

What is Difference Between Abstract Class and an Interface:
Today we will discuss the differences between an Interface and Abstract Class. For the beginners, it’s a little bit difficult to understand the concept and difference between them. As we know in C# multiple inheritance is not allowed but we can achieve this by using Interface and this is the main difference between them, A class can implement more than one Interface but can inherit only one abstract class.
However, let’s have a look on some other features and differences.
1. Default Implementation: An interface does not have any type of code implementation it just provides the signature of methods and properties but An Abstract class can have code implementation, definition and may have details to be overridden.
2. Access Modifier: As we know interface provide signature and which is going to implement, this interface, that will define and provide the code implementation so in Interface there is no access modifier all properties and functions are by default public whereas an abstract class can have access modifier for subs, properties and functions.
3. Multiple Inheritance: Interface provide multiple inheritance in C# by inheriting multiple interfaces whereas a class may inherit only one abstract class.
4. Performance: Interfaces are slower than abstract class because an interface requires more time to check the signature and exact method in related classes.
5. Changes or Add New Functions: when we update or add new function to an interface then we have to trace all implementations of interface and need to update all references which is a tough task. In abstract class if we add some new function then we have default code implementation, due to this, all code will work properly no need to change.
Now let's see code implementation.
Abstract Class: abstract class cannot be instantiated so its methods can be called with class name or by using inherited class object.

abstract class ABS_CLS1
{
    public int Addition(int a, int b)
    {
        return (a + b);
    }
}
class Simple_CLS : ABS_CLS1
{
    public int Multiplication(int a, int b)
    {
        return a * b;
    }
}
class Check_Impl
{
    static void Main(string[] args)
    {
        Simple_CLS ob = new Simple_CLS();
        int Total = ob.Addition(5, 10);
        Console.WriteLine("Result is {0}", Total);
        Console.ReadLine();
    }
}

In the above example, we can see, we created the object of class Simple_CLS which inherited our abstract class, so, by using that object we call abstract class method so it clears one more thing abstract class provide the public method in it and also those members which inherited from abstract class's base class.
Interface: interface is not a class, it is by self an entity nominated with word Interface.

interface TestInterface
{
    void testMethod();
}
class CallClass : TestInterface
{
    public static void Main()
    {
        CallClass cls = new CallClass();
        cls.testMethod();
    }
    public void testMethod()
    {
        Console.WriteLine("Called Interface method from implemented class");
        Console.ReadLine();
    }
}

As interface, cannot have code implementation so only one method signature is in interface and calling class have code implementation of that method because its mandatory to calling class implement interface method and properties.
Comments and Suggestions are always welcome!

Differences between Class and Struct Asp Net

Today we will discuss the difference between class and struct in Asp.Net. As we already know that .Net is object oriented based so it has inside all concepts of OOP with their context.

If you have a little bit idea what is Reference Type and What is Value Type, then it’s very easy to understand the difference between classes and structs because this is the main and first difference in both.

Let's understand with a simple example Reference Type and Value Type:

Basically, structures are Value Type and classes are Reference Type, when we said reference type it shows from the name of this concept.

Reference Type is a reference to some location in the memory and if there is any change in a reference type or class object then it will be reflected on all instances of that object because it’s going to update the referred memory location not specific value on a single position. have a look on below example:

        Class Vehicle
    {
        Public Int NoOfTyres;     
    }

when we will use this class, and create an instance of this class then it will allocate the memory for this instance of this class type and will store the address of memory the class.

        Vehicle Vehicle_car1 =new Vehicle();
    Vehicle_obj1.NoOfTyres=4;
    Vehicle Vehicle_car2 =Vehicle_car1;
    Vehicle_car2.NoOfTyres=6;

In this example, we can check both instances of Vehicle class belong to same memory location because we assign Vehicle_car1 to Vehicle_car2 so they have same location. it also indicates that if there is any change in one it will update both because they both have same reference of memory.

As we update the value of second object Vehicle_car2.NoOfTyres=6; it will set both instances to 6. basically, we are getting NoOfTyres of an object by using different pointers.

But Structures are value type as we discuss earlier,

if we take same example,

        Structure Struct_Vehicle
    {
        Public Int NoOfTyres;     
    }
    
    Struct_Vehicle Str_Car1 =new Struct_Vehicle();
    Str_Car1.NoOfTyres=4;
    Struct_Vehicle Str_Car2 =Str_Car1;
    Str_Car2.NoOfTyres=6;

As per Value type when we create different instance and assign the first to second one then it will make copy of first and assign to second it will not refer to same location in memory. so, by updating the second it will not affect first's value and vice versa.

Value Type always contains a value and reference type can have null reference means it does not refer to anything.

Class also support the inheritance but struct does not.

Classes may have parameter less constructor but struct does not.

Structure cannot have destructors but a class can have a destructor.

Struct are in real an actual value and these can be empty but not null whereas class be referred to null.

Struct are best to use on small data of related groups.

Please share your suggestions and feel free to comments.

Non-WWW to WWW with HTTP to HTTPS

Today we will discuss how to redirect non www to www.domain.com with http to https both at time. few days back while moving a domain from http to https as now google chrome 56 is marking the website with http as non-secure and it’s also mentioned by google that it’s just a warning and near future it will be fully implemented so i suggest you people also to move your domain to https. there are many benefits of https we are not going to discuss here so let's come to the point.

we will discuss the web.config rule to resolve the problem. i implemented https perfectly and on my website all URL mentioned below are working fine:

http://domain.com
    https://domain.com
    http://www.domain.com
    https://www.domain.com

but the problem was that google consider every URL different and in SEO it is not a good practice. so I want something like below:

http://domain.com => https://www.domain.com
    https://domain.com => https://www.domain.com
    http://www.domain.com => https://www.domain.com
    https://www.domain.com => https://www.domain.com

so all URL should be resolved to same URL so it will not make problem in SEO and also good for alexa ranking. In Asp.Net we can do this by URL Redirecting rules in your web.config. for URL Redirecting more information please check here Let's have a look on code how it will be done by using web.config URL Redirect rewrite rules.

In web.config section you can put these rule like below:

<rewrite>
      <rules>
        <clear />
        <rule name="Redirect to https" stopProcessing="true">
          <match url=".*" />
          <conditions>
            <add input="{HTTPS}" pattern="off" ignoreCase="true" />
          </conditions>
          <action type="Redirect" url="https://{HTTP_HOST}{REQUEST_URI}" redirectType="Permanent" appendQueryString="false" />
        </rule>
    </rewrite>

First i make this rule and it was working perfect for redirecting http to https for all url on my domain.

http://domain.com => https://www.domain.com working ok
http://www.domain.com => https://www.domain.com working ok
https://www.domain.com => https://www.domain.com working ok

but there was a problem with https non www url.
https://domain.com => https://www.domain.com not working with above URL Redirect rule. after that i tries to change the

From: <action type="Redirect" url="https://{HTTP_HOST}{REQUEST_URI}" redirectType="Permanent" appendQueryString="false" />
    TO: <action type="Redirect" url="https://www.{HTTP_HOST}{REQUEST_URI}" redirectType="Permanent" appendQueryString="false" />

but there was no change so after searching and too much R&D i came back to my old url redirect rule which was before working fine from simple http to www http and i try that rule again. give below:

<rule name="Redirects to www" patternSyntax="ECMAScript" stopProcessing="true">
            <match url=".*" />
            <conditions logicalGrouping="MatchAny">
                <add input="{HTTP_HOST}" pattern="^domain.com$" />
            </conditions>
            <action type="Redirect" url="https://www.domain.com/{R:0}" />
        </rule>

so I came to a result that with a single rule it’s not possible to resolve both problems, from http to https and from non www to www.
Above mentioned both rules we have to put in same web.config file and it's working fine for both issues.
here is the full version of both rules:

<system.webServer>
    <rewrite>
      <rules>
        <clear />
        <rule name="Redirect to https" stopProcessing="true">
          <match url=".*" />
          <conditions>
            <add input="{HTTPS}" pattern="off" ignoreCase="true" />
          </conditions>
          <action type="Redirect" url="https://{HTTP_HOST}{REQUEST_URI}" redirectType="Permanent" appendQueryString="false" />
        </rule>
        <rule name="Redirects to www.domain.com" patternSyntax="ECMAScript" stopProcessing="true">
            <match url=".*" />
            <conditions logicalGrouping="MatchAny">
                <add input="{HTTP_HOST}" pattern="^domain.com$" />
            </conditions>
            <action type="Redirect" url="https://www.domain.com/{R:0}" />
        </rule></rules>
</rewrite>
</system.webServer>

Note: its not final, i am still working on this if you people can comment/suggest some good thing better than this so please share it will be appreciable.

Comments and Suggestion are always welcome!

Validation Controls in Asp Net

Today we will discuss Validation Controls in Asp.Net and we will have a deep look on Custom Validator control in Asp.net.

Validation is a most important process either it is a web based application, desktop application or some other like android or iPhone. without proper validation, it is very difficult for a system to survive because we don't know the nature of client/audience so as per our requirements we will must have to check the input from user and then process it.

Asp.Net provides very powerful controls for validation. In Asp.Net we have basically six validation control which can be used as per the requirements. we can validate the useless or contradictory data input from user. if something is going to harm the system we can validate and stop the user request with proper message or user friendly alert.

Asp.Net gives following validation controls:

• RequiredFieldValidator
• RangeValidator
• CompareValidator
• RegularExpressionValidator
• CustomValidator
• ValidationSummary

What is BaseValidator Class: All validation control performs some operation according to their nature and these control have their built-in classes, these control classes are inherited from a base class that's called BaseValidator class, which give some common properties and method to all validation controls. you can check in below image:

Now we will check validation control in details.

1. RequiredFieldValidator Control:

RequiredFieldValidator is generally used with input text field to check whether the input field is empty or have some text and it will validate that input text field should must have some text not empty.

Example/use of RequiredFieldValidator:

<asp:TextBox ID="txtUserName" runat="server"></asp:TextBox>
<asp:RequiredFieldValidator ID="rfvcUserName" runat="server" ControlToValidate ="txtUserName" ErrorMessage="Please enter Username"></asp:RequiredFieldValidator>

In above example, we can check how we will use RequiredFieldValidator with a Asp.Net TextBox.

2. RangeValidator Control:

On mostly website we have seen it asks for password should be minimum 6 and maximum 20 in length. if we enter less than 6 or greater than 20 it will never let us proceed further. RangeValidator control is used to check whether input from the user falls between this range or no.

RangeValidator has three specific properties:

Type: It check the type of input from the user. The available values are: Date, Double, Currency, Integer, and String.

MinimumValue specifies minimum value of the range.

MaximumValue specifies maximum value of the range.

Syntax/Example of RangeValidator control is as:

<asp:TextBox ID="txtPassword" runat="server" TextMode="Password"></asp:TextBox>
        <asp:RangeValidator ID="rvPasswords" runat="server" ControlToValidate="txtPassword" ErrorMessage="Enter your password between 6 - 12 (only number)" MaximumValue="12" MinimumValue="6" Type="Integer"></asp:RangeValidator>

In above example, we create a password textbox field and in RangeValidator we have set the properties like user can only enter length between 6 to 12 because MinimumValue will check that input should not be less than 6 and MaximumValue will verify input should not b greater than 12, we have set Type is Integer so user can only enter Integers otherwise RangeValidtor will not pass the validation.

3. CompareValidator Control:

When we are submitting a registration form to create a user profile then mostly it requires to set Password for your account, always there are two password fields with label Password and Confirm Password. whatever password we set for the account we have to match the Password and Confirm Password fields. how this confirm password verifies the user input is same that could be done in Asp.Net by using CompareValidator control. we can perform this operation by many other ways and also, we can use CompareValidator control for many other purposes but it was most general and used example for this control.

however, let's have a look on some specific properties of this control:

Type: specifies the data type.

ControlToCompare check the value of the input control to compare with.

ValueToCompare verifies constant value to compare with.

Operator it provides comparison operator, the available values are: GreaterThan, GreaterThanEqual, LessThan, Equal, NotEqual, LessThanEqual, and DataTypeCheck.

Syntax/Example of this control is:

<asp:TextBox id="TextBox1" runat="server"/><br />
        <asp:TextBox id="TextBox2" runat="server"/>
        <asp:CompareValidator id="Compare1" ControlToValidate="TextBox1" ControlToCompare="TextBox2" Type="String" Text="Value does not match" runat="server"/>

In above example, we have two Textboxes and we are comparing their values with each other. if user input is different in both textboxes then it will not pass validation and show the error message "Value does not match".

4. RegularExpressionValidator Control:
RegularExpressionValidator is used when we want our input to be verified with a specific pattern,it may be some phone number format,currency.etc,or we want our input should only contain alphabets not numbers.basically we use a regular expression to match the input which can be done by using RegularExpressionValidator control. we set a regular expression in this control and tell the validator control name of input field then it verifies that input field should validate the expression.
Let's have a look on simple example:

<asp:TextBox ID="txtName" runat="server"/>
    <asp:RegularExpressionValidator ID="regexpName" runat="server" ErrorMessage="This expression does not validate." ControlToValidate="txtName" ValidationExpression="^[a-zA-Z']$" />

5. CustomValidator Control:

Sometime we do not require above all control to check our input and we want to perform some other operation on the user input. so, for such purpose we can use customValidator control. we can perform client side operation and server side also by using this customer control validator. for check input at client side we can use ClientValidationFunction property and for server we can use ServerValidate event handler. client routine can be built by using any script language like Javascript or VBScript or any other understand by browser and in server side we can use any Asp.Net language like C# or VB.Net.

Syntax/Example for the control is:

<asp:TextBox id="Text1" runat="server" />
    <asp:CustomValidator id="CustomValidator1" ControlToValidate="Text1" ClientValidationFunction="ClientValidateFunction" OnServerValidate="ServerValidationFunc" ErrorMessage="Not an even number!" runat="server"/>

In above example, we can see we set the client side and server side routines to perform the operation.

6. ValidationSummary Control:

ValidationSummary is basically used to summarize the error messages from all validation control on the page. it shows the error messages per the DisplayMode property. it collects all validation control error message from a common property "ErrorMessage" of each control. if we skip the ErrorMessage property of any validation control then it will not show error message for that control. there are different properties to present error messages nicely on page by using ValidationSummary Control.

Syntax/Example Lets understand with an example:

<asp:TextBox ID="TextBox2" runat="server" />
            <asp:RequiredFieldValidator ID="RequiredFieldValidator1" ControlToValidate="TextBox2" ErrorMessage="Enter Card Type" Text="*" runat="server"/>
            <asp:TextBox ID="TextBox1" runat="server" />
            <asp:RequiredFieldValidator ID="RequiredFieldValidator2" ControlToValidate="TextBox1" ErrorMessage="Enter Card Number" Text="*" runat=server/>
            <asp:ValidationSummary id="valSum" DisplayMode="BulletList" EnableClientScript="true" HeaderText="You must enter a value in the following fields:" runat="server"/>

In above example validationsummary will show error message, in bullets, from the both required field validator control with a header text.

Comments and Suggestions are always welcome

Foreach Loop in C#

In this tutorial we are going to learn about foreach loop in c#. So let's start learning

1. In for loop we use initialization, termination and increment or decrement to loop over the data but in foreach loop we are not required any initialization, condition or increment and decrement. It is a looping constructs which ignore/remove the errors which occur due to index handling.
2. Mainly it performs its operation on collections like Array, Lists etc. and process inside values one by one.
3. There are many ways to exit or stop the loop like if we want to break the loop we can use break keyword, if want to move on next iteration continue keyword, to exit the loop we can use return, throw or goto statement.

Syntax:-

foreach(string emp_id in employees)
{

}

Example:-

string[] employees = new string[3]; // declare the array 
    //Add data to array of employees
    array[0] = "Doe-1452";
    array[1] = "Joh-2365";
    array[2] = "Gen-2589"; 
    //show data using foreach
    foreach (string emp_id in employees)
    {
        Console.WriteLine(emp_id + " Entered to Office");
    }
    //Output
    Doe-1452 Entered to Office
    Joh-2365 Entered to Office
    Gen-2589 Entered to Office