[BUG] Common project dependency missing
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- build-system, ci-cd
Research direction
Start with tools/code/common/common.csproj and tools/code/common/Functional.cs to confirm the missing MoreLinq reference. Run the documented DotNetCoreCLI build across the .csproj files; done means the Common project and full build complete without the CS0246 error.
Written by the indexing model from the issue text.
Description
Release version
6.0.14
Describe the bug
The csproj file of the Common project does not have a reference to the MoreLinq nuget package and the build is failing because of that.
Error from DevOps build step:
/home/vsts/work/1/s/tools/code/common/Functional.cs(1,7): error CS0246: The type or namespace name 'MoreLinq' could not be found (are you missing a using directive or an assembly reference?) [/home/vsts/work/1/s/tools/code/common/common.csproj]
This is applicable only when we need to import the code, compile it and then generate the exe.
Expected behavior
The build step should finish successfully.
Actual behavior
Error from DevOps build step:
/home/vsts/work/1/s/tools/code/common/Functional.cs(1,7): error CS0246: The type or namespace name 'MoreLinq' could not be found (are you missing a using directive or an assembly reference?) [/home/vsts/work/1/s/tools/code/common/common.csproj]
The build step fails.
Reproduction Steps
Add the following step in the pipeline to build the solution
- task: DotNetCoreCLI@2
displayName: 'dotnet build'
inputs:
command: 'build'
projects: '**/*.csproj'
arguments: '-verbosity:diag'
- Dominant language
- C#
- Stars
- 448
- Forks
- 247
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/apiops
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·