<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0">
  <channel>
    <title>DotNetKicks.com : Stories kicked by linksaussen</title>
    <description>Stories kicked by linksaussen</description>
    <link>http://www.dotnetkicks.com/</link>
    <language>en-us</language>
    <copyright>Atweb Publishing Ltd.</copyright>
    <docs>http://backend.userland.com/rss</docs>
    <generator>DotNetKicks.com - .NET links, community driven</generator>
    <ttl>30</ttl>
    <item>
      <title>WPF Printing: How to print a PageRange with WPF's PrintDialog ...</title>
      <description>WPFs PrintDialog has no logic for printing a page range of a FixedDocument (XPS). It allows the User to define a pagerange, but then all pages are printed and it's up to you to implement the logic to only print the pages defined in the PrintDialog. This blog-post describes an elegant way how to implement generic logic to support the printing of page ranges. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.thomasclaudiushuber.com%2fblog%2f2009%2f11%2f24%2fwpf-printing-how-to-print-a-pagerange-with-wpfs-printdialog-that-means-the-user-can-select-specific-pages-and-only-these-pages-are-printed%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.thomasclaudiushuber.com%2fblog%2f2009%2f11%2f24%2fwpf-printing-how-to-print-a-pagerange-with-wpfs-printdialog-that-means-the-user-can-select-specific-pages-and-only-these-pages-are-printed%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/wpf/WPF_Printing_How_to_print_a_PageRange_with_WPF_s_PrintDialog</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/wpf/WPF_Printing_How_to_print_a_PageRange_with_WPF_s_PrintDialog</guid>
      <pubDate>Tue, 24 Nov 2009 17:51:18 GMT</pubDate>
    </item>
    <item>
      <title>Here it is: The UpdateSourceTrigger for PropertyChanged in Silverlight</title>
      <description>Shows an implementation for supporting the UpdateSourceTrigger PropertyChanged for DataBindings in Silverlight. So a databound TextBox will update its source everytime the Text-Property changes, and not only when it loses focus. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.thomasclaudiushuber.com%2fblog%2f2009%2f07%2f17%2fhere-it-is-the-updatesourcetrigger-for-propertychanged-in-silverlight%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.thomasclaudiushuber.com%2fblog%2f2009%2f07%2f17%2fhere-it-is-the-updatesourcetrigger-for-propertychanged-in-silverlight%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/silverlight/Here_it_is_The_UpdateSourceTrigger_for_PropertyChanged_in_Silverlight</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/silverlight/Here_it_is_The_UpdateSourceTrigger_for_PropertyChanged_in_Silverlight</guid>
      <pubDate>Fri, 17 Jul 2009 09:59:08 GMT</pubDate>
    </item>
    <item>
      <title>Developing Multicolumn-DropDown with ASP.NET, the GridView and AJAX</title>
      <description>This article shows, how to develop a really useful multicolumn-dropdownlist with ASP.NET, the GridView and the AJAX Control Toolkit.  &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.thomasclaudiushuber.com%2fblog%2f2008%2f07%2f31%2fdeveloping-multicolumn-dropdowndropdownlist-with-aspnet-the-gridview-and-the-ajax-control-toolkit%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.thomasclaudiushuber.com%2fblog%2f2008%2f07%2f31%2fdeveloping-multicolumn-dropdowndropdownlist-with-aspnet-the-gridview-and-the-ajax-control-toolkit%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/aspnet/Developing_Multicolumn_DropDown_with_ASP_NET_the_GridView_and_AJAX</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/aspnet/Developing_Multicolumn_DropDown_with_ASP_NET_the_GridView_and_AJAX</guid>
      <pubDate>Thu, 31 Jul 2008 19:31:01 GMT</pubDate>
    </item>
    <item>
      <title>Lazy instantiation one-liner with the coalesce operator</title>
      <description>The one-liner for lazy instantiation of instance fields using the coalesce-operator &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2frealfiction.net%2f%3fq%3dnode%2f157"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2frealfiction.net%2f%3fq%3dnode%2f157" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/csharp/Lazy_instantiation_one_liner_with_the_coalesce_operator</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/csharp/Lazy_instantiation_one_liner_with_the_coalesce_operator</guid>
      <pubDate>Wed, 14 May 2008 15:31:33 GMT</pubDate>
    </item>
    <item>
      <title>WPF + INotifyPropertyChanged Proxy = Epic Fail!</title>
      <description>Sending property changed events when a property is changed is repetitive boilerplate code that can be factored out into an aspect of your system's behaviour. This can be done with a proxy generator library like the Castle's DynamicProxy2. Alas, it is not as pretty as it seems... &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2frealfiction.net%2f%3fq%3dnode%2f156"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2frealfiction.net%2f%3fq%3dnode%2f156" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/csharp/WPF_INotifyPropertyChanged_Proxy_Epic_Fail</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/csharp/WPF_INotifyPropertyChanged_Proxy_Epic_Fail</guid>
      <pubDate>Fri, 09 May 2008 13:37:56 GMT</pubDate>
    </item>
    <item>
      <title>LostFocus (TextBox) vs. Buttons IsDefault-Property</title>
      <description>If a Buttons IsDefault-Property is set to true, it'll be clicked, when the user presses the Enter-Key. If a TextBox has Focus, and its Text-Property is databound, the Source of the Data Binding won't be updated. This Post describes the problem and the solution.  &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.thomasclaudiushuber.com%2fblog%2f2008%2f05%2f02%2flostfocus-textbox-vs-buttons-isdefault-property%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.thomasclaudiushuber.com%2fblog%2f2008%2f05%2f02%2flostfocus-textbox-vs-buttons-isdefault-property%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/wpf/LostFocus_TextBox_vs_Buttons_IsDefault_Property</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/wpf/LostFocus_TextBox_vs_Buttons_IsDefault_Property</guid>
      <pubDate>Fri, 02 May 2008 17:51:55 GMT</pubDate>
    </item>
  </channel>
</rss>
