This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.
↧
New Post: Enum localization
↧
New Post: Dynamic resource dll loading
Only compiled RESX files (wich means DLL) can be used. Loading can be done by simply calling Assembly.Load(...) or equivalent on the target DLL.
↧
↧
New Post: "key: " in designer
No news so far on that topic :-(.
↧
New Post: switching DesignCulture doesn't seem to work
It just works in my environment. Is the library up to date?
Please note, that the designtime support is limited for VS2012 due to changes in their way how to work with sattelite assemblies. Please read the other discussions to get an overview of that topic.
Please note, that the designtime support is limited for VS2012 due to changes in their way how to work with sattelite assemblies. Please read the other discussions to get an overview of that topic.
↧
Updated Release: v2.1.5
- Fix to #9306
↧
↧
Edited Issue: Possible Bug in Resource Buffering [9306]
Hi,
I think that I have the same issue. I have multiple independent modules with its own resx files (eg. one english and one swedish) and it has worked great defining the default assembly in the Xaml views until now. What happens is that I have the same resource key name in two separate resx files for two separate dlls. If I load the view in the on assembly it looks ok and shows the correct resource but when i load the second module it uses the resource from the first dll even though ive specified the correct default assembly in both.
Does it merge all already loaded resources with the new resource and only add missing keys? Is it possible to unload old resources prior to loading new?
//Christian
I think that I have the same issue. I have multiple independent modules with its own resx files (eg. one english and one swedish) and it has worked great defining the default assembly in the Xaml views until now. What happens is that I have the same resource key name in two separate resx files for two separate dlls. If I load the view in the on assembly it looks ok and shows the correct resource but when i load the second module it uses the resource from the first dll even though ive specified the correct default assembly in both.
Does it merge all already loaded resources with the new resource and only add missing keys? Is it possible to unload old resources prior to loading new?
//Christian
↧
Commented Issue: Possible Bug in Resource Buffering [9306]
Hi,
I think that I have the same issue. I have multiple independent modules with its own resx files (eg. one english and one swedish) and it has worked great defining the default assembly in the Xaml views until now. What happens is that I have the same resource key name in two separate resx files for two separate dlls. If I load the view in the on assembly it looks ok and shows the correct resource but when i load the second module it uses the resource from the first dll even though ive specified the correct default assembly in both.
Does it merge all already loaded resources with the new resource and only add missing keys? Is it possible to unload old resources prior to loading new?
//Christian
Comments: Will be published with v2.1.5
I think that I have the same issue. I have multiple independent modules with its own resx files (eg. one english and one swedish) and it has worked great defining the default assembly in the Xaml views until now. What happens is that I have the same resource key name in two separate resx files for two separate dlls. If I load the view in the on assembly it looks ok and shows the correct resource but when i load the second module it uses the resource from the first dll even though ive specified the correct default assembly in both.
Does it merge all already loaded resources with the new resource and only add missing keys? Is it possible to unload old resources prior to loading new?
//Christian
Comments: Will be published with v2.1.5
↧
Edited Feature: Retrieve extension that is bound to an object's property [9304]
The engine should be able to get the extension instance, that is already bound to a certain object's property.
↧
Edited Issue: Possible Bug in Resource Buffering [9306]
Hi,
I think that I have the same issue. I have multiple independent modules with its own resx files (eg. one english and one swedish) and it has worked great defining the default assembly in the Xaml views until now. What happens is that I have the same resource key name in two separate resx files for two separate dlls. If I load the view in the on assembly it looks ok and shows the correct resource but when i load the second module it uses the resource from the first dll even though ive specified the correct default assembly in both.
Does it merge all already loaded resources with the new resource and only add missing keys? Is it possible to unload old resources prior to loading new?
//Christian
I think that I have the same issue. I have multiple independent modules with its own resx files (eg. one english and one swedish) and it has worked great defining the default assembly in the Xaml views until now. What happens is that I have the same resource key name in two separate resx files for two separate dlls. If I load the view in the on assembly it looks ok and shows the correct resource but when i load the second module it uses the resource from the first dll even though ive specified the correct default assembly in both.
Does it merge all already loaded resources with the new resource and only add missing keys? Is it possible to unload old resources prior to loading new?
//Christian
↧
↧
Updated Release: v2.1.5
- Fix to #9306
- Implemented #9304
↧
Updated Release: v2.1.5
- Implemented #9304
- Fix to #9306
- Fix to #9308
↧
Updated Release: v2.1.5
- Implemented #9304
- Fix to #9306
- Fix to #9308
- Implemented #9309
↧
Edited Feature: Static ResolveLocalizedValue [9309]
It is available in the LocalizeDictionary class that is in fact called in ResolveLocalizedValue like this:
LocalizeDictionary.Instance.GetLocalizedObject(resourceKey, target, targetCulture)
The key and targetCulture are clear how to be used and the target is the target object (or null in your case). Note, that this goes with the drawback, that no (custom) converter is called and no buffering is used. I'll therefore add a static method that fits your needs.
LocalizeDictionary.Instance.GetLocalizedObject(resourceKey, target, targetCulture)
The key and targetCulture are clear how to be used and the target is the target object (or null in your case). Note, that this goes with the drawback, that no (custom) converter is called and no buffering is used. I'll therefore add a static method that fits your needs.
↧
↧
Edited Issue: LocExtension.ResolveLocalizedValue method is not thread-safe [9308]
LocExtension.ResolveLocalizedValue method throws "An element with the same key already exists" if called from multiple threads simultaneously.
↧
Edited Issue: Resource Assembly and GAC OR Satellite Assemblies and GAC [9307]
Actually I found the issue here,
```
var cultures = CultureInfo.GetCultures(CultureTypes.AllCultures);
foreach (var c in cultures)
{
var dir = Path.Combine(assemblyLocation, c.Name);
if (Directory.Exists(dir) && Directory.GetFiles(dir, "*.resources.dll").Length > 0)
AddCulture(c);
}
```
The code below, its slow ~~10x to directory.
```
var cultures = CultureInfo.GetCultures(CultureTypes.AllCultures);
foreach (var c in cultures)
{
ResourceSet rs = resManager.GetResourceSet(c, true, false);
if (rs != null)
AddCulture(c);
}
```
```
var cultures = CultureInfo.GetCultures(CultureTypes.AllCultures);
foreach (var c in cultures)
{
var dir = Path.Combine(assemblyLocation, c.Name);
if (Directory.Exists(dir) && Directory.GetFiles(dir, "*.resources.dll").Length > 0)
AddCulture(c);
}
```
The code below, its slow ~~10x to directory.
```
var cultures = CultureInfo.GetCultures(CultureTypes.AllCultures);
foreach (var c in cultures)
{
ResourceSet rs = resManager.GetResourceSet(c, true, false);
if (rs != null)
AddCulture(c);
}
```
↧
Updated Release: v2.1.5
- Implemented #9304
- Fix to #9306
- Fix to #9307
- Fix to #9308
- Implemented #9309
↧
Updated Release: v2.2.0
- Implemented #9304
- Fix to #9306
- Fix to #9307
- Fix to #9308
- Implemented #9309
This release will add another function to the Resource Provider interface. Please review your own implementations regarding compatibility.
↧
↧
Edited Issue: Possible Bug in Resource Buffering [9306]
Hi,
I think that I have the same issue. I have multiple independent modules with its own resx files (eg. one english and one swedish) and it has worked great defining the default assembly in the Xaml views until now. What happens is that I have the same resource key name in two separate resx files for two separate dlls. If I load the view in the on assembly it looks ok and shows the correct resource but when i load the second module it uses the resource from the first dll even though ive specified the correct default assembly in both.
Does it merge all already loaded resources with the new resource and only add missing keys? Is it possible to unload old resources prior to loading new?
//Christian
I think that I have the same issue. I have multiple independent modules with its own resx files (eg. one english and one swedish) and it has worked great defining the default assembly in the Xaml views until now. What happens is that I have the same resource key name in two separate resx files for two separate dlls. If I load the view in the on assembly it looks ok and shows the correct resource but when i load the second module it uses the resource from the first dll even though ive specified the correct default assembly in both.
Does it merge all already loaded resources with the new resource and only add missing keys? Is it possible to unload old resources prior to loading new?
//Christian
↧
Commented Issue: Possible Bug in Resource Buffering [9306]
Hi,
I think that I have the same issue. I have multiple independent modules with its own resx files (eg. one english and one swedish) and it has worked great defining the default assembly in the Xaml views until now. What happens is that I have the same resource key name in two separate resx files for two separate dlls. If I load the view in the on assembly it looks ok and shows the correct resource but when i load the second module it uses the resource from the first dll even though ive specified the correct default assembly in both.
Does it merge all already loaded resources with the new resource and only add missing keys? Is it possible to unload old resources prior to loading new?
//Christian
Comments: Sorry, I have to review this proposal, because it brings too much RESX detail into the Provider interface (assembly, dictionary). I'll just need another day for this.
I think that I have the same issue. I have multiple independent modules with its own resx files (eg. one english and one swedish) and it has worked great defining the default assembly in the Xaml views until now. What happens is that I have the same resource key name in two separate resx files for two separate dlls. If I load the view in the on assembly it looks ok and shows the correct resource but when i load the second module it uses the resource from the first dll even though ive specified the correct default assembly in both.
Does it merge all already loaded resources with the new resource and only add missing keys? Is it possible to unload old resources prior to loading new?
//Christian
Comments: Sorry, I have to review this proposal, because it brings too much RESX detail into the Provider interface (assembly, dictionary). I'll just need another day for this.
↧
Edited Issue: Possible Bug in Resource Buffering [9306]
Hi,
I think that I have the same issue. I have multiple independent modules with its own resx files (eg. one english and one swedish) and it has worked great defining the default assembly in the Xaml views until now. What happens is that I have the same resource key name in two separate resx files for two separate dlls. If I load the view in the on assembly it looks ok and shows the correct resource but when i load the second module it uses the resource from the first dll even though ive specified the correct default assembly in both.
Does it merge all already loaded resources with the new resource and only add missing keys? Is it possible to unload old resources prior to loading new?
//Christian
I think that I have the same issue. I have multiple independent modules with its own resx files (eg. one english and one swedish) and it has worked great defining the default assembly in the Xaml views until now. What happens is that I have the same resource key name in two separate resx files for two separate dlls. If I load the view in the on assembly it looks ok and shows the correct resource but when i load the second module it uses the resource from the first dll even though ive specified the correct default assembly in both.
Does it merge all already loaded resources with the new resource and only add missing keys? Is it possible to unload old resources prior to loading new?
//Christian
↧