TFS Online Build Fails - NuGet package Restore Not working

build entity-framework-6 msbuild tfs

Question

I would love to get your help to resolve this issue. The code compiles in local box but TFS build fails for a project saying -

Entity\DbModel.Context.cs (16): The type or namespace name 'Entity' does not exist in the namespace 'System.Data' (are you missing an assembly reference?)

Entity\DbModel.Context.cs (19): The type or namespace name 'DbContext' could not be found (are you missing a using directive or an assembly reference?)

Entity\DbModel.Context.cs (26): The type or namespace name 'DbModelBuilder' could not be found (are you missing a using directive or an assembly reference?)

I am using EntityFramework 6.1.1. NuGet package for the project and Package Restore is enabled (in NuGet.targets file) -

<RestorePackages Condition="  '$(RestorePackages)' == '' ">true</RestorePackages>

I think that the package download for the EntityFramework is also failing in TFS even though the other NuGet packages for the same project are getting downloaded before the build the starts in TFS.

I am using 2 packages for this project -

<packages>
<package id="EntityFramework" version="6.1.1" targetFramework="net45" />
<package id="Newtonsoft.Json" version="6.0.6" targetFramework="net45" />
</packages>

Build Log file -

RestorePackages:
  "C:\a\src\.nuget\NuGet.exe" install "C:\a\src\<project name>\packages.config" -source ""  -NonInteractive -RequireConsent -solutionDir "C:\a\src\ "
  Restoring NuGet packages...
  To prevent NuGet from downloading packages during build, open the Visual Studio Options dialog, click on the Package Manager node and uncheck 'Allow NuGet to download missing packages'.
  Installing 'Newtonsoft.Json 6.0.6'.
  Successfully installed 'Newtonsoft.Json 6.0.6'.
  All packages listed in packages.config are already installed.

But after Newtonsoft.Json, it didn't even download the EntityFramework Dlls.

1
3
11/21/2014 6:42:10 PM

Accepted Answer

Finally I made it work. It took a while. At this point, 2 different options available :

  1. Keep the NuGet.targets file and refer that NuGet.targets file from all the project (Didn’t work for me)

  2. Explicitly call the NuGet.Exe package restore before the build

The option 1 didn’t work for me, that’s why to go ahead with the 2nd option, I had to do:

  1. Delete the NuGet.targets file from the .nuget folder (do not checkin that file)

  2. Delete and do not check in the packages file

  3. Open all the projects file in notepad and remove the reference of NuGet.targets file as mentioned in http://docs.nuget.org/docs/workflows/migrating-to-automatic-package-restore

  4. Go to VS 2013 – Tools > Extensions and Update > VS Gallery – make sure that you have the latest NuGet

  5. At this point, your project is ready to download Nuget packages right before any build, to test that delete the packages folder and start build, it should download all NuGet packages.

  6. Now, for TFS Continuous build, instead of pointing the solution file directly in the build template, use a custom XML build.proj file as mentioned in the http://blogs.msdn.com/b/dotnet/archive/2013/08/27/nuget-package-restore-with-team-foundation-build.aspx.

  7. This XML first calls NuGet.EXE restore path\.sln file, if the *.sln file is not mentioned it picks up any other solution file in the same directory

  8. Check in the build.proj, NuGet.exe all in the root folder along with the solution file

Now, things are going smooth for me with the TFS online CI. Do not right click on the Visual Studio solution to enable the NuGet package restore - it will undo all of the above since it brings back the NuGet.targets file and direct reference to the file in each proj file.

3
11/21/2014 6:38:18 PM


Related Questions





Related

Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow
Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow