Step 1: Create a resource file:

Visual Studio provides a simple way to do this, just select new item and then select resource file as a type. Insert your strings and values using IDE designer. Result is a file like Resource1.resx.

Step2: Generate a binary .reource file from your original .resx file:

resgen command provided by .Net SDK is the easiest way to do this step, here is an example

C:\Windows\Microsoft.Net\Framework\v2.0.50727> resgen.exe  Resource1.resx

A file with .resource extension will be created like Resource1.resource

Step3: Generate Satellite assembly file from .resource:

Again .Net SDK provides a command to easily create a satellite assembly out of a file, here is an example

C:\Windows\Microsoft.Net\Framework\v2.0.50727> al.exe /embed: Resource1.resources /out:Resource1.dll

Step4: Setting up Satellite Assemblies to be downloaded on Demand:

After adding your satellite assemblies as a reference to your project, open project manifest then select Publish tab. Satellite assemblies will be displayed here in Application files. Insert a new group name for the ones that need to be downloaded on demand. By doing this step you are specifying that ClickOnce won’t download them as part of its deployment process and it will be up to the next step to where and when to download them.

Step5: Place code where you want to download assembly on demand:

To do this step you need to be familiar with ClickOnce Deployment APIs in .Net, here is a sample code to download Reosurce1.dll (satellite Assembly) on application startup based on the user machine’s culture.

using System.Deployment.Application;

using System.Threading;

using System.Globalization;

public partial class App : System.Windows.Application

{               

   protected override void OnStartup(StartupEventArgs e)

   {

        base.OnStartup(e);

        Thread.CurrentThread.CurrentUICulture = new CultureInfo("en-US");

    GetSatelliteAssemblies(Thread.CurrentThread.CurrentUICulture.ToString());

   }

   static void GetSatelliteAssemblies(string groupName)

   {

        if (ApplicationDeployment.IsNetworkDeployed)

        {

           ApplicationDeployment deploy = ApplicationDeployment.CurrentDeployment;

           if (deploy.IsFirstRun)

           {

                try

                {

                   deploy.DownloadFileGroup(groupName);

                }

                catch (DeploymentException de)

                {

                    // Log error. Do not report error to the user, as there may not be a satellite                   

                 }

             }

         }

     }        

}

How ClickOnce Performs Application Updates 

ClickOnce uses the file version information specified in an application's deployment manifest to decide whether to update the application's files. After an update begins, ClickOnce uses a technique called file patching to avoid redundant downloading of application files.

File Patching

When updating an application, ClickOnce does not download all of the files for the new version of the application unless the files have changed. Instead, it compares the hash signatures of the files specified in the application manifest for the current application against the signatures in the manifest for the new version. If a file's signatures are different, ClickOnce downloads the new version. If the signatures match, the file has not changed from one version to the next. In this case, ClickOnce copies the existing file and uses it in the new version of the application. This approach prevents ClickOnce from having to download the entire application again, even if only one or two files have changed.

File patching also works for assemblies that are downloaded on demand using the DownloadFileGroup and DownloadFileGroupAsync methods.

Compiling using Visual Studio

If you use Visual Studio to compile your application, it will generate new hash signatures for all files whenever you rebuild the entire project. In this case, all assemblies will be downloaded to the client, although only a few assemblies may have changed.

Data Exceptions

File patching does not work for files that are marked as data and stored in the data directory. These are always downloaded regardless of the file's hash signature. For more information on the data directory, see Accessing Local and Remote Data in ClickOnce Applications.

Size Limitations

A single partially-trusted, online application is limited to occupying half of the quota space. Installed applications are not limited by the cache size and do not count against the cache limit. For all ClickOnce applications, the cache retains only the current version and the previously installed version.

By default, client computers have 250 MB of storage for online ClickOnce applications. Data files do not count toward this limit. A system administrator can enlarge or reduce this quota on a particular client computer by changing the registry key, HKEY_CURRENT_USER\Software\Classes\Software\Microsoft\Windows\CurrentVersion\Deployment\OnlineAppQuotaInKB, which is a DWORD value that expresses the cache size in kilobytes. For example, in order to reduce the cache size to 50 MB, you would change this value to 51200.

Choosing an Update Strategy

There are three basic strategies that you can use:

-          checking for updates on application startup

-          checking for updates after application startup (running in a background thread)

-          providing a user interface for updates

Providing a User Interface for Updates

