Skip to content

Remove machine-specific absolute paths from two project files - #131

Merged
electricessence merged 1 commit into
masterfrom
fix/remove-machine-paths
Nov 12, 2026
Merged

electricessence merged 1 commit into
masterfrom
fix/remove-machine-paths

Conversation

@electricessence

Copy link
Copy Markdown
Collaborator

Remove machine-specific absolute paths from two project files.

Visual Studio tooling had written absolute paths, naming a developer machine, into two project files:

  • the test project: a code-coverage run-settings path (RunSettingsFilePath);
  • the SqlClient project: two item groups with an absolute .editorconfig path (EditorConfigFiles Remove and None Include).

They do nothing on any other machine and do not belong in the repository. This removes them from the tip of master; no other change.

Checks

  • A search of every tracked file for drive-letter paths and user folders finds nothing left.
  • Visual Studio 2026's MSBuild builds the whole solution in Debug and in Release with 0 errors; a filtered test run (173 tests) passes on net10.0 and net11.0 without the run-settings property.

🤖 Generated with Claude Code

Visual Studio tooling had written absolute paths into the test project (a code-coverage run-settings
path) and into the SqlClient project (two editorconfig entries). They name a developer machine, do nothing
on any other machine, and do not belong in the repository. No other change.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@electricessence
electricessence merged commit e66894b into master Nov 12, 2026
1 check passed
@electricessence
electricessence deleted the fix/remove-machine-paths branch November 12, 2026 16:09
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