Daniel Plaisted

> Maybe we can use https://api.nuget.org/v3/invalid.json ? That way we at least have some more influence/knowledge on what goes on with the url Yes, that seems like a good idea...

Here is another workaround which may be better than creating publish profiles for each project. Create a `Directory.Build.props` file in the root of your repo with the following contents: ```xml...

This is helpful, but once we switch the default to use workload sets, we shouldn't see the ShouldInstallAWorkloadSet message anymore. Given that, I don't think the OnlyBaselineManifestFound message is really...

Looks good, but in Chet's screenshot, it seems a bit confusing that it says the workload version is `9.0.100-manifests. (not installed)`. That seems to imply that the baseline manifest version...

This was superseded by https://github.com/dotnet/sdk/pull/43472

Looks like a race condition or similar in `TimestampedFileLogger` between disposing the object and writing out the messages. Since it's a timing issue, it could start occurring without any specific...

This started showing up a lot more in validation for .NET SDK 8.0.300. See https://github.com/dotnet/aspire/issues/4145 I was able to debug it, and it looks like the issue is here: https://github.com/dotnet/templating/blob/a78c4f56224c801d10db62257a78c86cdf778a92/src/Microsoft.TemplateEngine.Edge/Settings/TemplatePackageManager.cs#L351-L363...

In case they help, here are some stack traces of the code that ends up accessing the workload resolver in parallel: ``` Microsoft.DotNet.TemplateLocator.dll!Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadResolver.LoadManifestsFromProvider(Microsoft.NET.Sdk.WorkloadManifestReader.IWorkloadManifestProvider manifestProvider) Line 196 C# Microsoft.DotNet.TemplateLocator.dll!Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadResolver.InitializeManifests() Line 164...

Because it's buried in the linked issue, here's what the failure would actually look like when you tried to create a project using a template that used the workload constraint:...

For the CLI team, we'd like this as soon as possible. Currently we are handling this via time-consuming, error-prone processes.