Using this strategy, the application developer provides a user interface that allows the user to choose when or how often the application will check for updates. For example, you might provide a "Check for Updates Now" menu item, or an "Update Settings" dialog box with choices for different update intervals. The ClickOnce deployment APIs (System.Deployment.Application namespace) provides a framework for programming your own update user interface.

Permission Elevation and Updates

 If a new version of a ClickOnce application requires a higher level of trust to run than the previous version, ClickOnce will prompt the user, asking him if he wants the application to be granted this higher level of trust. If the user declines to grant the higher trust level, the update will not install. ClickOnce will prompt the user to install the application again when it is next restarted. If the user declines to grant the higher level of trust at this time, and the update is not marked as required, then the old version of the application will run. If the update is required, however, then the application will not run again until the user accepts the higher trust level.

Downloading Assemblies on Demand with the ClickOnce Deployment API

By default, all of the assemblies included in a ClickOnce application are downloaded when the application is first run. You might, however, have parts of your application that are used by a small set of your users. In this case, you want to download an assembly only when you create one of its types. You can mark certain assemblies in your application as "optional", and download them by using classes in the System.Deployment.Application namespace when the common language runtime demands them.

Assembly Binding Redirection

You can redirect an assembly binding reference to another version of an assembly by using entries in the application or machine configuration files. You can redirect references to .NET Framework assemblies, third-party assemblies, or assemblies of your own application.

When you build a .NET Framework application against a specific version of a strong-named assembly, the application uses that version of the assembly at run time. However, sometimes you might want the application to run against a newer version of an assembly. An application configuration file, machine configuration file, or a publisher policy file can redirect one version of an assembly to another.

You can use the .NET Framework Configuration tool (Mscorcfg.msc) to redirect assembly versions at both the application level and the machine level, or you can directly edit the configuration file.

Note : You cannot redirect versions for assemblies that are not strong-named. The common language runtime ignores the version for assemblies that are not strong-named.

The other nice feature of PageFunction is that it won’t be included in the navigation history, making navigation process much simpler for both the user and the developer.

Now we need to come up with a scenario that the PageFunction would make sense. Let’s say you need to have a search page that the user can navigate to by clicking on a link, after the user found his/her item then it would navigate back to the main page with the search result displayed in a textbox. This is very common scenario.

This is what you need first, a textbox and a link in the main page that navigates to the search page:

<Grid DockPanel.Dock="Top">

          <Grid.ColumnDefinitions>

                   <ColumnDefinition Width="0.3*" />

                   <ColumnDefinition Width="0.4*" />

                   <ColumnDefinition Width="0.3*" />

          </Grid.ColumnDefinitions>                       

          <TextBlock Grid.Row="0" Grid.Column="0">Selected Name:</TextBlock>

          <TextBox Grid.Row="0" Grid.Column="1" Name="txtResult" ></TextBox>

          <TextBlock  Grid.Row="0" Grid.Column="2">

                   <Hyperlink Click="SelectHyperlink_Click">Search</Hyperlink>

          </TextBlock>

</Grid>

We will work on the event handler “SelectHyperlink_Click” later. So far nothing new… Now you need to define your search page as a PageFunction in order to meet your requirement. So this is how you would implement your search page:

<PageFunction

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

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

    x:Class="MSLWPFPrototype.SearchPageFunction"

    xmlns:sys="clr-namespace:System;assembly=mscorlib"

    x:TypeArguments="sys:String"

    Title="OrganizationSearchPageFunction">

     <Grid DockPanel.Dock="Top" Name="grid2" >

          <Grid.ColumnDefinitions>

                   <ColumnDefinition Width="0.1*" SharedSizeGroup="Number"/>

                   <ColumnDefinition Width="0.1*" SharedSizeGroup="Name"/>

                   <ColumnDefinition Width="0.1*" SharedSizeGroup="StartDate"/>

                   <ColumnDefinition Width="0.13*" SharedSizeGroup="EndDate"/>

          </Grid.ColumnDefinitions>

          <Grid.RowDefinitions>

                   <RowDefinition Height="0.2*" />

                   <RowDefinition Height="0.2*" />

                   <RowDefinition Height="0.2*" />

                   <RowDefinition Height="0.2*" />

                   <RowDefinition Height="0.2*" />

                   <RowDefinition Height="0.2*" />

          </Grid.RowDefinitions>

          <TextBlock Grid.Column="0" Grid.Row="0">

             <Hyperlink Click="okButton_Click"  Tag=”Value1”>Value1</Hyperlink>

          </TextBlock>

          <TextBlock Grid.Column="1" Grid.Row="0">Value2</TextBlock>

          <TextBlock Grid.Column="2" Grid.Row="0">Value3</TextBlock>

          <TextBlock Grid.Column="3" Grid.Row="0">Value3</TextBlock>

