localizable assembly discovery fails

[twest820]

Visual LocBaml reports no localizable assemblies found in a localizable WPF project. It would be helpful if some sort of diagnostic information was available to support investigation short of cloning the repo and debugging.

x64 build from Visual Studio 15.8.2 with an assembly utilizing the default Properties\Resources.resx for invariant strings and producing satellite assemblies in the expected culture folders. Relevant XAML elements have Uid attributes, also per instructions. Target framework is .NET 4.7.1.

From a look at the (possibly stale) Visual LocBaml sources in this repo I did notice LoadedAssembly.IsNetAssembly() p/invokes GetFileVersion() rather than using supported assembly paths. I'd expect this to be fairly stable but it's a potentially fragile failure point.

[dok-net]

@twest820, could you please check dok-net@8501ab6? Thanks!

[twest820]

Hi, sorry, but I didn't incorporate satellite assemblies into my build. (Went with merging localized resource dictionaries from XAML instead.)

[dok-net]

@twest820 Hi, in case you still remember enough of what you did back then and what didn't work, I can't quite tell the difference to #1 - for that, a direct fix in XAML was suggested there. For me, too, it's been awhile since I last worked with XAML localization, and even back then, the responsible developer eschewed LocBAML and probably went the same path that you chose :-)

[twest820]

Hi Dirk, compare satellite assembly creation to ResourceDictionary plus LocalizedApplication.TryLoadCultureResources().