August 2003 - Posts

Still posting from infiniblog...

I've been sick for the past few days. I hate being sick, it makes me delerious (sp?). Even worse, I'm currently working on a 'rad' project that is making the developer in me cringe. It's really bad.

I'm having to convert a flat table into a 'normal' database, which would be okay but there are a number of fields for each row that require a one to many relationship. So what I've decided to do in the interest of the 'r' part is just throw the logic into a class that loops thru the records to fill the new structure with data.

The data in the original table has some fields with names like A_this and A_that thru M_this and M_that, much like a spreadsheet. This is the part that is making the developer scream "you shouldn't be doing that!!" It's really hard for me to go against my gut feelings, but I suppose that just shows my lack of experience. Not only do I have a cold, but this code is really making me sick.

Today I wanted to do a test on a .cs file that was written by someone that I work with. For some reason, the code wouldn't run on his Windows XP pro. BTW, it was calling unmanaged gdi methods (GetDeviceCaps) and would compile fine, it just wouldn't run.

So I have him send over the code, all in one .cs file, and I open it up in TextPad. The code itself looks fine, so I fire up the csc in TextPad and the code compiles fine. I then go to the output directory, run the .exe, and bam! it works. So, it must be his installation of XP that is messed up, I guess.

For those of you who want to know what 'the csc in TextPad' means:

  • Go to Configure->Preferences...
  • Highlight the Tools treenode.
  • click the Add button
  • Browse to C:\%windir%\Microsoft.NET\Framework\%version%\csc.exe
  • I also put the label on as csc (v1.1.4322), b/c I have version 1.0 on my machine as well.
  • write some code, then click Tools-> csc

That was it. So now I can write some simple code and compile it directly from my text editor of choice. The only caveat: it compiles with the default options of the compiler, for example I compiled a winform but did not specify /t:winexe, so a command prompt shows up before the window. If you wanted to play with the options, I suppose you could write a batch file and call it from the command line. Or you could use Nant. whatever.

I have a project that requires that I convert a flat FoxPro Database to a 'normalized' Sql Server database. So far, I've gotten the foxpro data into SqlServer.

Today I created an Importer utility class to generate the proper data from flat-> normal database. Now I just need to create the logic that will migrate the data from one to the other... I've gotten as far as creating the datacontainers and filling the initial data from the original flat database into memory.

Also, I learned that you can have two different Main() methods in a solution, which one gets used depends on which one is selected as the startup project.  

Wow. This is something I could have sworn Scoble would post. Are ya fallin off, buddy? Anyways, from Microsoft-Watch:

Microsoft Watch: What's the future of Mono, Ximian's implementation of .Net on Linux?

Stone: We are going to continue to push it. .Net on Linux is a great idea. We just hope Microsoft isn't against the idea.

Yes, .Net on Linux is a good idea, and I doubt Microsoft will have a problem with it. I mean, have they yet? Read the Article.

Too funny. I try to post mainly .net related findings, and enjoy relatively low traffic here other than the occasional google or yahoo search on "object reference...".

All it takes is a nearby Texan to post about one thing non-dotnet...and I've gotten a bunch of hits about my potty humor. I'm not that good a programmer, anyway:)

I get the following error nearly every time I get a newsletter from 

I haven't found out what it means yet, but isn't it ironic? Dontcha think?

Alex Lowe says:

My motto: You've got to know someone's pain to make it go away.

Adding to others who have stated it, I'd like to congratulate Alex Lowe on his new position at Microsoft. I spoke with him directly about this, and got the above quote in response to a discussion about some Evangelists that I've met (not that one, he's actually pretty cool in person) getting out of touch with what's going on "In the trenches".

The quote alone makes me confident that Microsoft has made a wise decision. Good luck, Alex!

More Posts