Apart for doing all this manually, is there a way to benefit from
Visual Studio .NET localization support with Forms, and NOT make it
create a satellite assembly for every non-default culture, but instead
embed those resources in the main assembly?

Thanks.

Set currentRow in dgv
MdiChild Icon in Parent Form
Redraw flashing problem with ListView in virtual mode.
System.IO is to FileStream as X is to SharePoint
Re: Errors Found Code 80244019 Windows Vista Business