OdeToCode IC Logo

Auto resize DataGrid columns

Wednesday, January 21, 2004 by scott
I just updated an article on OdeToCode which resizes the columns in a Winforms DataGrid to match the longest content. Although I'm fairly happy with the reflection method - I'm still wondering how to determine the MappingName property without an ugly switch statement. This feature was in the early beta of VS.NET - I wonder why it dropped?


Sunday, January 18, 2004 by scott
I know people who will laugh at me but I am positive Windows gets a really bad rap on uptime. I was in crunch mode recently and hammering on my 2000 Server desktop at the office. I’d actually terminal service into the machine on my desk (while at my desk) so when I had to leave I could just disconnect the session. Later I’d terminal service from home over a VPN and pick up right where I left off.

At one point I began thinking it had been a long time since I logged out of this terminal service session, much less rebooted the computer. I grabbed an UPTIME utility and saw it was 89 days since the last reboot.

Around day 98 my co-workers began to become annoyed with me talking about hitting “the big 1 – zero – zero”. One person threatened to come into the office some night and power the machine down.

The real problem started around 110 days of uptime. I received an internal CD writer drive for the machine. I wanted to see how long I could keep the machine up, so I hid the drive under my desk.

Around day 120 I was getting very nervous. A co-worker started asking if I was ever going to use the drive. When working at a startup you can’t just leave unused resources laying around. People will scavenge any piece of extra equipment that isn’t tied down, bolted, duct taped, and labeled clearly with your name in permanent ink. You can’t even leave a spare CAT5 cable laying around much less a CD burner. After some ceremony, I powered down, opened the case, and installed the drive.

I’ll never know how long the machine could have gone – but I do know current uptime is 32 days, 10 hours, 55 minutes, and 16 seconds. Still a long way to go to catch up to the servers with the longest uptime on the net.

Nifty New Downloads

Thursday, January 15, 2004 by scott

I found a few interesting downloads over the last couple days.

The Open Watcom C/C++ compiler 1.2 Get the binaries and source code here. I have not used a Watcom compiler for 10 years but I am curious to peek around the source code. (via Slashdot).

Microsoft has a 45 day trial download for Virtual PC. If you are a dev and not running a VPC of some sort, you probably should be.

For those of you into OLAP:

Creating Large-Scale, Highly Available OLAP Sites is a must read if you are rolling out a mission critical solution with Analysis Services. Many good pratical answers on how to cluster, stage and setup a solid enviornment.

The OLAP Scribe is a Word macro that uses DSO to dump OLAP database metadata into a nicely formatted Word document.

Best Whidbey Feature Found So Far

Tuesday, January 13, 2004 by scott
I was experimenting with Whidbey and found some really nice new features. My favorite feature, however, is the new File-system web site. You can keep all the files for an ASP.NET app in a simple folder – no dependency on IIS!

This is great news. On several occasions I’ve been driven to screaming fits of hysteria with Visual Studio and where I want a web application to be. I’m tired of editing virtual directory properties and hacking .webinfo files. Simply copying code to a different location or computer should not be this hard (or this hard). The first time I put an ASP.NET app into source control for team development it was quite the ordeal – but that long before they started publishing 17 page and 30 page white papers on the subject.


Robot, Heal Thyself

Monday, January 12, 2004 by scott

So I follow a medical informatics blog since it is sometimes relevant to software I’m currently working on. The blog had a post about an Alabama Hospital trying out an “RN Robot”. This reminded me of a Wired article last year about a Hopkins trail with a “robotic medical surrogate”. I found this article interesting but also amusing because of the following two excerpts:

"People love it. I was very surprised how much our patients enjoy remote video interactions via the robot," says Dr. Louis Kavoussi, a Johns Hopkins professor of urology and a pioneer in robotic surgery

… One patient said she barely noticed Kavoussi had been replaced by a robot.

Obviously amusing to read. Also:

"Even the patients with dementia seemed unsurprised by (the robot's) presence,"

I can imagine there are some patients with illnesses where you just don’t want an android rolling into the room unexpectedly.

In any case, this got me to thinking about some of the hospitals I’ve been in with my current job. The number of nurses who have moved into IT departments initially surprised me. After talking to them, it is pretty obvious why. After ten or fifteen years of being on call and working the midnight shift on a holiday weekend before a major blizzard, any position which is (in theory, anyway) a 9-5 job looks pretty swell. Nurses are highly educated people who can learn new concepts.

What also surprised me was the reporting software some of these nurses / IT people need to use. The report language looks something like:



IF{@occupation!@emp.status @occupation_IF{@emp.status " ("_@emp.status_")"}^/MV["P",Q+1^Q,5]},



Egads. I thought I was back in a mainframe college course 15 years ago. This is not legacy software - this stuff is sold and installed today.

But that’s ok – wherever there is inefficiency there is opportunity…

Good and Bad Software

Sunday, January 11, 2004 by scott
Currently on my bad software list is the MSDN search engine. It seems it has been many months since the search engine worked well. Last night a search produced results where the same article appeared about 100 times in the result list. Search results never seem to find MSDN Magazine articles, unless you go to the home page and search just magazine content. It used to find them. It seems very broke.

On the good software list is Virtual PC.

I currently have the following Virtual PCs setup:
  • Whidbey - Windows 2000 Server with the Whidbey beta installed
  • RSBETA - Windows 2000 with the Reporting Services beta and SQL 2000 installed
  • Mandrake - Mandrake 9 distro of linux. Complete with a functional Mono .NET environment.
  • Longhorn - The PDC build of Longhorn, with Whidbey and the SDK installed.
  • Experiment 2000 - My Win 2000 plaground for trial software, etc.
  • Exchange - Where I installed Exchange Server 2003 to play around.
  • CSK2000 - Where I play with the ASP.NET Community Starter Kit on Windows 2000
  • CSK2003 - Where I play with the ASP.NET Community Starter Kit on Windows 2003 WebEdition

Virtual PC is a great way to experiment with software, test, use different browser versions - there are so many possibilities. It has an undo feature to reset any changes you've made - so even the worst software install can be undone. I keep a Virtual PC image of a Windows 2000 SP4 install around, and whenever I need a new virtual PC I make a copy of the file, attach it to a Virtual PC, and I'm off.

Best of all it keeps my primary OS (2003 Enterprise Server) nice and tidy.

Improving .NET Application Performance and Scalability

Saturday, January 10, 2004 by scott
A newsgroup posting caught my eye and took me to the home of the Microsoft Performance Team. They are working on a guide for anyone interested in the performance and scalability of .NET applications and soliciting feedback.

After reading just two of the chapters (on ASP.NET and ADO.NET) I realized this guide is going to be the reference for .NET performance. It leaves very few stones unturned and mentions or references almost every perf tip I know of (and quite a few I did not). Why do jagged arrays perform better than multidimensional arrays? When could an ASPX page get compiled into a single asembly? The guide is super.

I thought of a few ideas while reading through, and since they are soliciting comment I sent some along. I'm interested to see or hear if they have an impact.