Solving the issue where unexpected languages appear when you submit to the Windows 10 Store (#mvvmlight)MVVM, Technical stuff, Universal Windows Platform UWP, Windows 10, Work
Ah the joy of developing for new platforms
Over the past few weeks, I received a few bug reports where an application that was supporting only one, non en-US language was receiving some errors when being submitted to the store. In short, the store thought that the application was bi-lingual (original language + en-US) and asked for all the assets (description etc) in en-US as well. Needless to say it is no fun for the developer who has to prepare all the assets in en-US at the last minute.
This issue was described here in the CommonServiceLocator library. And unfortunately, because MVVM Light has a dependency on this library, it can also occur in MVVM Light applications too.
It’s a bug!
After reporting the issue to Microsoft, and having one member of the team spend some time on it (thanks!), it so happens that it is due to a bug in Visual Studio 2015. This is a regression in the handling of portable class libraries. And what’s great is that (while waiting for the bug to be fixed), there is a workaround:
- Open your application’s CSPROJ file in a text editor.
- In the first PropertyGroup of the project, add the following line:
This line will prevent the bug from happening, and you should be able to submit your app to the store as usual.