Real World F#
blogs.msdn.com
blogs.msdn.com
The only nit I have is the way MS keeps wanting to pitch F#. I know the spin is to use F# for math-y type things, but I really don't know why you just wouldn't use it for everything. I mean, underlying it is the CLR and the OS. It's not like somehow if you know F# somehow you need to also switch to C# to make a window. In fact, if you keep it functional, many times your functions can work their way into what you previously thought of as framework code, simplifying the entire kit and caboodle. I find that every time I switch languages, start declaring mutable values, or framing up reusable classes -- I end up severely limiting my options for refactoring later on. And functional code is nothing if not hugely refactorable.
Simply because you can switch languages doesn't mean you have to, or even that it's a good idea to do so.
I'd argue that F# is marketed the way it is because it doesn't have a business group with a marketing budget yet or a real evangelism team - it's really the guys at Microsoft Research who are driving its adoption, and they happen to be scientists and mathematicians.
There's a lot of room for trailblazers who want to show off how to use it more everyday scenarios and not just math / science scenarios.
I regret I have not yet learned F#, but studying the Project Euler solutions would be a good approach.