Today I stumbled over a framework v1.1 issue related to the wellknown System.Collections.Specialized.NameValueCollection. I used it in a public interface as a return parameter and somewhere again as method parameter within a assembly marked with the attribute CLSCompliant(true). The MSDN docs are silent about CLS compliance in that case and I figured out, it is not compliant! Got compile errors like this:

ADSIAuthenticationProvider.cs(31,37): error CS3001: Argument type 'PROCOS AG.Components.Authentication.Shared.IAuthenticationConfiguration' is not CLS-compliant

or

And still very busy at work. Not much free time left to get more progress at Rss Bandit, but recently we get the bugfix release 114 ready for download.

Just read this at Early Adopter's:

"Every line of code you write today (and have to maintain) is 4 lines of new code that you don't get to write in the future. Write your code wisely." [80% of the cost comes after RTM]

He is soo right. I should have made the quote bold and 40pt size...

Today I got a technical support mail from my e-mail provider (GMX):

Does it looks like a real warning? Yes, reading the first two lines of the mail in my OL2003 preview (I'm careful) of the inbox I opened that (bad! But who knows?) and got another warning:

Scan type:  Realtime Protection Scan
Event:  Virus Found!
Virus name: W32.Beagle@mm!zip
File:  Readme.zip
Location:  Mail System

Morality: spamers and worm/virus mass mail senders are real humans. They did not simply take over random e-mail addresses to spoof the sender address, they impersonate it! Fortunately nothing badly happens to my system :-/

You are carefully enough?

...to my wife and all the other people celebrating today all the best!

Today I stumbled over this issue with the Visual Studio 7 Forms Designer:

 "The class Main can be designed, but is not the first class in the file.  Visual Studio requires that designers use the first class in the file.  Move the class code so that it is the first class in the file and try loading the designer again."

Here is the sample code:

namespace Test
{
 public class MyEventArgs {
  public string Param1;
  public bool Param2;
 }
 /// <summary>
 /// Summary description for Main Form.
 /// </summary>
 public class Main : System.Windows.Forms.Form
 {
 }
}

So: avoid this by using separate files for each class if possible or keep at least the forms class code alone.

Now also our public RSS Bandit forums at http://www.rssbandit.org/forum has feeds: http://www.rssbandit.org/forum/rss.asp (returns top 25 recently posted topics). You can have a look to the rss content to get infos about how to limit postings or subscribe to a special subsection.

And: today I found I can also read feeds from my local living region: http://www.szon.de/xml/rss_info/?SZONSID=7831f2ef8071d0bee0cef8ff4ecf284c (Schwäbische Zeitung, local news).

Was nice to watch and see my Rss Bandit coworker alive

if (System.Runtime.Version.Major == 1 && 
    System.Runtime.Version.Minor < 1 ) {...} else {...}

Isn't this (and variations) enough to have:

if (Environment.OSVersion.Major == 5 && 
    Environment.OSVersion.Minor >= 1 ) {...} else {...}

There are really enough differences we have to consider... :-(

Hey, partitially good news: my local RssBandit beat build 109 does not fail anymore on Sam's test feed, if it is compiled with .NET 1.0: http://intertwingly.net/stories/2004/01/12/broken.rss. It display the Not so smart quotes post with content Postels law. But IE and also the validator still fails and complain about:

The XML page cannot be displayed

Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.

---

An invalid character was found in text content. Error processing resource 'http://intertwingly.net/stories/2004/01/12/broke...

      <description>Postel

Sorry

This feed does not validate.

line 15, column 25: XML Parsing error: <unknown>:15:25: not well-formed (invalid token) [help]
      <description>Postel’s law</description>
                        ^

Looks like, we "simply gathering the data" now...

But note: if I compile against .NET 1.1, it fails parsing on invalid character in the given enconding. 
So .NET 1.0 uses a more lazy XML implementation? 

Should we switch back to just "gather the data"?

I recently refreshed the beta bits because of some more fixed bugs and to enable testing of the newly added UI languages portuguese (bras.) and polish.

Yesteray we visited the island Mainau, Lake of Constance. Yes, we live at the lake, but it isn't just a trip of 10 minutes: a hour by car followed by a 20 minutes cruise. But the childs really like it! It has a huge playground, wild and animals to stroke, pony riding, a house full of exotic butterflys, last but not least: nice flowers bushes and trees from all over the world. And at that moment it does not have too much tourists Overall: nice weather and a nice restful day.

Which OS are You?