Search This Blog

Tuesday, December 27, 2011

Installing IIS 7 on Windows Vista and Windows 7

  1. In , open Control Panel and then click Programs. 
    IIS install Step 1
  2. Under Programs and Features, click Turn Windows features on or off.
    Turn Windows Features On or Off
    How to install IIS on Windows 7
    If Control Panel is set to display in Classic view, click Programs and Features,
    and in then in the left pane, click Turn Windows features on or off.
  3. The Windows Features dialog box is displayed.Expand Internet Information Services.
    Expand Internet Information Services
    Step 3
  4. Expand Web Management Tools, expand IIS 6 Management Compatibility, and then select the IIS 6 Metabase and IIS 6 configuration compatibility check box.
    Step 4
  5. Expand World Wide Web Services, expand Application Development Features, and then select the ASP.NET check box.
    The options that are required for Web application development will automatically
    be select
  6. Expand World Wide Web Services, expand Security, and then select the Windows Authentication check box. To enable Visual Studio to debug applications, you must configure IIS 7.0 with the Windows Authentication module. By default, the module is not configured as part of IIS.
    Step 6
  7. Expand the World Wide Services, expand the Common HTTP Features then check the Static Content.
    Step 7
  8. Click OK to start the IIS and ASP.NET installation process.
  9. When the configuration process finishes, close Control Panel.
  10. After clicking OK button it will take some time to install IIS and others features on your computer. After doing this you need to be sure that every thing is OK! for this open your browser and navigate to http://localhost. If you can see the following page then every thing is OK.

Friday, December 16, 2011

Details and Limitations of Blobs, Tables, and Queues of Windows Azure

  • Block Id - 64 Bytes Per Block
  • PutBlob - 64 MB Total
  • Blob MetaData - 8 KB Per Blob
  • PutBlock / PutBlockList - 50 GB Each
  • Blocks - 4 MB Each

Container Name:

  • Valid DNS Name
  • All Lowercase
  • 3 to 63 Characters
  • Starts With Letter or Number
  • Letters, Numbers, and Dash (-)
  • Every Dash (-) Must Be Immediately Preceded and Followed by a Letter or Number
Blob Name:
  • 1,024 Characters Max
  • Any combination of characters, but reserved URL characters must be properly escaped
  • Specify a delimiter within a blob name to create a virtual hierarchy though blob storage is flat and not a hierarchical 

    Table Name:

  • Only Alphanumeric Characters
  • Case-Insensitive
  • 3 to 63 Characters
  • May Not Begin With a Numeric Character
  • Up to 255 Entity Properties (including PartitionKey, RowKey, and Timestamp)
  • 1 MB Max for Combined Size of All Data in an Entity's Properties
Property Name:

  • Case-Sensitive
  • 255 Characters Max
  • Only Alphanumeric Characters
  • Must Begin With a Letter
  • Messages - 8 KB Max
  • Messages pushed to end of queue and popped from front of queue (FIFO)
  • Unlimited number of messages

Queue Name:

  • Valid DNS name
  • All Lowercase
  • 3 to 63 Characters
  • Start With a Letter or Number
  • Letters, Numbers, and Dash (-)
  • First and Last Letters Must be Alphanumeric
  • Dash (-) character may not be the first or last letter

Windows Azure One of the request inputs is out of range

