Dan Ricker

My feedback

  1. 117 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    18 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

    We are change the model in v4.0, which is currently a Technical Preview. Once this v4.0 work is completed, it will allow enablement the Shared project. As such, the shared project will have its own set of XLF files, eliminating the duplication of the XLF files.

    Dan Ricker commented  · 

    Ok... Rebuilt from scratch a sample project ensuring the shared projects were referenced in the Main project. New changes were picked up. I'll sift through the project/solution files in my "real" work and make them match the current success for MAT references.

    As a side note, because I'm a disbeliever in general, I documented the details of each step for the above verification... The disbeliever in me wanted proof:-) I have that document if you want to add an edited version to the Knowledge base or Q&A for MAT.

    Thank you for responding.

    Dan Ricker commented  · 

    Update on state of MAT V 4.0.1605.0.

    The only way I have been able to update the xlf files with new resw changes is to delete the existing xlf files. Arg...

    Again.. a "Manual" refresh would help a lot here. Having to delete the existing xlf is painful and will cause pain on later updates if I have to delete then manually merge to preserver previous changes.

    Dan Ricker commented  · 

    Update on state of MAT V 4.0.1605.0
    1) The "Things I've done to get MAT working in a VS2015 Universal 10 Solution: " post I made still applies. The *.shproj and *.projitems files need to be manually edit as described to enable MAT.

    2) Mat Successfully detects resw changes in the "main" project.
    3) FAILURE: Mat does not detect resw changes in shared projects.

    I have not found a way to manual force MAT to refresh, manually compare xlf state with source resw state.

    Adding this capability (force a manual update) would allow me to more easily move forward.

    Dan Ricker commented  · 

    Things I've done to get MAT working in a VS2015 Universal 10 Solution:
    -- Environment: Win10, VS2015, Universal 10 (UAP Version 10.0.10586.0)
    -- Solution Projects:
    Main - Application
    Shared1 - Shared Project 1 - Contains UI components
    Shared2 - Shared Project 2 - Contains UI components

    -- Manual Changes:

    1) Shared1.shproj and Shared2.shproj: Add default language xml tag in Globals Property Group:

    <PropertyGroup Label="Globals">
    ...
    <DefaultLanguage>en-US</DefaultLanguage>
    </PropertyGroup>

    2) Shared1.projitems and Shared2.projitems: Added MultilingualAppToolkit Property Group that I copied from Main.csproj file

    <PropertyGroup Label="MultilingualAppToolkit">
    <MultilingualAppToolkitVersion>4.0</MultilingualAppToolkitVersion>
    <MultilingualFallbackLanguage>en-US</MultilingualFallbackLanguage>
    </PropertyGroup>

    THIS DID NOT FIX EVERYTHING.

    I was able to add languages and translate them once. After the first time, the updated to the en-US resw file are not picked up by MAT.

    As a last resort, I'm considering removing all MAT generated content and start new using the updated en-US resw file

  2. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Dan Ricker shared this idea  · 

Feedback and Knowledge Base