I’ve recently encountered a lot of frustrating DX (developer experience) problems while working on my WPF OpenGL project. For those curious, I’m disentangling my personal research from the OpenGL libraries and controls (hopefully, I’ll post by Monday). These gripes have no real order, so I’ll just mention a couple:

Renaming a Window class.

Rename the class in the .xaml.cs file. VS will nicely refactor all references including dependency properties (I hate that specific class names are needed for these).

Rename the class in .xaml file. That’s right; VS doesn’t refactor XAML code. It’s not even nice enough to give you a compiler error, you have to run the program to find the unintelligable, unlocalized error. WTF?!?

To maintain sanity, rename the the .xaml file with the new class name. VS is at least nice enough to rename the .xaml.cs file automatically.

If you renamed the file of the startup window, you’ll get another meaningless runtime error. Yay! The fix is to open App.xaml and change the StartupUri.

Compile and hope you didn’t make a single typo anywhere. Then recall fond memories of the winform days when refactoring took care of everything.

Converting an application project into a library. It’s simple but unintuitive. Change the “Output type” in the project properties to “class library”. Now your application will completely break. The fix is to drop app.xaml and the .cs file from the class project. We shouldn’t have to do this!

I needed the ability to manipulate lots of geometry in WPF. Unfortunately, that’s just not feasible with the current framework, so I made this little demo to test out an OpenGL framework that I’ve been working on. It uses vertex shaders, pixel shaders, and framebuffers with some hacked together binding.

I got to the airport an hour and a half before my flight to MIX09 (very unusual for me). I actually decided to be semi-productive and threw this app together before and during the flight. Video coming soon.