Encodings Matter with .fx Files

I was tearing my hair out, trying to figure out why my .fx file wasn’t compiling with fxc.

Eventually I figured out that if I saved the .fx file with a text editor (TextPad), fxc would just work … (previously I was saving this file using Visual Studio).

Ok, by chance I ran across Pavan Podila’s post on the matter. Ah, that’s why!

Apparently, the default encoding for text files is Unicode (UTF-8 with signature) – Codepage 65001 … and apparently fxc doesn’t compile .fx files if they have his encoding.

Argh! Wish I had seen that post sooner.

Some good news on the matter, however, is that the Visual Studio templates that Greg Schechter has posted on his blog … set the encoding to Western European (Windows) – Codepage 1252 … which does compile.

So, if you use these templates, you won’t have to think about it … which is a good thing.

So Cool: GPU Based Effects in WPF

I just have to blog about this … although there must be a million other things that I would like to blog about. (Where do people find the time?)

With the service release of .NET 3.5 (now in beta), you can program effects that will run on the GPU. This means all the coolness, none of the badness (slow performance).

Greg Schechter is running a series of blog posts to introduce people on how to create these effects.

Channel 9 also recently had a great video by David Teitlebaum covering some of the new graphics capabilities (including GPU rendered effects) with the soon-to-be-release .NET 3.5 SP1.

Here are some more posts on .NET 3.5 SP1:

I can’t wait to see the effects that are going to come out of the WPF community.

Very cool news indeed.