Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

--project-file does not accept relative paths

See original GitHub issue

I have the following file structure for my Application.

ExampleApp
├─ Sources
│  ├─ Project1
│  ├─ Project2
│  ├─ Project3
│  └─ Project4
├─ Tests
│  ├─ Project1.Tests
│  ├─ Project2.Tests
│  │  └─ stryker-config.json
│  ├─ Project3.Tests
│  └─ Project4.Tests
└─ ExampleApp.sln

When my current directory is Project1.Tests and I run dotnet stryker --project-file="../../Sources/Project1/Project1.csproj", I get the error message Project reference issue.

Likewise I get the same error message when my current directory is Project2.Tests and I run dotnet stryker with a stryker-config.json containing the following;

{
    "stryker-config":
    {
        "project-file": "../../Sources/Project2/Project2.csproj"
    }
}

The error does not occur when using absolute paths. The version of dotnet-stryker I am using is Version 0.11.0 (beta). The issue happens both in Windows 10 and macOS.

Issue Analytics

State:
Created 4 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

4reactions

jisperliucommented, Jul 3, 2019

+1 the logging is confusing. It’s probably better to let ppl know they can just use project name instead of giving a full path and this intuition that ppl can use relative path

0reactions

rouke-broersmacommented, Nov 6, 2021

I think this has been improved sufficiently