<?xml version="1.0" encoding="iso-8859-1"?>
<!-- generator="WebEdit.NET" -->
<rss version="0.92">
  <channel>
    <title>Gregor R. Peisker</title>
    <link>http://peisker.net/</link>
    <description>Gregor R. Peisker's Site</description>
    <webMaster>gregor@peisker.de</webMaster>
    <copyright>&#169; Gregor R. Peisker</copyright>
    <lastBuildDate>Sun, 3 Oct 2004 07:44:35</lastBuildDate>
    <pubDate>Sun, 3 Oct 2004 12:44:36</pubDate>
    <generator>WebEdit.NET</generator>
    <image>
    	<title>Gregor R. Peisker</title>
    	<url>http://peisker.net/favicon.ico</url>
    	<link>http://peisker.net/</link>
    	<width>16</width>
    	<height>16</height>
    	<description>Gregor R. Peisker</description>
    </image>

<item>
    <title> <![CDATA[ Happy New Year 2009 ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20090102.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
I wish you all the best for the new year. May your dreams come true, but be careful what you wish for.
</p>
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;;font-style: italic;">
It's just a box of rain<br />
I don't know who put it there<br />
Believe it if you need it<br />
Or leave it if you dare<br />
But it's just a box of rain<br />
Or a ribbon for your hair<br />
Such a long long time to be gone<br />
And a short time to be there
</p>

<p style="margin-top: 0pt;">
<a href="20090102.htm" title="Happy New Year 2009">Permanent Link</a>
</p>
        ]]>
    </description>
    <pubDate> Fri, 2 January 2009 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Fourty-Two K ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20080426.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Today, I finally cracked the fourty-two-dot-one-eight-something kilometers limit, aka, marathon distance.
The walk wasn't so bad, really. Not too much pain, plenty of sunshine, cool air, and a bit of wind.
</p>
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
As far as I know, I'm still alive, at least I'm aware of typing this now in my favorite text editor.
I'm having water and bananas with my favorite <a href="20060827.htm">Hot Tuna</a> music, and I won't
be of much use for anything else today.
</p>

<p style="margin-top: 0pt;">
<a href="20080426.htm" title="Fourty-Two K">Permanent Link</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 26 April 2008 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Happy New Year 2008 ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20080103.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
A happy new year 2008, and a good time offline whenever you dare.
</p>
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
WebEdit.NET runs on Vista, indeed (with CLR v2.0.50727).
</p>

<p style="margin-top: 0pt;">
<a href="20080103.htm" title="Happy New Year 2008">Permanent Link</a>
</p>
        ]]>
    </description>
    <pubDate> Thu, 3 January 2008 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Boxing In The Dark ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20070915.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Since I've addressed various aspects of .NET delegates at this site in the past,
I thought I'd share another piece of trivia, if only for the sake of completeness:
</p>
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
If you point a delegate to an instance method of a value type, then that value gets
boxed. The boxed object can then only be retrieved through the <span class="beispiel">Target</span>
property of the delegate. 
</p>
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
This is not an issue in properly designed code: Structs are used when the focus is on
simple data, not complex data structures and loads of tricky interactions. Normally,
there's no reason for a delegate to point to any instance unless the data in that
instance is either used or changed by the call. Since value types follow value, aka
copy, semantics, it's hard to know which data the call will operate on. This means
that using a value type instance method for a delegate is a bad idea to begin with,
so the implicit boxing doesn't really make things worse. 
</p>

