Content & Localization Verbiage Changes Are Not Working

    Applies to:
  • Legacy SecureAuth IdP
Deployment model:
  • On Premises
  • SecureAuth version affected: All


    Changes are not showing up once C&L verbiages are changed.  The changes are saved in the .RESX successfully, but the resource compiler is not pushing the new builds.


    There are numerous causes for this to happen; it could be some files are missing, possible corrupt hierarchy of resource files, missing text lines in certain files, or even simply a stuck build. See here for another article


    Push the build manually to see what errors it throws, from there, you can deduct what is going on and figure out how to solve it.


    1. Open up command prompt as administrator, and run this command.

      (Run this command for pre 8.1.1)
      C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\MSBuild.exe D:\SecureAuth\ResourceCompiler\MFA.SecureAuth.Resource.csproj /p:Configuration=Release

      (Run this command for post 8.1.1)
      C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe D:\SecureAuth\ResourceCompiler\MFA.SecureAuth.Resource811.csproj /p:Configuration=Release

    2. There will be a lot of colored text, but go ahead and ignore most of them for now and we're just looking for what is in red before the Build FAILED part.  

    3. From here, you can see that it throws an error saying 'Properties\AssemblyInfo.cs could not be found.  If we go look at the file directory, here is what we see in this case.


    4. We see that AssemblyInfo.cs exists, but for some peculiar reason, the Properties folder is not there.  Go ahead and create the folder and place the respective file in that folder.


    5. Once that is complete, go ahead and run the build manually again and see if it returns errors.  If not, it'll say Build succeeded.  Then you're done!  The verbiage will now reflect the proper changes.

    SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

    Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.

    0 out of 0 found this helpful



    Please sign in to leave a comment.