You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm picking up trying to make localization work on a project where I was using localization some years ago, but then the specific customer that wanted a different language went away, so I forgot about it for ages, but now the requirement is back.
When I Import resources from my existing ResX files, they are created in the database with just the filename as the resource set name:
(the full filename here is c:\sourcecode\monad\code\ui\sales\checkout\App_LocalResources\Delivery.aspx.resx and it's just extracting "Delivery.aspx" as the resource name)
But at runtime, when it's trying to find a resource in the database, the relative path IS being used in the resource set name:
which means that there's no match.
Am I doing something wrong here? It seems like it shouldn't be possible to configure it to work one way in one place and a different way in another.
The text was updated successfully, but these errors were encountered:
I'm picking up trying to make localization work on a project where I was using localization some years ago, but then the specific customer that wanted a different language went away, so I forgot about it for ages, but now the requirement is back.
When I Import resources from my existing ResX files, they are created in the database with just the filename as the resource set name:
(the full filename here is c:\sourcecode\monad\code\ui\sales\checkout\App_LocalResources\Delivery.aspx.resx and it's just extracting "Delivery.aspx" as the resource name)
But at runtime, when it's trying to find a resource in the database, the relative path IS being used in the resource set name:
which means that there's no match.
Am I doing something wrong here? It seems like it shouldn't be possible to configure it to work one way in one place and a different way in another.
The text was updated successfully, but these errors were encountered: