This document describes how to implement a very common document compatibility mode, EmulateIE7, supported by Windows Internet Explorer 8, on a per-site basis, using custom headers in Internet Information Services (IIS).

Specifying Custom HTTP Response Headers
A document mode can be specified for your Web site by defining a custom header for the site using IIS Web server. To enable Microsoft IIS to define a custom HTTP response header that automatically renders all pages in EmulateIE7 mode, you can use the following web.config example.

XML
<?xml version=”1.0″ encoding=”utf-8″?>
<configuration>
<system.webServer>
<httpProtocol>
<customHeaders>
<clear />
<add name=”X-UA-Compatible” value=”IE=EmulateIE7″ />
</customHeaders>
</httpProtocol>
</system.webServer>
</configuration>
You can also configure IIS 7 on a Windows Server 2008-based computer to include a custom HTTP response header by following these steps:

Click Start, click Administrative Tools, and then click Internet Information Services (IIS) Manager.
In the connections pane, expand the node for the server, and then expand .
Click the Web site where you want to add the custom HTTP response header.
In the Web site pane, double-click in the section.
Under Actions, click Add.
In the Name box, type X-UA-Compatible.
In the Value box, type IE=EmulateIE7.
Click OK.
To configure IIS 6 and earlier versions to include a custom HTTP response header, follow these steps:

Click Start, click Run, type inetmgr.exe, and then click OK.
Expand the server you want and then expand Web Sites.
Right-click the Web site you want and then click Properties.
Click the HTTP Headers tab.
Under Custom HTTP headers, click Add.
In the Custom header name box, type X-UA-Compatible.
In the Custom header value box, type IE=EmulateIE7.
Click OK two times.
If you specify a default document compatibility mode using your Web server, you can override that setting by specifying a different document compatibility mode in a specific Web page. The mode specified within the Web page takes precedence over the mode specified by the server.

Silverlight is a client side technology, which means nothing has to be installed on the Web Server, and it would work regardless of the type of Web Server in use. However, I ran into a small issue when trying to activate the first Silver Light enabled Website in our Hosting environment. The Server must have the MIME types specified for the following file types:

• .xaml = application/xaml+xml
• .xap = application/x-silverlight-app

Once you add these two MIME Types to the Server, Silverlight works just fine.

Adding the MIME Types for Silverlight

In case you need further help on how to add the MIME Types, Here is a screen shot that shows where in the IIS MMC Snap-in you can add them:

Since it is fairly straight forward, I hope no further explanation is necessary.

If you add the MIME Types to the root Website, all Websites will have Silverlight enabled right away.

The Screen shot is from Windows Server 2003.

CREATE PROCEDURE Find_SPName_With_Text
@StringToSearch VARCHAR(100)
AS
SET @StringToSearch = ‘%’ + @StringToSearch + ‘%’
SELECT DISTINCT SO.NAME
FROM SYSOBJECTS SO (NOLOCK)
WHERE SO.TYPE = ‘P’
AND SO.NAME LIKE @StringToSearch
ORDER BY SO.Name
GO

CREATE PROCEDURE Find_Text_In_SP
@StringToSearch VARCHAR(100)
AS
SET @StringToSearch = ‘%’ +@StringToSearch + ‘%’
SELECT DISTINCT SO.Name
FROM sysobjects SO (NOLOCK)
INNER JOIN syscomments SC (NOLOCK) on SO.Id = SC.ID
AND SO.Type = ‘P’
AND SC.Text LIKE @stringtosearch
ORDER BY SO.Name
GO

    <script type=”text/javascript” src=”http://ecn.dev.virtualearth.net/mapcontrol/mapcontrol.ashx?v=6.2″></script>

    <script type=”text/javascript”>
        var map = null;
        function GetMap() {
            map = new VEMap(‘myMap’);
            map.LoadMap();
            var options = new VERouteOptions();
            options.RouteCallback = onGotRoute;
            map.GetDirections(["Microsoft", "Everett WA", "Bellingham WA"], options);
        }
        function onGotRoute(route) {
            // Unroll route          
            var legs = route.RouteLegs;
            var turns = “Total distance: ” + route.Distance.toFixed(1) + ” mi\n”;
            var numTurns = 0; var leg = null;
            // Get intermediate legs           
            for (var i = 0; i < legs.length; i++) {
                // Get this leg so we don’t have to derefernce multiple times              
                leg = legs[i];
                // Leg is a VERouteLeg object                                
                // Unroll each intermediate leg              
                var turn = null;  // The itinerary leg                                
                for (var j = 0; j < leg.Itinerary.Items.length; j++) {
                    turn = leg.Itinerary.Items[j];
                    // turn is a VERouteItineraryItem object
                    numTurns++;
                    turns += numTurns + “.\t” + turn.Text + ” (” + turn.Distance.toFixed(1) + ” mi)\n”;
                }
            }
            alert(turns);
        }   
    </script>

