More detailed information from one of our developers:

"We have a mixed WinForms/WPF project. Our development department has decided to do the entire localization process exclusively with the traditional Resx files.

The problem is that the program, including the contained Xaml files, is constantly being developed. Although language resources are created on the basis of a relatively up-to-date version, the program is often no longer exactly the same once it has been completed. After delivery to the customer, it may also happen that corrections and enhancements are made to the program, but not to the resources. In both cases, it is harmful if updated Xaml settings in the program are overwritten by the old resource settings. In this scenario, it would be useful to keep Baml resources out of the resource files. We would welcome such a feature.

Until then, we will probably have to make sure that Xaml files and resx resources are not in the same assembly. "

The main problem are the views contained in the BAML. If there is no workaround we will have to live with it.

Thanks,

Andreas

Hello Adrian,
do you know about any progress on this issue. We have exactly the same problem as reported by Andreas in more detail below. The main problem is that obsolet controls are still referenced in the satellite dlls causing runtime exceptions.
Thanks, Olaf