Remove exception throwing from InitializeManifests to allow workload commands to proceed

Copilot · marcpopMSFT · Copilot · commit a978b87e0dc6 · 2026-01-09T00:29:55.000Z
- Reverted throwing behavior in InitializeManifests()
- Workload install/update/restore commands can now proceed without being blocked
- Error messages still displayed in info commands via ShowWorkloadsInfo()
- This allows users to run 'dotnet workload update' to fix missing manifests

Co-authored-by: marcpopMSFT &lt;12663534+marcpopMSFT@users.noreply.github.com&gt;
diff --git a/src/Resolvers/Microsoft.NET.Sdk.WorkloadManifestReader/WorkloadResolver.cs b/src/Resolvers/Microsoft.NET.Sdk.WorkloadManifestReader/WorkloadResolver.cs
@@ -84,20 +84,6 @@ private void InitializeManifests()
             if (!_initializedManifests)
             {
                 LoadManifestsFromProvider(_manifestProvider);
-                
-                // If manifests from a workload set are missing, throw the error when trying to use workloads
-                // This ensures errors are shown when building apps that require workloads
-                if (_manifestProvider is SdkDirectoryWorkloadManifestProvider sdkProvider)
-                {
-                    var manifestError = sdkProvider.GetManifestErrorMessage();
-                    if (manifestError != null)
-                    {
-                        // There's an error with missing manifests from a workload set
-                        // Throw it so users know what's wrong
-                        throw new FileNotFoundException(manifestError);
-                    }
-                }
-                
                 ComposeWorkloadManifests();
                 _initializedManifests = true;
             }
