StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12591876
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-09-25T22:14:08.343
FavoriteCount
0
LastActivityDate
2012-09-26T04:19:44.300
LastEditDate
2012-09-26T04:19:44.300
LastEditorUserId
796323
OwnerUserId
796323
ParentId
12591421
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
You don't need any markup extensions to accomplish this. You can do it with a simple ValueConverter. <ol> <li>Add .resx file to your project (for this example we will call it Resource1.resx, with a string value named "String1" value "Hello world!")</li> <li>Create a converter that will convert a string to a localized string. <pre><code>namespace WpfApplication1.Converters { public class ResxLocalizationConverter : IValueConverter { public object Convert(object value, Type targetType, object parameter, System.Globalization.CultureInfo culture) { string result = Resource1.ResourceManager.GetString(value.ToString()); if (result == null) { result = value.ToString(); } return result; } public object ConvertBack(object value, Type targetType, object parameter, System.Globalization.CultureInfo culture) { throw new NotImplementedException(); } } } </code></pre></li> <li>Add a converter instance to App.xaml <pre><code><Application x:Class="WpfApplication1.App" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" StartupUri="Window1.xaml" xmlns:converters="clr-namespace:WpfApplication1.Converters"> <Application.Resources> <converters:ResxLocalizationConverter x:Key="ResxLocalizationConverter" /> </Application.Resources> </Application> </code></pre></li> <li>Put the non-localized string values (or keys) in your XAML. <pre><code><Window x:Class="WpfApplication1.Window1" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" Title="Window1" Height="300" Width="300"> <Grid> <TextBlock Text="{Binding Source='String1', Converter={StaticResource ResxLocalizationConverter}}"/> </Grid> </Window> </code></pre></li> </ol> This will display "Hello world!" in the TextBlock. To localize for French, for example, you would just need to add Resource1.fr-FR.resx to the Visual Studio project (with a string value named "String1" value "Salut tout le monde!"). This will display the French version on French localized PCs, or you can use the ResourceManager.GetString(...) overload that lets you explicitly select the language.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORecommendation on a XAML RESX markup extension
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USHarlow Burgess
UserOwnerUserId
1. USHarlow Burgess
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COInteresting approach. Would that also support runtime changes to the CurrentUICulture?
 singulars
 PostPostId
 PO
 UserUserId
 USKeith Hill

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.