eWorld.UI - Matt Hawley

Preface: For my new version of WebDeploy, I wanted to disband the idea of using extensions. Now, don't freak out...I have a good reason why. One of the most pressing requests has been

Scott Watermasysk likes WebDeploy! Good! BTW - I've you've not seen or used WebDeploy, now is the time. I'm working on version 1.2 which is slated for a 1.2 release. If you follow to scott's post, you'll see some previews.

So I had to make a change to a demo at work today, which is checked into VSS. This change basically was to modify the color of an element in CSS (which happens to be on every page, thats about 250 demo HTML pages).

Who want's to read your news on your TiVo? I'll wait while you think for a second...okay, thats enough. So, for those of you who have your hand raised right now, or those that don't read on...

Today I was visiting a client site doing some data mining on a third party product that they own. Ultimately we will be building reports off of their data using SQL Reporting Services. Well, as I was going through the tables, I kept seeing date fields that didn't look like a normal date field. Much to my dismay, this third party company (who uses SQL Server 2000 as a back end database) doesn't believe that the SQL DateTime field is appropriate for storing dates. No, instead they use a long integer data type and store the date as YYYYMMDD.

How lucky are MajorNelson and others that work at MS and got the Halo2 beta disk. I envy them.

Crazy, isn't it. I thought so too as I was reading an article about how a China based company will be building .NET-based enterprise and e-government packages for the Chinese market. Towards the end of the article, it had a link to an older article about Microsoft's .NET initiative.

I just ran across a great ASP.NET 2.0 Resource Blog by Fredrik Normen. The stuff he posts is just amazing, make sure to check it out.