.Net 360°

Generic Delegate Types : Func,Action and Predicate

Pawan_Mishra — Sun, 21 Nov 2010 13:30:51 GMT

C# language has observed dramatic transformation from 2.0 to 3.0 and finally with 4.0. C# 2.0 added generics , simplified delegate syntax, nullable types etc. C# 3.0 takes it a level next by adding LINQ , anonymous methods , anonymous types etc and finally...(read more)

Understanding “Dispatcher” in WPF

Pawan_Mishra — Sun, 06 Jun 2010 07:38:59 GMT

Level : Beginner to intermediate Consider the following program MainWindow.xaml 1: < Window x:Class ="DispatcherTrial.MainWindow" 2: xmlns ="http://schemas.microsoft.com/winfx/2006/xaml/presentation" 3: xmlns:x ="http://schemas...(read more)

Using IComparable Interface

Pawan_Mishra — Sun, 11 Apr 2010 16:07:29 GMT

Level : Beginner to Intermediate C# language has constantly evolved over a constant period of time.Each new version introduced new features which changed the way we programmed and solved the problems. Whether it was introduction of generics in C# 2.0...(read more)

Collections in .Net

Pawan_Mishra — Thu, 14 Jan 2010 09:47:50 GMT

Undoubtedly anyone who has ever programmed with any computer programming language has one way or the other has used some data structure , class etc to collect similar kind of data in one place.For example in C/C++ in order to handle multiple data of similar...(read more)

Covariance and Contra-Variance in Delegates

Pawan_Mishra — Thu, 14 Jan 2010 07:22:21 GMT

If it comes to day to day normal programming with C# language then delegates by far are the most complicated thing to understand.Delegates add the asynchronous programming model to .Net Framework.Working with delegates involve following steps : Declare...(read more)

Wintellect’s Power Collection Library

Pawan_Mishra — Fri, 01 Jan 2010 20:03:06 GMT

First of all a very happy and prosperous new year wishes to everyone ……… :) CLR via C# by Jeffery Richter is one book which I really enjoyed reading.Any .Net developer whether experienced or a beginner will immediately benefit from the content provided...(read more)

Another VS 2010 feature : Pin-Up

Pawan_Mishra — Sat, 26 Dec 2009 18:20:33 GMT

Hello,

I have been using VS 2010 Beta 2 for sometime and today I came across another beautiful feature.Now , I don't know in technical terms what to call this feature, so its that I rather explain it with few pictures.

Following is a very small piece of code I wrote as reply to one of the answer in MSDN forum :

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;

namespace Forum
{
    class Program
    {
        static void Main(string[] args)
        {
            string str = "Pawan Mishra";

            string str2 = String.Intern(str);
            str2 = "Hello";
            Console.WriteLine("{0} : {1}", str, str2);
            Console.ReadLine();
        }
    }
}

Next what I did was I placed a break point in my code somewhere , so that compiler breaks at that point and I can actually see the values of the variables.

So while debugging , we hover our mouse over the variable name and then in visualizer we can check the value of the variable.And as soon as the mouse cursor is moved the visualizer also disappears.This is where VS 2010 is getting different.

In VS 2010 once you have hovered the mouse cursor over a variable name , you get option like to pin that visualizer.Didn’t get , its all right , just check the following screenshot.

As soon as you click on the pin icon , the variable and its corresponding value will be pinned just in front of the statement.Its shown in the following screenshot.

