WPF: problem with 1.*, non-globalized, locally defined component, & signing
We believe it only happens if all of these things are true:
1) Your project has a version number with an asterisk in it (auto-incrementing).
2) You are not building a globalized application (set via UICulture setting in the project file).
3) In a XAML file, which is configure to be compiled as a Page, you are referencing a type that is from the same assembly that the baml file will be compiled into. (Locally defined component is the term our team often uses for that.)
4) You are signing your assembly.
Currently, we think we aren’t going to fix this problem in v1, since it is a bit risky, we are done, and there are 4 different work arounds.
Please yell if this is going to be an extremely common scenario…or if we are crazy for not fixing this now.