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.

Dot Net Core Wild Card Paths Ignore

See original GitHub issue

I recently upgraded a VSTS task group from 0.* to 1.* for dot net core restore, build, test, and publish tasks. My repository has a mix of dotnet core and dotnet 4.6 projects. previously i could exclude the 4.6 projects with the slug **/*.csproj;-:**/My46Project.csproj.

When upgrading to the 1.* build task the dot net core task fail to find my .csproj files and my build fails.

Any suggestions on how I can exclude the “legacy” 4.6 project while still using the upgraded VSTS tasks?

Issue Analytics

State:
Created 6 years ago
Reactions:3
Comments:9 (3 by maintainers)

Top GitHub Comments

4reactions

dasithscommented, Apr 11, 2019

I think this worked for me

projects: |
         '**/*.csproj'
         '**/*.Tests.csproj'

2reactions

irontobycommented, Feb 23, 2021

I had to omit the single quotes in order to use variable substitution, e.g:

variables:
  basedir: 'MyCorp.MyProject/**'
  buildProjects: |
    $(basedir)/*.csproj
    !$(basedir)/*.SkipMe.csproj

steps:
- task: DotNetCoreCLI@2
  displayName: 'dotnet build'
  inputs:
    command: 'build'
    projects: '$(buildProjects)'