WPF Story

VS2010 now support multi-monitors!

(SunKwon Kim) — Tue, 01 Sep 2009 18:08:45 +0900

Using Multi-monitors have become one of the basic environments for developing softwares.

But, from VS6 to VS2008 there was no development environment to support multi-monitors. Only we can drag a window of VS2008 to expand the width of it across the monitors. Happy news comes to us from Scott Guthrie. Now we can extract windows from the VS2010 and throw it to another window! I don't doubt it will enhance our productivity.
Scott Guthrie posted it detail.

How to bind WPF controls to Application settings

(SunKwon Kim) — Wed, 08 Apr 2009 23:43:46 +0900

When to bind WPF controls to settings

At Sometimes, i want to show program verion in my application. And I wrote it in Application settings ("Settings.Settings"). How could I do that? If we don't know how to bind it, we have to write twice at each time upgrading our programs. Jerome Laban and Michael jp posted how to do that with different approaches.

Method 1: using resource declaration

I simplify the method 1. First, write a string you want to show like this.

Secondly, add namespace for application settings. and declare a setting object in the resource
<window x:class="WpfApplication1.Window1" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:settings="clr-namespace:WpfApplication1.Properties" title="Window1" height="300" width="300"> <window.resources> <settings:settings x:key="settings"> </settings:settings></window.resources> </window>
Lastly, bind a control to the Settings object like this.
<textblock text="{Binding Source={StaticResource settings},Path=Default.Version}">

Method 2: using x:Static keyword

Or if you want to bind it as a static, just do like this.
First, declare the namespace for application settings. it is the same with method 1.
xmlns:Properties="clr-namespace:WindowsApplication1.Properties" Second, bind the control to the settings using x:Static keyword like this.
<textblock name="textps" text="{Binding Path=Setting1, Source={x:Static Properties:Settings.Default}}">

How to log using XmlDataProvider in WPF

(SunKwon Kim) — Mon, 09 Mar 2009 00:35:21 +0900

Multithread logger in WPF

Tamir Khason posted "Multithread logger in WPF". In that article, we can learn about how to log errors using XmlDataProvider in WPF. It is clear and interest.
He posted his article here (or you can it here.)

