I have a .net project using SQL Server backend that I'm looking at localising. Handling localisation within .net is straightforward enough, got it managing the views, data annotations, messages etc.
I am in an ongoing debate with my technical managers regarding accessing lookup tables and he keeps waving the "best practices" mantra at me but offers nothing concrete, I have several lookup tables ...
What’s the state abbreviation for Arkansas? Is it AR? AK? AS? Maybe you’ve got a data frame with the information. Or any info where there’s one column with categories, and another column with values.
Some results have been hidden because they may be inaccessible to you
Show inaccessible results
Feedback