View previous topic :: View next topic |
Author |
Message |
marcjvr
Joined: 28 Apr 2009 Posts: 1
|
Posted: Tue Apr 28, 2009 2:36 pm Post subject: Shared resx file generation instead of resx file per xaml |
|
|
Hi
Is it possible to get the Globalizer tool to generate one resx file that can contain all the resources for multiple xaml files?
My project team does not wish to have a resx file for every xaml doc we have. We rather want to have one shared resx file that all our xaml docs use.
Thanks
Marc |
|
Back to top |
|
|
Infralution
Joined: 28 Feb 2005 Posts: 5027
|
Posted: Tue Apr 28, 2009 11:11 pm Post subject: |
|
|
The ResxExtension supports placing resources in any resx file (so it is possible) however the Globalizer.NET converter (that converts existing XAML to use the ResxExtension) creates a separate Resx file for each window. This means that if you wanted to go this approach you would need to hand code or modify the converted code to put all the resources in one file.
Putting all the resources in one file has a few drawbacks:
- It creates version control issues when there are multiple developers working on different windows
- It makes it more difficult to know which resources are required for specific windows
- It requires resource names to be unique for the whole application (instead of just the window)
The only issue with using separate resx files is managing them – however Globalizer.NET takes the pain out of that and means your translator only has to deal with one file.
Have you seen the article on Code Project about the Resx Extension? – this explains in more detail some of the design rationale. _________________ Infralution Support |
|
Back to top |
|
|
|