CI Build broke after nugit update

One of those moments where your heart drops : Your using CI on a remote hosting service (like AppHarbor) and your build fails. You look into the fail reason and find out it is because you updated the packages in your build.

Wait, my update from nuGet broke everything?! Wtf?!

The error looks something like this, putting it in here for search engine's :

Build started 6/10/2013 12:30:20 AM.
     1>Project "D:\temp\xly5bsff.qvp\input\.sln" on node 1 (default targets).
     1>ValidateSolutionConfiguration:
         Building solution configuration "Release|Any CPU".
     1>Project "D:\temp\xly5bsff.qvp\input\.sln" (1) is building "D:\temp\xly5bsff.qvp\input\\.csproj" (2) on node 1 (default targets).
     2>D:\temp\xly5bsff.qvp\input\\.csproj(880,3): error MSB4019: The imported project "D:\temp\xly5bsff.qvp\input\packages\Microsoft.Bcl.Build.1.0.7\tools\Microsoft.Bcl.Build.targets" was not found. Confirm that the path in the  declaration is correct, and that the file exists on disk.
     2>Done Building Project "D:\temp\xly5bsff.qvp\input\\.csproj" (default targets) -- FAILED.
     1>Done Building Project "D:\temp\xly5bsff.qvp\input\.sln" (default targets) -- FAILED.

Build FAILED.

       "D:\temp\xly5bsff.qvp\input\.sln" (default target) (1) ->
       "D:\temp\xly5bsff.qvp\input\\.csproj" (default target) (2) ->
         D:\temp\xly5bsff.qvp\input\\.csproj(880,3): error MSB4019: The imported project "D:\temp\xly5bsff.qvp\input\packages\Microsoft.Bcl.Build.1.0.7\tools\Microsoft.Bcl.Build.targets" was not found. Confirm that the path in the  declaration is correct, and that the file exists on disk.
"

Simple fix, courtesy of MarC C Brooks on the msdn forums for pointing me to BenHu's awesome fix :
1. Close your project
2. Go to the solution's .csproj file and open it with your fav text editor.
3. Find the following line:
Project="..\packages\Microsoft.Bcl.Build.1.0.7\tools\Microsoft.Bcl.Build.targets" ..

4. Replace it with this one:

 Project="..\packages\Microsoft.Bcl.Build.1.0.7\tools\Microsoft.Bcl.Build.targets"



 Condition="Exists('..\packages\Microsoft.Bcl.Build.1.0.7\tools\Microsoft.Bcl.Build.targets')" />

5. Open your project again, commit your changes to your local Git.
6. Update your remote repo, in my case it is bitbucket:
   git push origin master:master
7. Open your project again, commit your changes to your local Git
8. Rejoice, build fixed

Comments

Jamie R said…
What I did to fix this issue was loaded up the Package Manager Console (you could also use the regular command line) and fired up this following nuget command.

nuget install .\GlobalInit_MVC\packages.config -OutputDirect packages

This worked great for us.
June 21, 2013 at 11:48 AM
Post a Comment

Popular posts from this blog

Sharepoint 2007 - Access Denied when you try to edit

I'v had this solution for a little while now but never wrote it down anywhere for people to see. Here is the situation: In a site collection, you make a new list/document library in any sub-site or the main website. You then add a new item/document to the folder, and then attempt to edit the item You then see something along the lines of "Access Denied" , even if you are on the system account. This happens with every new list you create on any site or subsite. Your problem is a corrupted field definition at the site collection level. Specifically the "Effective Permissions Mask" is missing an attribute in it's xml scheme - RenderXMLUsingPattern="TRUE" The fix comes in 3 steps: 1. Update your server to the most recent cumulative update package (Service pack 2 or greater). You can get more information about this from the Sharepoint team blog post on SP2 . Included in SP2 is a hotfix that prevents this from occurring ever again on any other site co
Read more

Project 2010 and Project Pro 2007

Just a FYI since no one knew this from what i can tell already: If you are enabling BCM (Backwards Compatibility Mode) for project 2007 to connect to Project Server 2010, there are a few things you should know first. Right off the bat, clients have to be updated to Service Pack 2 . Next, when your setting up your project server, Note this key fact I could not find anywhere, and did not get hint about in the technet forms when i posted about my problems: You CAN NOT use Claims based authentication on your web application that is hosting Project Server 2010. The 2007 Client will not connect to the server. The 2010 client will connect with no problems. Quick and dirty, hope that helps everyone!
Read more