</head>
<body onload=”GetMap();”>
    <div id=’myMap’ style=”position: relative; width: 400px; height: 400px;”>
    </div>
</body>
</html>

<Window x:Class=”Window1″
    xmlns=”http://schemas.microsoft.com/winfx/2006/xaml/presentation“
    xmlns:x=”http://schemas.microsoft.com/winfx/2006/xaml“
    Title=”Window1″ Height=”368″ Width=”322″>
    <Grid>
        <Button Height=”35″ VerticalAlignment=”Top” Margin=”38,26,40,0″ Click=”Button_Click”>
            This is simple button
        </Button>
        <Button Margin=”38,82,100,108″ Click=”Button1_Click”>
            <StackPanel>
                <Image Source=”Water lilies.jpg” Height=”73″ Width=”97″></Image>
                <TextBlock FontWeight=”Bold” FontSize=”25″>Hi</TextBlock>
            </StackPanel>
        </Button>
        <Button Height=”61″ VerticalAlignment=”Bottom” Margin=”38,0,65,22″ Content=”Brush button”>
            <Button.Background>
                <LinearGradientBrush EndPoint=”0.5,1″ StartPoint=”0.5,0″>
                    <GradientStop Color=”#FFFFFFFF” Offset=”1″/>
                    <GradientStop Color=”#FFDB8120″ Offset=”0.42″/>
                </LinearGradientBrush>
            </Button.Background>
        </Button>
    </Grid>
</Window>

OUTPUT

XAML stands for Extensible Application Markup Language. Its a simple language based on XML to create and initialize .NET objects with hierarchical relations. Altough it was originally invented for WPF it can by used to create any kind of object trees.

Today XAML is used to create user interfaces in WPF, Silverlight, declare workflows in WF and for electronic paper in the XPS standard.

All classes in WPF have parameterless constructors and make excessive usage of properties. That is done to make it perfectly fit for XML languages like XAML.

Advantages of XAML

All you can do in XAML can also be done in code. XAML ist just another way to create and initialize objects. You can use WPF without using XAML. It’s up to you if you want to declare it in XAML or write it in code. Declare your UI in XAML has some advantages:

• XAML code is short and clear to read
• Separation of designer code and logic
• Graphical design tools like Expression Blend require XAML as source.
• The separation of XAML and UI logic allows it to clearly separate the roles of designer and developer.

XAML vs. Code

As an example we build a simple StackPanel with a textblock and a button in XAML and compare it to the same code in C#.

 <StackPanel>

    <TextBlock Margin=”20″>Welcome to the World of XAML</TextBlock>

    <Button Margin=”10″ HorizontalAlignment=”Right”>OK</Button>

</StackPanel>

The same expressed in C# will look like this:

// Create the StackPanel

StackPanel stackPanel = new StackPanel();

this.Content = stackPanel;

// Create the TextBlock

TextBlock textBlock = new TextBlock();

textBlock.Margin = new Thickness(10);

textBlock.Text = “Welcome to the World of XAML”;

stackPanel.Children.Add(textBlock);

// Create the Button

Button button = new Button();

button.Margin= new Thickness(20);

button.Content = “OK”;

stackPanel.Children.Add(button);

   As you can see is the XAML version much shorter and clearer to read. And that’s the power of XAMLs expressiveness.

Properties as Elements

Properties are normally written inline as known from XML

<Button Content=”OK” />.

But what if we want to put a more complex object as content like an image that has properties itself or maybe a whole grid panel? To do that we can use the property element syntax. This allows us to extract the property as an own chlild element.

<Button> 

<Button.Content>     

<Image Source=”Images/OK.png” Width=”50″ Height=”50″ />  

</Button.Content>

</Button>

Implicit Type conversion

A very powerful construct of WPF are implicit type converters. They do their work silently in the background. When you declare a BorderBrush, the word “Blue” is only a string.

