Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support Localization Resource Generation & Translation
See original GitHub issueMoving from https://github.com/dotnet/cli/issues/4967 on behalf of @hishamco
Last few days I started a new
dotnetCLI tool to generate and translate localization resources calleddotnet resgenthis is the link to my repo https://github.com/hishamco/LocalizationResourceGenerator, it would be nice to support such utility tool during the development phase on all the localization web applications. FYI the tool is under development, and may it needs a lot of improvements by the time
Moving this https://github.com/aspnet/DotNetTools/issues/203 to home repo
Issue Analytics
- State:
- Created 7 years ago
- Reactions:3
- Comments:13 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Until this is added it’s basically impossible to generate localization files on a linux machine short of using Rider as an example with is problematic for anyone that has a worldwide market for a small example.
This needs to be embedded into dotnet cli asap.
Sure. Support it for now, but the better solution is to provide a one click upgrade in VS.net that converts them to JSON and a dotnet tool for converting and then switch to a modern format that is fully supported by the CLI and doesn’t require VS.net.