KeyValuePair seems to be sealed.. Kind of irratating, since all I want to do is to change the ToString behaviour. So now I have to extend it, and provide wrappers for all the functions, instead of just ToString. Oh well..
Got another invite to go to Microsoft to take part in evaluating the new .NET exams. Unfortunately this time they have put the meeting in the middle of the week, and since I've currently got the minimise my time out of the office, and considering the travel times, I can't go. Sigh.. Would have been nice to see Seattle again. Also when they sent the invitation out, they put everybodies names in the TO field.. Duh.
Continuing to work on the Query generator, finally having decided how to proceed. At first I started working on the screens, but the problem was a lack of clarity regarding the underlying objects. So now I'm starting with the objects, building up a object tree which can be rendered into sql commands (wrapped in a stored procedure). Basically I'm trying to replicate one of our existing queries (done in Access/VBA). Once I'm happy with the result, I can design the screens which will create the objects, followed by a simple compiler to allow experienced users to just type the queries. I guess I'm going to end up with a language vaguely like vb (but, unbelievingly, a lot simpler). While this is all very fun, I can't help thinking theres got to be a better way. Part of the problem is the sheer level of configurability we allow the end user.
Writing it in VS2005 (even with issues, it's a better environment), but it's going to run under VS2003 (for now), which seems to be working ok (after a quick recompile) as long as I remember not to use Generics.. Sigh. The amount of code it could save. But at least I should soon be able to upgrade at work to 2005.
Was running a process to synchronise two databases, which involves the system pulling down a days worth of data from both databases, and comparing them. Every time a difference is found, I log it, and for some of the changes I execute a update command (which gets logged). So, I ran the program from within Visual Studio 2003, and I started the process yesterday. It ran for approx 12 hours, logging some 2.1 million messages, all to the debug window!
When I came in this morning, I discovered that Visual Studio has taken approx 2.5Gb of memory (total of 2GB memory, 2GB swap), and had then stopped. :)
So, unable to break the code, I just stopped it. The memory was reclaimed, but VS then crashed with a Out of Memory exception. Ha ha
Was quite impressed with just how many log messages it did take through.
Print | posted on Wednesday, March 22, 2006 4:20 AM