The implicit BrushConverter makes a System.Windows.Media.Brushes.Blue out of it. The same regards to the border thickness that is beeing converted implicit into a Thickness object. WPF includes a lot of type converters for built-in classes, but you can also write type converters for your own classses.

<Border BorderBrush=”Blue” BorderThickness=”0,10″> </Border>

Markup Extensions

Markup extensions are dynamic placeholders for attribute values in XAML. They resolve the value of a property at runtime. Markup extensions are surrouded by curly braces (Example: Background=”{StaticResource NormalBackgroundBrush}”). WPF has some built-in markup extensions, but you can write your own, by deriving from MarkupExtension. These are the built-in markup extensions:

• Binding
  To bind the values of two properties together.
• StaticResource
  One time lookup of a resource entry
• DynamicResource
  Auto updating lookup of a resource entry
• TemplateBinding
  To bind a property of a control template to a dependency property of the control
• x:Static
  Resolve the value of a static property.
• x:Null
  Return null

The first identifier within a pair of curly braces is the name of the extension. All preciding identifiers are named parameters in the form of Property=Value. The following example shows a label whose Content is bound to the Text of the textbox. When you type a text into the text box, the text property changes and the binding markup extension automatically updates the content of the label.

<TextBox x:Name=”textBox”/>

<Label Content=”{Binding Text, ElementName=textBox}”/>

Namespaces

At the beginning of every XAML file you need to include two namespaces.
The first is http://schemas.microsoft.com/winfx/2006/xaml/presentation. It is mapped to all wpf controls in System.Windows.Controls.
The second is http://schemas.microsoft.com/winfx/2006/xaml it is mapped to System.Windows.Markup that defines the XAML keywords.
The mapping between an XML namespace and a CLR namespace is done by the XmlnsDefinition attribute at assembly level. You can also directly include a CLR namespace in XAML by using the clr-namespace: prefix.

<Window xmlns=”http://schemas.microsoft.com/winfx/2006/xaml/presentation”         xmlns:x=”http://schemas.microsoft.com/winfx/2006/xaml”>
</Window>

SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER ON

GO

SET ANSI_PADDING ON

GO

– CREATE TABLE EMPLOYEE

CREATE TABLE [dbo].[tbl_Employee](

      [FirstName] [varchar](50) NOT NULL,

      [LastName] [varchar](50) NOT NULL,

      [Salary] [money] NOT NULL,

      [EmpID] [varchar](10) NULL

) ON [PRIMARY]

GO

SET ANSI_PADDING OFF

GO

– INSERT DATE INTO EMPLOYEE