</Grid>

The only thing interesting here in this code is:

xmlns:sys="clr-namespace:System;assembly=mscorlib"

x:TypeArguments="sys:String"

The first line is to specify that you want to use .Net type like string here in XMAL file and the TypeArguments is the type of the object that the PageFunction returns back to the caller page.

You also need to implement these two event handler as part of your PageFunction:

void okButton_Click(object sender, RoutedEventArgs e)

{

     // Accept task when Ok button is clicked

     Hyperlink cmd = (Hyperlink)sender;         

     OnReturn(new ReturnEventArgs<string>((string)cmd.Tag));

}

void cancelButton_Click(object sender, RoutedEventArgs e)

{

     // Cancel task

     OnReturn(null);

}

That is it for the PageFunction, not that difficult!!! Now you need to add couple more event handlers to your caller page to accept the result and display it in the textbox:

void taskPageFunction_Return(object sender, ReturnEventArgs<string> e)

{

     if (e == null) return;

     // If a task happened, display task data

     this.txtResult.Text = e.Result;

}

And the event handler for the link to navigate to the Search page:

void SelectHyperlink_Click(object sender, RoutedEventArgs e)

{

     // Instantiate and navigate to task page function

     SearchPageFunction taskPageFunction = new SearchPageFunction("Initial Data Item Value");

     taskPageFunction.Return += taskPageFunction_Return;

     this.NavigationService.Navigate(taskPageFunction);

}

Done, enjoy your Search PageFunction!!!!

First you need to define the ListView:

<ListView Name="listSearchResult" Height="150" SelectionMode="Single"   Style="{StaticResource ListViewStyle}" MouseDoubleClick="Selected">

     <ListView.View>

            <GridView ColumnHeaderContainerStyle="{StaticResource HeaderStyle}" >

                 <GridViewColumn Header="Header1">

                         <GridViewColumn.CellTemplate>

                                <DataTemplate>

                                        <TextBlock Text="{Binding Path=Name}"></TextBlock>

                                </DataTemplate>

                          </GridViewColumn.CellTemplate>

                 </GridViewColumn>

            <GridViewColumn Header="Header2" >

                    <GridViewColumn.CellTemplate>

                          <DataTemplate>

                               <TextBlock  Text="{Binding Path=Number}"></TextBlock>

                           </DataTemplate>

                    </GridViewColumn.CellTemplate>

            </GridViewColumn>

      </GridView>

   </ListView.View>

</ListView>

As you may have noticed I added one event handler for MouseDoubleClick event, That is how you can enable selection feature in the list by just setting the MouseDoubleClick or any other event on the ListView.

And this is what the select event handler looks like:

void Selected(object sender, RoutedEventArgs e)

{

      ListView cmd = (ListView)sender;

      string selectedItem = (string)(((System.Data.DataRowView)(cmd.SelectedItem)).Row[0]);           

}

It just seems easier to define Style as resource for me, so here is the style for the ListView. I need to note that if your list is too big you will need to enable the Scroll feature enable. This is how you should do this: just set ScrollViewer.HorizontalScrollBarVisibility to Visible. The ScrollViewer embedded in the ListView will use this property accordingly.

<Style  x:Key="ListViewStyle" TargetType="ListView">

          <Setter Property="Margin" Value="5"/>

          <Setter Property="HorizontalAlignment" Value="Stretch" />

          <Setter Property="VerticalAlignment" Value="Top" />               

          <Setter Property="ScrollViewer.CanContentScroll" Value ="True" />

          <Setter Property="ScrollViewer.HorizontalScrollBarVisibility" Value ="Visible" />

          <Setter Property="ScrollViewer.VerticalScrollBarVisibility" Value="Visible" />               

</Style>

Now you have a very nice DataGrid. If you are interested to make your datagrid’s look more interesting, you can use ControlTemplate like what I am using here:

<ControlTemplate x:Key="HeaderTemplate" TargetType="{x:Type GridViewColumnHeader}">

          <Border  BorderThickness="1" CornerRadius="3" TextBlock.Foreground="Chocolate"

