Errors in Azure DevOps build - are you missing an assembly reference?

13
votes

I am using VSTS (Azure DevOps) for the first time and am setting up my first build (I have previously been using TFS). I'm trying to build a .NET application targeting .NET Framework 4.6.

However I'm getting build errors relating to missing namespaces and / or assemblies.

Error CS0246: The type or namespace name 'OwinStartupAttribute' could not be found (are you missing a using directive or an assembly reference?)

Error CS0234: The type or namespace name 'Http' does not exist in the namespace 'System.Web' (are you missing an assembly reference?)

Error CS0234: The type or namespace name 'Azure' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?)

The issues all seem to be related i.e. the nuget packages aren't getting restored during the build process.

I've therefore added a Nuget restore task to the pipeline before my build step.

enter image description here

And have checked the option Restore Nuget packages on the build step.

enter image description here

3
azure-devopsazure-pipelines
...and what happens when you run the build with the NuGet Restore task present? – Daniel Mann
I get the errors mentioned in my post above. – DomBurf
Do you get errors during the NuGet restore step? – Daniel Mann
I don't get any errors in the Nuget restore. – DomBurf
I'm facing the same problem. Anyone else know how to solved ? In My case It's a dll that references a lot of external dll from other projects. – Fábio Carvalho

3 Answers

4
votes

I managed to get this working as I had some of the Nuget packages checked-in as part of source-control. I removed the entire packages folder from the solution and this has resolved the issue. There must have been some conflict between the packages I had in source-control and the packages I was trying to restore.

4
votes

I had some projects in a large solution with this problem; they had the old "packages.config" files. To fix, In Solution Explorer, right-click on a packages.config file and select Migrate packages.config to PackageReference.

Docs.

2
votes

In my case, this would happen because, for some reason, the local cache was only partially populated. Disabling the local cache in the build definition fixed the issue.

enter image description here