Porting Localized VSCT from VS2008 to VS2010

Hello,

I have a VS2008 VSCT file which gets compiled into a .cto via vsct.exe compiler, then merged with resx via <MergeWithCTO>true</MergeWithCTO>.

• For 2008, the VSCT file contains 'langauge' properties for text, one for EN culture, and the other for JA culture. This is compiled using VS2008 vsct.exe.
• For 2010, the VSCT file contains 'language' properties for text, one for EN culture, and the other for JA culture. This is compiled by using VS2010 vsct.exe.

After building the package and registering it,

• In VS 2008, my package is correctly localized and all is great.
• In VS 2010, my package is only in English.

I know the cto file generated is valid in VS2010 because I have correct menu entries, I just don't have the localization.

So after searching around a bit, it seems that I can no longer use a single .vsct file in VS2010. I now need a vsct file for each language:

 <ItemGroup>

   <VSCTCompile Include="VsPackage.en-US.vsct">

     <ResourceName>Menus.ctmenu</ResourceName>

   </VSCTCompile>

   <VSCTCompile Include="VsPackage.ja-JP.vsct">

     <ResourceName>Menus.ctmenu</ResourceName>

   </VSCTCompile>

 </ItemGroup>

My question is, whats the point of the 'language' element property if it doesn't work unless it is in a vsct file which is already culture specific?

Is there a way to force VS2010 to use a single vsct file for multiple languages? Would simply duplicating the vsct file and naming one ja-JP and the other en-US work?

Thanks