Mindphreaker wrote:
My problem is that I use localizeable forms so I can switch the language of the software. After the built process with Assemblur it can't switch the language any more. Normally it builds 2 seperate ressource files. (2 languages).
With Assemblur it creates only one ressource file. Maybe I've forgot something to add or I use wrong settings.
When a form resource is about to be renamed, Assemblur searches all assemblies specified in the configuration, trying to find matching localizable resources.
For example, if the name of the form resource is MyNamespace.MyForm.resource, Assemblur will look for MyNamespace.MyForm.[culture].resource in all assemblies.
From the top of my head, I can think of two possible reasons why things go wrong:
1. One or more resource assemblies are not part of the Assemblur configuration
2. All resource (satellite) assemblies are part of the configuration, but Assemblur fails to identify localized form resources in those assemblies.
In any case, Assemblur does not create any assemblies -- it just modifies existing ones. If there's one less (obfuscated) assembly in the destination folder, it could mean that its corresponding source assembly is not part of the configuration.
If it's not too complicated, you could also post here a trimmed-down VS solution with just some dummy source files in it (no real source code, just empty forms), if such solution still helps reproducing the problem.