{"id":23,"date":"2014-08-17T13:17:00","date_gmt":"2014-08-17T13:17:00","guid":{"rendered":""},"modified":"2016-01-30T23:34:03","modified_gmt":"2016-01-30T23:34:03","slug":"resharper-localizable-string-literals","status":"publish","type":"post","link":"https:\/\/tpodolak.com\/blog\/2014\/08\/17\/resharper-localizable-string-literals\/","title":{"rendered":"Resharper – localizable string literals"},"content":{"rendered":"

Everyone who has ever tried to create multilingual application knows, that this is very tedious task. The most repetitive work is usually moving hard-coded strings to resource files. Fortunately with Resharper this is definitelly less painfull than usuall.
In order to point out localizable parts of application , it is necessary to decorate classes with System.ComponentModel.LocalizableAttribute<\/i>. \"LocalizableAttribute\"<\/a>However, usually we want to localize an entire program, so more universal solution is to set appropriate project configuration in properties window. To bring up this window, select project file and then press F4<\/i> button.
\n\"PropertiesWindow\"<\/a>
\nFrom now on, Resharper shows warnings indicating that our hard-coded strings might be moved to resource file. Pressing ALT+ENTER<\/i> on these strings will bring up the context menu action, where new option – “Move to resource”<\/i> is available.
\n\"MoveToResourceContextAction\"<\/a>
\nChoosing this option will bring up the “Move to Resource<\/i>” window. However if we do not have any resource files in our project, we will get this message.
\n\"NoResourcesFound\"<\/a>
\nIn order to create these files, right click on project and choose Add->New Item<\/i>. Now, select Resource.resx<\/i> file and name it for example LocalizableStrings.resx<\/i>.
\n\"AddingsResource\"<\/a>
\nIn this resource file we will store values for our “default language”<\/i>. Supporting more languages require us to create additional LocalizableString files with appropriate LETF<\/i> tags suffixes.
\n\"Allfiles\"<\/a>
\nNow, we are able to move our hard-coded string to resource files.
\n\"MoveToResource\"<\/a>
\n\"aftermove\"<\/a>
\nBy default Resharper adds hard-coded strings to default resource file, so we have to specify values for localizable string for other languages. In order to do that, first navigate to resource entry in LocalizableStrings.resx<\/i> file by holding CTRL<\/i> and clicking property “Program_Main_This_is_localizable_string”<\/i>
\n\"GoToProperty\"<\/a>
\n\"overriden\"<\/a>
\nand then press ALT+ENTER<\/i> and choose “Override ‘PropertyName\u2026'”<\/i>. This operation brings up “Edit Resource”<\/i> window where You can easily navigate between resource files and update given resource property
\n\"EditResourceDialog\"<\/a>
\nResharper not only is able to move strings to resource files but also can use existing ones. This basically means that if we use hard-coded string which already has been added to resource file, Resharper will suggest to use predefined resource
\n\"localizable<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Everyone who has ever tried to create multilingual application knows, that this is very tedious task. The most repetitive work is usually moving hard-coded strings to resource files. Fortunately with Resharper this is definitelly less painfull than usuall. In order to point out localizable parts of application , it is necessary to decorate classes with […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[52,51,53,50],"tags":[196,197,198,199],"class_list":["post-23","post","type-post","status-publish","format-standard","hentry","category-globalization","category-localization","category-r","category-resharper","tag-globalization","tag-localization","tag-r","tag-resharper"],"_links":{"self":[{"href":"https:\/\/tpodolak.com\/blog\/wp-json\/wp\/v2\/posts\/23","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tpodolak.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/tpodolak.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/tpodolak.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/tpodolak.com\/blog\/wp-json\/wp\/v2\/comments?post=23"}],"version-history":[{"count":7,"href":"https:\/\/tpodolak.com\/blog\/wp-json\/wp\/v2\/posts\/23\/revisions"}],"predecessor-version":[{"id":534,"href":"https:\/\/tpodolak.com\/blog\/wp-json\/wp\/v2\/posts\/23\/revisions\/534"}],"wp:attachment":[{"href":"https:\/\/tpodolak.com\/blog\/wp-json\/wp\/v2\/media?parent=23"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/tpodolak.com\/blog\/wp-json\/wp\/v2\/categories?post=23"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/tpodolak.com\/blog\/wp-json\/wp\/v2\/tags?post=23"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}