Sunny's Dev

The IIS Live Smooth Streaming extension for Internet Information Services (IIS) 7 allows you to set up a Web server as a Live Smooth Streaming server that delivers compelling, uninterrupted live video streams that instantly adjust quality (bit rate) to match changing network and CPU conditions at the client.

Live Smooth Streaming enables adaptive streaming of live events to Smooth Streaming-compatible clients, such as Microsoft Silverlight. Using HTTP to deliver a live Web broadcast leverages the scale of existing HTTP networks by keeping content close to the user and making true HD (720p+) a realistic option for Web broadcasts. The additional advantage of using HTTP-based delivery for live events is that the existing HTTP infrastructure provides much more availability. For many popular live Web broadcasts, content providers and content distribution networks (CDNs) want to know how much capacity they can dedicate on their resource-constrained streaming networks. By using their primary HTTP networks, which are typically 10-to-20-times larger than their streaming networks, they don't have to worry about maximizing network capacity and limiting the number of users for live events.

A Live Smooth Streaming server sources content from Live Smooth Streaming-capable encoders for delivery to Smooth-Streaming compatible clients. In addition to Microsoft Expression Encoder, there are many third-party encoding solutions available for encoding both live and on-demand Smooth Streaming video in production environments. To help you determine which encoding solution is best-suited for your Smooth Streaming configuration, see the list of our encoding parters.

In this walkthrough:

• Setting Up a Live Smooth Streaming Web Server
• Creating a Live Smooth Streaming Publishing Point
• Pushing a Stream to the Live Smooth Streaming Publishing Point
• Serving the Live Stream to Clients

Setting Up a Live Smooth Streaming Web Server

To install IIS Live Smooth Streaming, see the IIS Media Services Readme Installation Notes. This walkthrough describes how to set up a Live Smooth Streaming server using IIS Live Smooth Streaming in IIS Media Services 4.0, so be sure to select this version of IIS Media Services for installation.

After installation is completed, to verify that the Live Smooth Streaming extension is installed correctly, click the server name in the Connections pane in IIS Manager and locate the Live Smooth Streaming icon in the Media Services area.

Note If IIS Manager was running during the installation process, you may need to restart it to see Live Smooth Streaming.

Creating a Live Smooth Streaming Publishing Point

This section describes how to create a publishing point that can accept a live broadcast from a Live Smooth Streaming-capable encoder.

1. In IIS Manager, select the desired Web Site or virtual directory, and then double-click the Live Smooth Streaming Publishing Points icon.
   
   
2. On the Live Smooth Streaming Publishing Points page, in the Actions pane, click Add.
   
   
3. In the Add Publishing Point dialog box, on the Basic Settings tab, enter the following information:
   
   
• File name. Enter a name for the Live Smooth Streaming publishing point definition file. In this example and throughout the rest of this walkthrough, we use the file name LiveSmoothStream. If you specify a different file name, be sure to substitute it appropriately as you follow the steps in this walkthrough.
• Estimated duration. If known, enter the duration (in hours:minutes:seconds) of the live event so that the Silverlight-based client can scale its Seek bar to the length of the content. In our example, we use an event duration of 1 hour (01:00:00).
• Live source type. In our example, the Live Smooth Streaming server is an "origin server" that receives the content that is pushed to it from an encoder; therefore, we select the default Push option.
  
  Note The Pull option for Live source type configures the publishing point to "pull" content from a publishing point on another Live Smooth Streaming server. This is a common configuration for syndication of content. For more information, see Live Smooth Streaming for IIS 7 - Syndicating Content between Servers.
  
4. On the Advanced Settings tab, select the Start publishing point automatically upon first client request check box. This setting allows an encoder to connect to the publishing point when the broadcast starts. Connection errors might occur if you don't enable this setting.
   
   
   For more information about the additional settings that you can configure on the Advanced Settings tab, see Add/Edit Dialog Box.
   
5. If you want to deliver live streams to Apple® mobile digital devices, on the Mobile Devices tab, select the Enable output to Apple mobile digital devices check box.
   
   
   Important Before proceeding, be sure to check out the the following walkthrough article for more information about the requirements and publishing point configuration for Apple HTTP Live Smooth Streaming: Apple HTTP Live Streaming with IIS Media Services.
   