How to use XmlDataProvider from code behind (c# code)

(SunKwon Kim) — Sat, 07 Mar 2009 23:19:51 +0900

In many cases, XML is very useful in programming

For example, I have written a program which support many product catalogs. In traditional programming, we had used a database or a customized file which support hierarchy structures. But in recent day, we can easily do that by XML. In WPF, XmlDataProvider was given to us to handle XML data.

how to use XMLDataProvider from code behind (c# code)

It was not problem when I use XmlDataProvider in xaml. The problem occurs when I use XmlDataProvider in code behind (C# code)!. I wrote the code like this
//codes in xaml <Window.Resources> <XmlDataProvider x:Key="ProductDS" Source="Product.xml" XPath="/Product"/> </Window.Resources> //codes in code behind XmlDataProvider dp = Resources["ProductDS"] as XmlDataProvider; System.Xml.XmlDocument doc = dp.Document;
But dp.Document has null! And After running it twice, dp.Document has data I wants. It looks very strange to me. If you have same problem, don't worry about it. The key to solve this situation is following.
dp.IsAsynchronous = false; After changing "IsAsynchronous" property to false, XmlDataProvider will give you all the results you order.
//codes in xaml <Window.Resources> <XmlDataProvider x:Key="ProductDS" Source="Product.xml" XPath="/Product"/> </Window.Resources> //codes in code behind XmlDataProvider dp = Resources["ProductDS"] as XmlDataProvider; dp.IsAsynchronous = false; System.Xml.XmlDocument doc = dp.Document;

How to deploy .net framework 3.5 sp1 with your setup project.

(SunKwon Kim) — Thu, 05 Mar 2009 14:31:52 +0900

Update the Package Data

Open the [Program Files]\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 folder or %ProgramFiles(x86)%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 on x64 operating systems
Edit the Product.xml file in Notepad.
Paste the following into the &ltPackageFiles> element:
&ltPackageFile Name="TOOLS\clwireg.exe" />
&ltPackageFile Name="TOOLS\clwireg_x64.exe" />
&ltPackageFile Name="TOOLS\clwireg_ia64.exe" />
Find the element for &ltPackageFile Name="dotNetFX30\XPSEPSC-x86-en-US.exe" and change the PublicKey value to: 3082010A0282010100A2DB0A8DCFC2C1499BCDAA3A34AD23596BDB6CBE2122B794C8EAAEBFC6D526C232118BBCDA5D2CFB36561E152BAE8F0DDD14A36E284C7F163F41AC8D40B146880DD98194AD9706D05744765CEAF1FC0EE27F74A333CB74E5EFE361A17E03B745FFD53E12D5B0CA5E0DD07BF2B7130DFC606A2885758CB7ADBC85E817B490BEF516B6625DED11DF3AEE215B8BAF8073C345E3958977609BE7AD77C1378D33142F13DB62C9AE1AA94F9867ADD420393071E08D6746E2C61CF40D5074412FE805246A216B49B092C4B239C742A56D5C184AAB8FD78E833E780A47D8A4B28423C3E2F27B66B14A74BD26414B9C6114604E30C882F3D00B707CEE554D77D2085576810203010001
Find the element for <PackageFile Name="dotNetFX30\XPSEPSC-amd64-en-US.exe" and change the PublicKey value to the same as in step 4 above
Save the product.xml file

Download and Extract the Core Installation Files

Navigate to the following URL: http://go.microsoft.com/fwlink?LinkID=118080
Download the dotNetFx35.exe file to your local disk.
Open a Command Prompt window and change to the directory to which you downloaded dotNetFx35.exe.
At the command prompt, type:
dotNetFx35.exe /x:.
This will extract the Framework files to a folder named “WCU” in the current directory.
Copy the contents of the WCU\dotNetFramework folder and paste them in the %Program Files%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 folder (%ProgramFiles(x86)%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 on x64 operating systems). Note: Do not copy the WCU\dotNetFramework folder itself. There should be 5 folders under the WCU folder, and each of these should now appear in the DotNetFx35SP1 folder. The folder structure should resemble the following:
o DotNetFx35SP1 (folder)
- dotNetFX20 (folder
- dotNetFX30 (folder)
- dotNetFX35 (folder)
- dotNetMSP (folder)
- TOOLS folder)
- en (or some other localized folder)
- dotNetFx35setup.exe (file)

How to set color of a button into default value in WPF

(SunKwon Kim) — Mon, 09 Feb 2009 12:51:47 +0900

How to set color of a button into default value

If you want set color of a button into default, then just use the following code.
Button btn = new Button(); btn.Background = (Brush) Button.BackgroundProperty.DefaultMetadata.DefaultValue;

How to evalulate your code: "Calculate Code Metrics" in Visual Studio 2008

(SunKwon Kim) — Tue, 20 Jan 2009 11:38:21 +0900

Do you know What is "Calculate Code Metrics" as a new feature of Visual Studio 2008

I have wanted to know how to evaluate my code easily. But It is not easy to buy the solution privately for that. :) Like preparing the exam into University, it helps to enhance our programming skill. Programming and rating it. And we can do it using Visual Studio 2008 easily.

InfoSys posted "Calculate Code Metrics Features in Visual Studio 2008"

It is a good post. It is easy to read and understand about "Calculate Code Metric". All the thing you have to for "Calculate Code Metric" are just two steps.
Click Mouse right button on your Visual Studio Solution and select "Calculate Code Metrics".
Read five indices, which means the followings

Meaning of the indices are explained in here. The summary of that is following.

Maintainability Index: This index tells how maintainable your code is. It is like a total score. Higher the value better your code is.
Cyclomatic Complexity: This index is calculated at a method level. and it tells how complex the relation between methods in your code is. So lower the value better your code is.
Depth of Inheritance: This tells the number of base classes. it is good to maintain the number of inheritance appropriately. Infosys recommended to keep this value to 6 or below
Class Coupling: This number shows the number of classes a particular class depends on. It is better to keep this value lower.
Lines of Code; It tells the number of lines except white space, comments, braces and so on. So it can shows your daily work.

It is easy, isn't it?

Window Presentation Foundation (WPF) animated Progressbar with code and xaml

(SunKwon Kim) — Wed, 22 Oct 2008 03:28:35 +0900

Introduction to WPF Animation

Animation is one of the most fascinating features of Window Presentation Foundation (WPF). To support easy usage of animation, Microsoft release Expression Blend, which is software for WPF designer.If you use Expression Blend, you can draw animation in your program very easily. But to optimize the animation and solve the problem when it occurs, we need to know about how to write WPF Animation in the code and extensible application markup language (XAML).

Three ways to write WPF Animation

   1. With only code.
   2. With only XAML
   3. With both code and XAML

We can make WPF application with only code, or with only XAML. To make application with only code enables most flexible logic, but it needs more times than the others. In other case, with only XAML, we can make it easily, but its flexibility is low. So, at usually, animation with both code and XAML is widely used. In this article, we will study about how to write WPF animation with both code and XAML. It is most flexible way; we can modify it in both sides. In the XAML side, we will define UI Component, and Animation with the UI is declared in the Code.

This diagram shows three steps to do WPF animation. First, UI components like slider and progress bar are declared in the XAML. Second, Callback function (event function) is declared in the code. Third, WPF animation about progress bar is written in the function. Let's do animated WPF Progress bar.

1. Create a new project and modify UI to have a slider and a progress bar. slider has a ValueChanged event. In the callback function of that event, we will make WPF animation about the progress bar.

<Window x:Class="AnimatedProgressbar.Window1"
xmlns="http://schemas.microsoft.com/winfx/2006 ··· entation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
Title="Animated Progress Bar" Height="100" Width="300">
<StackPanel>
<Slider Name="slider" Minimum="0" Maximum="100"
ValueChanged="slider_ValueChanged"/>
<ProgressBar Name="progressBar" Height="30" Minimum="0" Maximum="100"/>
</StackPanel>
</Window>

2. Declare WPF animation to the slider bar.

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.Windows.Media.Animation;
namespace AnimatedProgressbar
{
/// <summary>
/// Interaction logic for Window1.xaml
/// </summary>
public partial class Window1 : Window
{
public Window1()
{
InitializeComponent();
}
private void slider_ValueChanged(object sender, RoutedPropertyChangedEventArgs<double> e)
{
DoubleAnimation animation = new DoubleAnimation(e.NewValue, new Duration(TimeSpan.FromSeconds(4)));
Storyboard.SetTargetName(animation, "progressBar");
Storyboard.SetTargetProperty(animation, new PropertyPath(ProgressBar.ValueProperty));

Storyboard sb = new Storyboard();
sb.Children.Add(animation);
sb.Begin(progressBar);

e.Handled = true;
}
}
}

Animation is defined in the namespace, "System.Windows.Media.Animation", we need to add the namespace into the code. Callback function to ValueChanged event of the slider is painted with red color. In the function, we have to define animation with destination value and duration firstly. And then, let's attach the animation into the target. In this case, the target is ProgressBar. We can set the target with its name, "progressBar", defined in the XAML. Nextly, we need to choose property of the target, which will be animated. In this examples, Value property is chosen.Now, we declare Storyboard object which has the animation, and then begin it. we can see the animated progress bar.

I hope this article will be helpful.

How to write data binding between code and xaml in WPF

(SunKwon Kim) — Mon, 20 Oct 2008 01:05:09 +0900

The most example of data binding is about binding between WPF controls. For example, it is data binding between value of slider and font size of textbox. But after knowing this, we want to know how to declare data binding between code and xaml.

In this article, we will see one of most simple example of data binding between code and xaml. Through this example, you can take first look about data binding between code and xaml.

Before reading this article, you must understand basic of data binding, like DataContext, Path.

The data binding between code and xaml is following.

First, Create new Project file and add new class named "Data".

[##_1C|9770339687.png|width="600" height="359" alt="Create Data class"|This Class is used for handling data which will be binded into xaml._##]

// Data.cs

using System;

using System.Collections.Generic;

using System.Linq;

using System.Text;

using System.Windows;

namespace EasyDataBinding

{

public class Data : DependencyObject

{

public double FontSize

{

get { return (double)GetValue(FontSizeProperty); }

set { SetValue(FontSizeProperty, value); }

}

// Using a DependencyProperty as the backing store for FontSize. This enables animation, styling, binding, etc...

public static readonly DependencyProperty FontSizeProperty = DependencyProperty.Register("FontSize", typeof(double), typeof(Data), new UIPropertyMetadata(10.0));

}

Newly added codes are painted with Red color. Dependency property supports two-way data binding naturally, so using dependency property is easy for data binding. For using dependency property, Data class is derived from DependencyObject.

Second, connect the Data object into DataContext in the codes of main window.

// Window1.xaml.cs

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;

namespace EasyDataBinding

{

/// <summary>

/// Interaction logic for Window1.xaml

/// </summary>

public partial class Window1 : Window

{

public Window1()

{

InitializeComponent();

this.DataContext = new Data(); // connect the data object into the datacontext of the window

}

Third, Let's declare data binding in xaml.

<Window x:Class="EasyDataBinding.Window1"

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

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

Title="Window1" Height="300" Width="300">

<Grid>

<Grid.RowDefinitions>

</Grid.RowDefinitions>

</Grid>

</Window>

Now we can see the result of data binding by running the program. Let's click F5 key, then see the result.

[##_1C|5593786112.png|width="300" height="300" alt="User image"|_##][##_1C|1762542081.png|width="300" height="300" alt="User image"|_##]

You must use Source Control like TortoiseSVN

(SunKwon Kim) — Wed, 15 Oct 2008 01:10:36 +0900

It is a day near I join a company. I had written codes for new software all day. And near the time I went out, I saw the blue screen in the computer. I grabbed my head and banging it. I feel I was going to be mad. Well, everybody who writes codes has one or two experiences like that. :)

So I strongly recommend using source control tool to you. If you use the source control, someday you wil appreciate it. It handles source code history and solves conflict of source code between co-workers. It can save our time which is maybe lost, if we doesn't use it. So I strongly recommend using it again.

There are three source controls widely used in the world, tortoiseSVN, source safe and CVS.

tortoiseSVN is fast, easy and free. so it is widely used as time goes. And there is a brother tool, VisualSVN. If you want to handle tortoiseSVN in Visual Studio, you can do it with VisualSVN, but it is not free. Its price is 49$ per one person. :) It is very handy and useful in Visual Studio.

Source safe is provided from Microsoft. If the company you work for have purchased MSDN subscription license, maybe you can use it. It is not free :)

At last, I don't have used CVS before. I am sorry for that. But there is many person using CVS.

Amit posted "How To Use SVN Client and Start Working With Your SubVersion Control" in his blog. He wrote Quick guide for SVN, it will be helpful to use tortoiseSVN firstly. And you can download it in tortoiseSVN.NET.