Skip to content

Mysterious type/namespace errors in release/3.1 #20687

Closed
@wtgodbe

Description

@wtgodbe

Errors like the following started popping up in release/3.1 on April 6:

FormPipeReader.cs(9,17): error CS0234: The type or namespace name 'Pipelines' does not exist in the namespace 'System.IO' (are you missing an assembly reference?)

The last green build was on 5019088

The first red build was on 31203f0

As the failures started on a no-op merge PR, this is very confusing. It may be related to a recent update to the VS versions on the build machines, or it may not.

Info:

  • It repros on VS 16.5.0 & 16.5.1, but not 16.4.5
  • Adding rollForward: major and updating the VS version in global.json didn't fix it in CI
  • Experimental build confirms that it's not due to a code change, but the VS Rollout: https://dev.azure.com/dnceng/internal/_build/results?buildId=594826
  • It affects only non-packable projects in the shared framework
  • It happens when a test project is building its project references (One example being IIS.NewHandler.FunctionalTests)

Still digging, but this is a blocker for 3.1.4 and needs to be fixed by Tuesday

CC @dotnet/aspnet-build

Metadata

Metadata

Assignees

Labels

DoneThis issue has been fixedarea-infrastructureIncludes: MSBuild projects/targets, build scripts, CI, Installers and shared framework

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions