Description
The SDK has a functionality called advertising manifests which is used to make sure that your installed workloads are up-to-date. The process in simple terms consists of a check that happens daily against your configured feeds to see if there are any newer versions of the workloads than the ones you have. Later, if you run a dotnet command like dotnet build, the SDK prints out a message letting you know that there are updates in your installed workloads, so that you can update them.
It seems like this functionality is broken when a workload is installed by Visual Studio, as opposed to being manually installed via the command line. This is bad for a group of users like Windows .NET Aspire users, as they mostly rely on getting their workloads installed via Visual Studio. The reason why this is bad is because if Aspire ever decides to ship a newer version of the workload before it is available in a Visual Studio update, then users will have no way of knowing that a newer version is available. In Aspire, we are considering shipping our workloads in a different schedule (that may not necessarily match Visual Studio schedule), but this issue is currently being a blocker for that. It would be great if this issue can be fixed, so we can start having an alternative for notifying customers when newer versions are available.