TextBlock.TextAlignment="Center" Width="{TemplateBinding  Width}"

BorderBrush="Chocolate" Background="AntiqueWhite"  >

                   <ContentPresenter Content="{TemplateBinding Content}" ></ContentPresenter>

          </Border>

</ControlTemplate>

And of course you can apply this template through the style of the Header or column.

<Style x:Key="HeaderStyle" TargetType="GridViewColumnHeader">

          <Setter Property="Template" Value="{StaticResource HeaderTemplate}" />

          <Setter Property="Height" Value="25"/>

          <Setter Property="Padding" Value="2"/>

</Style>

If you want to display a large number of rows in a grid you will definitely need a scroll feature in your grid but does the grid control in WPF has this feature? The answer is pretty straight, NO.

Hmm, then how I am supposed to display 100 records in a grid? Well the first answer to that is just use the ScrollViewer control around the grid. That would be a short time solution, once run your app you will come to agreement that is not really what you want.  You will notice that the header part of the grid will get included in the ScrollViewer as well, which is not very pleasant to the user basically when the user scrolls down, the header gets disappear.

Is there any other solution? Yes, there is a nicer way. It is just not very obvious at first but you will get used to that after using it for couple times. Here are the steps: First of all you need to have two grids one for the header and the other one for the main body. The main grid will be in the ScrollViewer control as you would also guess. So this will solve the problem, very simple!!!

<Grid Name="grid1"  TextBlock.Foreground="Chocolate">

   <Grid.Resources>

          <Style  TargetType="{x:Type Border}">

                   <Setter Property="BorderThickness" Value="1" />

                   <Setter Property="Background" Value="AntiqueWhite" />

                   <Setter Property="BorderBrush" Value="Gray" />

          </Style>                                             

   </Grid.Resources>

   <Grid.ColumnDefinitions>

          <ColumnDefinition Width="0.2*"/>

          <ColumnDefinition Width="0.2*"/>

          <ColumnDefinition Width="0.2*"/>

          <ColumnDefinition Width="0.2*"/>

   </Grid.ColumnDefinitions>

   <Border Grid.Column="0" >

          <TextBlock>Role</TextBlock>

   </Border>

   <Border Grid.Column="1"  >

          <TextBlock>Name</TextBlock>

   </Border>

   <Border Grid.Column="2"  >

          <TextBlock>Start Date</TextBlock>

   </Border>

   <Border Grid.Column="3"  >

          <TextBlock>End Date</TextBlock>

   </Border>

</Grid>

<ScrollViewer Height="100" HorizontalScrollBarVisibility="Visible" VerticalScrollBarVisibility="Visible" >

  <Grid Name="grid2"  >

    <Grid.ColumnDefinitions>

          <ColumnDefinition Width="0.08*"/>

          <ColumnDefinition Width="0.1*"/>

          <ColumnDefinition Width="0.14*"/>

          <ColumnDefinition Width="0.14*"/>

    </Grid.ColumnDefinitions>

    <Grid.RowDefinitions>

          <RowDefinition Height="0.2*" />

          <RowDefinition Height="0.2*" />

    </Grid.RowDefinitions>

          <TextBlock Grid.Row="0" Grid.Column="0">Role1</TextBlock>

          <TextBlock Grid.Row="0" Grid.Column="1">

                   <Hyperlink NavigateUri="Page1.xaml">Name1</Hyperlink>

          </TextBlock>

          <TextBlock Grid.Row="0" Grid.Column="2">01/01/2006</TextBlock>

          <TextBlock Grid.Row="0" Grid.Column="3">01/01/2007</TextBlock>

          <TextBlock Grid.Row="1" Grid.Column="0">Role2</TextBlock>

          <TextBlock Grid.Row="1" Grid.Column="1">

                   <Hyperlink NavigateUri="Page2.xaml">Name2</Hyperlink>

          </TextBlock>

          <TextBlock Grid.Row="1" Grid.Column="2">01/01/2007</TextBlock>

          <TextBlock Grid.Row="1" Grid.Column="3">01/01/2008</TextBlock>

   </Grid>

</ScrollViewer>