6. In the Add Publishing Point dialog box, click OK. A newly created Live Smooth Streaming publishing point definition file named LiveSmoothStream.isml is added to the Web site root.
   
   
7. On the Live Smooth Streaming Publishing Points page, select the publishing point, and then in the Actions pane, click Start Publishing Point.
   
   
8. The publishing point State value changes from Idle to Starting, which means it is waiting for external data (in this case, a live stream pushed to it from an encoder).
   
   
   Because we have not yet configured an encoder to push live streams to the publishing point, the Publishing Point Summary panel shows that there are no incoming streams.
   
   Note The Summary panel for Live Smooth Streaming publishing points is new in IIS Media Services 4.0 and is used to display summary information about the live Smooth Streams that are received from all live sources (such as encoders or other Live Smooth Streaming publishing points) by the selected publishing point. You can also view details about the tracks within all of the live streams, and stream origin and destination information, in a new Publishing Point Details page. For more information, see Viewing Publishing Point Details.
   
   Note After the publishing point begins receiving data from an encoder, its State value changes to Started. However, due to a known issue, the change in the State value isn't visible until after you refresh the Live Smooth Streaming Publishing Points page in IIS Manager.
   
9. See the next section, which describes how to configure Microsoft Expression Encoder to push data to this publishing point.

Pushing a Stream to the Live Smooth Streaming Publishing Point

This section describes how to create a Live Smooth Streaming broadcast in Microsoft Expression Encoder 4 and push it to the Live Smooth Streaming publishing point that you configured in the previous section. The steps in this section outline a general workflow, with details only on the specific tasks that you need to create Live Smooth Streaming output. For detailed information about how to create a live broadcast from various live and file-based sources in Expression Encoder 4, including how to assemble a complete program, encode it, encrypt it with Digital Rights Management (DRM), and instantly distribute it to your audience using Smooth Streaming technology, see Creating a Live Broadcasting Project.

Important If you enabled the publishing point to stream content to Apple devices, such as iPhone® and iPad™ devices, be sure to review the encoding requirements and settings outlined in Apple HTTP Live Streaming with IIS Media Services.

Note Live Smooth Streaming is available only in Microsoft Expression Encoder Pro.

1. Start Expression Encoder (click Start > All Programs > Microsoft Expression > Microsoft Expression Encoder 4).
2. In the Load a new project dialog box, select Live Broadcasting Project, and then click OK.
   
   
3. Set up the source to use for your live broadcast. For File Sources, you can use audio or video sources in any file format that Expression Encoder can import. For Live Sources, you can connect multiple camera devices, such as USB webcams or FireWire (IEEE 1394) digital video cameras. Although you can connect multiple live sources, you can stream only one at a time.
   
4. On the Presets tab, choose an encoding preset that supports the bit rates and encoding requirements for your Live Smooth Streaming Scenario. Be sure to choose a preset with IIS Smooth Streaming in the preset name, and then click Apply.
   
   
   To find out more information about a preset, such as the numbers of streams in the output and the codecs used, hover your mouse pointer over a preset name. The preset information is displayed in a box.
   
   Note Clicking the Apply button automatically updates the Output Format, Video, and Audio settings on the Encode tab with the values used by the selected preset.
   
   
   You can choose to not select a preset and specify your own values for the Output Format, Video, and Audio options on the Encode tab instead.
   
