Well when I try to run my published .application it looks for the translated file.
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of D:\Tests\EasyBamlClickOnceTest\EasyBamlClickOnceTest\publish\EasyBamlClickOnceTest.application resulted in exception. Following failure messages were detected:
+ Downloading file:///D:/Tests/EasyBamlClickOnceTest/EasyBamlClickOnceTest/publish/Application Files/EasyBamlClickOnceTest_1_0_0_9/fr/EasyBamlClickOnceTest.resources.dll.deploy did not succeed.
/fr/EasyBamlClickOnceTest.resources.dll.deploy exists in my regular /bin/debug output directory, but it's not in the publish folder nor is it in the application files list in Project Properties -> Publish -> Application Files. But the published application
is looking for it during installation so somewhere there was a manifest that was updated right.
I just opened my ClickOnce manifest with MageUI and /fr/EasyBamlClickOnceTest.resources.dll.deploy is in the file list (with a warning sign, because he can't find it). So ClickOnce knows it should be there, but somehow VisualStudio doesn't when publishing.
When I build with Diagnostic verbosity, I see these lines
Culture = fr
TargetPath = fr\EasyBamlClickOnceTest.resources.dll
AssemblyType = Satellite
OriginalItemSpec = obj\x86\Debug\fr\EasyBamlClickOnceTest.resources.dll
DependencyType = Install
So the manifest really seems fine.
But later on there is
Target "GenerateSatelliteAssemblies: (TargetId:86)" in file "c:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets" from project "D:\Tests\EasyBamlClickOnceTest\EasyBamlClickOnceTest\EasyBamlClickOnceTest.csproj" (target "CreateSatelliteAssemblies" depends on it):
Building target "GenerateSatelliteAssemblies" completely.
Output file "obj\x86\Debug\fr\EasyBamlClickOnceTest.resources.dll" does not exist.
So there might be some conflicting clean-up in-between...