Now as you can see , the variable and its corresponding value is fixed.Also you can add comments for your future reference.You can also drag and drop this pin up thing(please forgive me as I don't know what else to call it ) across the screen.

Other interesting aspect is if the pinned up variable value is changed somewhere down the line , the original value will also be refreshed automatically.

Now If you have looked closely then I have encircled another small pin icon.On click of it the corresponding variable becomes editable and you can change its value.This changed value will be reflected in the subsequent lines.Following screenshot explains the same.

Finally , these pinned up values will be retained even when the application is stopped.And once you hover over the corresponding variable , it will highlight the value retained from last debug.

Well , I guess this feature is really cool and will definitely ease out debugging effort.The only question remains unanswered about this feature is what exactly is it called ?

Mole : Visual Studio Visualizer

Pawan_Mishra — Sat, 12 Dec 2009 19:58:05 GMT

Visualizer’s are of great help when debugging your application.Visualizer’s essentially provide a the complete view of the data in separate modal dialogue window.I guess almost all of us have worked with DataSet’s and in order to see the data contained inside the DataSet , we hover our mouse cursor over the dataset variable and then select the magnifying glass.This in turn opens up a separate window , showing the content of DataSet.Visual Studio debugger comes with visualizer’s for plain text , HTML , XML based data , DataSet and its corresponding dependents.If you haven’t understood what visualizer’s are actually , then refer to the following screenshot.

In the above screenshot , once the magnifying glass corresponding to “LastName” property is clicked , the actual value will be displayed in a separate window.This separate popup window is actually known as a Visualizer in Visual Studio.If you are interested in learning more about Visualizer’s the check out the following blog :- Custom Visual Studio Visualizer

Mole

I came to know about MOLE while reading an article in the blog Dr. WPF.Mole is also a visualizer built for Visual Studio.The team who have developed Mole have already published an excellent article on CodeProject.You can check out that article from following link :- Mole For Visual Studio - With Editing - Visualize All Project Types

Essentially Mole was targeted towards helping developers who where working on WPF.many of the feature's in Mole Visualizer like Logical Tree , Visual Tree etc helped the WPF developer’s in understanding the overall structure of elements in the application and also Mole helped them in viewing and understanding the corresponding XAML mark-up.

Mole has still a lot to offer to those people who are not working on WPF.And to know that lets start first by getting Mole visualizer into our Visual Studio.You can download the Mole visualizer dll from the download link provided at the CodeProject site by the team of Mole.Once downloaded copy and paste the Mole.Visualizer.dll at anyone of the following locations :

%Start\Documents\Visual Studio 2008\Visualizers\
%Root%\Program Files\Microsoft Visual Studio 9.0\Common7\Packages\Debugger\Visualizers\

Mole helps in visualizing following three things:

Current state of any custom object
Current State of any Collection in the code
Current state of any collection which is in turn inside some custom object

Lets take up each of the above mentioned points one by one.Before that , I will provide one small sample code which will help in explaining the usage of Mole even more clearly.Here’s the code :

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using Wintellect.PowerCollections;

namespace MoleVisualizerText
{
    class Program
    {
        static void Main(string[] args)
        {
            Person adam = new Person("Adam", "Smith", 23);
            Person mark = new Person("Mark", "Ion", 29);

            List<Location> adamLocation = new List<Location>();
            adamLocation.Add(new Location("London", 2, LocationInterest.Yes));
            adamLocation.Add(new Location("Tokyo",3,LocationInterest.Yes));
            adamLocation.Add(new Location("Manila",1,LocationInterest.No));            
            adam.Location = adamLocation;

            Console.WriteLine(adam);
            Console.WriteLine(mark);

            Console.ReadLine();
        }
    }

    public class Person
    {
        public string FirstName { get; set; }
        public string LastName { get; set; }
        public int Age { get; set; }
        public List<Location> Location { get; set; }

        public Person(string FirstName, string LastName, int Age)
        {
            this.FirstName = FirstName;
            this.LastName = LastName;
            this.Age = Age;
        }

        public override string ToString()
        {
            return FirstName + " " + LastName + " " + Age;
        }
    }

    public class Location
    {
        public string LocationName { get; set; }
        public int NumberOfYears { get; set; }
        public LocationInterest Interest { get; set; }

        public Location(string Location, int TimeSpent, LocationInterest interest)
        {
            this.LocationName = Location;
            this.NumberOfYears = TimeSpent;
            this.Interest = interest;
        }
    }

    public enum LocationInterest
    {
        Yes,
        No
    }
}

Following are the key points of above mentioned code

Person class used to represent a given Person.
Person class contain fields like FirstName , LastName , Age to hold the respective value’s.
Also Person Class contain property called “Location” which is a collection of type “Location”.
Type “Location” is used to represent the various location wherein a given person has stayed , for how many years he/she stayed there and finally did he/she really enjoyed staying there or not.In order to represent the last point I have used an Enum called “LocationInterest”.

Current state of any custom object

In order to view the current state of a particular object in your code in Mole , you will first have to put a break point on any line of your code.

Once that's done , then run the application and wait for the breakpoint to be hit.At that moment open the watch window and add the following expression in watch window : new WeakReference(<name of the custom object>).In my case I have created an instance of Type “Person” and named it as “adam”.So the expression in watch window becomes new WeakReference(adam).Following screenshot will explain it more clearly.

So with the above declaration , I have attached a watch expression on “adam” which is an instance of type “Person”.Finally click on the magnifying glass to open the Mole visualizer.

Mole visaulizer has got lots of options and covering them in this article is not possible.Fore more detailed explanation you can check out the article on CodeProject site from the team of Mole.In the above diagram , we can see the current state of “adam” instance.It clearly explains that the properties like FirstName , LastName , Age have been set but the last property i.e. Location is null and has still not been initialized.

If you think this is just normal , then here is the sweetest part.Mole actually remembers the instances which has been added in the watch expression , even in case of application restarts.So once you have added “adam” in watch window , you can view its state at any point of time while debugging the application.

Current State of any Collection in the code

Similar to viewing custom objects , you can also view collections (List , Dictionary etc) in Mole.And the way to do is almost same as that of custom objects which is explained in the above segment.In the above mentioned code , I have defined “adamLocation” as a collection of type “Location” to hold the details of location adam has visited.So I will attach adamLocation in watch window.

Once done , click on the magnifying glass to open the Mole visualizer to view the various items in the adamLocation collection.

Since I have added details about three locations , I can see three entries like [001],[002],[003] in the visualizer.To see the exact details , click on anyone of the hyperlinks of Value field.

Since I clicked on item number [001] , I can see the corresponding details.So with Mole , viewing the details of your collection is so easy.

Well but that's not all.If viewing of details is concerned , then the next view provided by Mole will really take you by surprise.Lets see …..

Current state of any collection which is in turn inside some custom object

Person adam = new Person("Adam", "Smith", 23);

List<Location> adamLocation = new List<Location>();
adamLocation.Add(new Location("London", 2, LocationInterest.Yes));
adamLocation.Add(new Location("Tokyo",3,LocationInterest.Yes));
adamLocation.Add(new Location("Manila",1,LocationInterest.No));            
adam.Location = adamLocation;

In the above code,I have created an instance of type “Person” and named it as “adam”.Then a collection of type “Location” and in last line I assigned that collection variable to the Location property of “adam” instance.Finally “adam” instance has some static information and a collection of locations where he has stayed.

Following the same way as we did in previous two steps , put a breakpoint , add the “adam” instance in watch window and once the breakpoint is hit , click the magnifying glass corresponding to the “adam” instance in watch window.Following is the screen shot of the Mole visualizer.

The view looks pretty ordinary.Here click on the “Collection” hyperlink .Once clicked view changes to the following :-

Interesting thing to note here is that the “View Data” button is now enabled.Click on the button to open a new popup window , which displays the details of the Location collection in a nice , tabular manner.

I think this is the biggest advantage of Mole i.e. showing the details of collection in a nice , readable manner that too with very few minimal clicks.

Mole is quiet a big enough to be covered in a single article.And I also say that the coverage of Mole has already been done in an excellent manner in the official article by the team of Mole.I wrote this article to highlight one of the feature of Mole which I really liked and I guess everyone else will like it too.

Web.config file in VS 2010 and .Net Framework 4.0 website

Pawan_Mishra — Fri, 11 Dec 2009 17:43:48 GMT

With every new framework of .Net , the size of Web.config file kept on increasing.Initially the size was quiet minimal but then came Asp.Net Ajax and it brought along with itself its own set of config section entries , corresponding HTTP Handlers and HTTP Module.With .Net 3.5 framework the size increased even more by the addition of other tags like <system.codedom> , <runtime> etc.And once .Net framework was done with its addition of entries in web.config file , we developer’s added our own set of entries.If you are working with winFx technologies like WCF or WF then further more additions are required in the Web.config file.

Finally , with the new .Net Framework 4.0 this issue(not exactly an issue) has been resolved.Following is what the default web.Config file will look like in the default website template in VS 2010 and .Net Framework 4.0 .

<?xml version="1.0"?>

<!--
  For more information on how to configure your ASP.NET application, please visit
  http://go.microsoft.com/fwlink/?LinkId=152368
  -->

<configuration>
  <connectionStrings>
    <add name="ApplicationServices"
         connectionString="data source=.\SQLEXPRESS;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|\aspnetdb.mdf;User Instance=true"
         providerName="System.Data.SqlClient" />
  </connectionStrings>
  <system.web>
    <compilation debug="false" targetFramework="4.0" />
    <authentication mode="Forms">
      <forms loginUrl="~/Account/Login.aspx" timeout="2880" />
    </authentication>
    <membership>
      <providers>
        <clear/>
        <add name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider" connectionStringName="ApplicationServices"
             enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="false" requiresUniqueEmail="false"
             maxInvalidPasswordAttempts="5" minRequiredPasswordLength="6" minRequiredNonalphanumericCharacters="0" passwordAttemptWindow="10"
             applicationName="/" />
      </providers>
    </membership>
    <profile>
      <providers>
        <clear/>
        <add name="AspNetSqlProfileProvider" type="System.Web.Profile.SqlProfileProvider" connectionStringName="ApplicationServices" applicationName="/"/>
      </providers>
    </profile>
    <roleManager enabled="false">
      <providers>
        <clear/>
        <add name="AspNetSqlRoleProvider" type="System.Web.Security.SqlRoleProvider" connectionStringName="ApplicationServices" applicationName="/" />
        <add name="AspNetWindowsTokenRoleProvider" type="System.Web.Security.WindowsTokenRoleProvider" applicationName="/" />
      </providers>
    </roleManager>
  </system.web>
  <system.webServer>
     <modules runAllManagedModulesForAllRequests="true"/>
  </system.webServer>
</configuration>

So as its clear from the above web.config file lots of entries have been taken off and the current web.config file is left with some very basic contents.But again if the previous entries like config section , compilation etc are not present in the default web.config file then where they actually went.Its simple all those contents which are essential for normal functioning of a website and the one which remains unchanged are actually moved to machine.config file.Following is the machine.config file in .Net Framework 4.0.

<?xml version="1.0" encoding="UTF-8"?>
<!--
    Please refer to machine.config.comments for a description and
    the default values of each configuration section.

    For a full documentation of the schema please refer to
    http://go.microsoft.com/fwlink/?LinkId=42127

    To improve performance, machine.config should contain only those
    settings that differ from their defaults.
-->
<configuration>
    <configSections>
        <section name="appSettings" type="System.Configuration.AppSettingsSection, System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" restartOnExternalChanges="false" requirePermission="false"/>
        <section name="connectionStrings" type="System.Configuration.ConnectionStringsSection, System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" requirePermission="false"/>
        <section name="mscorlib" type="System.Configuration.IgnoreSection, System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowLocation="false"/>
        <section name="runtime" type="System.Configuration.IgnoreSection, System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowLocation="false"/>
        <section name="assemblyBinding" type="System.Configuration.IgnoreSection, System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowLocation="false"/>
        <section name="satelliteassemblies" type="System.Configuration.IgnoreSection, System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowLocation="false"/>
        <section name="startup" type="System.Configuration.IgnoreSection, System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowLocation="false"/>
        <section name="system.codedom" type="System.CodeDom.Compiler.CodeDomConfigurationHandler, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
        <section name="system.data" type="System.Data.Common.DbProviderFactoriesConfigurationHandler, System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
        <section name="system.data.dataset" type="System.Configuration.NameValueFileSectionHandler, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" restartOnExternalChanges="false"/>
        <section name="system.data.odbc" type="System.Data.Common.DbProviderConfigurationHandler, System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
        <section name="system.data.oledb" type="System.Data.Common.DbProviderConfigurationHandler, System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
        <section name="system.data.oracleclient" type="System.Data.Common.DbProviderConfigurationHandler, System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
        <section name="system.data.sqlclient" type="System.Data.Common.DbProviderConfigurationHandler, System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
        <section name="system.diagnostics" type="System.Diagnostics.SystemDiagnosticsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
        <section name="system.runtime.remoting" type="System.Configuration.IgnoreSection, System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowLocation="false"/>
        <section name="system.windows.forms" type="System.Windows.Forms.WindowsFormsSection, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
        <section name="windows" type="System.Configuration.IgnoreSection, System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowLocation="false"/>
        <section name="uri" type="System.Configuration.UriSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
        <sectionGroup name="system.runtime.caching" type="System.Runtime.Caching.Configuration.CachingSectionGroup, System.Runtime.Caching, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a">
            <section name="memoryCache" type="System.Runtime.Caching.Configuration.MemoryCacheSection, System.Runtime.Caching, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowDefinition="MachineToApplication"/>
        </sectionGroup>
        <sectionGroup name="system.xml.serialization" type="System.Xml.Serialization.Configuration.SerializationSectionGroup, System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
            <section name="schemaImporterExtensions" type="System.Xml.Serialization.Configuration.SchemaImporterExtensionsSection, System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
            <section name="dateTimeSerialization" type="System.Xml.Serialization.Configuration.DateTimeSerializationSection, System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
            <section name="xmlSerializer" type="System.Xml.Serialization.Configuration.XmlSerializerSection, System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false"/>
        </sectionGroup>
        <sectionGroup name="system.net" type="System.Net.Configuration.NetSectionGroup, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
            <section name="authenticationModules" type="System.Net.Configuration.AuthenticationModulesSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
            <section name="connectionManagement" type="System.Net.Configuration.ConnectionManagementSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
            <section name="defaultProxy" type="System.Net.Configuration.DefaultProxySection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
            <sectionGroup name="mailSettings" type="System.Net.Configuration.MailSettingsSectionGroup, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
                <section name="smtp" type="System.Net.Configuration.SmtpSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
            </sectionGroup>
            <section name="requestCaching" type="System.Net.Configuration.RequestCachingSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
            <section name="settings" type="System.Net.Configuration.SettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
            <section name="webRequestModules" type="System.Net.Configuration.WebRequestModulesSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
        </sectionGroup>
        <sectionGroup name="system.runtime.serialization" type="System.Runtime.Serialization.Configuration.SerializationSectionGroup, System.Runtime.Serialization, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
            <section name="dataContractSerializer" type="System.Runtime.Serialization.Configuration.DataContractSerializerSection, System.Runtime.Serialization, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
        </sectionGroup>
        <sectionGroup name="system.serviceModel" type="System.ServiceModel.Configuration.ServiceModelSectionGroup, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
            <section name="behaviors" type="System.ServiceModel.Configuration.BehaviorsSection, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
            <section name="bindings" type="System.ServiceModel.Configuration.BindingsSection, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
            <section name="client" type="System.ServiceModel.Configuration.ClientSection, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
            <section name="comContracts" type="System.ServiceModel.Configuration.ComContractsSection, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
            <section name="commonBehaviors" type="System.ServiceModel.Configuration.CommonBehaviorsSection, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowDefinition="MachineOnly" allowExeDefinition="MachineOnly"/>
            <section name="diagnostics" type="System.ServiceModel.Configuration.DiagnosticSection, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
            <section name="extensions" type="System.ServiceModel.Configuration.ExtensionsSection, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
            <section name="machineSettings" type="System.ServiceModel.Configuration.MachineSettingsSection, SMDiagnostics, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowDefinition="MachineOnly" allowExeDefinition="MachineOnly"/>
            <section name="protocolMapping" type="System.ServiceModel.Configuration.ProtocolMappingSection, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
            <section name="serviceHostingEnvironment" type="System.ServiceModel.Configuration.ServiceHostingEnvironmentSection, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowDefinition="MachineToApplication"/>
            <section name="services" type="System.ServiceModel.Configuration.ServicesSection, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
            <section name="standardEndpoints" type="System.ServiceModel.Configuration.StandardEndpointsSection, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
            <section name="routing" type="System.ServiceModel.Routing.Configuration.RoutingSection, System.ServiceModel.Routing, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
            <section name="tracking" type="System.ServiceModel.Activities.Tracking.Configuration.TrackingSection, System.ServiceModel.Activities, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
        </sectionGroup>
        <sectionGroup name="system.serviceModel.activation" type="System.ServiceModel.Activation.Configuration.ServiceModelActivationSectionGroup, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
            <section name="diagnostics" type="System.ServiceModel.Activation.Configuration.DiagnosticSection, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
            <section name="net.pipe" type="System.ServiceModel.Activation.Configuration.NetPipeSection, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
            <section name="net.tcp" type="System.ServiceModel.Activation.Configuration.NetTcpSection, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
        </sectionGroup>
        <sectionGroup name="system.transactions" type="System.Transactions.Configuration.TransactionsSectionGroup, System.Transactions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, Custom=null">
            <section name="defaultSettings" type="System.Transactions.Configuration.DefaultSettingsSection, System.Transactions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, Custom=null"/>
            <section name="machineSettings" type="System.Transactions.Configuration.MachineSettingsSection, System.Transactions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, Custom=null" allowDefinition="MachineOnly" allowExeDefinition="MachineOnly"/>
        </sectionGroup>
        <sectionGroup name="system.web" type="System.Web.Configuration.SystemWebSectionGroup, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a">
            <section name="anonymousIdentification" type="System.Web.Configuration.AnonymousIdentificationSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowDefinition="MachineToApplication"/>
            <section name="authentication" type="System.Web.Configuration.AuthenticationSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowDefinition="MachineToApplication"/>
            <section name="authorization" type="System.Web.Configuration.AuthorizationSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
            <section name="browserCaps" type="System.Web.Configuration.HttpCapabilitiesSectionHandler, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
            <section name="clientTarget" type="System.Web.Configuration.ClientTargetSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
            <section name="compilation" type="System.Web.Configuration.CompilationSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
            <section name="customErrors" type="System.Web.Configuration.CustomErrorsSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
            <section name="deployment" type="System.Web.Configuration.DeploymentSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowDefinition="MachineOnly"/>
            <section name="deviceFilters" type="System.Web.Mobile.DeviceFiltersSection, System.Web.Mobile, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
            <section name="fullTrustAssemblies" type="System.Web.Configuration.FullTrustAssembliesSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowDefinition="MachineToApplication"/>
            <section name="globalization" type="System.Web.Configuration.GlobalizationSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
            <section name="healthMonitoring" type="System.Web.Configuration.HealthMonitoringSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowDefinition="MachineToApplication"/>
            <section name="hostingEnvironment" type="System.Web.Configuration.HostingEnvironmentSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowDefinition="MachineToApplication"/>
            <section name="httpCookies" type="System.Web.Configuration.HttpCookiesSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
            <section name="httpHandlers" type="System.Web.Configuration.HttpHandlersSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
            <section name="httpModules" type="System.Web.Configuration.HttpModulesSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
            <section name="httpRuntime" type="System.Web.Configuration.HttpRuntimeSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
            <section name="identity" type="System.Web.Configuration.IdentitySection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
            <section name="machineKey" type="System.Web.Configuration.MachineKeySection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowDefinition="MachineToApplication"/>
            <section name="membership" type="System.Web.Configuration.MembershipSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowDefinition="MachineToApplication"/>
            <section name="mobileControls" type="System.Web.UI.MobileControls.MobileControlsSection, System.Web.Mobile, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
            <section name="pages" type="System.Web.Configuration.PagesSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
            <section name="partialTrustVisibleAssemblies" type="System.Web.Configuration.PartialTrustVisibleAssembliesSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowDefinition="MachineToApplication"/>
            <section name="processModel" type="System.Web.Configuration.ProcessModelSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowDefinition="MachineOnly" allowLocation="false"/>
            <section name="profile" type="System.Web.Configuration.ProfileSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowDefinition="MachineToApplication"/>
            <section name="protocols" type="System.Web.Configuration.ProtocolsSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowDefinition="MachineToWebRoot"/>
            <section name="roleManager" type="System.Web.Configuration.RoleManagerSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowDefinition="MachineToApplication"/>
            <section name="securityPolicy" type="System.Web.Configuration.SecurityPolicySection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowDefinition="MachineToApplication"/>
            <section name="sessionPageState" type="System.Web.Configuration.SessionPageStateSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
            <section name="sessionState" type="System.Web.Configuration.SessionStateSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowDefinition="MachineToApplication"/>
            <section name="siteMap" type="System.Web.Configuration.SiteMapSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowDefinition="MachineToApplication"/>
            <section name="trace" type="System.Web.Configuration.TraceSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
            <section name="trust" type="System.Web.Configuration.TrustSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowDefinition="MachineToApplication"/>
            <section name="urlMappings" type="System.Web.Configuration.UrlMappingsSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowDefinition="MachineToApplication"/>
            <section name="webControls" type="System.Web.Configuration.WebControlsSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
            <section name="webParts" type="System.Web.Configuration.WebPartsSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
            <section name="webServices" type="System.Web.Services.Configuration.WebServicesSection, System.Web.Services, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
            <section name="xhtmlConformance" type="System.Web.Configuration.XhtmlConformanceSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
            <sectionGroup name="caching" type="System.Web.Configuration.SystemWebCachingSectionGroup, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a">
                <section name="cache" type="System.Web.Configuration.CacheSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowDefinition="MachineToApplication"/>
                <section name="outputCache" type="System.Web.Configuration.OutputCacheSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowDefinition="MachineToApplication"/>
                <section name="outputCacheSettings" type="System.Web.Configuration.OutputCacheSettingsSection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowDefinition="MachineToApplication"/>
                <section name="sqlCacheDependency" type="System.Web.Configuration.SqlCacheDependencySection, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowDefinition="MachineToApplication"/>
            </sectionGroup>
        </sectionGroup>
        <sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
            <sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
                <section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" allowDefinition="MachineToApplication"/>
                <sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
                    <section name="jsonSerialization" type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" allowDefinition="Everywhere"/>
                    <section name="profileService" type="System.Web.Configuration.ScriptingProfileServiceSection, System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" allowDefinition="MachineToApplication"/>
                    <section name="authenticationService" type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" allowDefinition="MachineToApplication"/>
                    <section name="roleService" type="System.Web.Configuration.ScriptingRoleServiceSection, System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" allowDefinition="MachineToApplication"/>
                </sectionGroup>
            </sectionGroup>
        </sectionGroup>
        <sectionGroup name="system.xaml.hosting" type="System.Xaml.Hosting.Configuration.XamlHostingSectionGroup, System.Xaml.Hosting, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
            <section name="httpHandlers" type="System.Xaml.Hosting.Configuration.XamlHostingSection, System.Xaml.Hosting, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
        </sectionGroup>
        <section name="system.webServer" type="System.Configuration.IgnoreSection, System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
        <section name="system.serviceModel.activities.management" type="System.ServiceModel.Activities.Configuration.WorkflowManagementServiceSection, System.ServiceModel.Activities, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
    </configSections>
    <configProtectedData defaultProvider="RsaProtectedConfigurationProvider">
        <providers>
            <add name="RsaProtectedConfigurationProvider" type="System.Configuration.RsaProtectedConfigurationProvider,System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" description="Uses RsaCryptoServiceProvider to encrypt and decrypt" keyContainerName="NetFrameworkConfigurationKey" cspProviderName="" useMachineContainer="true" useOAEP="false"/>
            <add name="DataProtectionConfigurationProvider" type="System.Configuration.DpapiProtectedConfigurationProvider,System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" description="Uses CryptProtectData and CryptUnProtectData Windows APIs to encrypt and decrypt" useMachineProtection="true" keyEntropy=""/>
        </providers>
    </configProtectedData>
    <runtime/>
    <connectionStrings>
        <add name="LocalSqlServer" connectionString="data source=.\SQLEXPRESS;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|aspnetdb.mdf;User Instance=true" providerName="System.Data.SqlClient"/>
    </connectionStrings>
    <system.data>
        <DbProviderFactories><add name="Microsoft SQL Server Compact Data Provider" invariant="System.Data.SqlServerCe.3.5" description=".NET Framework Data Provider for Microsoft SQL Server Compact" type="System.Data.SqlServerCe.SqlCeProviderFactory, System.Data.SqlServerCe, Version=3.5.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91"/></DbProviderFactories>
    </system.data>
    <system.serviceModel>
        <extensions>
            <behaviorExtensions>
                <add name="persistenceProvider" type="System.ServiceModel.Configuration.PersistenceProviderElement, System.WorkflowServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
                <add name="workflowRuntime" type="System.ServiceModel.Configuration.WorkflowRuntimeElement, System.WorkflowServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
                <add name="enableWebScript" type="System.ServiceModel.Configuration.WebScriptEnablingElement, System.ServiceModel.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
                <add name="webHttp" type="System.ServiceModel.Configuration.WebHttpElement, System.ServiceModel.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
                <add name="serviceDiscovery" type="System.ServiceModel.Discovery.Configuration.ServiceDiscoveryElement, System.ServiceModel.Discovery, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
                <add name="endpointDiscovery" type="System.ServiceModel.Discovery.Configuration.EndpointDiscoveryElement, System.ServiceModel.Discovery, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
                <add name="etwTracking" type="System.ServiceModel.Activities.Configuration.EtwTrackingBehaviorElement, System.ServiceModel.Activities, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
                <add name="routing" type="System.ServiceModel.Routing.Configuration.RoutingExtensionElement, System.ServiceModel.Routing, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
                <add name="soapProcessing" type="System.ServiceModel.Routing.Configuration.SoapProcessingExtensionElement, System.ServiceModel.Routing, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
                <add name="workflowIdle" type="System.ServiceModel.Activities.Configuration.WorkflowIdleElement, System.ServiceModel.Activities, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
                <add name="workflowUnhandledException" type="System.ServiceModel.Activities.Configuration.WorkflowUnhandledExceptionElement, System.ServiceModel.Activities, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
                <add name="bufferedReceive" type="System.ServiceModel.Activities.Configuration.BufferedReceiveElement, System.ServiceModel.Activities, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
                <add name="sendMessageChannelCache" type="System.ServiceModel.Activities.Configuration.SendMessageChannelCacheElement, System.ServiceModel.Activities, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
                <add name="sqlWorkflowInstanceStore" type="System.ServiceModel.Activities.Configuration.SqlWorkflowInstanceStoreElement, System.ServiceModel.Activities, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
                <add name="Microsoft.VisualStudio.Diagnostics.ServiceModelSink.Behavior" type="Microsoft.VisualStudio.Diagnostics.ServiceModelSink.Behavior, Microsoft.VisualStudio.Diagnostics.ServiceModelSink, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/></behaviorExtensions>
            <bindingElementExtensions>
                <add name="webMessageEncoding" type="System.ServiceModel.Configuration.WebMessageEncodingElement, System.ServiceModel.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
                <add name="context" type="System.ServiceModel.Configuration.ContextBindingElementExtensionElement, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
                <add name="byteStreamMessageEncoding" type="System.ServiceModel.Configuration.ByteStreamMessageEncodingElement, System.ServiceModel.Channels, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
                <add name="discoveryClient" type="System.ServiceModel.Discovery.Configuration.DiscoveryClientElement, System.ServiceModel.Discovery, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
            </bindingElementExtensions>
            <bindingExtensions>
                <add name="wsHttpContextBinding" type="System.ServiceModel.Configuration.WSHttpContextBindingCollectionElement, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
                <add name="netTcpContextBinding" type="System.ServiceModel.Configuration.NetTcpContextBindingCollectionElement, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
                <add name="webHttpBinding" type="System.ServiceModel.Configuration.WebHttpBindingCollectionElement, System.ServiceModel.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
                <add name="basicHttpContextBinding" type="System.ServiceModel.Configuration.BasicHttpContextBindingCollectionElement, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
            </bindingExtensions>
            <endpointExtensions>
                <add name="dynamicEndpoint" type="System.ServiceModel.Discovery.Configuration.DynamicEndpointCollectionElement, System.ServiceModel.Discovery, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
                <add name="discoveryEndpoint" type="System.ServiceModel.Discovery.Configuration.DiscoveryEndpointCollectionElement, System.ServiceModel.Discovery, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
                <add name="udpDiscoveryEndpoint" type="System.ServiceModel.Discovery.Configuration.UdpDiscoveryEndpointCollectionElement, System.ServiceModel.Discovery, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
                <add name="announcementEndpoint" type="System.ServiceModel.Discovery.Configuration.AnnouncementEndpointCollectionElement, System.ServiceModel.Discovery, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
                <add name="udpAnnouncementEndpoint" type="System.ServiceModel.Discovery.Configuration.UdpAnnouncementEndpointCollectionElement, System.ServiceModel.Discovery, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
                <add name="workflowControlEndpoint" type="System.ServiceModel.Activities.Configuration.WorkflowControlEndpointCollectionElement, System.ServiceModel.Activities, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
                <add name="webHttpEndpoint" type="System.ServiceModel.Configuration.WebHttpEndpointCollectionElement, System.ServiceModel.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
                <add name="webScriptEndpoint" type="System.ServiceModel.Configuration.WebScriptEndpointCollectionElement, System.ServiceModel.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
            </endpointExtensions>
        </extensions>
        <client>
            <metadata>
                <policyImporters>
                    <extension type="System.ServiceModel.Channels.ContextBindingElementImporter, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=MSIL"/>
                </policyImporters>
                <wsdlImporters>
                    <extension type="System.ServiceModel.Channels.ContextBindingElementImporter, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=MSIL"/>
                </wsdlImporters>
            </metadata>
        </client>
        <tracking>
            <profiles>
                <trackingProfile name="">
                    <workflow activityDefinitionId="*">
                        <workflowInstanceQueries>
                            <workflowInstanceQuery>
                                <states>
                                    <state name="*"/>
                                </states>
                            </workflowInstanceQuery>
                        </workflowInstanceQueries>
                        <activityStateQueries>
                            <activityStateQuery activityName="*">
                                <states>
                                    <state name="Faulted"/>
                                </states>
                            </activityStateQuery>
                        </activityStateQueries>
                        <faultPropagationQueries>
                            <faultPropagationQuery faultSourceActivityName="*" faultHandlerActivityName="*"/>
                        </faultPropagationQueries>
                    </workflow>
                </trackingProfile>
            </profiles>
        </tracking>
        <standardEndpoints>
            <workflowControlEndpoint>
                <standardEndpoint name="WorkflowControlNetPipeEndpoint" address="System.Activities.DurableInstancing_IWorkflowInstanceManagement" binding="netNamedPipeBinding" bindingConfiguration="WorkflowControlNetPipeBinding"/>
                <standardEndpoint name="WorkflowControlHttpsEndpoint" address="System.Activities.DurableInstancing_IWorkflowInstanceManagement" binding="wsHttpBinding" bindingConfiguration="WorkflowControlHttpsBinding"/>
                <standardEndpoint name="WorkflowControlHttpEndpoint" address="System.Activities.DurableInstancing_IWorkflowInstanceManagement" binding="wsHttpBinding" bindingConfiguration="WorkflowControlHttpBinding"/>
                <standardEndpoint name="WorkflowControlNetTcpEndpoint" address="System.Activities.DurableInstancing_IWorkflowInstanceManagement" binding="netTcpBinding" bindingConfiguration="WorkflowControlNetTcpBinding"/>
            </workflowControlEndpoint>
        </standardEndpoints>
        <bindings>
            <netNamedPipeBinding>
                <binding name="WorkflowControlNetPipeBinding" transactionFlow="true">
                    <security mode="Transport">
                        <transport protectionLevel="Sign"/>
                    </security>
                </binding>
            </netNamedPipeBinding>
            <wsHttpBinding>
                <binding name="WorkflowControlHttpsBinding" transactionFlow="true">
                    <security mode="Transport">
                        <transport clientCredentialType="Windows"/>
                    </security>
                </binding>
                <binding name="WorkflowControlHttpBinding" transactionFlow="true">
                    <security mode="Message">
                        <message clientCredentialType="Windows"/>
                    </security>
                </binding>
            </wsHttpBinding>
            <netTcpBinding>
                <binding name="WorkflowControlNetTcpBinding" transactionFlow="true">
                    <security mode="Transport">
                        <transport clientCredentialType="Windows" protectionLevel="Sign"/>
                    </security>
                </binding>
            </netTcpBinding>
        </bindings>
        <commonBehaviors><endpointBehaviors><Microsoft.VisualStudio.Diagnostics.ServiceModelSink.Behavior/></endpointBehaviors><serviceBehaviors><Microsoft.VisualStudio.Diagnostics.ServiceModelSink.Behavior/></serviceBehaviors></commonBehaviors></system.serviceModel>
    <system.web>
        <processModel autoConfig="true"/>
        <httpHandlers/>
        <membership>
            <providers>
                <add name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" connectionStringName="LocalSqlServer" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="true" applicationName="/" requiresUniqueEmail="false" passwordFormat="Hashed" maxInvalidPasswordAttempts="5" minRequiredPasswordLength="7" minRequiredNonalphanumericCharacters="1" passwordAttemptWindow="10" passwordStrengthRegularExpression=""/>
            </providers>
        </membership>
        <profile>
            <providers>
                <add name="AspNetSqlProfileProvider" connectionStringName="LocalSqlServer" applicationName="/" type="System.Web.Profile.SqlProfileProvider, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
            </providers>
        </profile>
        <roleManager>
            <providers>
                <add name="AspNetSqlRoleProvider" connectionStringName="LocalSqlServer" applicationName="/" type="System.Web.Security.SqlRoleProvider, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
                <add name="AspNetWindowsTokenRoleProvider" applicationName="/" type="System.Web.Security.WindowsTokenRoleProvider, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
            </providers>
        </roleManager>
    </system.web>
</configuration>

In your local machine you can access this machine.config file by going through the following path :-

%Root%/Windows/Microsoft.net/Framework/v4.0.21006/Config/

And yes you will get this config file only if you are having .Net Framework installed.Also do not modify anything in the machine config file.

VS 2010 Beta 2 : Quick Glance

Pawan_Mishra — Sun, 29 Nov 2009 09:35:00 GMT

I got my copy of VS 2010 Beta 2 installable DVD just a few days back. Without wasting much time I straight away installed the beta version of VS 2010 .Installation was pretty smooth , just like its predecessor VS installation requires quiet a big amount of space in your hard drive.Since its only a beta version , you need to connect to internet to get some high end features.But no worries , whatever comes with the DVD installable is sufficient enough that you can kick start your development process.

Note : Do not use the beta version of VS 2010 to write application code for your production environment.Its meant only for your personal use so that you can gain familiarity with this new development environment.

So let me take you through a quick tour of VS 2010 Beta 2 , thereby highlighting some major changes that have been done to this new development environment.

Start the VS 2010 IDE by going to Start –> Microsoft Visual Studio 2010 –> Visual Studio 2010 – ENU.

Once opened , go to File and select “New Project”.Following dialog box comes up :-

This is the dialog box which will be used to add new items to your existing solution or to add a new solution all together.Very much like VS 2008 , the layout is same but with some minor differences in terms of UI and colour scheme.On extreme right we have small description of the item which is selected in the central pane.You can sort the list in central pane by making use of “Sort By” option provided at the top of the window.Also similar to VS 2008 , VS 2010 offers the capability of multiple framework target support which you can leverage by selecting the appropriate .Net Framework from option provided in “.Net Framework” dropdown.Default is .Net Framework 4 , which happens to be the latest .Net Framework from Microsoft.

Select console application from the options give project name as “FirstApplication”.Once clicked okay VS 2010 opens up with the following window which is the default one for console applications.

Now just like previous VS IDE’s here also the screen is divided into multiple sections.”FirstApplication” in solution explorer is the default project and to overall solution I added one more “Class Library” project called “BIZLayer”.At the bottom left of the screen , you can see value like “100%”, which is used to set the font size of the IDE.

Now there is something interesting going on and for that to know you have to right click on the project “FirstApplication” and select “Add Reference”.Following window comes up which is in sync with what we used to get in previous versions.

Now we can see a major change here in the form of Versions of the dll’s.Most of the dll’s are of version 4.0.0.0 .And when I say most of them then I also mean to say dll’s like “System” , “System.Data” etc .Till .Net 3.5 framework these core dll’s where not modified but with .Net Framework 4.0 , all the dll’s(classes , libraries etc) have been modified so as to target the new CLR version.Yes new CLR version , is being shipped with .Net Framework 4.0.Till .Net 3.5 framework only the upper layer classes got changed , new functionalities where added on top of previous layers but the internal CLR engine remained same.But here even the CLR engine has been modified or say upgraded.Well this is one of the biggest changes that .Net framework 4.0 has to offer.Since I have mentioned about CLR , I highly recommend .Net developer’s to read “CLR via C#” book by Jeffery Richter.

There is one more things to notice here,once you have selected .Net framework 4.0 as your choice of framework and then you say “Add Reference” then this dialog window will only list dll’s of version 4.0.0.0 . Whereas in previous .Net Framework all the dll’s where listed irrespective of their versions but some of them will be greyed out if their version if higher than the version of the project.You can verify this in your local machine.

Hold on , the dll story is still not over.To know about one more feature excellent feature of .Net Framework , all you have to do is right click of the “FirstApplication” project and select “Project Properties”.In the newly opened window , select the “Target Framework” dropdown and you will notice one more unique feature and it is called “Client Profile”.

To know more about this concept called “Client Profile” check out the following article :- .NET Framework 4 Client Profile - Introduction

Now under BIZLayer library add one class file say “BizLayer” and to that add one method named “ReturnTime” which returns the current DateTime.Following code window shows the code of both “BIZLayer” and the “FirstApplication” project.

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;

namespace FirstApplication
{
    class Program
    {
        static void Main(string[] args)
        {
            Console.WriteLine(BIZLayer.BizLayer.ReturnTime());
            Console.ReadKey();
        }
    }
}

Code For BIZLayer Class :

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;

namespace BIZLayer
{
    public class BizLayer
    {
        public static DateTime ReturnTime()
        {
            return DateTime.Now;
        }
    }
}

Code is fairly simple , a call is made from Main() method to ReturnTime() method in BizLayer , which returns the current time and then that time is displayed in console window.One real interesting thing in VS 2010 is the refined intellisense.Until VS 2008 intellisense option listed all the possible entries irrespective of what member we are looking for and in that list we have to scroll up/down to look for the desired method or property.Example :-

But with VS 2010 , as soon as we type the very first letter of our desired method/property etc the list gets shorted and it only shows the members beginning with our entered text.

Following is the output of above program.

All right , forget about the output rather concentrate on the extreme right hand side of the image and what we can see is one of the most important feature of VS 2010 and it is called “IntelliTrace”.You can check out for more about this feature by checking out the following article :- VS 2010 Beta 2 IntelliTrace In-Depth First Look .

Another feature to notice is the “Architecture” tab in the toolbar.

Selection of anyone of the options generates the “Dependency Graph”.Which initially looks like this :-

In the above diagram we can see how the various class libraries are interconnected.”FirstApplication” is dependent upon “BIZLayer” and “Externals”.Externals here are the other dll’s on which your applications depends upon.Dll’s which run behind the scene are a part of externals.You can also expand the individual node in the above diagram to explore its corresponding nesting structure.Following diagram highlights the same :-

Here I have expanded the BIZLayer node using the expander icon provided at the top of each node.That's not all , you can do lots of other operations on this designer and explore the various layering and interdependent function calls.Next few images highlights the same :-

Highlight Individual Link : To know more about a particular dependency , highlight the link and select the up and down arrow.In the image below the highlighter is shown on the link between Main method and the Externals node.

Once we select the right side arrow in the highlighter it expands the “Externals” node and gives the basic preview of it.

You can also perform other operations on this Node diagram by making use of advanced selection criteria's.Image below highlights the same :

Next on the list is the Analyze tab in the toolbar.With this option you can perform various types of analysis either at application level or at individual function level.

Various kinds of analysis are there that can be performed.Few of them are Performance , Code Analysis and Code Metrics etc.

Once you run the Code Metrics , it highlights the information like Cyclomatic Complexity , Depth Of Inheritance , Class Coupling , Lines Of Code etc.

And in case of performance wizard it provides insight regarding the performance issues of your application.Following is one sample Profiling Report.

I guess I have mentioned quiet a lot about VS 2010 special and new feature in the current writing.Topics like IntelliTrace , Code Metrics , Performance Analysis , Architecture etc are require separate attention.But I included their overview just to inform users that there is lots of new features that are coming up in new versions of VS 2010 and we should prepare ourselves for an altogether different kind of programming experience with VS 2010.

In the above article I have referenced many other blogs or article which will help you in providing in-depth understanding of that particular concept.I would like to thank all of them for providing such excellent articles.

I will continue exploring VS 2010 and .Net Framework 4.0 and will come up with new articles on my blog with more information.Till then cheers ….

Microsoft Pattern’s and Practices : Improving Web Services Security

Pawan_Mishra — Sat, 28 Nov 2009 07:50:57 GMT

I was going through the patterns and practices section of MSDN website when I came across this pattern and practice guide on how to Improve Web Service Security.Basically this guide is for people who are developing web services using WCF.

This guide provides guidelines on how to secure your WCF services in both intranet and internet scenario.Following are the various sections in which the guide is divided :

• Part I – Security Fundamentals for Web Services
• Part II – WCF Security Fundamentals
• Part III – Intranet Application Scenarios
• Part IV – Internet Application Scenarios

Part –1

• Chapter 01 – Security Fundamentals for Web Services
• Chapter 02 – Threats and Countermeasures for Web Services
• Chapter 03 – Security Design Guidelines for Web Services

Part –2

• Chapter 04 – WCF Security Fundamentals
• Chapter 05 – Authentication, Authorization, and Identities in WCF
• Chapter 06 – Impersonation and Delegation in WCF
• Chapter 07 – Message and Transport Security
• Chapter 08 – Bindings

Part –3

• Chapter 09 – Intranet – Web to Remote WCF Using Transport Security (Original Caller, TCP)
• Chapter 10 – Intranet – Web to Remote WCF Using Transport Security (Trusted Subsystem,HTTP)
• Chapter 11 – Intranet – Web to Remote WCF Using Transport Security (Trusted Subsystem TCP)
• Chapter 12 – Intranet – Windows Forms to Remote WCF Using Transport Security (Original Caller, TCP)

Part –4

• Chapter 13 – Internet – WCF and ASMX Client to Remote WCF Using Transport Security(Trusted Subsystem, HTTP)
• Chapter 14 – Internet – Web to Remote WCF Using Transport Security (Trusted Subsystem,TCP)
• Chapter 15 – Internet – Windows Forms Client to Remote WCF Using Message Security(Original Caller, HTTP)

Well the guide is pretty big(more than 600 pages) but it provides invaluable information regarding the development of secure WCF application.

You can download the guide from CodePlex.Following is the URL :- Improving Web Services Security

PageSpeed – Another FireFox Plugin

Pawan_Mishra — Sun, 08 Nov 2009 07:53:48 GMT

Hello,

With all new and more powerful frameworks coming up in web development , which in turn has helped web developers across the globe to try and implement new features and ideas thereby making websites more user friendly and responsive.And one such ground breaking technology is Ajax.Currently around 128 Ajax implementations are in market with Asp.Net Ajax , jQuery being the most powerful one.

But these new technologies also come up with new challenges.Thanks to various supports in terms of libraries , tools and plug-ins , today's web developer is equipped with more sophisticated tools which helps him in understanding things more clearly.

In this article I will be speaking about one such Firefox plug-in called PageSpeed which helps in identifying the potential bottlenecks in a given web page.I came to know about this plug-in in one of the threads in Asp.Net Forum where one user asked how to reduce the page size ? Following is the URL for that particular thread :- How to Reduce PageSize ?

It will be more accurate to say that PageSpeed is actually a Firebug plug-in . Once you have opened a web page and also opened the Firebug console , you can find the PageSpeed tab in the header.Following is the screenshot :

Now once you run any of your application’s web page , just open the Firebug cancel and you can start analyzing the page’s performance with PageSpeed.Click on “Analyze Performance” button and PageSpeed will inform you with vital information that will help you in enhancing the page’s performance.Just have a look at the following screenshot for one of the webpage which I have developed locally :-

For e.g. : expand the Minify JavaScript link and it will tell you what's the current size of all *.js files and how much will be saved once the JavaScript minimisation is done.

Well so just go ahead and add the PageSpeed plug-in into your Firebug browser and analyze your webpage's.

Unit Testing WebMethods

Pawan_Mishra — Thu, 29 Oct 2009 15:31:49 GMT

Any Asp.net developer working with Asp.Net Ajax cannot deny the importance of “Asp.net Ajax WebService” and with WCF coming up this feature is going to be one of the most admired feature of the asp.net web development.

Most of the current application follows layered architecture. Wherein the CRUD functionality lies in the Data Access Layer(DAL) .These methods are in turn invoked through the Business Layer functions which in turn are invoked through the web methods defined in our web services layer.

Unit testing, at least this is one feature whose importance cannot be denied. Unit testing DAL or Business layer methods are fairly simple but testing web methods are not that straight forward. Don’t worry I am not saying it’s going to be a very challenging task , in order to unit test a web method all you have to do is to add a “Default.aspx” web page into your solutions root directory.

Let’s say you have a web method with the following definition:-

Step 1 : Defining WebMethod

public string HelloWorld()
{
     return "Hello World";
}

Step 2: Adding the Default.aspx Page

To your solution(website) just add a new webpage with name "Default.aspx".Note if you have multiple sub directories under the root folder then you have to place this webpage outside any such sub directories i.e. directly under the application directory.

Step 3: Adding a new Test Project to your solution

Select the solution --> File --> Add New Project --> Select TestProject --> Give Some Name(say MyTest) and click Okey.

Step 4: Writing the Unit Test

Writing unit test is fairly simple.Right Click on the TestProject(named MyTest) –> Add –> Select UnitTest.
Once you have made the selection a modal window(popup window) will come up.This in turn will list down all the projects which are under the current solution.

Once you have the window opened , select your application "WebSite" and expand it.Once expanded it will have two options namely "No Namespace" and "_Asp".Well I guess these categories can differ.

Now you will have to look for your web method(HelloWorld) inside the "No Namespace" category.Once found just check the corresponding checkbox and click okey.And here you have your unit test method for the web method (HelloWorld).

This is how the unit test method will look like in case of above mentioned web method.

/// 
///A test for HelloWorld
///
// TODO: Ensure that the UrlToTest attribute specifies a URL to an ASP.NET page (for example,
// http://.../Default.aspx). This is necessary for the unit test to be executed on the web server,
// whether you are testing a page, web service, or a WCF service.
[TestMethod()]
[HostType("ASP.NET")]
[AspNetDevelopmentServerHost("C:\\My Application Data\\My Work\\VP\\UI", "/UI")]
[UrlToTest("http://localhost/UI")]
public void HelloWorldTest()
{
       Users_Accessor target = new Users_Accessor(); // TODO: Initialize to an appropriate value
       string expected = string.Empty; // TODO: Initialize to an appropriate value
       string actual;
       actual = target.HelloWorld();
       Assert.AreEqual(expected, actual);
       Assert.Inconclusive("Verify the correctness of this test method.");
}

The above code is specific to my application development environment.And yes I have used the VS 2008 testing framework for writing the above test case for web method.In order to run the test , simply right click on method and select either run the test or debug the test.

In the above code , you will have to set the expected value and then unit test will evaluate it will the actual returned value.

This article is more verbose but while implementing most of the tasks will be automated, thanks to Visual Studio IDE.

AjaxControlToolkits AsyncFileUpload Control

Pawan_Mishra — Tue, 20 Oct 2009 15:51:42 GMT

Finally , the wait for a control to upload files asynchronously is over.AjaxControlToolkit latest release has introduced new control called AsyncFileUpload control which is compatible with UpdatePanel and can be used to upload files asynchronously.You can download the latest release from the following URL:-

AjaxControlToolkit Release 33804 , September 30th 2009 :- http://ajaxcontroltoolkit.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=33804

AsyncFileUpload Control

Following is one very simple and short example explaining the usage of the newly introduced control :-

MarkUp

<%@ Register Assembly="AjaxControlToolkit" Namespace="AjaxControlToolkit" TagPrefix="cc1" %>
<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
 <title></title>
</head>
<body>
 <form id="form1" runat="server">
 <asp:ScriptManager runat="server" ID="src">
 </asp:ScriptManager>
 <div>
 <asp:UpdatePanel runat="server" ID="upd" UpdateMode="Conditional">
 <ContentTemplate>
 <cc1:AsyncFileUpload ID="AsyncFileUpload1" runat="server" UploaderStyle="Traditional"
 runat="server" OnClientUploadStarted="Start" ThrobberID="imgThrobber"
 OnClientUploadComplete="Fire"/>
 </ContentTemplate>
 <Triggers>
 <asp:AsyncPostBackTrigger ControlID="btnClick" EventName="Click" />
 </Triggers>
 </asp:UpdatePanel>
<input type="button" id="btnCheck" onclick="FileUpload();" value="Upload Files Client Side" />
 <asp:Button runat="server" ID="btnClick" Text="Upload File Server Side" OnClick="btnClick_Click" />
<img alt="Trial" src="ajax-loader.gif" id="imgThrobber" runat="server" />
 </div>
 </form>
</body>
</html>

Client Side Code

function FileUpload() {
    var asyncFileUpload = $find('AsyncFileUpload1');
    alert(asyncFileUpload.get_postBackUrl());
    alert($get('AsyncFileUpload1_ctl00').value);
    // do something
}

function Fire() {
    var asyncFileUpload = $find('AsyncFileUpload1');
    // do something
}

function Start() {
    var asyncFileUpload = $find('AsyncFileUpload1');
    // do something
}

protected void btnClick_Click(object sender, EventArgs e)
{
     if (AsyncFileUpload1.HasFile)
     {
         AsyncFileUpload1.SaveAs(@"C:\Upload Files\" + AsyncFileUpload1.PostedFile.FileName);
     }
}

Well the above example is fairly basic but whats interesting is that the control offers the same properties to work with in code behind which are offered by
the regular asp:FileUpload control.As we can see above I have wrapped the control inside the updatepanel and then in code behind I am uploading the file to some temp directory.The whole process of uploading file takes place asynchronously, without a full page postback.So now we can happily upload files through controls like "ModalPopUpExtender" with the help of "AsyncFileUpload" control whithout refreshing the pop-up screen.

Lets have a look at some other properties of AsyncFileUpload Control :-

ThrobberId : Id of the control which will be shown while the file is being posted by the "AsyncFileUpload" control.As explained in the above sample code , we can use this attribute to show some "Loading..." kind of image during the process of posting of file.You can work with file only if it is posted properly by the control.For this the control offers certain color scheme to notify the end user whether the file is posted correctly or not.If file is posted correctly the background color of the control will turn to Green and if there is an error then background color will turn to Red .Also we can change this color scheme as per our preference.
OnClientUploadStarted and OnClientUploadComplete : These are client side events offered by the control wherein the former event will be fired once the posting of file has started and later being fired once the process of posting of file has completed.We can handle these events on client side to perform extra functionality while the file is being posted.In the above example I have show how we can access the control in our client side code.The control offers various getter and setter method which we can use in our client side code to manipulate certain attributes of the control programmatically.In the above posted client side code I am alerting the postback URL and the name of the file which is currently being posted.You can check out my other blog in which I have explained on how to work with "AjaxControlToolkit" extender controls effectively in our client side code.Blog :- Working With AjaxControlToolkit.
UpdateStyle : It offeres two mode "Traditional" and "Modern".By default "UpdateStyle" is set to "Traditional" which resembles with the regular asp:FileUpload control.In case of "Modern" the control offers a more stylish look.But I am facing certain difficulties in working with "Modern" styling as the control is not getting cleared once I have successfully uploaded the file into some temp directory.With "Traditional" styling everything works fine.
OnClientUploadError : :- Like the previously mentioned client side events , this event is fired if in case there is some error in posting the file by the control.We can handle this event to do some cleanup task or notify the users with a more "user friendly" message .

Working With AjaxControlToolkit

Pawan_Mishra — Sun, 18 Oct 2009 06:15:33 GMT

Hello,

Already plenty of articles have been published explaining how to work with AjaxControlToolkit extender controls.In this article I will provide with a general tip on working with AjaxControlToolkit which is applicable to all the extender controls of the Toolkit.

In general we can incorporate extender controls in our web page by declaring their markup code.But many times it is required to access these extender controls in our client side javascript code so that we can manipulate certain attributes or properties of the extender control declared in our web page. Its same as like declaring a asp:TextBox control in our web page and then setting its "Text" property in code behind.But unlike asp.net server controls , AjaxControlToolkit extender controls and their handling in client side javascript code is not very well documented and thus it becomes quiet difficult to work with them.

Solution 1

This solution requires you to download the source code of the AjaxControlToolkit from CodePlex.Remember to download the correct version of Toolkit controls which are dependent upon the .Net Framework you are using in your development envoirnment.You can get the latest version of Toolkit from following URL.
Once you have downloaded the solution you need to open it up in Visual Studio.
If project(AjaxControlToolkit) opens normally then in "Solution Explorer" you will find seperate directories for each of the Extender Controls present in AjaxControlToolkit library.
Expand any of your favourite Extender Control's directory and in that look for <ExtenderControlName><Behaviour>.js file i.e. in case of AutoComplete Extender control you will find a jScript file called AutoCompleteBehaviour.js.
Open the file and in that you can see the client side code for that particular extender control. Code will basically be a collection of various methods which will be of format mentioned in the following point.
get_<MethodName> or set_<MethodName> : : These are the getter and setter methods for each property of the extender control.We can use these methods to get and set the values of various propertiesof the control.
Method starting with Underscore('_') : These methods are like private variables and are not meant to be used directly in our production code.Well there are chances of there variables getting modified or even removed in later version but I don't think it will happen that soon.
So now you know how to retrive and set the values of various properties of AjaxControlToolkit Extender control.

Solution 2

I can totally understand that this whole concept of opening the entire solution and then going through the entire code of Extender control to just find out how to get the value of one property is far too tedious.Luckily we can easily avoid this all together by making use of two extremely useful plugins of FireFox.Plugins are :

Download the lastest version and install these plugins into your Firefox browser.Once done then run your web application in Firefox.Remember to start the "FireBug" which will come as a small icon in your browser taskbar.Once started it will look something like this :-

As we can see in the above screen shot I have selected the "FireAtlas" tab in "FireBug" and inside "FireAtlas" tab select "Get Application Component" tab.Once clicked it will list down all the client side component downloaded for the current webpage.It will also list down the toolkit extender controls.For e.g. in above screenshot we can see AjaxControlToolkit.CalandarBehaviour which is downloaded because I have calandar exyender in my webpage.After this just expand the extender control(CalandarBeh option).I have provided "CalanderBeh" as the BehaviourID for the calandar extender control in my sample application.

Once expanded you will see a list of functions in the same format as described above i.e. getter , setter and one which start with UnderScore("_").Thus you have the list of all the getter and setter functions of your favourite extender control and they are ready to be used in your client side code.

Example

Through the following code snippet I will show you how you can use these getter and setter methods to alter the behavior of extender controls.In the code below I will change the default display of CalanderExtender control from "Days in Current Month" to "Years in Current Decade".

<asp:TextBox runat="server" ID="txtCal"></asp:TextBox>
 <ajaxToolkit:CalendarExtender runat="server" ID="CalandarID" BehaviorID="CalandarBeh" TargetControlID="txtCal"></ajaxToolkit:CalendarExtender>

And here is the client side code

function pageLoad() {
    var cal = $find('CalandarBeh');
    cal.add_shown(onCalShown);
}

function onCalShown(evt) {
    evt._switchMode("years", false);
}

In the above client side code , I am getting a reference stored in variable 'cal' by passing the behaviour-id of the extender control in $find() method.And this is how it should be done in normal programming , use $find() to get the reference to your extender control.Once I have the refrence then I am attaching a call back method for the "shown" event of the calander.In that event handler method I am switching the mode of display to years.

Note in the above code I am using "_switchMode" variable which is actually a private variable.But like I said before name or functionality of these variable being modified in near future are pretty low, so we can go ahead with this implementation.