Hi Gary,

Sorry for the delay, I was indeed quite busy, trying to understand
what was the magic behind the CtcFile build action.
The good news is I was finally able to localize my ctc file.
The last issue I have today is to integrate the localized .cto into the
satellite dll in an automatic way.
To be more precise, I have been able to do it by hand,
*once* I understood what the CtcFile build action does,
which is to "inject" the .cto into the VSPackage.resources
file as a byte[] resource with id=1000.
So to have the same result than the CtcFile build action you have to:
.create a localized version of VSPackage.resx (eg VSPackage.fr.resx)
.compile the localized ctc invoking ctc.exe
.add the resulting cto to the VSPackage.fr.resx as a byte[] resource id=1000
.then rebuild your project to rebuild the new VSPackage.fr.resources file
and update the new satellite dll.
Then it works.
I now have to figure out how to implement these steps automatically
in the build process, avoiding these two pass. Indeed, the problem is
I cannot edit the VSPackage.fr.resx file to add the .fr.cto since the cto
only exists at build time. A solution would have been to set the CtcFile as
the build action of my localized ctc, but then the build action failed
because it tries to add two cto files in the same .resources file (instead
of
detecting that it should add the fr.cto to the fr.resources) which
is unsupported unfortunately. Maybe the solution is to use another project
just for the satellite dll.
So for the time being, I am working on resolving this issue.
But as I have not look at it deeply yet, I will first
perform some research and tests before bothering you with it (of course,
any hints is welcome though).

My only wish at this time: improve the doc about the CtcFile build action.

Thanks for your support,
Patrick