5. On the Output tab, select the Streaming check box to activate streaming.
   
   
   With Streaming selected on the Output tab, your only choice for publishing your content is to use the Publishing Point option, which is automatically selected (If it isn't selected, select it). In the Location box, type the URL of the Live Smooth Smooth Streaming publishing point that you want to publish your live broadcast to.
   
   
   URL syntax: http://ServerName/SiteName/DirectoryName/PublishingPointDefinitionFileName.isml
   
   For the example Live Smooth Streaming publishing point that we created in the previous section, the URL would be:
   
   http://IISMedia-Server/LiveSmoothStream.isml
   
   Note You can click the Connect button to test the connection to the publishing point after you specify its URL in the Location box. The publishing point must be started for the connection to be validated.
   
6. If you want to add Digital Rights Management (DRM) to your content, select the Digital Rights Management check box on the Output tab, and then type the License URL (the server that supplies the license), the Key ID, and the Key Seed (available from the license provider). For more information, see Set DRM options.
   
   Note The license provided for a Live Smooth Streaming session is non-persistent, meaning that after the user closes the client application being used to view the Web broadcast, the license expires.
   
   Important You should not use this setting if you want to stream the content to Apple devices. To provide protected content to Apple devices, you can configure the Live Smooth Streaming publishing point to encrypt the content by using the Advanced Encryption Standard (AES) with a 128-bit key. For more information about how to configure Apple AES-128 encryption, see Add/Edit Dialog Box.
   
7. Click Cue to enable your source for broadcasting (a cued file source is shown in the following figure)...
   
   
   ...and then click Start to begin your live broadcast.
   
   
   As the broadcast runs, you can monitor Statistics and Connections data in the corresponding panels.

Serving the Live Stream to Clients

This section describes how to use the Microsoft Silverlight Media Framework 2.0 SmoothStreamingPlayer.XAP, a sample player that can easily be embedded in your Web site to enable client playback of Smooth Streaming media.

Important Apple devices use an HTML 5 Web page to play the Live Smooth Streaming presentation. If you enabled the publishing point to stream content to Apple devices, see Creating an HTML 5 page for use in Safari.

Note The latest version of Microsoft Silverlight must be installed on the client computer that you want to use to observe Live Smooth Streaming.

1. On the Web server, click the following link to download the sample player executable file: SmoothStreamingPlayer.exe.
2. To extract the sample player files immediately, click Run.
   -or-
   To copy the sample player files to your Web server in order to extract them at a later time, click Save, and then open the file from the saved location.
3. When you are prompted for a location to store the extracted sample player files, enter the directory path of a temporary folder on your desktop. For example:
   
   
4. Open the temporary desktop folder, review the terms in the End User License Agreement (EULA) file, and then right-click the zipped folder and click Extract All to extract the sample player files.
   
   
5. When you are asked to select the destination folder to which the sample player files will be extracted, select a Web site or virtual directory that you want to use for client access to the live broadcast. In our example, we extract the files to the default Web site, which also contains the Live Smooth Streaming publishing point definition file (LiveSmoothStream.isml).
   
   
6. To view the sample player files, in IIS Manager, open the Web site or virtual directory in Content View.
   
   
   The following files are included in the download:
   • Smooth Streaming Player-ReadMe.doc. Configuration instructions.
   • SmoothStreamingPlayer.html. A sample Web page in which you must update the media reference to your live broadcast, and if necessary, width and height attributes to achieve a presentation size that fits your Web site design.
   • SmoothStreamingPlayer.xap. A sample Smooth Streaming player.
     
7. In a text editor, such as Notepad, open SmoothStreamingPlayer.html and update the mediaurl attribute value with the fully qualified URL of the Live Smooth Streaming publishing point definition (.isml) file. In our example, this is:
   
   http://IISMedia-Server/LiveSmoothStream.isml/manifest
   
   If necessary, also update the width and height attributes to appropriate values for your Web site design. For complete instructions, see the Readme file (Smooth Streaming Player-ReadMe.doc).
   
8. In a Web browser on the client computer, download the sample Web page from the Web server and begin viewing the stream. In our example, in the Web browser address bar, type http://IISMedia-Server/SmoothStreamingPlayer.html.
   
   The Live Smooth Streaming broadcast opens in the Web browser, using the Silverlight browser plug-in for Live Smooth Streaming.
   

For more information about how to to build rich Silverlight user experiences that take full advantage of live and on-demand IIS Smooth Streaming capabilities, see the Smooth Streaming Client Web page.

출처 : http://learn.iis.net/page.aspx/620/getting-started-with-iis-live-smooth-streaming/

오늘은 Silverlight를 주제와 관련된 정보를 정리했습니다.
아래에 보는 링크는 Silverlight를 배울 수 있는 링크를 정리했습니다.

아래 내용만 잘 따라가셔도 충분한 기본 스킬을 확보 할 수 있을 만큼 좋은 자료들 입니다.

아래 자료는 추가적인 Hands On Lab 입니다.

앞으로도 자주 뵙겠습니다.
감사합니다.

출처 : http://blogs.msdn.com/b/eva/archive/2011/08/08/eva-news-letter-2011-08-08-silverlight.aspx

Important methods, properties for OOB in Silverlight

Application.IsRunningOutOfBrowser (Gets a value that indicates whether the application was launched from the out-of-browser state.)
Application.Install() (Attempts to install the application so that it can run outside the browser.)
Application.InstallState (Gets the current out-of-browser installation state of the application.)
InstallState Enumeration (Defines constants that indicate the installation state of an application that is configured to run outside the browser.)

A complete guidance on Out of Browser Support in Silverlight.

Where to find installed OOB applications?

A list of all silverlight applications is available in a hidden folder
C:\Users\{user name}\AppData\LocalLow\Microsoft\Silverlight\OutOfBrowser\
Notice also a folder sibling …\Silverlight\is\ which is an isolated storage for running Silverlight apps.

Name of the files in this folder is done by the address of the location (e.g. localhost, microsoft.com). Most of these files are empty, but those which are installed for OOB mode has some information within. Open that file and you will see the ID of the application and the whole URL where the original (web version) is located. ID with name of file creates ApplicationID (e.g. 972856442.localhost, 3326975874.zdechovan.com) which we will use to launch our application in a section below.

How to launch a Silverlight OOB?

There is an application sllauncher.exe, that is used to launch Silverlight application in Out of Browser mode. This application is located in C:\Program Files\Microsoft Silverlight\sllauncher.exe.

To run a silverlight application you have to pass some parameters to this sllauncher, if you try to run it without any of them, you’ll see the usage pattern:

SLLauncher.exe [app_id] [debug] [/install:<file path to XAP>]
[/emulate:<file path to XAP>] [/overwrite] /origin:<original app uri>
/uninstall /shortcut:<desktop|startmenu|desktop+startmenu|none> [/pid]

You can experiment with a lots of variations of parameters set up if you wish, for me, the most importat is to set a shortcut, which will launch our application. It’s because I experienced a problem, that after install from application the shortcut was corrupted and didn’t work.

Working shortcut should contain {path to sllauncher}/sllauncher.exe {ApplicationId} so for example C:\Program Files\Microsoft Silverlight\sllauncher.exe 972856442.localhost in my case.

If you want to debug your OOB application simply add a debug parameter.

I found an article Installing Silverlight applications without the browser involved by Tim Heuer about how to use  sllauncher to install/uninstall a silverlight application.

Smooth Streaming UI : http://silverlightsdk.net/37
Smooth Streaming 설정 : http://silverlightsdk.net/38

XAML코드와 Window Loaded Event부분은 UI구성에 필요한 부분이므로 설명은 생략하도록 하겠습니다. ScrollPanel Class를 살펴보겠습니다. ScrollPanel은 생성자로 스크롤이 될 Target Control을 입력받으며 내부적으로 Target과 Target의 부모를 가지고 있습니다. 그리고 MouseEvent 가 발생할 경우 에 따라서 움직이는 Animation을 적용시켰습니다. 코드를 보고 이해가 안되는 부분이나 추가 설명이 필요하신 부분은 리플 달아주세요.

아래는 전체 소스코드 파일입니다.

IPhoneScroll.zip

This is the way how I implemented paging among a wrap panel in WPF. For this example I used simple buttons inside the wrap panel. My example dynamically takes the height of the control inside the wrap panel to determine the quantity of controls that the wrap panel must show.

In this example the columns always stay static, 1 column Min and 2 columns Max. You can also create a column function to show dynamically the quantity of columns you want.

The result is this:

This is the window when is loaded:

This is the window when is resized:

XAML:

<Window x:Class=”PagingWrapPanel.PagingWithDuff”

xmlns=”http://schemas.microsoft.com/winfx/2006/xaml/presentation”

xmlns:x=”http://schemas.microsoft.com/winfx/2006/xaml”

Title=”PagingWithDuff” Height=”250″ Loaded=”Window_Loaded”

MaxHeight=”500″ MinHeight=”120″ MaxWidth=”500″ MinWidth=”500″>

<Grid>

<Grid.RowDefinitions>

<RowDefinition />

<RowDefinition Height=”24″ />

<RowDefinition Height=”26″ />

</Grid.RowDefinitions>

<ItemsControl Grid.Row=”0″ Name=”RowsContainer” Background=”Transparent” ItemsSource=”{Binding}” SizeChanged=”RowsContainer_SizeChanged” >

<ItemsControl.ItemTemplate>

<DataTemplate>

<Label />

</DataTemplate>

</ItemsControl.ItemTemplate>

<ItemsControl.ItemsPanel>

<ItemsPanelTemplate>

<WrapPanel Orientation=”Vertical” IsItemsHost=”True”

Width=”Auto” HorizontalAlignment=”Center” />

</ItemsPanelTemplate>

</ItemsControl.ItemsPanel>

</ItemsControl>

<Grid Grid.Row=”1″ HorizontalAlignment=”Center” >

<Label Name=”label1″ VerticalAlignment=”Top” Height=”Auto” >Page 1 out of 1</Label>

</Grid>

<Grid Grid.Row=”2″ >

<Grid.ColumnDefinitions>

<ColumnDefinition Width=”*”/>

<ColumnDefinition Width=”*” />

</Grid.ColumnDefinitions>

<Button Grid.Column=”0″ x:Name=”btnBack” Click=”btnBack_Click” MaxHeight=”25″ >Back</Button>

<Button Grid.Column=”1″ x:Name=”btnNext” Click=”btnNext_Click” MaxHeight=”25″ >Next</Button>

</Grid>

</Grid>

</Window>

By the way, you must change in the App.xaml the StartupUri string to - StartupUri=”PagingWrapPanel.xaml” -

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Windows;
using System.Windows.Controls;
using System.Windows.Data;
using System.Windows.Documents;
using System.Windows.Input;
using System.Windows.Media;
using System.Windows.Media.Imaging;
using System.Windows.Navigation;
using System.Windows.Shapes;
using System.Collections.ObjectModel;

namespace PagingWrapPanel

{

///

/// Interaction logic for Window1.xaml

///

public partial class PagingWithDuff : Window

{

ObservableCollection<Label> collection;

WrapPanel currentPanel;

int rowsInPanel, pagingPressed;

double height;

//RowsContainer SizeChanged event is raised before the Loaded event for this class

//We need to raise Loaded event first, using this variable

bool isLoaded;

public PagingWithDuff()

{

InitializeComponent();

collection = new ObservableCollection<Label>();

isLoaded = false;

//Generate 100 Labels to Page

for (int generator = 1; generator <= 100; generator++)

{

Label newLbl = new Label();

newLbl.Name = “Label” + generator;

newLbl.Content = “Label “ + generator;

newLbl.Width = 160;

newLbl.Background = Brushes.Black;

newLbl.Foreground = Brushes.White;

newLbl.HorizontalContentAlignment = HorizontalAlignment.Center;

collection.Add(newLbl);

}

btnBack.IsEnabled = false;

btnNext.IsEnabled = false;

pagingPressed = 1;

RowsContainer.DataContext = collection;

}

//Calculate how many rows will be showed in the container

public int rowsToShow()

{

currentPanel = VisualTreeHelper.GetChild(VisualTreeHelper.GetChild(VisualTreeHelper.GetChild(RowsContainer, 0), 0), 0) as WrapPanel;

int rows = 0;

height = this.currentPanel.ActualHeight;

double RowControlHeight = 0.0;

//Get the first Visible Label in the Panel and get its Height

for (int iterator = 0; iterator <= collection.Count - 1; iterator++)

{

Visibility isVisible = (Visibility)(currentPanel.Children[iterator] as Label).Visibility;

//If is visible get height and break iteration

if (isVisible == Visibility.Visible)

{

RowControlHeight = (double)(currentPanel.Children[iterator] as Label).ActualHeight;

break;

}

}

rows = (int)Math.Floor((decimal)height / (decimal)RowControlHeight);

return rows;

}

//Shows the controls inside the wrap panel

public void setRowsControlsToShow()

{

bool endOfList = false;

bool startOfList = false;

bool medOfList = false;

bool overflow = false;

int collectionCount = 0;

collectionCount = collection.Count;

//Once the datacontext is displayed, we need to show up only the labels in this case we need

if (RowsContainer.Items.Count > 0)

{

int start = PagingWithDuff.startFromIndex(rowsToShow(), pagingPressed);

int end = PagingWithDuff.endInIndex(start, rowsToShow() * 2);

if (start > collectionCount - 1)

//If this happens, means that the panel have no content to show

{

end = collectionCount - 1;

start = (collectionCount - 1) - rowsToShow();

overflow = true;

}

if (start == 0) startOfList = true;

if (end > collectionCount)

{

end = collectionCount - 1;

endOfList = true;

}

else

{

if (!startOfList && !endOfList) { medOfList = true; }

}

for (int iter = 0; iter <= collectionCount - 1; iter++)

{

Label currentRow = currentPanel.Children[iter] as Label;

if ((iter < start) || (iter > end))

{

currentRow.Visibility = Visibility.Collapsed;

}

else

{

currentRow.Visibility = Visibility.Visible;

}

}

if (endOfList)

{

btnNext.IsEnabled = false;

if (pagingPressed > 1) btnBack.IsEnabled = true;

}

else

btnNext.IsEnabled = true;

if (medOfList)

{

if (end <= collectionCount - 1)

{

btnBack.IsEnabled = true;

}

}

if (startOfList)

{

btnBack.IsEnabled = false;

if ((rowsInPanel * 2) <= collectionCount)

btnNext.IsEnabled = true;

}

if (overflow)

{

btnNext.IsEnabled = false;

pagingPressed -= 1;

}

}

else

{

btnNext.IsEnabled = false;

btnBack.IsEnabled = false;

}

}

public void setPagingInfo()

{

int totalQty = collection.Count;

rowsInPanel = rowsToShow();

int totalPages = (int)Math.Floor((double)totalQty / rowsInPanel);

if (totalPages == 0)

{

totalPages = 1;

btnNext.IsEnabled = false;

btnBack.IsEnabled = false;

}

if (pagingPressed > totalPages)

this.label1.Content = “Page “ + totalPages + ” out of “ + totalPages;

else

this.label1.Content = “Page “ + pagingPressed + ” out of “ + totalPages;

}

private static int startFromIndex(int qtyToShow, int page)

{

if (page == 1) return 0;

return ((page - 1) * qtyToShow);

}

private static int endInIndex(int start, int qtyToShow)

{

return (start + qtyToShow) - 1;

}

private void Window_Loaded(object sender, RoutedEventArgs e)

{

setRowsControlsToShow();

setPagingInfo();

isLoaded = true;

}

private void RowsContainer_SizeChanged(object sender, SizeChangedEventArgs e)

{

if (isLoaded)

{

setRowsControlsToShow();

setPagingInfo();

}

}

private void btnNext_Click(object sender, RoutedEventArgs e)

{

pagingPressed++;

setRowsControlsToShow();

setPagingInfo();

}

private void btnBack_Click(object sender, RoutedEventArgs e)

{

pagingPressed -= 1;

setRowsControlsToShow();

setPagingInfo();

}

}

}

하지만 WPF에서 위에 방법을 App.xaml.cs 에 적용시켜도 원하는 데로 동작하지 않습니다.
그래서 오늘은 WPF에서 사용할 수 있는 방법을 올려드리겠습니다.
아래 예제는 뮤텍스를 사용한 중복 방지 소스를 구글링해서 힘들게 찾은 소스입니다.
제가 잘 동작하는 것은 확인 하였습니다. 이 밖에 다른 예제 소스도 보여드리겠습니다만 아래 예제를 쓰시는 것이 가장 좋습니다.

위에 예제는 OnStartUp이벤트와 Mutex의 WaitOne을 이용하여 중복방지를 구현하였습니다.



그럼 이번에는 약간 다른 방법으로 구현해 보겠습니다.
이 방법은 WPF 초기화를 C# 코드로 직접 구현하는 방식입니다.

 

이 방법을 사용하면 App.xaml의 Build Action 속성을 ApplicationDefinition 에서 Page로 변경해 주어야 합니다.
WPF가 구성해주는 진입점을 직접 작성하셔야 하므로 여러가지로 귀찮은 일이 생길 수 있을 거 같습니다.

마지막으로 소개해 드릴 방법은 프로세서의 네임 중복을 체크하는 방법입니다. 
이 방법은 잘 동작하지만 실행파일의 이름을 바꾸기만 해도 쉽게 중복 실행이 가능해 집니다.

이런 방법들을 사용하시면 WPF에서 중복방지를 구현하실수 있습니다.
길게 읽지 않으시고 첫번째 소개해 드린 방법을 사용하시면 됩니다.
나머지는 참고만 하셔도 될 것 같습니다.

출처 : http://wpfkorea.com/?document_srl=3047#0