Open damageboy opened 5 years ago
Question for @diverdan92 @OliaG
Cc @merriemcgaw
AFAIK, MAT is the recommend tool for localizing apps and it will be supported on .NET Core. Adding @TheMATDude to provide more details.
The last version of MAT for VS 2017+ removed some of the barriers for managing .net core apps from within Visual Studio IDE. True CLI support is in the backlog..
Hi any update on this? I have a WPF .NET Core app now using MAT and I'm looking for a way to include it in my build process (local build server)
@TheMATDude do you know if there will be new updates to MAT?
@TheMATDude .net 7 wpf application I try to enable MAT: Project '' was not enabled - it is not a supported project type.
?
(others seem to have also this issue: https://stackoverflow.com/questions/75547404/how-to-enable-multilingual-toolkit-for-wpf-application-net-7-0-type-project )
The Multilingual App Toolkit v4.0 is currently, to the best of my knowledge, Microsoft's current go-to solution for developers aiming to localize their WinForms and WPF applications (amongst other application types support by MAT).
The VS 2017/2019 add-on seems to be made of build-time components, that have various responsibilities, such as generating resource files for localized languages and much more. On top of that, the MAT Visual Studio UI/functionality is responsible for various tasks such as adding new languages and generating rough translations through Microsoft's machine translation services.
From the little I see / understand, there is no current support for MAT inside .NET Core 3.0 projects: When installed in VS2019, MAT fails to even recognize existing projects with MAT items, or add MAT support for such projects.
Except for MAT, there seems to be various support throughout .NET Core for generating resource files from XLF files such as xliff-tasks and deep inside of arcade.
Is there any direct MAT support planned for 3.0 at some point?
Will MAT support include ability to compile MAT enabled project without the plugin installed in VS2019 in Windows? (For example, updating an XLF file by hand on Linux / Mac and invoking
dotnet build
)...?Some clarity about XLF and MAT support in .NET Core 3.0 is probably important for developers considering porting their desktop applications to .NET Core 3.0