Mike Bedan @ Work:
This is a test post from my new laptop...

Spent the weekend building a custom ASP.NET server control that does dynamic data-driven page generation.  I'm planning to give it away publicly, so it needs docs and a setup.  I used Ant to build, although NAnt is also a good choice.  It was a breeze to integrate NDoc into the build, and in no time I had MSDN-style help files being automatically generated.  It took a little longer to decipher the XML format used by msi2xml/xml2msi, but with a little bit of help from MSDN and Orca (for looking at what other MSIs do), I have a nicely-branded MSI autogenerate from XML as part of the build, even installing my assembly into the GAC.

~

I've been using RSS Bandit to read my news.  Now you can, too, and you can even mess with the source code.

~

Today I got the first 65 episodes of Hikaru no Go on DVD.  It's a pretty good series; very dramatic.  If we had a hit song based on the game chess, why not a hit cartoon based on go?  I also just saw an episode of Rurouni Kenshin for the first time.  It's one of the most inspiring I've seen in a long while.  It looks like another looming expense.

 

[Better Living Through Software]

Yes! All sofware should be developed with Replaceability in mind! <quote> In my opinion, open source content management --- OSCOM --- can take advantage of this customer unhappiness by deeply embracing replaceability. Make the fight against customer lock-in a deeply-held value which is translated directly into software features. Tell the customers: "Your business strategy counts more than our software strategy. We'll back up our words by ensuring you can throw out our product and switch to another OSCOM product without losing everything you've invested in." Replaceability is also future-proofing. What if the vendor goes out of business? What if the open source project is in trouble next year? Customers have the right to not hate themselves in the morning. </quote> [Roland Tanglao: KLogs]