<p style="margin-top: 0pt;">
<a href="20070915.htm" title="Boxing In The Dark">Permanent Link</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 15 September 2007 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Parameterizing Event Subscriptions ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20070728.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
When registering for an event, the subscriber normally uses syntax like this:
</p>
<p style="margin-top: 0pt;">
<a href="20070728.htm" title="Parameterizing Event Subscriptions">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 28 July 2007 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Parse Tree Visualization ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20070401.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Check out the the FCodeTree form in the Gregor.NetConsole project. The form consists of a
tree view and a text box. You can load code into the form, then it's parsed, and whenever
you navigate in the tree, the selection in the text box updates to highlight the code that
corresponds to that node in the parse tree. Vice versa, if you move the caret in the text
box, the corresponding node is selected.
</p>
<p style="margin-top: 0pt;">
<a href="20070401.htm" title="Parse Tree Visualization">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 1 April 2007 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Calling Open Instance Delegates in .NET Console ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20070311.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Have a look at the <span class="beispiel">filter</span> user function, coded in WebEdit.NET for
evaluation with the built-in code interpreter (.NET Console):
</p>
<p style="margin-top: 0pt;">
<a href="20070311.htm" title="Calling Open Instance Delegates in .NET Console">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 11 March 2007 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Flexible Binary Searches ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20070203.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Suppose you need to perform a binary search under the following conditions:
</p>
<p style="margin-top: 0pt;">
<a href="20070203.htm" title="Flexible Binary Searches">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 3 February 2007 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ 2006 Summary ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20061225.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
2006 has been my best year up to now, by far, and that's it.
</p>
<p style="margin-top: 0pt;">
<a href="20061225.htm" title="2006 Summary">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Mon, 25 December 2006 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Open Instance Delegates and Weak References ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20061119.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Let's run this code:
</p>
<p style="margin-top: 0pt;">
<a href="20061119.htm" title="Open Instance Delegates and Weak References">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 19 November 2006 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ New Project: Gregor.Media ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20061105.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
I'm delighted to welcome a new project in the Gregor.NET application
framework: <a href="dotnet/media.htm">Gregor.Media</a> is the latest
entry.
</p>
<p style="margin-top: 0pt;">
<a href="20061105.htm" title="New Project: Gregor.Media">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 5 November 2006 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Syntax Highlighting for Embedded Code ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20061101.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
How's
<a class="PicLink" href="javascript:top.showPicture('WebEdit.NET - Embedded Syntax Parser', 'dotnet/weembeddedparser.png');">that</a>
for syntax highlighting? Just configure a language in WebEdit.NET
so that it uses Gregor.Editing.Coloring.CEmbeddedLanguageParser as its
syntax parser, specify the tokens that mark embedded code, and optionally
say which language information to use for the embedded and embedding code,
respectively.
</p>
<p style="margin-top: 0pt;">
<a href="20061101.htm" title="Syntax Highlighting for Embedded Code">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Wed, 1 November 2006 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Concurrent Document Views ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20061028.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
WebEdit.NET has been supporting multiple document views for some time now.
From now on, users may also view them concurrently.
<a class="PicLink" href="javascript:top.showPicture('WebEdit.NET - four document views in parallel', 'dotnet/wemultiviews.png');">See here</a>.
</p>
<p style="margin-top: 0pt;">
<a href="20061028.htm" title="Concurrent Document Views">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 28 October 2006 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Resource Storage Provider ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20061021.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
WebEdit.NET offers a new built-in storage provider: the Resource Storage
Provider allows users to read embedded textual resources:
</p>
<p style="margin-top: 0pt;">
<a href="20061021.htm" title="Resource Storage Provider">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 21 October 2006 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Wave That Flag ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20061008.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Have a look at the FlagSet8 struct in Gregor.Core, which is supposed to
compact boolean flags into a more memory-efficient structure. It works
like a flags enum, but it's got a more convenient interface, one that
can safely be exposed to clients, too.
</p>
<p style="margin-top: 0pt;">
<a href="20061008.htm" title="Wave That Flag">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 8 October 2006 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Implementing ToString ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20060904.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
The <span class="beispiel">ToString()</span> method can be used for
several purposes, as <a href="20041226.htm">practice proves</a>. In the
case of using it for diagnostic purposes, as is the original purpose,
you'd typically want to look at all of an object's properties.
</p>
<p style="margin-top: 0pt;">
<a href="20060904.htm" title="Implementing ToString">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Mon, 4 September 2006 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Walkin' Blues ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20060827.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Right now, I'm listening to Walkin' Blues, followed by Invitation,
(off America's Choice, by Hot Tuna), for what must be the twentieth
time.
</p>
<p style="margin-top: 0pt;">
<a href="20060827.htm" title="Walkin' Blues">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 27 August 2006 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Vacation ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20060522.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
I'm taking a vacation from web publishing, until further (implicit?) notice.
</p>
<p style="margin-top: 0pt;">
<a href="20060522.htm" title="Vacation">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Mon, 22 May 2006 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Up and Running ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20060321.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Just to let you know that I'm still up and running, notice that
the Gregor.NET Framework Version 2005 (Whidbey) doesn't run if
Visual Studio isn't installed, because of a dependency on the C
runtime debug version. I'll fix it some time.
</p>
<p style="margin-top: 0pt;">
<a href="20060321.htm" title="Up and Running">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Tue, 21 March 2006 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Universal Callbacks ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20060226.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
The <span class="beispiel">CHandler</span> class of Gregor.Core, which
is a <a href="dotnet/lateevents.htm">universal handler</a> for any event
that follows the common event signature pattern used in
<a href="20050220.htm">dynamic</a><a href="20050606.htm">scenarios</a>,
has attracted a more general companion that allows routing any callback
to a single handler, also for dynamic scenarios:
<span class="beispiel">CCallback(Of DelegateType)</span>.
</p>
<p style="margin-top: 0pt;">
<a href="20060226.htm" title="Universal Callbacks">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 26 February 2006 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Anonymous Methods and Exceptions ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20060222.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
I have outed myself on believing that event handlers are not only to handle
events, but should also <a href="20050226.htm">handle any exceptions</a>
that pop up.
</p>
<p style="margin-top: 0pt;">
<a href="20060222.htm" title="Anonymous Methods and Exceptions">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Wed, 22 February 2006 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Tuples and Projection ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20060219.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Suppose you have a list of people:
</p>
<p style="margin-top: 0pt;">
<a href="20060219.htm" title="Tuples and Projection">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 19 February 2006 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Enums and Generics ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20060216.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Recall that we
<a href="dotnet/languages2005.htm#enumconstraints">cannot constrain
generic parameters to enumerations</a>.
In other words, we can't use <span class="beispiel">System.Enum</span>
as a type constraint. The best we can do is use the value type constraint
(<span class="beispiel">where T : struct</span>), as well as further
constrain T to the interfaces we know every enumerated type happens
to implement.
</p>
<p style="margin-top: 0pt;">
<a href="20060216.htm" title="Enums and Generics">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Thu, 16 February 2006 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Walking Arrays ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20060212.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Question: How do you walk through all elements in a .NET array?
</p>
<p style="margin-top: 0pt;">
<a href="20060212.htm" title="Walking Arrays">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 12 February 2006 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Check the Flow ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20060207.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
The methods in the <span class="beispiel">Check</span> and <span class="beispiel">Flow</span>
modules in Gregor.Core are very similiar. In the first case, an
<span class="beispiel">ArgumentException</span> is thrown if some criterion
is not met; in the second case, a boolean value returned. There are two
problems with this approach:
</p>
<p style="margin-top: 0pt;">
<a href="20060207.htm" title="Check the Flow">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Tue, 7 February 2006 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Multi-Level Sorting ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20060205.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Let's talk about sorting again. Our goal is to set up ad-hoc multi-level
comparisons in a simplified, but type-safe fashion. Recall the problem of
<a href="20050430.htm">not having a suitable comparer</a>, or items that
are not comparable at all. With Whidbey, I've settled on two techniques:
</p>
<p style="margin-top: 0pt;">
<a href="20060205.htm" title="Multi-Level Sorting">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 5 February 2006 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Templated Text Generation, Simplified ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20060201.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
In recent posts, I have introduced the
<a href="dotnet/textgeneration.htm">text generation</a>
facilities in the Gregor.Core library. These are quite a complex beast:
an entire graph of objects is used as input for the text generation, and
that graph being shaped by path information contained in an XML document,
with further assistance by a code interpreter
(like <a href="dotnet/netconsole.htm">.NET Console</a>).
</p>
<p style="margin-top: 0pt;">
<a href="20060201.htm" title="Templated Text Generation, Simplified">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Wed, 1 February 2006 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Closed Delegates ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20060128.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
I've talked about
<a href="20051219.htm">open instance and closed static delegates</a>
recently.
What if we could close in on all arguments used in a delegate invocation,
not just the first one? This is handy when you need to save some context,
namely, local variables, for later use.
</p>
<p style="margin-top: 0pt;">
<a href="20060128.htm" title="Closed Delegates">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 28 January 2006 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Generic Method Support ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20060122.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
From now on, <a href="dotnet/netconsole.htm" title="NetConsole">.NET Console</a>
supports calls to generic methods. It was not all that hard to do, because:
</p>
<p style="margin-top: 0pt;">
<a href="20060122.htm" title="Generic Method Support">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 22 January 2006 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Searching for Text in WebEdit.NET ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20060118.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
I've reworked the text searching features in WebEdit.NET. So far, searching
text was limited to the current document (using the Find Text tool window),
or given folders in the file system (with the Find Files tool window).
</p>
<p style="margin-top: 0pt;">
<a href="20060118.htm" title="Searching for Text in WebEdit.NET">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Wed, 18 January 2006 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Using Shell Context Menus ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20060115.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Gregor.WinShell, which brings the Windows Shell to .NET applications,
provides the <span class="beispiel">CShellContextMenu</span> class that
let's an application retrieve context menu items for any item in the
Shell Namespace. This post gives some into how to use it.
</p>
<p style="margin-top: 0pt;">
<a href="20060115.htm" title="Using Shell Context Menus">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 15 January 2006 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ More Fun With Callbacks ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20060112.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
A common pattern in programming is using callbacks. Callbacks come in
various forms, such as function pointers, delegates, overridden virtual
methods, interface implementations, or event handlers. What's common is
that a general algorithm exists, with the callback providing some form
of behavioural detail.
</p>
<p style="margin-top: 0pt;">
<a href="20060112.htm" title="More Fun With Callbacks">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Thu, 12 January 2006 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Implementing Equals ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20060105.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
One of the rules for implementing the Equals() method is that that it
should be reflexive, that is, if object a considers itself equal to
object b, then object b should deem itself equal to a in reverse. And
vice versa.
</p>
<p style="margin-top: 0pt;">
<a href="20060105.htm" title="Implementing Equals">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Thu, 5 January 2006 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ 2005, Anyway ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20051228.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
I'm so much at peace. Snow is falling outside, and colder temparatures
have been promised. The heating in my room is humming; it is the
background noise of my happiness.
</p>
<p style="margin-top: 0pt;">
<a href="20051228.htm" title="2005, Anyway">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Wed, 28 December 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Open Instance Delegates, Finally ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20051219.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
So I've finally figured out how to use open instance delegates, which
are available in .NET 2.0 (Whidbey). For some background on this, read
<a href="20050430.htm" title="Open Instance Property Delegates and Generic Comparers">this post</a>.
</p>
<p style="margin-top: 0pt;">
<a href="20051219.htm" title="Open Instance Delegates, Finally">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Mon, 19 December 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Whidbey Migration ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20051203.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
I have upgraded all projects of the Gregor.NET framework to .NET 2.0,
aka Whidbey. Things have gone rather smoothly, and so I have even
migrated Gregor.WinShell, a C++ project, from Managed Extensions syntax
to the new C++/CLI syntax.
</p>
<p style="margin-top: 0pt;">
<a href="20051203.htm" title="Whidbey Migration">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 3 December 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ .NET Console on the Console ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20051114.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
I've started work on console application utilities, with a console app
infrastructure as the ultimate goal in mind. Every console app should
have easy access to the its environment, to the command line, including
simple validation facilities. You can see how far I have progressed in
the classes in Gregor.Core.Configuration.
</p>
<p style="margin-top: 0pt;">
<a href="20051114.htm" title=".NET Console on the Console">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Mon, 14 November 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Reshaping The Site ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20051103.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
As non-IE users will have noticed, I have decided to reshape my web site
into a very different design. I'm moving away from the complex, scripted,
and framed configuration, though it's hard to give it up. Therefore, for
the foreseeable future, there are going to be two versions of the site:
the old complex one for IE, the new simple one for everybody else. 
</p>
<p style="margin-top: 0pt;">
<a href="20051103.htm" title="Reshaping The Site">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Thu, 3 November 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ New .NET Console Features ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20051030.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
.NET Console has been the focus of attention this weekend:
</p>
<p style="margin-top: 0pt;">
<a href="20051030.htm" title="New .NET Console Features">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 30 October 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Nulls ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20051020.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Wesner Moise has a
<a href="http://wesnerm.blogs.com/net_undocumented/2005/10/null_comparison.html" target="_blank">detailed and insightful post</a>
comparing how C# and VB.NET treat null values (System.Nullable).
</p>
<p style="margin-top: 0pt;">
<a href="20051020.htm" title="Nulls">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Thu, 20 October 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Text Generation ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20051010.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
In my last post on
<a href="20050925.htm" title="Flexibly Navigated Object Graphs">object graphs</a>
I've hinted at code and document generation and the CTextGenerator class.
<a href="dotnet/textgeneration.htm" title="Text Generation">This article</a>
provides more details.
</p>
<p style="margin-top: 0pt;">
<a href="20051010.htm" title="Text Generation">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Mon, 10 October 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Killing Projects ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20051008.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
I've killed the Gregor.Scripting project, because VSA (Visual Studio for
Applications) has been deprecated; yes, there's now Visual Tools for
Applications, but I won't have any part in it. Also, there has been
a great deal of functionality overlap - AddIns, .NET Console, code
editing and building features in WebEdit.NET.
</p>
<p style="margin-top: 0pt;">
<a href="20051008.htm" title="Killing Projects">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 8 October 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Short Updates Note ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20051004.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Today, just for the record, a few notes on recent updates:
</p>
<p style="margin-top: 0pt;">
<a href="20051004.htm" title="Short Updates Note">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Tue, 4 October 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Flexibly Navigated Object Graphs ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050925.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Remember that I introduced a general API for <a href="20050330.htm" title="Simple Object Graphs">navigating among objects</a> using
reflection this spring? This is implemented at two levels:
</p>
<p style="margin-top: 0pt;">
<a href="20050925.htm" title="Flexibly Navigated Object Graphs">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 25 September 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Orcas ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050920.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Whidbey (.NET 2.0) has not even shipped yet, but there's already a lot
of excitement over the next major version, code-named Orcas. The biggest
thing promised is data integration.
</p>
<p style="margin-top: 0pt;">
<a href="20050920.htm" title="Orcas">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Tue, 20 September 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Visual Studio to Command Line ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050917.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Suppose you have a Visual Studio 2002 or 2003 project, but not Visual
Studio, and need to build the project. It's easy to invoke the compiler
on the command line for C# or VB.NET sources - you can simply pass
wildcards for the sources, and a few options.
</p>
<p style="margin-top: 0pt;">
<a href="20050917.htm" title="Visual Studio to Command Line">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 17 September 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Identifier Confusion in VB.NET ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050913.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Understanding the semantics of a VB.NET program is sometimes hard. Sure,
the language has got many descriptive keywords, and the names exported by
its libraries actually make sense.
</p>
<p style="margin-top: 0pt;">
<a href="20050913.htm" title="Identifier Confusion in VB.NET">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Tue, 13 September 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Outlining Documents in WebEdit.NET ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050907.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
There's another member in the family of configurable language objects in
WebEdit: Outline Providers. They scan documents for interesting places,
like headings or method signatures, all depending. The results are
displayed in a new tool window (the Outline Window).
</p>
<p style="margin-top: 0pt;">
<a href="20050907.htm" title="Outlining Documents in WebEdit.NET">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Wed, 7 September 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Creating Web Articles ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050904.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Today, I'll give a little insight into how I create my web site articles,
Journal entries mainly, using WebEdit.NET. The focus is on template-based
editing, with the help of the code interpreter.
</p>
<p style="margin-top: 0pt;">
<a href="20050904.htm" title="Creating Web Articles">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 4 September 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Fixup Providers ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050831.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Lately, I have moved some functionality that wrappes code snippets for
compilation as Script AddIns from WebEdit.NET to the Gregor.Core project.
For C# and VB.NET, there exist so-called fixup providers, which wrap
certain types of code (like method header, types, or using statements)
arround snippets of code. They're part of the language objects now,
which means things are extensible for other languages, and configurable.
</p>
<p style="margin-top: 0pt;">
<a href="20050831.htm" title="Fixup Providers">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Wed, 31 August 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Case Sensitivity in AutoText ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050826.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
WebEdit's IntelliSense-like AutoText feature, provided by the
<a href="dotnet/editing.htm">Gregor.Editing</a> project, supports
case sensitivity in several different ways. In short, we need
to distinguish:
</p>
<p style="margin-top: 0pt;">
<a href="20050826.htm" title="Case Sensitivity in AutoText">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Fri, 26 August 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Command Shells ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050819.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Since .NET Console can be used as an interactive interpreter, how does
it compare against other command shells? I'll just grab a couple of
random points, and compare that against tcsh, which I frequently use.
</p>
<p style="margin-top: 0pt;">
<a href="20050819.htm" title="Command Shells">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Fri, 19 August 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Working With Text In WebEdit.NET ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050807.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Text is universal. It's a good choice for both data formats as well as
interfaces to software (user input, programming). In fact, the most
powerful techniques for working with computers are those that rely on
the ubiquity of that simple, universal format.
</p>
<p style="margin-top: 0pt;">
<a href="20050807.htm" title="Working With Text In WebEdit.NET">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 7 August 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Data Access and Strong Typing ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050731.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
There is a gap between the world of SQL data and objects in statically
typed language environments. Efforts are being made to bridge it, and
there are different approaches pursued.
</p>
<p style="margin-top: 0pt;">
<a href="20050731.htm" title="Data Access and Strong Typing">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 31 July 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Scripting Session ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050723.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Today, I'm just playing with new .NET Console capabilities. I'm running
WebEdit.NET, and my aim is to access an ODBC database, perform a query,
and create an HTML table from it.
</p>
<p style="margin-top: 0pt;">
<a href="20050723.htm" title="Scripting Session">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 23 July 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Language Configuration in WebEdit.NET ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050709.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Finally, users can configure language-support in WebEdit.NET's settings
dialog instead of having to resort to the configuration files. Here are
some example of what can be done:
</p>
<p style="margin-top: 0pt;">
<a href="20050709.htm" title="Language Configuration in WebEdit.NET">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 9 July 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Wants and Needs ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050701.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;"><span style="font-style: italic;">It ain't what you want, it's what you need."</span>
- Jefferson Starship (Sketches Of China).
</p>
<p style="margin-top: 0pt;">
<a href="20050701.htm" title="Wants and Needs">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Fri, 1 July 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ .NET Sheet : .NET Console ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050622.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Since I'm talking so much about .NET Console lately, I thought I'd break
the boredom by talking about .NET Sheet, a spreadsheet program.
</p>
<p style="margin-top: 0pt;">
<a href="20050622.htm" title=".NET Sheet : .NET Console">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Wed, 22 June 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Implementing Nested Procedures ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050618.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
.NET Console supports nesting of user functions. Part of this feature
is capturing variables declared in blocks enclosing the definition of
the nested function:
</p>
<p style="margin-top: 0pt;">
<a href="20050618.htm" title="Implementing Nested Procedures">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 18 June 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Custom Auto-Completion Code Revisited ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050612.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Here's a new version the GetInterfaceImplementation function, which I
presented <a href="20050318.htm">here</a> as an example for custom code
usable in WebEdit.NET's token expansion feature. That function would be
build as part of a Script AddIn.
</p>
<p style="margin-top: 0pt;">
<a href="20050612.htm" title="Custom Auto-Completion Code Revisited">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 12 June 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Why Generics Make Sense In Scripting ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050610.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Generics are about improving compile-time type checking, right? Why do
I support them in .NET Console, then?
</p>
<p style="margin-top: 0pt;">
<a href="20050610.htm" title="Why Generics Make Sense In Scripting">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Fri, 10 June 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Event Handling with .NET Console ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050606.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
OK, with support for user functions in .NET Console, and plenty of dynamic
event management utilities already available, it's no surprise that .NET
Console supports hooking up user function to events:
</p>
<p style="margin-top: 0pt;">
<a href="20050606.htm" title="Event Handling with .NET Console">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Mon, 6 June 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Loops, Functions, and Generics in .NET Console ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050605.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Fire up the latest build of WebEdit, and run the following commands in
the Console window:
</p>
<p style="margin-top: 0pt;">
<a href="20050605.htm" title="Loops, Functions, and Generics in .NET Console">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 5 June 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ .NET Console Revamp ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050522.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Finally! I've managed to write a tokenizer, and a parser, and reworked
.NET Console to use a syntax tree.
</p>
<p style="margin-top: 0pt;">
<a href="20050522.htm" title=".NET Console Revamp">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 22 May 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ The Virtues of Long Names ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050518.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
What's right with the parameter names in the following method:
</p>
<p style="margin-top: 0pt;">
<a href="20050518.htm" title="The Virtues of Long Names">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Wed, 18 May 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Open Instance Property Delegates and Generic Comparers ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050430.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Sure you know the following situation:
</p>
<p style="margin-top: 0pt;">
<a href="20050430.htm" title="Open Instance Property Delegates and Generic Comparers">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 30 April 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Auto-Completion for .NET Console ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050416.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
WebEdit.NET now provides some rudimentary form of IntelliSense for
commands of the "code:" protocol when entered in the Console window.
To be more specific, there is an AutoText list:
</p>
<p style="margin-top: 0pt;">
<a href="20050416.htm" title="Auto-Completion for .NET Console">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 16 April 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Late-bound Delegate Creation, Once Again ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050409.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
With Whidbey, <a href="20040606.htm">late-bound delegate creation</a>,
that is, instantiating a delegate for an event and/or a handler
determined at runtime, is finally as flexible as I've ever wanted
it to be.
</p>
<p style="margin-top: 0pt;">
<a href="20050409.htm" title="Late-bound Delegate Creation, Once Again">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 9 April 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Update History of Downloadables ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050404.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Starting now, you can view the - generated -
<a href="downloads/updates.htm" title="Updates">update history</a>
of all .NET-related download items, back to May 2004. The page is located under
and linked from the downloads page.
</p>
<p style="margin-top: 0pt;">
<a href="20050404.htm" title="Update History of Downloadables">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Mon, 4 April 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Adding Line Comments in WebEdit.NET ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050402.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
A feature long overdue in WebEdit.NET is adding/removing comments on multiple
lines. It's been added now, but it requires the proper language configuration
(syntax providers and syntax parsers are queried for the appropriate strings).
If some a language lacks these helper objects, or isn't configured at all,
you can still prefix lines with a textual command. Here's how to do it for
DOS batch files, of all things:
</p>
<p style="margin-top: 0pt;">
<a href="20050402.htm" title="Adding Line Comments in WebEdit.NET">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 2 April 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Simple Object Graphs ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050330.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Walking object graphs with no special information about the object
relationships is an interesting concept. It's used in Serialization,
but also in property browsers, like the Windows Forms property grid.
It isn't that hard to accomplish with, you guessed it, Reflection:
</p>
<p style="margin-top: 0pt;">
<a href="20050330.htm" title="Simple Object Graphs">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Wed, 30 March 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Data Types as Measurement Abstractions ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050322.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
You'd think now that high-level languages have won the battle, and
developers have easy ways to define abstract data types, we could finally
remember a few lessons from physics class.
</p>
<p style="margin-top: 0pt;">
<a href="20050322.htm" title="Data Types as Measurement Abstractions">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Tue, 22 March 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ The Last Program You'll Ever Download ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050319.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
The Clown utility of my <a href="downloads/gdnfiletools.zip">FileTools</a>
collection (which can be found on the downloads page) now supports building
and running from sources stored on a web server (which is yet another strike
against security):
</p>
<p style="margin-top: 0pt;">
<a href="20050319.htm" title="The Last Program You'll Ever Download">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 19 March 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Alias Substitution and Custom Code ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050318.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
WebEdit.NET's token expansion capabilities enable running custom code
that generates the text to insert. This is best used with alias expansion,
because the text typed is overwritten entirely, and so need not be part
of the final text (which means it can be short &amp; catchy).
</p>
<p style="margin-top: 0pt;">
<a href="20050318.htm" title="Alias Substitution and Custom Code">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Fri, 18 March 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ PowerPoint ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050313.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
I've done a litte ppt <a href="ygsb.ppt" title="?">presentation</a>.
See if you can grok it at the gut level.
</p>
<p style="margin-top: 0pt;">
<a href="20050313.htm" title="PowerPoint">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 13 March 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Markup Entities ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050310.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
In the last post, I wondered how I'd efficiently encode HTML entities
when editing text. Well, the functionality is already there. Suppose
you have a function "EncodeEntities(String) : String" that does it
(there's one in Gregor.Core.Parse), all you need is to place the
following token in the token list, select it, select the text to
encode, and press Ctrl+Shift+T:
</p>
<p style="margin-top: 0pt;">
<a href="20050310.htm" title="Markup Entities">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Thu, 10 March 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Tuples ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050306.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Sheesh, I hate generics! All those angle brackets are a holy PITA when
writing articles about generics in HTML. I guess I need some editor
feature that helps out with that.
</p>
<p style="margin-top: 0pt;">
<a href="20050306.htm" title="Tuples">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 6 March 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ WebEdit.NET Languages Configuration ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050305.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Editor support for programming languages includes various things, such as
syntax coloring, auto-completion, editing conversions, and so on. I have
consolidated these things a bit, aiming at extensibility, configurability,
and general mix-N-match support. The new Gregor.Core.CLanguageInfo class
serves as the root for various configurable things, such as syntax parsers,
token lists, editing converters, and more.
</p>
<p style="margin-top: 0pt;">
<a href="20050305.htm" title="WebEdit.NET Languages Configuration">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 5 March 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ When Not to Show Error Dialogs ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050301.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Imagine what happens if you pop up error messages in code that runs
in a context like the following:
</p>
<p style="margin-top: 0pt;">
<a href="20050301.htm" title="When Not to Show Error Dialogs">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Tue, 1 March 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Do Not Throw Exceptions in Event Handlers ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050226.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Exception handling works closely with the method stack. The decisions
when to throw exceptions, and where to handle them, are a natural part
of the method design process. The focal point is what the method does.
Typically (of course, *not* typically, but I'm being cynical), a short
glance at the method's name clears the point.
</p>
<p style="margin-top: 0pt;">
<a href="20050226.htm" title="Do Not Throw Exceptions in Event Handlers">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 26 February 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Security by Incentives ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050224.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Of all ideologies, the ideology of security is the most unforgiving one,
unlimited in its consequences due to its utopic, absolutist nature. As
Bruce Schneier said, <span style="font-style: italic;">When you put the
police in charge of security, the trade-offs they make result in measures
that resemble a police state</span>.
</p>
<p style="margin-top: 0pt;">
<a href="20050224.htm" title="Security by Incentives">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Thu, 24 February 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Declarative Event Handling ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050220.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
How's that for declarative event handling:
</p>
<p style="margin-top: 0pt;">
<a href="20050220.htm" title="Declarative Event Handling">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 20 February 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Nested Array Syntax ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050212.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
I gotta say that I find the array declaration syntax in the two .NET languages
not very intuitive as far as nested arrays are concerned. The outermost array's
rank specifier is declared left-most:
</p>
<p style="margin-top: 0pt;">
<a href="20050212.htm" title="Nested Array Syntax">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 12 February 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Escape Syntax Madness ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050205.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Have you ever used VBA to generate C# code that generates XML that includes
quotes in attribute values? I did so in a somewhat obscure situation, which
involved manipulating an XML file using rules laid down in an Excel sheet.
</p>
<p style="margin-top: 0pt;">
<a href="20050205.htm" title="Escape Syntax Madness">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 5 February 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Implicitness ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050129.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Although porting my Managed Extensions C++ libraries to C++/CLI (the new
version as of 2005) isn't strictly necessary due to the /clr:oldsyntax
switch, I'll do so happily since the new language is a lot cleaner, more
expressive, and supports more features, such as interface mapping, param
arrays, a much better array syntax, and above all, a type system overhaul
that makes CLR types look natural (handles, tracking references, etc.).
C++/CLI is also the simplest .NET language to define a property.
</p>
<p style="margin-top: 0pt;">
<a href="20050129.htm" title="Implicitness">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 29 January 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ The Gregor.Lists Project Has Died ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20050123.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Another project done gone! I have moved the remaining collection classes,
including those for history management, from Gregor.Lists to Gregor.Core.
Besides having discontinued that silly linked lists class (which I hereby
euphemistically acknowledge (in a subordinate clause (not that I care (oh,
no, I'm over-parenthesizing (is that spelled correctly?))))), all that's
changed for existing code is the namespace: it's Gregor.Core.Collections
from now on.
</p>
<p style="margin-top: 0pt;">
<a href="20050123.htm" title="The Gregor.Lists Project Has Died">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 23 January 2005 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Morning Breeze of Freedom ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20041228.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
By today, early in the morning (European Time), when the maniacs rise,
I have spent half my life living in freedom.
</p>
<p style="margin-top: 0pt;">
<a href="20041228.htm" title="Morning Breeze of Freedom">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Tue, 28 December 2004 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ ToString Revisited ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20041226.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
While the documentation for ToString() says the method is intended to provide
debugging output, this isn't the only way the method is used in practice. I've
come up with at least three - not mutally exclusive - categories, not including
the default behaviour implemented in System.Object:
</p>
<p style="margin-top: 0pt;">
<a href="20041226.htm" title="ToString Revisited">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 26 December 2004 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Spam-filtered History ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20041221.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
How do you manage your browser's history, that is, keep it tidy, yet save
information long enough so as to be useful still? On today's browsers, you
can set an expiration time, like "keep history entries for 21 days" or such
like. 
</p>
<p style="margin-top: 0pt;">
<a href="20041221.htm" title="Spam-filtered History">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Tue, 21 December 2004 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Granny Engineering ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20041126.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
If your grandma needs to keep a list of her contacts, she'll create a
table whose columns are named Last Name, First Name, Date Of Birth,
City, Street, and so on.
</p>
<p style="margin-top: 0pt;">
<a href="20041126.htm" title="Granny Engineering">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Fri, 26 November 2004 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Languages in .NET Assembly Browser ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20041024.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
WebEdit.NET's assembly browser now supports multiple programming languages
in an extensible fashion. Configuration is command-based so far:
</p>
<p style="margin-top: 0pt;">
<a href="20041024.htm" title="Languages in .NET Assembly Browser">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 24 October 2004 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Indexing and Slicing ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20041013.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Should a rectangle be defined as a point and a size, or as two points?
Should a List.Slice method take an initial index and a length, or two
indices called begin and end? Should a period of time be represented
by a start timestamp and a timespan, or by the interval between two
timestamps?
</p>
<p style="margin-top: 0pt;">
<a href="20041013.htm" title="Indexing and Slicing">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Wed, 13 October 2004 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Team Oriented Tokenizing ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20041012.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
The trouble with the <span class="beispiel">strtok</span> routine is that
it uses per-process data to keep track of the tokenizing: if you call some
other code after the first call to strtok, you can never be sure that this
code won't start a tokenizing session of its own, invaliding you sequence.
</p>
<p style="margin-top: 0pt;">
<a href="20041012.htm" title="Team Oriented Tokenizing">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Tue, 12 October 2004 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Abstracting Client Specifics ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20040924.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Suppose you need to implement a custom solution for some client that
deviates from the standard behaviour of your application. The code
goes like this:
</p>
<p style="margin-top: 0pt;">
<a href="20040924.htm" title="Abstracting Client Specifics">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Fri, 24 September 2004 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Method Covariance ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20040914.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
It turns out that the C# folks are aware of the idea of using
argument-compatible, but not exact-matching handler methods for delegates
of a given type. See <a href="dotnet/languages2005.htm">here</a> for more.
</p>
<p style="margin-top: 0pt;">
<a href="20040914.htm" title="Method Covariance">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Tue, 14 September 2004 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ The Doom of the DOM ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20040912.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
IE has an interesting way of interpreting anchor elements (used for
creating document fragment link targets) when it builds up the DOM:
</p>
<p style="margin-top: 0pt;">
<a href="20040912.htm" title="The Doom of the DOM">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 12 September 2004 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Ch-Ch-Changes ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20040905.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
That namespace reorg I pushed on the Gregor.NET framework makes me
a very bad person, but I just couldn't help it.
</p>
<p style="margin-top: 0pt;">
<a href="20040905.htm" title="Ch-Ch-Changes">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 5 September 2004 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Whidbey ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20040822.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
I just downloaded the .NET Framework 2005 (2.0) Beta, and I'm pleased
so far. Except for a few minor glitches, things are working. Of couse
I'm excited about the new language features, but also about the new
framework (Windows Forms, for example).
</p>
<p style="margin-top: 0pt;">
<a href="20040822.htm" title="Whidbey">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 22 August 2004 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Constants, OO-Style ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20040820.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
If someone complains to you about the use of raw int literals instead
of named constants, ask him if this is the proper OO way:
</p>
<p style="margin-top: 0pt;">
<a href="20040820.htm" title="Constants, OO-Style">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Fri, 20 August 2004 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Logic ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20040731.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Suppose you've got the following tasks to accomplish:
</p>
<p style="margin-top: 0pt;">
<a href="20040731.htm" title="Logic">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 31 July 2004 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Three Things on Trees ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20040711.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
It's all about trees this time:
</p>
<p style="margin-top: 0pt;">
<a href="20040711.htm" title="Three Things on Trees">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 11 July 2004 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Coding Blues ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20040620.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Sure everybody has been hit by this mistake before:
</p>
<p style="margin-top: 0pt;">
<a href="20040620.htm" title="Coding Blues">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 20 June 2004 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Late-bound Delegate Creation Revisited ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20040606.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
It turns out that the .NET framework already supports creating delegates
based on method information at run time. The System.Delegate.CreateDelegate
methods are roughly equivalent to what I offer in the Gregor.Core.Reflect
module, although non-public and special (i.g., property accessors) methods
must be shared (see their overload list). My reinventing the wheel has another
advantage: it's possible to use handler method that don't match the delegate's
signature, but are argument-compatible.
</p>
<p style="margin-top: 0pt;">
<a href="20040606.htm" title="Late-bound Delegate Creation Revisited">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 6 June 2004 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Late-bound Delegate Creation ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20040531.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Reflection, delegates, and events is a topic I can't seem to abandon.
I've written about how to create and hook event handler delegates by
means of reflection (recall that instantiating a delegate involves
passing an actual function pointer), but I haven't incorporated that
stuff fully into the Gregor.NET framework until now. While the
Gregor.Core.Reflect module was able to create
<a href="dotnet/propertydelegates.htm">property delegates</a> for
some time, the more common case of creating method delegates was
not supported directly.
</p>
<p style="margin-top: 0pt;">
<a href="20040531.htm" title="Late-bound Delegate Creation">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Mon, 31 May 2004 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Building Code in WebEdit.NET ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20040529.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
You may have noticed that I have been toying arround with custom .NET
build tools for some time (ScriptBuilder.NET, the "Build" and "Clown"
programs of my FileTools collection, and some others not published).
Well, the newest trend is make WebEdit.NET into a modest IDE. I've
dropped the Scripting IDE, at least GUI-wise, some time ago: its
functionality is either available directly through the editor (for
short-term solutions, see the "Execute Code" context menu item, which
allows for statement execution, as well as temporary macros and modules),
or has been taken over by AddIns (long term solutions and persistent
macros).
</p>
<p style="margin-top: 0pt;">
<a href="20040529.htm" title="Building Code in WebEdit.NET">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 29 May 2004 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ IBM on Positional Parameters ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20040507.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
While I'm sure there are plenty of good ways to explain positional
method parameters so that even a dullard like me would understand
them, nobody can quite teach it the way IBM does (excerpted from
<a href="http://www-306.ibm.com/cgi-bin/db2www/data/db2/udb/winos2unix/support/document.d2w/report?fn=db2v7s0methdef.htm#HDRMTHDRESL" target="_blank">DB2 documentation</a>):
</p>
<p style="margin-top: 0pt;">
<a href="20040507.htm" title="IBM on Positional Parameters">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Fri, 7 May 2004 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ You Get What You Pay For ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20040425.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Although the market price for a given good or service isn't always
considered to be as accurate as it should be in a perfect market,
real markets are mostly correct in that they pay very little for
something that doesn't take a lot of effort to produce or provide.
But there's an underlying principle which applies even if there is
no buyer nor seller, but rather some in-house work that's to be
balanced against some internal benefit striven for. In the same way
that, in the market, the price is a good indicator of the value of
something (although some would disagree here), the time and effort
it takes to develop something for one's own use is a sure indication
of its worth. The problem with non-marketable activities is that
predicting the cost/benefit equation is harder, especially if you're
acting as a salaried employee at the workplace. Software development
is no exception.
</p>
<p style="margin-top: 0pt;">
<a href="20040425.htm" title="You Get What You Pay For">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 25 April 2004 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Hacking Like Mad ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20040221.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
What happens if you don't have a working XML implementation on an esoteric
system, like OS/390, that your application is supposed to run on? Case in
point, at work I devised an XML-based document templating solution. There
are roughly two dozen of such templates in use; the bulk of the data
displayed by the application depends on those. And the XML lib won't parse
them, because, well, it's never been intended for EBCDIC.
</p>
<p style="margin-top: 0pt;">
<a href="20040221.htm" title="Hacking Like Mad">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 21 February 2004 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Compatibility, Processes, Solutions ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20040122.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
When API's get changed, and you're not within close physical proximity of the
people responsible, you can do two things: let the problem escalate, because
it's really not your problem if things get thrown arround for no reason, or go
adapt your code, because that gets results much faster. The first option is a
waste of time for at least half a dozen co-workers, but especially for yourself,
since you need to deal with people ("Can you summarize that in an e-mail?") as
opposed to compilers ("Unexpected argument: szName"), and at the end of the day
(or the week), the decision is made, amidst great fanfare, to, well, get with
the program. So you might as well fix the compile errors right away, and call
it a day.
</p>
<p style="margin-top: 0pt;">
<a href="20040122.htm" title="Compatibility, Processes, Solutions">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Thu, 22 January 2004 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ The Song That the Morning Brings ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20040111.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;"><span style="font-style: italic;">
Wake now, discover that you are the song that the mornin' brings.
</span> (The Grateful Dead).
</p>
<p style="margin-top: 0pt;">
<a href="20040111.htm" title="The Song That the Morning Brings">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 11 January 2004 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ I'm Managed, I'm Bored ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20040103.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
With each of the posts on the <a href="http://www.devx.com/" target="_blank">DevX</a> Forums,
there is a link to "report this post to a moderator". I guess I'll add a similiar facility
to each article published here - "report this page to the authorities", or "report this
code sample to Wrox Publishing's legal department" - see, voluntary cooperation just enhances
my value-added personality. Oh, this "managed living" that used to be Life.
</p>
<p style="margin-top: 0pt;">
<a href="20040103.htm" title="I'm Managed, I'm Bored">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 3 January 2004 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ More DHTML Gimmickry ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20031221.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
A new preferenceable feature called Page Collapsing is the site's newest
gimmick.
</p>
<p style="margin-top: 0pt;">
<a href="20031221.htm" title="More DHTML Gimmickry">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 21 December 2003 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ The Groupie and the Geek ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20031216.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
If you're female, and not too flat, you may be a groupie. If you're a developer, and
have items in a flat list, you may want to <a href="dotnet/grouping.htm">group</a>
them.
</p>
<p style="margin-top: 0pt;">
<a href="20031216.htm" title="The Groupie and the Geek">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Tue, 16 December 2003 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Browser and Text Size ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20031130.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
So maybe there is interesting stuff to read on the web, after all. Accessiblity
matters, and a major concern right now is text size. If you browse my site with
Mozilla (have you tried Firebird lately?), using keyboard shortcuts lets you
quickly scale the font to however small you want. Me, I prefer obese fonts these
days for reading those other great sites whose authors actually have something to
say; but from an aesthetics angle, I prefer tiny Tahoma for the sugar-coated
jerkdom that is my own site. For IE, the architecture-arround is a cookie-saved
setting on the preferences page. If you browse with WebEdit.NET, the text browser,
you can use Mozilla-style shortcuts.
</p>
<p style="margin-top: 0pt;">
<a href="20031130.htm" title="Browser and Text Size">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 30 November 2003 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Focus Pocus ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20031105.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
So I tried to tidy up the start page, and make it more focussed, but with me, it's tough.
</p>
<p style="margin-top: 0pt;">
<a href="20031105.htm" title="Focus Pocus">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Wed, 5 November 2003 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Throw One Away ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20030919.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
It's been embarrasing to find out that certain files where missing from the site. My timestamp-based
publication strategy was responsible for this (doesn't work so well when a file with an "old" timestamp
is copied into a directory: which has me musing about the concept of file identity). More consequential
is the fact that the Publisher application (an FTP client offered at the downloads page) was indeed not
in the FileTools zip archive. The reason I learned of these things is nothing less than a crash of my
hard drive. So I just rewrote the Publisher application (plan to throw one away, right?).
</p>
<p style="margin-top: 0pt;">
<a href="20030919.htm" title="Throw One Away">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Fri, 19 September 2003 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Gone ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20030727.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;"><span style="font-style: italic;">
But it's been fourteen years of silence,
it's been fourteen years of pain.
It's been fourteen years that are gone forever,
that I'll never have again
</span>(Guns 'N Roses).
</p>
<p style="margin-top: 0pt;">
<a href="20030727.htm" title="Gone">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 27 July 2003 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Managed Namespace Extension Project ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20030726.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
I've written an article about the GregorView Namespace Extension project, which has already
been living at this site binarily for a few months.
</p>
<p style="margin-top: 0pt;">
<a href="20030726.htm" title="Managed Namespace Extension Project">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 26 July 2003 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ One Dot One, aka, 2003 ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20030628.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Fixed a single, but grave incompatibility issue in the UICore component (regarding the use
of the NativeWindow class for subclassing). That done, the Gregor.NET framework now runs
under the .NET runtime version 1.1 (I'm still cautious, but so far, things look promising).
It's no news that using different runtimes "side-by-side" works perfectly fine, but let me
just say: "me too"!
</p>
<p style="margin-top: 0pt;">
<a href="20030628.htm" title="One Dot One, aka, 2003">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 28 June 2003 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Custom Document Storage Providers ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20030518.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Fixed an incredibly stupid bug in WinShell. WebEdit.NET now supports linking files or any
other command on the toolbar by drag-and-drop; I also tweaked performance a bit. Then, the
DataDocs AddIn can now also write to a database, and the connection structure is persisted
to an XML file as well; furthermore, free form select statements are now supported. The
WebEdit.NET documentation, exclusively offered at this site, now gives some insight into
authoring a custom storage provider.
</p>
<p style="margin-top: 0pt;">
<a href="20030518.htm" title="Custom Document Storage Providers">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 18 May 2003 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Miscellaneous ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20030421.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
The site has got a new start page, which mandates using IE even more. I stand corrected on
a certain aspect of VB.NET's treatment of System.Object references pointing to boxed values
(see the "Changes" topic). The Gregor.NET projects have seen some changes: in WinShell
(custom auto-completion, support for internet shortcuts), UICore (consolidation of the
context menus for dockable tool windows), and WebEdit (again, the context menu, this time
in the edit pane).
</p>
<p style="margin-top: 0pt;">
<a href="20030421.htm" title="Miscellaneous">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Mon, 21 April 2003 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Who Needs This? ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20030309.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Pushed an extensible context menu management system onto WebEdit, a feature long overdue, and
fixed a few things here and there. So there is another update.
</p>
<p style="margin-top: 0pt;">
<a href="20030309.htm" title="Who Needs This?">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 9 March 2003 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Loudness, Wearyness ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20030223.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
What can I say? No updates today. I'm slowly cracking up. She won't let me listen to "Father
Bruce" (by the Great Society), since she's preparing for her exams, and wants things quiet
(she offered me head phones).
</p>
<p style="margin-top: 0pt;">
<a href="20030223.htm" title="Loudness, Wearyness">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 23 February 2003 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ ShellControls Moved ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20030202.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Some updates on Gregor.NET: The ShellControls projects has been taken over by the AppCore
project. The syntax parsers in the Editing project now support CSS, C, and C++. That's it.
</p>
<p style="margin-top: 0pt;">
<a href="20030202.htm" title="ShellControls Moved">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 2 February 2003 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ New, New, New ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20030101.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
A new year is always a new opportunity to try something new, like a new download strategy
or a new upgrade paradigm regarding new versions of my not-so-new Gregor.NET projects
(just have a quick browse to the downloads page to see). So, have a happy new year!
</p>
<p style="margin-top: 0pt;">
<a href="20030101.htm" title="New, New, New">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Wed, 1 January 2003 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ My Holiday Present ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20021222.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
The holiday installment of Gregor.NET includes performance improvements in WinShell, a
new tool window serialization model as well as a new toolbar class in UICore, and various
reworked bits and pieces in WebEdit. So then.
</p>
<p style="margin-top: 0pt;">
<a href="20021222.htm" title="My Holiday Present">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 22 December 2002 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ A New Record! ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20021124.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
I'll remember the 24th of November, since I put five new pages up the site - a new record.
But then, I'll only remember because of the Journal. Why is it, that I feel urged to save
and archive everything (well)? Is it really just the want to present at this site what the
idiot netizenry patronizingly call "content"?
</p>
<p style="margin-top: 0pt;">
<a href="20021124.htm" title="A New Record!">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 24 November 2002 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ .NET Console Integration ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20021102.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
Guess what? A new shipment is on the server (integration of the .NET Console into
WebEdit.NET being one feature).
</p>
<p style="margin-top: 0pt;">
<a href="20021102.htm" title=".NET Console Integration">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 2 November 2002 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Introducing .NET Console ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20020930.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
A new installment of Gregor.NET has arrived with major improvements in UICore and Scripting.
Since these are central components, everybody wins.
</p>
<p style="margin-top: 0pt;">
<a href="20020930.htm" title="Introducing .NET Console">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 30 September 2002 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ WebEdit.NET Sample AddIn ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20020903.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
New updates of my .NET projects have arrived. On the downloads page, you'll find the first
WebEdit.NET AddIn I've developed in my capacity as a third party.
</p>
<p style="margin-top: 0pt;">
<a href="20020903.htm" title="WebEdit.NET Sample AddIn">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Tue, 3 September 2002 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Text Finder ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20020803.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
The site's latest gadget is the Text Finder, which is supposed to ease finding text in a
page. It's got a few minor issues, but hey, it's just another sidebar. 
</p>
<p style="margin-top: 0pt;">
<a href="20020803.htm" title="Text Finder">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 3 August 2002 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Colored Scrollbars! ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20020713.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
I uploaded new versions of my Gregor.NET projects. Mainly, I've fixed bugs, but there's
also new functionality, such as scriptable AddIns in WebEdit.NET. Somehow related to the
latter, I think it's cool that the .NET framework includes command line compilers.
</p>
<p style="margin-top: 0pt;">
<a href="20020713.htm" title="Colored Scrollbars!">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 13 July 2002 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Some Pitiful Gregor.NET Docu ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20020530.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
I wrote a short introduction into each namespace found in my Gregor.NET assemblies. It's
not much, but yes, you guessed it, it's a start, and if you knew me, you'd see that this
is due to an obsession with "being done" with a task (in this case, commenting on what I've
vowed to comment on). VS.NET's just too damn fun and productive a tool, or maybe hobbying
in both coding and web authoring is just taking it's toll.
</p>
<p style="margin-top: 0pt;">
<a href="20020530.htm" title="Some Pitiful Gregor.NET Docu">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Thu, 30 May 2002 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Beyond the Beta ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20020420.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
I'm finally in: I got my copy of VS.NET v1, and after a surprisingly smooth upgrade from
Beta 2, I updated the Gregor.NET project downloads. I started a brain-stormy introduction
to the CodeBuilder application, but once again, I found the sheer amount of what I'd like
to talk about just too overwhelming.
</p>
<p style="margin-top: 0pt;">
<a href="20020420.htm" title="Beyond the Beta">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 20 April 2002 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ The Site Console ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20020323.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
So I finally took the time to write something on my .NET projects. The main motivation is
my growing excitement over WebEdit.NET. The article about it isn't that deep, so forgive me
if it sounds like marketing.
</p>
<p style="margin-top: 0pt;">
<a href="20020323.htm" title="The Site Console">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 23 March 2002 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ .NET Development ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20020203.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
That's what you get when you're too busy writing code with .NET: you forget to update your
web site. Anyway, my efforts at porting everything to the .NET platform are paying off.
I'm introducing a series of projects under the name Gregor.NET. Although I didn't get
arround to write any substantial articles about it, I provide an overview page, as well
as downloads.
</p>
<p style="margin-top: 0pt;">
<a href="20020203.htm" title=".NET Development">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 3 February 2002 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Visual Filters ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20011014.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
I recompiled my VB6 projects against VS.NET Beta 2 updated dependencies (but preserved
backward compatibility). Then, I've added an article about my VBInet project (which will
be continued in VB.NET, but it has been available for download for some time).
</p>
<p style="margin-top: 0pt;">
<a href="20011014.htm" title="Visual Filters">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 14 October 2001 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Site Quotes ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20010901.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
I've updated all my .NET samples and articles. Unfortunately, the topic on file icons is
now obsolete, in the sense that the techniques described there aren't supported anymore in
Beta 2; but I have found a work-arround already. The Collection topic has some good news
on NameObjectCollectionBase. Then, there's UICore, my first C# sample at this site.
</p>
<p style="margin-top: 0pt;">
<a href="20010901.htm" title="Site Quotes">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 1 September 2001 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Beta 2 ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20010815.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
After migrating to VS.NET Beta 2, I've updated a couple of topics on VB.NET ("Changes", and
"Traps"). The bad news is that the samples need some rework still before they're Web-ready.
</p>
<p style="margin-top: 0pt;">
<a href="20010815.htm" title="Beta 2">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Wed, 15 August 2001 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Limbo Time ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20010630.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
A couple of projects have been updated recently: the XML project (a VB6 DLL, just for
downloading) is now usable, although I'm far away from standards complicance. Or even
efficient string parsing, for that matter. Then, I've put an effort into VBInet (also
an ActiveX DLL without an accompanying article at this site). It's already much more
stable than its bastard predecessor equivalents in VB6Core, and new features keep coming
up. Speaking of VB6Core, I fixed a few bugs in CHistory and CRtfBox (the latter got an
interesting new method as well).
</p>
<p style="margin-top: 0pt;">
<a href="20010630.htm" title="Limbo Time">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sun, 30 June 2001 11:11:11 </pubDate>
</item>
<item>
    <title> <![CDATA[ Colors and Operators ]]> </title>
    <link>  <![CDATA[ http://peisker.net/20010616.htm  ]]> </link>
    <description>
        <![CDATA[
<p style="font-family: Tahoma,Verdana,Arial; font-size: 10pt; font-weight: normal; text-align: justify;">
I changed the colors for the sidebar, picking light silver for some entries. This reduces
the number of basic colors on the site to five (white, black, silver, light silver, and
the secret shade of navy blue [as the default]).
</p>
<p style="margin-top: 0pt;">
<a href="20010616.htm" title="Colors and Operators">Read On ...</a>
</p>
        ]]>
    </description>
    <pubDate> Sat, 16 June 2001 11:11:11 </pubDate>
</item>


  </channel>
</rss>

