Marc Paine

Thanks for confirming that worked for you. At this time, are you unblocked and can this issue be closed?

@Redth any ideas? @sangwook96 can you search for "new_6" in the dotnet\sdk-manifests folder? Can you also run dotnet --info and share the results as well?

Those NU1301 usually means you don't have access to a particular feed but since those are online feeds, I'm not sure. @aortiz-msft @JonDouglas who may know more about the nuget...

Was this resolved in 17.4.0?

@JakeRadMSFT looks like model builder. Where should this get routed?

/azp run

@vitek-karas I was looking at https://github.com/dotnet/runtime/commit/faa272f860f83802a9cee65619e6e2e841b05433 which improved the output for the tests in AzDo. That was later removed when fluent assertions was updated but making the same change here...

Also, AssertionScope doesn't appear to have a definition for AddFailure. I'm trying to figure out why it did in the runtime when your change went in but doesn't here.

Updating the version of Fluent didn't work and I still can't get the AddFailure workaround that Vitek had put into place to work in this repo. @vitek-karas how did you...

@vitek-karas thanks for the pointer. I missed that originally as there were two spots we have the fluent version listed and I hadn't updated the one the tests actually use....