RepoJournal
.NET

@dotnet

The .NET runtime, ASP.NET, and the C# tooling

Pick a date

Topics: .NET Full archive →

The Wire · Showcase

SOURCE.DOT.NET PROXY LAYER BROKEN, SOURCEBROWSER GETS MAJOR OVERHAUL

By RepoJournal · Filed · About .NET

source.dot.net is serving HTTP 500s and stale assets because the proxy layer exposes bugs that local-disk deployments never catch, and SourceBrowser just got a significant upgrade that's likely its last.

The proxied index serving defects [1] stem from a single root cause: Azure blob storage serving paths that local deployments never exercise, which is why the new SourceBrowser deployment [2] only broke production. One specific failure: `Helpers.ProxyRequestAsync` unconditionally converts null ContentHash to Base64, crashing on `SolutionExplorer.html` [3]. The overwrite files shadowing the fresh index are the second blow [3], serving 28KB stale CSS and empty HTML placeholders instead of the new 45KB chrome. The good news: SourceBrowser just absorbed 42 commits of feature work from the maintained fork [2], and this update to the latest upstream is likely the last time that'll be necessary since the original repo is soft-archived. Meanwhile, the nav-pane improvements [4] add per-subfolder repo filtering for the VMR via `GenerateVmrRepoTags`, letting source.dot.net's 26 repos stay behind a single URL while filter tags route searches to originating repos. On the extensions side, OpenTelemetry GenAI semantic conventions now have agentic workflows [5] that auto-scan upstream and maintain an evergreen draft PR, removing manual sync work.

Action items

References

  1. [1] Fix source.dot.net proxied-index serving (500, .js, references, SolutionExplorer) ↗ dotnet/source-indexer
  2. [2] Update to latest sourcebrowser and port a large number of additional features from tannergooding/sourcebrowser ↗ dotnet/source-indexer
  3. [3] Refresh stale index overwrite chrome for new SourceBrowser ↗ dotnet/source-indexer
  4. [4] Nav-pane layout, filtering, and lazy Solution Explorer improvements ↗ dotnet/source-indexer
  5. [5] Add agentic workflows that keep Microsoft.Extensions.AI aligned with OpenTelemetry GenAI semantic-conventions ↗ dotnet/extensions

Quick answers

What shipped in .NET on July 19, 2026?
source.dot.net is serving HTTP 500s and stale assets because the proxy layer exposes bugs that local-disk deployments never catch, and SourceBrowser just got a significant upgrade that's likely its last. In total, 6 commits and 6 pull requests landed.
Who contributed to .NET on July 19, 2026?
2 developers shipped this update, including tannergooding and jeffhandley.
What were the notable .NET updates?
Fix source.dot.net proxied-index serving (500, .js, references, SolutionExplorer), Update to latest sourcebrowser and port a large number of additional features from tannergooding/sourcebrowser, and Refresh stale index overwrite chrome for new SourceBrowser.

More from @dotnet

Daily updates, in your inbox

Follow .NET

The .NET runtime, ASP.NET, and the C# tooling We'll email you a link to confirm first.

Free. Confirm via email. Unsubscribe in one click.

— or follow the whole beat:

Elsewhere on the wire