"Quick" Intro

Alright, so I've created this blog mainly to post about my little (or sometimes rather larger) projects and potential ideas that I'm working on, which means a lot of .NET related stuff. At the moment, this looks like it's going to be XNA (for Windows) and my attempts at a 2D game engine. Of course, I can't resist having a few smaller side projects which usually focus on one or two cool parts of the framework.

Also, I suspect many of the posts will just be links to articles or other blogs on things I randomly come across in my searches. I've already built up a pretty solid collection of links on all sorts of great topics. It's just a matter of filtering through them and passing them on to you now.

As with most blogs, I'm not yet sure where it will take me but in the short term, you can look forward to:

• My library for playing animation/video in XNA... this seems like a much in demand missing feature of XNA. In addition, I've started on a Music class, which should hopefully mean no more down-sampling your huge WAV files until they get crackly and trying to fit them them into XAct without doubling the total size of your game.
  
• Some snippets on how to set up a useful remoting app in .NET (really, an beautifally simple way of getting two programs, whether on the same machine or miles apart, to communicate) - something that many coders have tried to create or replace without even knowing it exists. It seems that even the networking devs like to stay away from this area, and certainly the many newbie articles you might find are fairly useless for doing much more than a "Hello World" across two processes. This is a new area to me, but I've been doing a good bit of experimenting and you might like to know that remoting isn't just slow SOAP/TCP channels but has an IPC method too - that's a Windows equivalent of pipes, for Linux/Unix fans.
  
• Finally, an open-source obfuscator for any .NET executable. Ok, don't lose interest yet - I'll be explaining exactly how it works in a future post. In baisc terms, the primary purpose of the thing is to protect executables from being disassembled by mucking around with the MSIL (a friendly, text-based language at a similar level to VM byte code). .NET notoriously has the poorest security against reverse-engineering of any language out there. I suspect even Java, which also uses a VM, has at least *some* measures. And wait - before you criticise the irony of making OS sofware to encourage the development of closed-source, realise that some people really do need to protect their "intellectual property". That's why if this succeeds, it will be the only obfuscator for .NET that's both full-featured and free.

Ok, that's all I have to say. I don't want to defeat the whole purpose of a blog by condensing everything in an essay now, eh? Now hopefully I'll be able to make pretty regular posts here - and expect some good news if you're an XNA developer, as I'll be posting and explaining that library in a day or two.