Skip to content

Conversation

@imcarolwang
Copy link
Contributor

No description provided.

…tem.CodeDom codegen diffs; update tests to net10.0
1. Pin System.CodeDom to 8.0.0 to avoid pulling newer (net10-rc aligned) builds that can fail at runtime on older supported runtimes.

2. Ensure the generated SvcutilBootstrapper project can always load System.CodeDom when the tool is referenced by path (global-tool/bootstrapper flow) by adding an explicit System.CodeDom.dll reference when present next to dotnet-svcutil-lib.dll, update TFMBootstrap/TFMBootstrapGlobal test baselines accordingly.

3. Remove the previously-added CodeDom output post-processing that was only needed for System.CodeDom 10.x.
1. Replace the SVCUTIL_CLOSEASYNC_WRAP comment marker with a CodeRegionDirective marker around the generated CloseAsync member.

2. Update CodeSerializer post-processing to convert the matching #region/#endregion (or VB #Region/#End Region) into #if/#endif (or #If/#End If), avoiding brace-based member-end parsing.

3. Use CodeRegionMode (netstandard2.0 compatible) for the region directive start/end.
@imcarolwang imcarolwang marked this pull request as ready for review January 26, 2026 09:49
@imcarolwang imcarolwang requested a review from mconnew January 26, 2026 09:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant