[MilCodeGen] Optimize generated ValueSerializers code style and usings #10648
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Resolves numerous IDE warnings and reflects more closely current code-style in derived ValueSerializers.
Also removes redundant usings. Instead of using the collection from the resource tree, we only really need the managed namespace for the resource itself and
System.Windows.Markup
forValueSerializer
, this is static dependency so the definition doesn't need to be in the resource model itself (same thing asSystem.Windows.Markup.TypeConverterHelper
is directly linked in generator code).Reviewing
ManagedStruct.cs
shall be enough to get the grip of the changes, also the changes are always consistent per-folder so 1 file gives you overview of full set of changes for that particular set of resources.Customer Impact
Cleaner codebase for developers.
Regression
No.
Testing
Local build.
Risk
Low.
Microsoft Reviewers: Open in CodeFlow