project.json nuget restore causes recompilation when nothing changed

[wbradney]

I see the following the the build log:

Input file "project.lock.json" is newer than output file "obj\Release\MyAssembly.dll".
Using "Csc" task from assembly "C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Build.Tasks.CodeAnalysis.dll".

Nothing changed between builds. Why is the restore process touching the lock file even when the project.json file didn't change?

[rrelyea]

@wbradney - which version of nuget.exe or nuget.tools.vsix are you using?

[wbradney]

This was observed with a recent nightly build of the command line: v3.5.0.1240

[rrelyea]

that build is a dev branch build from 5/3/2016.

[wbradney]

Let me know if you need a simple repro solution and I can find time to create one.

[emgarten]

@wbradney a simple repro would be great 😄

[wbradney]

NugetRecompile.zip

Here you go. Just run msbuild build.proj several times from a dev command prompt and observe the build log.

[emgarten]

Thanks for the repro @wbradney I was able to track this down the cause, you can get a nightly build with the fix from: https://dist.nuget.org/index.html

[emgarten]

NuGet/NuGet.Client@4d5c9a5

[wbradney]

Thanks. The nightly seems old - is it building correctly?

[emgarten]

@wbradney looks like it is not updating on there, the build should be at least 1500.

[wbradney]

Sorry if I'm being dense, but where can I get the latest beta?

[harikmenon]

The latest 3.5 Beta 2 is available from https://dist.nuget.org/visualstudio-2015-vsix/v3.5.0-beta2/NuGet.Tools.vsix

[harikmenon]

http://blog.nuget.org/20160502/Introducing-The-NuGet-Beta-Channel.html. if you want to subscribe to the our Beta Channel.

[wbradney]

OK thanks - I think that's the same as what appears here: https://dist.nuget.org/win-x86-commandline/v3.5.0-beta2/NuGet.exe
If so, that version doesn't appear to fix this issue.
The milestone on this issue is 3.6 beta, so I thought that maybe there was another nightly build I could grab.

[harikmenon]

our VSIX nightly builds are not exposed publically. @rrelyea any change we give a wayne a signed latest build to try out?

[wbradney]

It's not a big deal - I can build the client from source. We mostly test with the command-line client anyway.

[wbradney]

Rebuilt from a clean fetch and confirmed that this issue is fixed. Thanks!

[wbradney]

Is this fix going to be available in a 3.5.x version?

[emgarten]

@wbradney yes, this will be in 3.5.0-rc1. It looks like this was added to the wrong milestone, I'll fix it.