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: This part is ready now.
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: This part is ready now.