CODEWITHSUNDEEP
azuremsbuildnugetcontinuous-deploymentazure-devops
RandallTo
RandallTo

Reputation: 395

New Azure portal and Visual Studio Team Services continuous deployment not using NuGet

When I create a test solution with 2 WebForms apps and on Class Lib, check into Visual Studio Team Services, continuous deployment works and publishes to our staging slots as expected. TestSite1 and TestSite2 both build and publish on the two azure website staging deployment slots.

I accomplish the multiple websites scenario with a custom build configuration for each web app and edit each build definition like so: Any CPU|ReleaseSite1 for test site 1 and Any CPU|ReleaseSite2 for test site 2.

The moment I add any NuGet library, like Newtonsoft Json then the Team Services MSBuild server fails.

This also fails for any out of the box VS2015 MVC app as the Team Services Build Server can't find System.Web.Mvc.

All this is using new Azure preview portal, Framework 4.5.2

Build

Exception Message: MSBuild error 1 has ended this build. You can find more specific information about the cause of this error in above messages. (type BuildProcessTerminateException) Exception Stack Trace: at System.Activities.Statements.Throw.Execute(CodeActivityContext context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation) Could not resolve this reference. Could not locate the assembly "Newtonsoft.Json, Version=7.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. default.aspx.cs (15, 0) The name 'Newtonsoft' does not exist in the current context

Upvotes: 0

Views: 174

Answers (1)

Vicky - MSFT
Vicky - MSFT

Reputation: 5010

The queued builds actually runs on build agent machine. You need to add NuGet package restore to the build process, so that the required NuGet packages can be downloaded during the build process.

Please check my reply in this link for the detailed steps for both vNext build system and XAML build: Failure to build on VS Online because of Nuget, works locally

Upvotes: 0

Related Questions