But now there is another issue that is the size of the header columns doesn’t match the size of the main grid columns. To fix this you just need to simply use this grid property SharedSizeGroup. Set this property on every column on the header grid to the unique name and then set the use the same names to set this property on the main grid columns. That simple!!!

    <Grid.ColumnDefinitions>

          <ColumnDefinition Width="0.08*" SharedSizeGroup="Role"/>

          <ColumnDefinition Width="0.1*" SharedSizeGroup="Name"/>

          <ColumnDefinition Width="0.14*" SharedSizeGroup="StartDate"/>

          <ColumnDefinition Width="0.14*" SharedSizeGroup="EndDate"/>

    </Grid.ColumnDefinitions>

One last thing that you will notice is that the size of the last column on the header does not match the last column on the main grid. Hmm, now you need to this last trick to fix this issue. First you need to add one more ColumnDefinition to your header grid by setting its width to Auto:

<ColumnDefinition Width="Auto" />

Then add this item to be the last column in the header grid and set the width to this DynamicResource.

   <FrameworkElement Grid.Column="4" Width="{DynamicResource {x:Static SystemParameters.ScrollWidthKey}}" />

Done! You have built the pretty nice looking grid that can scroll nicely.

Here is a sample code for a dynamic treeview. First thing is that you need to define your data staructure. I am using NavigationItem class for a single item and NavigationItemCollection class for the whole collection of items in the tree. The trick to maintaine the treeview as you change the source is to use ObservableCollection.

NavigationItem Class:

public class NavigationItem

{

        public NavigationItem(string in_name, string in_absolutePath, string in_relativePath, string in_title, Boolean in_enabled)

        {

            _name = in_name;

            _absolutePath = in_absolutePath;

            _relativePath = in_relativePath;

            _title = in_title;

            _enabled = in_enabled;

        }

        private ObservableCollection<NavigationItem> _subItems;

        public ObservableCollection<NavigationItem> SubItems

        {

            get { return _subItems; }

            set

            {

                _subItems = value;

            }

        }

        private String _relativePath;

        public String RelativePath

        {

            get { return _relativePath; }

            set

            {

                _relativePath = value;

            }

        }

        private String _absolutePath;

        public String AbsolutePath

        {

            get { return _absolutePath; }

            set

            {

                _absolutePath = value;

            }

        }

        private String _name;

        public String Name

        {

            get { return _name; }

            set

            {

                _name = value;

            }

        }

        private String _title;

        public String Title

        {

            get { return _title; }

            set

            {

                _title = value;

            }

        }

        private Boolean _enabled;

        public Boolean Enabled

        {

            get { return _enabled; }

            set

            {

                _enabled = value;

            }

        }

 }

NavigationItemCollection Class:

    public class NavigationItemCollection : BaseNavigationItemCollection

    {

        public NavigationItemCollection()

        {

            ObservableCollection<NavigationItem> _subItems = new ObservableCollection<NavigationItem>();

            _subItems.Add(new NavigationItem("MyNameSpace.Page1", "Folder1/Page1.xaml", "Page1.xaml", "Page Title 1", true));

            _subItems.Add(new NavigationItem("MyNameSpace.Page2", "Folder1/Page2.xaml", "Page2.xaml", "Page Title 2", true));

            _subItems.Add(new NavigationItem("MyNameSpace.Page3", "Folder1/Page3.xaml", "Page3.xaml", "Page Title 3", true));

            NavigationItem navitem = new NavigationItem("", "", "", "Tree Title", true);

            navitem.SubItems = _subItems;

            _navitems = new ObservableCollection<NavigationItem>();

            _navitems.Add(navitem);

        }

    }

The second step would be to define your tree as you would for any treeview and bind it to the proper datasource.

The Main Page XMAL file:

<DockPanel HorizontalAlignment="Stretch" VerticalAlignment="Stretch" >

          <Border DockPanel.Dock="Left">

                   <TreeView DockPanel.Dock="Left" Width="200"  Name="mytree" Margin="10,10,10,10" HorizontalAlignment="Stretch" VerticalAlignment="Stretch" SelectedItemChanged="NavigationChanged">

                             <TreeView.ItemTemplate>

                                      <HierarchicalDataTemplate ItemsSource="{Binding Path=SubItems}"  >

                                                <TextBlock Text="{Binding Path=Title}"/>                                         </HierarchicalDataTemplate>

                             </TreeView.ItemTemplate>

                   </TreeView>

          </Border>

          <Border DockPanel.Dock="Right">

                             <Frame Name="frmBody" Source="Page1.xaml"

                              HorizontalAlignment="Stretch" VerticalAlignment="Stretch"  NavigationUIVisibility="Hidden" ></Frame>

          </Border>

