Skip to content

Use commas for MSBuild configuration lists - #19

Merged
wieslawsoltes merged 1 commit into
mainfrom
agent/use-comma-msbuild-separators
Aug 11, 2026
Merged

wieslawsoltes merged 1 commit into
mainfrom
agent/use-comma-msbuild-separators

Conversation

@wieslawsoltes

@wieslawsoltes wieslawsoltes commented Aug 11, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • replace semicolon-delimited MSBuild examples with comma-delimited values
  • document why semicolons truncate CompilerVisibleProperty values and link the upstream Roslyn issue
  • add generator regression coverage for comma-separated namespace prefixes, replacement rules, and interface prefixes
  • retain semicolon parsing only as backward compatibility for values supplied outside the affected MSBuild path

Validation

  • combined with merged PR Allow empty type-name replacement targets #18: dotnet test StaticViewLocator.sln -c Release --nologo — 46 passed
  • dotnet build StaticViewLocator.sln -c Release --nologo — 0 warnings, 0 errors
  • dotnet format StaticViewLocator.sln --verify-no-changes --no-restore — passed
  • git diff --check — passed
  • GitHub CI build and test jobs passed on Linux, macOS, and Windows; package creation passed

Fixes #7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Using ';' as a separator when defining MSBuild configurations is invalid.

1 participant