Since XNA does not have 64 bit binaries; you need to compile everything to 32 bit. Right click and choose 'properties' on all the projects in your solution (including the lidgren projects) and in the 'Build' tab, choose Platform Target: "x86" - instead of "Any Cpu".

Well, up to one frame of latency, and only if vsync is turned off. Anandtech recently ran this article which answers most questions about triple buffering and vsync.

The problem seems to be you're not calling DrawText() anywhere; try adding a call from Draw(). Also, the title is a bit of a misnomer since your question has nothing to do with networking.

There are some NAT traversal code in the library; There's a thread about it in the discussion forum (http://groups.google.com/group/lidgren-network) - there's no wiki, at least not on the current library that I know of.

Did you try just passing (IntPtr)null to the creation method? I haven't yet gotten all things to work properly, but setting up the device seems work.

Another option is to use Matrix.CreateLookAt(). Rmember you may need to transpose your matrix afterwards.  

The only working solution I know of right now is to include MDX and use their Unproject().

Sorry dexy, but i'm getting the exact same result from your method as I do from Xna (... since they're almost the same). We still use the old MDX Unproject() to get correct behaviour, but it's an ugly dependency I'd like to get rid of.

JohnWestMinor:I was thinking more along the lines of other Lidgren based games. The LIVE! online components no doubt are robust. Any library bugs you report are greatly appreciated :-) --michael

I agree, in general winforms works better with xna and has a much lower learning threshold than wpf. But for larger applications you should definately consider WPF as its much more scalable performance wise and, once you've gotten used to the sometimes-ass-backwards WPF way of doing things, you will have a leaner and meaner application.