Are there any plans to have better localization support in the Orcas CTP's? The current method of localizing XAML using LOCBAML and manually editing csprog files is not very developer friendly.

The Winform designer has a property (Localizable) that when set will automatically move all strings to resources.

Steve

Steve,

this is an area we are continuing to investigate however we have no firm plans for any changes at present. What changes would you like to see?

mark

Mark,

Possibly something like the Winforms designer. When you set the Localizable property on a form to true, it moves string resources (for example button text) to a resource file (Form1.Resx)

Another approach would be to be able to right click on a XAML file on the solution explorer and click Generate Resource or Add to Resource. This will parse the XAML and put all the strings in a resource. The resource can then be edited in the Visual Studio Resource editor. this approach would be used if the XAML was not created in Cider using the Localizable property.

Steve

Steve, thanks for the feedback. Do you do the actual localization in Visual Studio or just use Visual Studio to create an app that can be localized?

mark

Mark,

We used VS 2005 to do the actual localization.

Steve

Thanks!

mark