I’m happy today as I’ve written my first bit of Production LINQ code in the form of LINQ-to-XML.
It’s not the most complicated bit of code – only a grabbing of data from a file, but it does do what it says on the tin – uses C# 3.0 and (unfortunately) causes Resharper to complain on a constant basis 🙂
I’ve been having a little bit of trouble lately with WPF, in particular the rendering of an image on the header of the TabItem or GroupBox headers (for example), I have the following code:
Which renders fine in Visual Studio, but the minute I run the app – F5ing – The image isn’t displayed.
It took me a while to figure out – even though the image is in the right location, it’s not actually part of the solution, i.e. I hadn’t added it to the Images folder of the solution. When added there (so it was visible in the solution explorer), happy days!
Recently a post from one of my ex-colleagues got me interested in working my way through a set of problems at the ‘Project Euler‘ site. He piqued my interest, and I started working my way through them (not at any great speed mind – I’ve only done 4 so far – and I’ve been doing it for 3 days!!).
Then he posted another post about the problems and solving them in a functional way rather than errr…. non-functional – thanks Steve! Now I feel compelled to look into the functional world, and with good reason from a .net development point of view.
F# is the Microsoft Research functional language, and is designed to fit in nicely with the .NET framework, and (indeed) Visual Studio. To be honest, I haven’t explored much beyond looking at the examples and playing with them – but it looks good. In line with what Steve (hackinghat.com) said, I too haven’t really played with functional programming since uni, though in my case, that’s only 4-5 years ago now 🙂
Until I can afford to buy my own hosting, I’ve opted to move my blog from my spaces location (cskardon.spaces.live.com) to the multiple tag freedom of wordpress!
(There will be more coming – I promise :))