I’m on a steady road of learning first the basics of this new (to me) technology. Coming from a FoxPro background this has been a massive change of direction and I’ve come to realise just how ‘loose’ FoxPro is as a development language / environment. FoxPro is really great at some things (obviously primarily as a desktop database language) its very easy syntax and loosely typed language are very easy to get going with but it does lack some of the raw power and solid structure of using something like C# and .NET.
One thing I’m noticing is that if your learning a new aspect of something and its proving hard to integrate into your C# code it could mean that you need to look at something again ‘further up the code chain’. If you have good code set up well from the outset it does appear to be fairly easy to integrate new features. Or it could be that you’ve just missed one valuable meaning from a sentence somewhere in the examples your looking at. Basically, if your having to go around the houses to get your new code shoehorned into the code you already have you should probably do a little code review before moving on.
What prompted me to write this post was that I have just gone through the process of implementing some serialization (damn, I hate the Americanisms in .NET!). I’m using a custom Type which I’m using in two ways one is just a fire and forget scenario and one needs to be persisted on the host machine. The strongly typed nature of C# and .NET made implementing the Serialization on the persisted data a breeze! Mind you I should hold fire on that since I’m yet to full test the code. Even though the compiler doesn’t complain that doesn’t mean its going to actually WORK!
Back to it …
EDIT! – OK, I’m pretty chuffed with myself. Its the first time I’ve attempted to perform object Serialization and my code worked first time! Hmm … now to try the Deserialization!