dotnet core dotnet build ignores changes

Question

I have a dotnet core class library that I have successfully been able to build using the dotnet cli "dotnet build --configuration Release". This is important because I am also building this project in Jenkins on a Linux server.

Recently, I needed to go in and make some modifications to the project. When building it again with "dotnet build --configuration Release", it built, but none of my changes and additions were present. Please note that it behaves consistently (successfully and unsuccessfully) between the Jenkins environment in Linux and my Windows 10 command prompt when using "dotnet build --configuration Release".

If I build with Visual Studio 2015 (which I assume uses MSBuild), all changes are then present after I build the class library, and all is right with the world.

I assume that there is something wrong with my project.json?

{
  "version": "1.0.0.*",

  "dependencies": {
    "NETStandard.Library": "1.6.0",
    "Dapper": "1.50.2",
    "Dapper.Mapper": "1.50.1"
  },

  "frameworks": {
    "netcoreapp1.0": {
      "imports": [
        "dotnet5.6",
        "portable-net45+win8"
      ]
    }
  }
}

double check that Jenkins pull your last changes before build — Set, Feb 23 '17 at 19:21
Yeah, it does. It even dumps the entire workspace and re-checks out. But what makes this weird is that this is happening on my local machine outside of jenkins. — AaronBastian, Feb 23 '17 at 19:55
@AaronBastian did you face any issue related to proxy in Linux? Some thing similar https://stackoverflow.com/questions/60889000/dotnet-build-fails-nuget-behind-a-proxy-in-linux — user2700022, Mar 28 '20 at 19:09

score 1 · Accepted Answer · answered Feb 27 '17 at 20:02

So it turns out that the root cause of this issue was simply that I had structured my solution incorrectly and did not have a gobal.json file referencing the project. I am not entirely sure WHICH fixed it, or WHY it fixed it, but my class library solution needs the following: global.json in the SolutionItems folder src folder - Project in the src folder - Unit Tests in the src folder

Next, the issue with the linux server is that its nuget push command didn't recognize the dotnet core Version string. This is resolved in nuget cli version 3.5.0, but that version is not yet supported for Linux. As a temporary backup, I created the same job on a Windows based machine running Jenkins and nuget cli version 3.5.0, and it all works flawlessly.

When the next version of dotnet core comes out, and has a dotnet nuget push command, I am sure that I can revisit the Linux server.

Then the commands that I run in Jenkins are dotnet restore dotnet pack --configuration Release --versionsuffux %BUILD_NUMBER% nuget push PackageName ApiKey -Source http://NugetSource

score 0 · Answer 2 · answered Feb 24 '17 at 09:32

0

You probably did it, but did you restart the service in linux?

answered Feb 24 '17 at 09:32

Stephane Duteriez

934
8
8

Yeah. A few times. – AaronBastian Feb 27 '17 at 19:53

score 0 · Answer 3 · answered Oct 26 '18 at 10:54

0

If dependencies or libraries have been changed, old files affect the packaging operation.

Remove obj and bin folders from project.
Run dotnet restore
Run dotnet build --configuration Release

answered Oct 26 '18 at 10:54

Hayrullah Cansu

262
5
14

dotnet core dotnet build ignores changes

3 Answers3