Localizable=true has no effect

[Peter Vestergaard]

Hi
I have a project with quite a number of dialogs in it all with
Localizable=true, and all except one working fine.
But the one is causing me trouble because even though Localizable=true is
set, all strings (.Text properties and the like) are still written to
InitializeComponent() in the .cs file instead of to the .resx file.
I have tried setting the Localizable to false again,
saving/building/restarting studio, and then setting Localizable to true
again but it does not help at all - all strings are still in the .cs file
and when I create a new Menu Item using the designer its .Text is written to
InitializeComponent.
It is only for this one dialog - all other dialogs work as expected.
I have checked my source control and it seems that the problems started when
I migrated from VS2003 to VS2005 - in the last 2003 version the dialog is
loading the strings from the resource manager in the same way as all the
other dialogs, and in the first 2005 version it has the strings written
directly in the .cs file while the other dialogs is doing
resources.ApplyResources. I am not entirely sure that it happened at
migration though as I made other changes after migrating and before checking
in to source control.
Anyone knows a solution? And please do not suggest reimplementing the
dialog - it's huge.
Best regards,
Peter

 

[Peter Vestergaard]

I have found out that this is caused by a 3rd party control I have added to
the dialog. If I remove this control the texts goes back in place (into the
..resx) again and then I add it returns to the .cs file.
Can anyone explain this behaviour and suggest what I can do to work around
it?
/Peter

 

[rossum]

I have found out that this is caused by a 3rd party control I have added to
the dialog. If I remove this control the texts goes back in place (into the
.resx) again and then I add it returns to the .cs file.
Can anyone explain this behaviour and suggest what I can do to work around
it?
/Peter

A long shot - perhaps the name of your dialog clashes with something
in the third party control. Try changing the name of your dialog and
see what happens.

Also read the manual for the third party control to see if that says
anything about the problem. Do they have a help desk or support forum
- that might also help.

rossum