No problem, glad you found it

Forgive it, I not select Messages_2058.XML on the project and change the property "Build Action" to "Embedded Resource" on it



Sorry

Thanks for all Trent, Ben and all the people of this great forum.



I leave the localization stuff for a time while trying to build my aplication and I don´t sure why when I put a Localization Key on a custom login, a problem appears :/ (I thinked that it was resolved setting to use the 2058 localization code)

the debug message is "The specified key [UsuarioyClaveTitulo] was not found within the localization database". I try what you recommend:



Sub GetManifestResourceNames()

For Each lcString As String In System.Reflection.Assembly.GetExecutingAssembly.GetManifestResourceNames()

System.Diagnostics.Debug.WriteLine(lcString)

Next

End Sub



result: I see that Message_Languages.xml appears but not Messages_2058.xml

I try to quit and add it again to the project but nothing changed



I add it to both projects I have (Presentation and bussiness objects), but I think it have to be on the BO project, but anyway on both of them can´t see the xml embedded, any idea? meanwhile I continue trying.



Thanks



- Fabian

The Messages_XXX.xml file generally does not reside on the root of the application.  It generally includes the root namespace and any folder it resides in as well in VB.NET.

My.Root.namespace.Messages_xxx.xml

You can always write a quick program to get the exact name using the GetMenifestResourcenames():

How about we just fix the problem and then give you the updated assembly Will that work

note on the ivan picture on the picture 2 say "Gravar" and in spanish "Save" is "Grabar"

can I change the source localization data where the browsedialog "autopopulate" this key? (I say change "Gravar" by "Grabar" myself without creating a new custom key)

Thanks

thanks Ivan 2058 worked OK
thanks again Trent with my basic questions

Trent, with 2058 worked, I don´t known why with 11274 doesn´t work.

anyway, I will create a Localization project with 2058 Español - Mexico and use it for now

I have a RegisterEmbeddedXmlFile problem? I dont sure but try to call (after reading a post on the forum)

and .net say when I copy this line that the method "Load" can't be called with those arguments

Thanks for all your help

Hi Fabian.

Try the:

MicroFour.StrataFrame.UI.Localization.MessageLocaleID = 2058

I use 1046, but tried 2058 to test and it worked fine, have a look:

Abraços.

After looking at the translation project, we have the Spanish versions set for Mexico and Argentina.  Do we need to add another?  Did it work when you set it to 11274?  Does it work when you set it to 2058?  If not, then you will probably need to manually call the RegisterEmbeddedXML and re-register the localization files.