MAT v4.0.1563.0 contains the feature and fixes based on reported customer issues.
Shared project support for Windows 8.1 apps
Reducing Enablement confusion
”Hey, I selected ‘Enable’ but nothing happened”. Does this sound familiar? Unfortunately it probably does. There are two conditions that cause this to happen. The first one is when the project does not have a default culture defined. Desktop templates such as WPF and WinForms require an extra step to define the default cultures. The second condition is when no resources are defined in the project. This is more common with Store projects as you need to add a resource file with the culture in the path – such as ‘en-US\Resources.resw’. To make things worse, the output panel is hidden by default so you don’t see the problem unless you go looking for it. We have take two steps to reduce this problem.
The first is when a project can’t be enabled, MAT will display a blocking dialog. As a rule we try to avoid block dialogs, but in this case it just makes sense.
The second change deals with projects that don’t have any localizable resources. Instead of blocking the ‘Enable’ step, the project is now enabled and a warning in added to the output panel. The Add translation language dialog will remain greyed out and a build warning is created starting that the project is enabled, but not localization resource were found.
And as with any update several bugs fixes are included. Specifically one pesky blocking bug in the editor that reports ”This type of CollectionView does not support changes to its SourceCollection from a thread different from the Dispatcher thread.” have been fixed.
For a complete list of the changes in this as well as previous updates, please see the change log on our User Voice site: Here is a direct link: http://multilingualapptoolkit.uservoice.com/knowledgebase/articles/460620