Something I haven't really played around with is using IL directly from my codebase. However, Whizzo's Development Blog: Dirty check on objects[^] looks to be an interesting way of determining whether an object has changed or not. Saves having to manually add IsDirty semantics to types (which can be fragile).
As discussed in this[^] post in the Lounge, I've decided to run a series of posts about the books that I recommend and the books I would recommend avoiding. In order to keep a permanent record, I'll update this entry as I go on.
Really well thanks Pete. Have been working on my business for the last few years but have had to go back to full time employment due to finances which is a bugger. We're in talks with quite a few investors and wotnot but the timeline hasn't quite married up yet. Watch this space!
I've just started working for a company in Bristol called Rock Solid Knowledge, really great guys. The founders all used to be Developmentor trainers one of which ran the course I attended way back in 2008 when I started .NET. Two of the founders recently wrote and published the Pro Async .NET book through Apress. Such a great learning experience.
How about yourself chap? I saw you've been doing a fair bit with Intel which is very cool!
It's good that you've got work to keep you going while you seek alternative funding and that you seem to like what you're doing.
Yeah, I've been doing a lot with Intel. It's pretty cool what they are doing and I am now involved in so many different areas with them that I have precious little time to myself because there's so much to learn.