Latest version of Microsoft.Toolkit.Uwp.UI.Controls is causing errors while running VSTS build

[emyfreya]

Describe the bug

Exactly this error #2452, but not quite the same conditions.
Building & Compiling is done via Visual Studio build using the Latest parameter in version. We're trying to build it in Release mode.

Works locally with the same command using msbuild.exe.

• Is this bug a regression in the toolkit? If so, what toolkit version did you last see it work: 6.0.0

Steps to Reproduce

1. Create an UWP app
2. Add Microsoft.Toolkit.Uwp.UI v6.1.1
3. Build via Pipelines, using msbuild.exe
4. Error appears after some time, indicating to validate some terms.

C:\windows\ServiceProfiles\NetworkService\.nuget\packages\microsoft.toolkit.uwp.ui.controls\6.1.1\lib\uap10.0.16299\Microsoft.Toolkit.Uwp.UI.Controls.pdb : fatal error CMF1106: failed to open input PDB file for reading (PDB error code = 13)3 input PDB file is not generated by /DEBUG:fastlinkW must read and agree to the Data Collection Policy at ?? before using /errorreport:send1 warning treated as error; the PDB file is intact@ specified output filename is too long (exceeding 0 characters)

##[error]C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\Microsoft\VisualStudio\v16.0\AppxPackage\Microsoft.AppXPackage.Targets(3515,5): Error MSB6006: "mspdbcmf.exe" exited with code 1106.

Expected behavior

The build to come to an end.

Environment

NuGet Package(s): 
- Microsoft.Toolkit
- Microsoft.Toolkit.Uwp
- Microsoft.Toolkit.Uwp.UI
- Microsoft.Toolkit.Uwp.UI.Controls
- Microsoft.Toolkit.Uwp.Controls.DataGrid
- Microsoft.Toolkit.Uwp.UI.Media

Package Version(s): 
- 6.1.1

Windows 10 Build Number:
- [ ] Fall Creators Update (16299)
- [x] April 2018 Update (17134)
- [ ] October 2018 Update (17763)
- [ ] May 2019 Update (18362)
- [ ] May 2020 Update (19041)
- [ ] Insider Build (build number: )

App min and target version:
- [ ] Fall Creators Update (16299)
- [x] April 2018 Update (17134)
- [ ] October 2018 Update (17763)
- [ ] May 2019 Update (18362)
- [ ] May 2020 Update (19041)
- [ ] Insider Build (xxxxx)

Device form factor:
- [x] Desktop
- [ ] Xbox
- [ ] Surface Hub
- [ ] IoT

Visual Studio 
- [ ] 2017 (version: )
- [x] 2019 (version: 16.0) 
- [ ] 2019 Preview (version: )

Additional context

Will add anything to help if necessary. I think every details is there.

Hello JeremyFerreira, thank you for opening an issue with us!

I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌

[emyfreya]

I can confirm by downgrading every package Microsoft.Toolkit. to 6.0.0 except Microsoft.Toolkit.Uwp.UI.Media that stayed in 6.1.1, the build passes without any error.
I did try to downgrade only some of them, but I think there is some dependencies that won't allow this to work.

[michael-hawker]

Thanks @JeremyFerreira for the initial investigation. Last time in the linked issue, it was due to dependencies on the Microsoft.NETCore.UniversalWindowsPlatform package version updated in this commit. But that was in the Color Code project.

The media package was updated in 6.1 with some new features, but it's weird that it's complaining about path length to the PDB in the Controls package, as they shouldn't be linked...

Did you try the base 6.1 package or the 7.0 previews? It'd be interesting to know if we could narrow-in on when this break occured.

@azchohfi @Sergio0694 any ideas here? @azchohfi you had updated something related to PDBs at some point, eh?

[emyfreya]

@michael-hawker As this is a company project, I cannot test out anything without getting into trouble. I only tried to upgrade our NuGet packages to the latest available (non-preview) version.

[michael-hawker]

@JeremyFerreira is this a MAX_PATH issue or something? Is it possible to try and build your project and use nugets from another location that's closer to the root of the drive? Would be good to at least rule that out as a possibility?

Can you also clarify about where it's succeeding and failing in VS/msbuild?

Works locally with the same command using msbuild.exe.

Does it also work locally in VS? It's only failing in your pipeline with msbuild?

And you mentioned building for the 17134 build of windows, is that the same machine version running in the pipeline?

[emyfreya]

@michael-hawker

is this a MAX_PATH issue or something? Is it possible to try and build your project and use nugets from another location that's closer to the root of the drive? Would be good to at least rule that out as a possibility?

I do not have the rights to change anything on the pipeline.
The path itself ( C:\windows\ServiceProfiles\NetworkService\.nuget\packages\microsoft.toolkit.uwp.ui.controls\6.1.1\lib\uap10.0.16299\Microsoft.Toolkit.Uwp.UI.Controls.pdb) doesn't look that long (153 char). In the documentation, they state that the max default is 260, which is probably the one we use.

Can you also clarify about where it's succeeding and failing in VS/msbuild?
Does it also work locally in VS? It's only failing in your pipeline with msbuild?

Cases

Pipeline

• Updating every package to 6.1.1 fails to build in Release but succeeds in Debug.
• Updating only Microsoft.Toolkit.Uwp.UI.Media to 6.1.1and letting the other packages to 6.0.0 works in Release and Debug.

The Task used in the pipeline is VS Build, and the command line used behind is with msbuild.exe.

Other

• Updating every package to 6.1.1 and building with VS 2019 Enterprise or against msbuild.exe (reproducing the command generated in the pipeline) works in Release and Debug.

And you mentioned building for the 17134 build of windows, is that the same machine version running in the pipeline?

Our application's version supports only the 17134 build. The SDK is indeed installed on the pipeline. The actual host version must be superior to 17134.

[michael-hawker]

I'm not surprised about the media package, as that doesn't have any other dependencies on toolkit packages.

The main thing we changed that I think could be related between 6.0.0 and 6.1.0 is switching from full to portable PDBs:

@azchohfi @clairernovotny any thoughts here on what might be happening here?

I've noticed a few bugs/threads on this topic like this one and this one

The first thread indicates the portable PDB to be a problem, the 2nd thread indicates this was a bug in Visual Studio/tooling itself, see report here.

Adding @nickrandolph who may have also experiences the Xamarin issue and may know a bit more about if it was resolved by updating?