INSERT [tbl_Employee](FirstName,LastName,Salary,EmpID) VALUES(‘David’,'Lichtenstien’,convert(money,’17000.00′),’100′)

INSERT [tbl_Employee](FirstName,LastName,Salary,EmpID) VALUES(‘Adam ‘,’Malley’,convert(money,’22000.00′),’101′)

INSERT [tbl_Employee](FirstName,LastName,Salary,EmpID) VALUES(‘Raquel ‘,’Clementine’,convert(money,’25000.00′),’102′)

INSERT [tbl_Employee](FirstName,LastName,Salary,EmpID) VALUES(‘Ian ‘,’Thomas’,convert(money,’35000.00′),’103′)

INSERT [tbl_Employee](FirstName,LastName,Salary,EmpID) VALUES(‘Delilah ‘,’Swanson’,convert(money,’40000.00′),’104′)

INSERT [tbl_Employee](FirstName,LastName,Salary,EmpID) VALUES(‘Maria’,'Sanchez’,convert(money,’17000.00′),’107′)

INSERT [tbl_Employee](FirstName,LastName,Salary,EmpID) VALUES(‘Walk’,'In’,convert(money,’17000.00′),’108′)

– SELECT SECOND HIGHEST SALARY FIRST METHOD

SELECT MAX(Salary) FROM tbl_Employee

      WHERE salary NOT IN (SELECT MAX(Salary) FROM  tbl_Employee)

SELECT  FirstName,LastName,Salary FROM tbl_Employee

      WHERE salary = (SELECT MAX(Salary) FROM tbl_Employee

                                    WHERE Salary NOT IN (SELECT MAX(Salary) FROM  tbl_Employee))

– SELECT SECOND HIGHEST SALARY SECOND METHOD

SELECT MAX(Salary) FROM tbl_Employee

      WHERE Salary < (SELECT MAX(Salary) FROM  tbl_Employee)

SELECT  FirstName,LastName,Salary FROM tbl_Employee

      WHERE Salary = (SELECT MAX(Salary) FROM tbl_Employee

                                    WHERE Salary < (SELECT MAX(Salary) FROM  tbl_Employee))

Enjoy……

To Use it run this script in your database.

SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO

CREATE PROC MyInsertScriptGenerator
(
 @tableName varchar(100)
)
AS

–Declare a cursor to retrieve column specific information for the specified table
DECLARE cursCol CURSOR FAST_FORWARD FOR
SELECT column_name,data_type FROM information_schema.columns WHERE table_name = @tableName
OPEN cursCol
DECLARE @string nvarchar(3000) –for storing the first half of INSERT statement
DECLARE @stringData nvarchar(3000) –for storing the data (VALUES) related statement
DECLARE @dataType nvarchar(1000) –data types returned for respective columns
SET @string=’INSERT ‘+@tableName+’(‘
SET @stringData=”

DECLARE @colName nvarchar(50)

FETCH NEXT FROM cursCol INTO @colName,@dataType

IF @@fetch_status<>0
 begin
 print ‘Table ‘+@tableName+’ not found, processing skipped.’
 close curscol
 deallocate curscol
 return
END

WHILE @@FETCH_STATUS=0
BEGIN
IF @dataType in (‘varchar’,'char’,'nchar’,'nvarchar’)
BEGIN
 SET @stringData=@stringData+””+”’+isnull(””’+””’+'+@colName+’+””’+””’,”NULL”)+”,”+’
END
ELSE
if @dataType in (‘text’,'ntext’) –if the datatype is text or something else
BEGIN
 SET @stringData=@stringData+””””’+isnull(cast(‘+@colName+’ as varchar(2000)),””)+”””,”+’
END
ELSE
IF @dataType = ‘money’ –because money doesn’t get converted from varchar implicitly
BEGIN
 SET @stringData=@stringData+”’convert(money,”””+isnull(cast(‘+@colName+’ as varchar(200)),”0.0000”)+”””),”+’
END
ELSE
IF @dataType=’datetime’
BEGIN
 SET @stringData=@stringData+”’convert(datetime,’+”’+isnull(””’+””’+convert(varchar(200),’+@colName+’,121)+””’+””’,”NULL”)+”,121),”+’
END
ELSE
IF @dataType=’image’
BEGIN
 SET @stringData=@stringData+””””’+isnull(cast(convert(varbinary,’+@colName+’) as varchar(6)),”0”)+”””,”+’
END
ELSE –presuming the data type is int,bit,numeric,decimal
BEGIN
 SET @stringData=@stringData+””+”’+isnull(””’+””’+convert(varchar(200),’+@colName+’)+””’+””’,”NULL”)+”,”+’
END

SET @string=@string+@colName+’,’

FETCH NEXT FROM cursCol INTO @colName,@dataType
END
DECLARE @Query nvarchar(4000)

SET @query =’SELECT ”’+substring(@string,0,len(@string)) + ‘) VALUES(”+ ‘ + substring(@stringData,0,len(@stringData)-2)+”’+”)” FROM ‘+@tableName
exec sp_executesql @query
–select @query

CLOSE cursCol
DEALLOCATE cursCol

GO
SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO

To Generate the insert script for your table you need to specify the table name.

here employee is your sql table

e.g  MyInsertScriptGenerator ‘employee’

Enjoy….

Presentation Framework, including large number of standard controls i.e. Button, Label, Menu, panels, and other types of controls. The vast majority of Windows Presentation Foundation developers will work exclusively with this layer.

PresentationCore.dll includes base types, such as UIElement and Visual, from which all shapes and controls derive.

WindowsBase.dll includes even more basic things that have the potential to be reused outside of WPF, such as DispatcherObject and DependencyObject,

Milcore.dll is the core of the WPF rendering system and the foundation of the Media Integration Layer (MIL). Its composition engine translates visual elements into the triangle and textures that Direct3D expects. Though milcore.dll is considered a part of WPF, it’s also an essential system component for Windows Vista. The Desktop Window Manager (DWM) in Windows Vista uses milcore.dll to render the desktop.

WindowsCodecs.dll is a low-level API that provides imaging support (e.g., processing, displaying, and scaling bitmaps and JPEGs).

Direct3D is the low-level API through which all the graphics in a WPF are rendered.

User32 is used to determine what program gets what real estate. As a result, it’s still involved in WPF, but it plays no part in rendering common controls.