</DockPanel>

The code behind for the XAML file:

#region Constructors

        public MainPage()

        {

            InitializeComponent();

            BindControls();

        }

#endregion

#region Methods

        public void BindControls()

        {

            NavigationItems objNav = new NavigationItems();

            App.Current.Resources.Add("NavigationItems", objNav);                       

            mytree.ItemsSource = (ObservableCollection<NavigationItem>) ((NavigationItems)App.Current.Resources["NavigationItems"]).EnabledNavItems;                            

        }

        public void NavigationChanged(object sender, RoutedPropertyChangedEventArgs<Object> e)

        {

            NavigationItem navTree = mytree.SelectedItem as NavigationItem;

            if (navTree != null)

            {

                if (!string.IsNullOrEmpty(navTree.RelativePath))

                {

                    frmBody.Source = new Uri(navTree.RelativePath, UriKind.Relative);

                }

            }

        }

#endregion

Now here is where you want to make your tree to be more flexible and change as the user walk through the pages.

The NavigationItem class and NavigationItemCollection class are pretty straight forward. But as you look more closely at NavigationItemCollection  class it inherits from BaseNavigationItemCollection class that has couple more methods:

GetNextItem()

MoveNext()

FindCurrentItem()

RemoveItem()

These methods will work on the collection to make changes to the items.

BaseNavigationItemCollection Class:

public class BaseNavigationItemCollection : ObservableCollection<NavigationItem>

    {

        public BaseNavigationItemCollection()

        {

        }

        protected ObservableCollection<NavigationItem> _navitems;

        private int _currentIndex;

        public ObservableCollection<NavigationItem> EnabledNavItems

        {

            get

            {

                return _navitems;

            }

        }

        public void RemoveItem(NavigationItem item)

        {

            for (int index = 0; index < _navitems[0].SubItems.Count; index++)

            {

                if (_navitems[0].SubItems[index].Name == item.Name)

                {

                    _navitems[0].SubItems[index].Enabled = false;

                }

            }

        }

        public NavigationItem GetNextItem(string currentpage)

        {

            FindCurrentItem(currentpage);

            MoveNext();

            while (_currentIndex < _navitems[0].SubItems.Count && !_navitems[0].SubItems[_currentIndex].Enabled)

            {

                MoveNext();

            }

            if (_currentIndex >= _navitems[0].SubItems.Count)

            {

                return _navitems[0];

            }

            else

            {

                return _navitems[0].SubItems[_currentIndex];

            }

        }

        private void MoveNext()

        {

            _currentIndex += 1;

        }

        private void FindCurrentItem(string name)

        {

            for (int index = 0; index < _navitems[0].SubItems.Count; index++)

            {

                if (_navitems[0].SubItems[index].Name == name)

                {

                    _currentIndex = index;

                    return;

                }

            }

        }

    }

The result: As the user walks through the pages and provides input values you can determine the next step in the app based on the values entered by the user and even make change in the navigation items including moving steps back and force, removing some steps, changing the Titles, and etc. The nice thing here is that the treeview on the left Nav will reflect those changes. J pretty neat.

I guess I am supposed to say something about myself in my first post. Well I started working for Microsoft about a year ago when I moved from Washington DC (truth to be said I still miss it) to Seattle.

I remember when I was in college having this goal of some day working for MS and now here I am, met one of my milestones. But you know it is just like hiking, you have a destination and you try to get there for hours and hours and then when you are there of course you feel good for a moment, but it does not take a week that what you remember from your trip is not just the pick of the mountain or the waterfall that you saw on the top or the bottom but the things that happened on the way getting there, the things that you saw, talked about, laughed at. In a short sentence the enjoyment exists in the journey as much as the destination.

Anyway it has been a good year so far for me with all the adjustments and definitely enjoying the new friends here in Seattle.

For a long time I was thinking of writing a blog myself although I am not reading many blogs (I may sound a bit selfish here) I should say that I like couple blogs out there.

Topic of this blog: Since I had a chance to work on WPF for a while in my team and wrote a prototype recently in WPF I felt it might be a good idea to share my learning in WPF with others here in my blog. I also like photography so whenever I have a chance to upload some I will share them as well.

I think I filled the purpose of self description for now. So let’s move on…

Martha

PS: I am a new blogger so bear with me J