mvdmio · Translation Tools
Your .resx files, translated for you.
For .NET developers who keep their translations in .resx files and want every locale in one grid.
A browser-based translation grid that reads and writes your project's own .resx files, fills empty locales with AI, and ships a NuGet client and CLI so your .NET app just consumes the result.
Try Translation Tools for 30 days without a credit card.
€999 / year, excl. VAT, for one project with every locale. See pricing →
Your .resx files stay the source of truth
The CLI reads and writes the same .resx files your build already uses, so there's no export step and no separate translation format to keep in sync.
translations pullwrites local, locale-specific.resxfiles from the server, keyed by the project-relative path of each neutral resource file (its "origin")translations pushscans those local files and posts only what changed since the last pull, so the server gets your human edits and not noisetranslations pull --pruneandpush --prunekeep local files and server rows aligned when a key is removed on either side
AI fills the gaps, never overwrites a human
A daily job fills every empty non-default locale value from your default-locale text. An immediate job does the same when a key first becomes translatable.
- Only empty or missing values are touched; anything a person, an import, or your API already wrote stays exactly as it is
- Each fill is grounded in your account's shared term bank, so a name or product term translates the same way everywhere it appears
- Filled cells carry an "Auto translated" badge in the grid and in the history, so you always know which values still need a human look
A NuGet client and a CLI built for .NET
Nothing to hand-roll: the client generates strongly-typed resource classes from your .resx files, and the CLI drives the whole pull/push cycle from a terminal or a build pipeline.
- Install the
mvdmio.TranslationTools.ClientNuGet package in your app, and the CLI withdotnet tool install --global mvdmio.TranslationTools.Tool. - The NuGet client's source generator reads your neutral
.resxfiles directly and emits one type per resource set, so you don't write key constants by hand - Generated properties read a runtime cache first, then an embedded snapshot, so lookups never block on the network
- The
translationsCLI (init,pull,push) runs from a single.mvdmio-translations.ymlconfig, with no Git integration or extra service to run - Built-in WebSocket live updates keep a running app's translations current without a redeploy
Related post: Effective .NET Web development for individuals and small teams
Plain pricing
Try Translation Tools for 30 days without a credit card. When the trial ends, access closes. Nothing is charged unless you subscribe.
Stop passing files around.
Point the CLI at your project and pull your keys. The grid and the AI take it from there.