<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://dotnet.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Articles by Richard Arthur</title>
 <link>http://dotnet.sys-con.com/</link>
 <description>Latest articles from Richard Arthur</description>
 <language>en</language>
 <copyright>Copyright 2008 SYS-CON Media</copyright>
 <generator>SYS-CON Media</generator>
 <lastBuildDate>Thu, 28 Aug 2008 02:36:07 EDT</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>10</ttl>
<item>
 <title>Microsoft .NET Feature Story - Powerful Forms Interaction</title>
 <link>http://dotnet.sys-con.com/node/299077</link>
 <description>You have probably seen applications that control their size and positions with greater fluidity than you can get with normal .NET Forms, such as maintaining an aspect ratio while resizing, or docking to the side of a screen. Thankfully there are ways of gaining access to the more powerful aspects of Windows, but they are a bit ugly. In this article, I want to help you write a subclass of Form, which has greater power over its position - namely, I would like to keep the form from ever leaving the screen, not even a part of the side. In the process, we will explore ways to find out about the messages that Windows sends to forms, and how to retrieve their extra data and process those messages in custom ways.&lt;p&gt;&lt;a href=&quot;http://dotnet.sys-con.com/node/299077&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 17 Nov 2006 12:15:00 EST</pubDate>
 <guid isPermaLink="true">http://dotnet.sys-con.com/node/299077</guid>
</item>
<item>
 <title>Catching SENS Events in .NET</title>
 <link>http://dotnet.sys-con.com/node/105651</link>
 <description>Microsoft Windows provides a process called the System Event Notification Service. This service raises events relative to interactive logon, network, and power changes. Using this service an application can be notified when network connectivity changes, when available power decreases, or when a person logs on, locks his or screen, or his or her screensaver starts. This service notifies COM+ of these events, which appropriates them to any subscribing application.&lt;p&gt;&lt;a href=&quot;http://dotnet.sys-con.com/node/105651&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Wed, 29 Jun 2005 16:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://dotnet.sys-con.com/node/105651</guid>
</item>
<item>
 <title>Developing for Outlook with the .NET Framework</title>
 <link>http://dotnet.sys-con.com/node/48808</link>
 <description>Microsoft Outlook has an object model that&#039;s useful for automating any of the objects that it manages. Items like calendar entries, e-mails and tasks are well designed, but sometimes they don&#039;t provide all the functionality that we&#039;d like. For instance, Outlook doesn&#039;t provide an easy way to assign a different e-mail background for each of your contacts.&lt;p&gt;&lt;a href=&quot;http://dotnet.sys-con.com/node/48808&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Tue, 22 Mar 2005 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://dotnet.sys-con.com/node/48808</guid>
</item>
</channel>
</rss>
