Before generating, scans all *.cs files for used codes (using the complete path prepend with I18N- e.g. I18N-PATH.PATH.PATH.ELEMENT, etc.)
When a line contains such a code, copy the entire line of code for generation
Copy the namespace and class name
When generating, create a new partial class for each found class
Replicate the copied lines, but set the actual content instead of the code
Provide a method (not async!) which gets called at the end of the constructor
Same method can be called, when the user switch the culture
This method is convenient. The developer pastes the codes in Visual Studio. The generator automatically handles e.g. renames of variables in Visual Studio.
Issues:
We must ensure, that deletes classes get recognized. Might we add a code to any generated class. When the generator is done, he can detect files which were not touched. These files can be deleted.
Settings to add:
Generator: Enable .NET WinForms
Generator: .NET WinForms Root
- Before generating, scans all `*.cs` files for used codes (using the complete path prepend with `I18N-` e.g. `I18N-PATH.PATH.PATH.ELEMENT`, etc.)
- When a line contains such a code, copy the entire line of code for generation
- Copy the namespace and class name
- When generating, create a new partial class for each found class
- Replicate the copied lines, but set the actual content instead of the code
- Provide a method (not `async`!) which gets called at the end of the constructor
- Same method can be called, when the user switch the culture
This method is convenient. The developer pastes the codes in Visual Studio. The generator automatically handles e.g. renames of variables in Visual Studio.
**Issues:**
- We must ensure, that deletes classes get recognized. Might we add a code to any generated class. When the generator is done, he can detect files which were not touched. These files can be deleted.
**Settings to add:**
- Generator: Enable .NET WinForms
- Generator: .NET WinForms Root
created branch [`7-add-code-generator-for-win-form-projects`](/open-source/dotnet/i18n-commander/-/compare/main...7-add-code-generator-for-win-form-projects) to address this issue
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
*.csfiles for used codes (using the complete path prepend withI18N-e.g.I18N-PATH.PATH.PATH.ELEMENT, etc.)async!) which gets called at the end of the constructorThis method is convenient. The developer pastes the codes in Visual Studio. The generator automatically handles e.g. renames of variables in Visual Studio.
Issues:
Settings to add:
marked this issue as related to #6
marked this issue as related to #8
changed the description
changed the description
changed the description
changed the description
marked this issue as related to #56
changed the description
created branch
7-add-code-generator-for-win-form-projectsto address this issuementioned in merge request !34
Decided not to support WinForms. Closed!