Exception :
  Microsoft.WindowsAzure.StorageClient.StorageClientException was unhandled
  Message=One of the request inputs is out of range.

  InnerException: System.Net.WebException
       Message=The remote server returned an error: (400) Bad Request.
            at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
            at Microsoft.WindowsAzure.StorageClient.EventHelper.ProcessWebResponse(WebRequest req,  IAsyncResult asyncResult, EventHandler`1 handler, Object sender)

Solution :
All container and queue names should not contain capital letters

for Windows Azure Details and Limitataions Click on below link

Monday, November 21, 2011

Best Sql Server Interview Questions 2000/2005/2008 : Part 4

Difference between INDEX SEEK AND INDEX SCAN :

The index scan will scan all the data in the data page. Index scan is useful if the table has small amount of datasets. The index scan can be considered as a table scan.
The index seek is good at performance optimization point of view. Index seek will only seek for the satisfying query conditions.

Wednesday, November 16, 2011

Difference between const, static and readonly in c#

Within a class, const, static and readonly members are special in comparison to the other modifiers.

const vs. readonly

const and readonly perform a similar function on data members, but they have a few important differences.


A constant member is defined at compile time and cannot be changed at runtime. Constants are declared as a field, using the const keyword and must be initialized as they are declared. For example;

public class MyClass
  public const double PI = 3.14159;
PI cannot be changed in the application anywhere else in the code as this will cause a compiler error.
Constants must be a value type (sbyte, byte, short, ushort, int, uint, long, ulong, char, float, double, decimal, or bool), an enumeration, a string literal, or a reference to null.

Since classes or structures are initialized at run time with the new keyword, and not at compile time, you can't set a constant to a class or structure.

Constants can be marked as public, private, protected, internal, or protected internal.
Constants are accessed as if they were static fields, although they cannot use the static keyword.
To use a constant outside of the class that it is declared in, you must fully qualify it using the class name.


A read only member is like a constant in that it represents an unchanging value. The difference is that a readonly member can be initialized at runtime, in a constructor as well being able to be initialized as they are declared. For example:

public class MyClass
  public readonly double PI = 3.14159;
public class MyClass
  public readonly double PI;
  public MyClass()
    PI = 3.14159;
Because a readonly field can be initialized either at the declaration or in a constructor, readonly fields can have different values depending on the constructor used. A readonly field can also be used for runtime constants as in the following example:

public static readonly uint l1 = (uint)DateTime.Now.Ticks;
  • readonly members are not implicitly static, and therefore the static keyword can be applied to a readonly field explicitly if required.
  • A readonly member can hold a complex object by using the new keyword at initialization.


Use of the static modifier to declare a static member, means that the member is no longer tied to a specific object. This means that the member can be accessed without creating an instance of the class. Only one copy of static fields and events exists, and static methods and properties can only access static fields and static events. For example:

public class Car
  public static int NumberOfWheels = 4;
The static modifier can be used with classes, fields, methods, properties, operators, events and constructors, but cannot be used with indexers, destructors, or types other than classes.
static members are initialized before the static member is accessed for the first time, and before the static constructor, if any is called. To access a static class member, use the name of the class instead of a variable name to specify the location of the member. For example:

int i = Car.NumberOfWheels;

Exposing 2 endpoints for same WCF service using different Bindings

I just created a simple which exposes a service through 2 different endpoints which uses different bindings.One is basicHttpBinding and another using wsHttpBinding.

Specifying 2 EndPoints 

If you have a basic idea about WCF you can easily understand the below configuration in web.config which exposes  Uploader service through 2 different end points.

<service behaviorConfiguration="DemoMTOM.Web.UploaderBehavior"  name="DemoMTOM.Web.Uploader">
<endpoint address="bh" binding="basicHttpBinding" contract="DemoMTOM.Web.IUploader">
<dns value="localhost"/>
<endpoint address="wh" binding="wsHttpBinding" contract="DemoMTOM.Web.IUploader">
<dns value="localhost"/>
<endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange"/>

In the sample the url to the basicHttpBinding endpoint is http://localhost:64738/Uploader.svc/bh and the url to the wsHttpBinding endpoint is http://localhost:64738/Uploader.svc/wh. You can check this by adding a service reference in to a WPF application. 

Creating ServiceClient to call the service in WPF
When we create service reference in the WPF application, the app.config in the WPF application will get 2 entries.One for basicHttpBinding and another for wsHttpBinding.See the sample app.config below.

<endpoint address="http://localhost:64738/Uploader.svc/bh" binding="basicHttpBinding"
bindingConfiguration="BasicHttpBinding_IUploader" contract="UploadServiceReference.IUploader"
name="BasicHttpBinding_IUploader" />
<endpoint address="http://localhost:64738/Uploader.svc/wh" binding="wsHttpBinding"
bindingConfiguration="WSHttpBinding_IUploader" contract="UploadServiceReference.IUploader"
<dns value="localhost" />

So at the calling side there will be confusion of course in selecting the end point.So to resolve that confusion we have to specify the endPointConfigurationName at the time of creating client. See code below which uses the basicHttpBinding.

UploadServiceReference.UploaderClient cli = new UploadServiceReference.UploaderClient("BasicHttpBinding_IUploader");
string res = cli.DoWork("Joy");

UploadServiceReference.UploaderClient cli = new UploadServiceReference.UploaderClient("WSHttpBinding_IUploader");
string res = cli.DoWork("Joy");

The second code snippet uses wsHttpBinding to call the service.

Hosting service using 2 endpoints in a Console Application

static void Main(string[] args)
        ServiceHost serviceHost =
new ServiceHost(typeof(Uploader),
new Uri("http://localhost:64738/Uploader.svc"));

typeof(IUploader), new BasicHttpBinding(), "bh");
typeof(IUploader), new WSHttpBinding(), "wh");

        ServiceMetadataBehavior smb =
new ServiceMetadataBehavior();
        smb.HttpGetEnabled =

        ServiceDebugBehavior sdb =  serviceHost.Description.Behaviors.Find<ServiceDebugBehavior>();
        sdb.IncludeExceptionDetailInFaults =


"Service running below are the Endpoints :");
foreach (ServiceEndpoint se in serviceHost.Description.Endpoints)
"Press any key to quit...");

catch (Exception ex)
string.Format("Error :{0}", ex.Message));

In the sample when you try to run the console application it will throw an error because the application also runs and uses the same port. So run the console application from command line or explorer.

There is no need to change the reference in the WPF application since both these console application and service host is using same url.

Popular Posts