Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
ValueLocID property keeps reverting back to earlier value RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi all,

    I am working on localizing some .rdlc files using a method I found online where you set the ValueLocID property of the string you want to localize to the name of the resource in your .resx file. The problem I have is that I accidentally misspelled it and now when I go back and change the ValueLocID to the correct value and build the solution again, it reverts back to the original value. Anybody know why this is happening? 

    Thanks in advance.


    Tuesday, January 2, 2018 6:57 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Aaron Sellers,

    Which version of Visual Studio do you use?

    >> The problem I have is that I accidentally misspelled it and now when I go back and change the ValueLocID to the correct value and build the solution again, it reverts back to the original value.

    What is your code like?

    Please refer to Step-by-Step Instructions in following link.

    https://www.codeproject.com/Articles/16835/Localization-Globalization-of-RDLC-reports-in-ASP

    In addition, our forum is discussing Visual Studio WPF/SL Designer, Visual Studio Guidance Automation Toolkit, Developer Documentation and Help System, and Visual Studio Editor.

    Your issue is related to ASP.NET develop, I suggest you repost a new thread to the following forum for a professional answer.

    https://forums.asp.net/

    Regards,

    Judyzh

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    • Marked as answer by Aaron Sellers Wednesday, January 3, 2018 7:36 PM
    • Unmarked as answer by Aaron Sellers Wednesday, January 3, 2018 8:06 PM
    Wednesday, January 3, 2018 8:13 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I am using VS 2017. I think I just figured it out. I needed to select the control, not the text. When I did that and changed the ValueLocID, it stuck and didn't revert back to the original when I rebuilt the solution. Thanks for your help.

    Wednesday, January 3, 2018 7:36 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Aaron Sellers,

    >> When I did that and changed the ValueLocID, it stuck and didn't revert back to the original when I rebuilt the solution.

    How about the result when you change the other property?

    As far as I know, each language and culture combination require a unique resource file. To add other cultures, you can use your default file as a starting point. So, the specific culture resource file is based on the default resx file. You need firstly set the default resource file.

    Reference: https://forums.asp.net/t/2133840.aspx?Default+Resource+file+and+Specific+Culture+Resource+file

    Therefore, please check that the VALUELOCID value has changed in the source file. If the Valuelocid property is not in the source file, then, the resx properties of other languages created on the source file are useless.

    In addition, RDLC has own forum, I suggest you repost a new thread to the following forum for a professional answer.

    https://forums.asp.net/15.aspx/1?Getting+Started

    Regards,

    Judyzh

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    • Proposed as answer by Judy ZhuY Tuesday, January 9, 2018 9:54 AM
    Thursday, January 4, 2018 7:26 AM