Skip to content

ci: restore and build projects directly instead of invalid .slnx#6

Open
circleci-app[bot] wants to merge 1 commit into
masterfrom
chunk/ci-restore-build-projects-no-slnx-1781875796082
Open

ci: restore and build projects directly instead of invalid .slnx#6
circleci-app[bot] wants to merge 1 commit into
masterfrom
chunk/ci-restore-build-projects-no-slnx-1781875796082

Conversation

@circleci-app

@circleci-app circleci-app Bot commented Jun 19, 2026

Copy link
Copy Markdown

Prompt Given

Fix main workflow (d6480cf6-193a-441f-aa10-966f01f52f39)

Updates CircleCI pipeline to avoid using an invalid .slnx solution file and explicitly restore/build the individual projects.

Changes:

  • In .circleci/config.yml, replace dotnet restore FileCabinet.slnx with:
    • dotnet restore FileCabinet.vbproj
    • dotnet restore FileCabinet.Cli/FileCabinet.Cli.vbproj
  • Replace solution-level build with explicit project builds:
    • dotnet build FileCabinet.vbproj --configuration Release --no-restore
    • dotnet build FileCabinet.Cli/FileCabinet.Cli.vbproj --configuration Release --no-restore
  • Keep tests as-is: dotnet test FileCabinet.Tests/FileCabinet.Tests.vbproj with TRX logging.
  • Add inline comments explaining that the custom .slnx is not a valid dotnet solution file.

Why:

  • .slnx is not recognized by dotnet, causing CI restore/build steps to fail.
  • Building/restoring the concrete project files ensures a working and deterministic CI pipeline without requiring a valid .sln.

Impact:

  • CI will successfully restore, build, and test the application and CLI projects.
  • No runtime or product behavior changes; CI configuration only.

View more about this proposed fix in the CircleCI web app →

Updates CircleCI pipeline to avoid using an invalid `.slnx` solution file and explicitly restore/build the individual projects.

Changes:
- In `.circleci/config.yml`, replace `dotnet restore FileCabinet.slnx` with:
  - `dotnet restore FileCabinet.vbproj`
  - `dotnet restore FileCabinet.Cli/FileCabinet.Cli.vbproj`
- Replace solution-level build with explicit project builds:
  - `dotnet build FileCabinet.vbproj --configuration Release --no-restore`
  - `dotnet build FileCabinet.Cli/FileCabinet.Cli.vbproj --configuration Release --no-restore`
- Keep tests as-is: `dotnet test FileCabinet.Tests/FileCabinet.Tests.vbproj` with TRX logging.
- Add inline comments explaining that the custom `.slnx` is not a valid dotnet solution file.

Why:
- `.slnx` is not recognized by `dotnet`, causing CI restore/build steps to fail.
- Building/restoring the concrete project files ensures a working and deterministic CI pipeline without requiring a valid `.sln`.

Impact:
- CI will successfully restore, build, and test the application and CLI projects.
- No runtime or product behavior changes; CI configuration only.

AI-Generated: true
@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

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.

0 participants