Show HN: Graphify C# – Compiler-accurate Find Usages for coding agents
Posted by zachsaw 15 hours ago
Comments
Comment by spicyusername 12 hours ago
Unions coming in .NET 11 / C# 15 are going to be great.
Comment by el_benhameen 11 hours ago
Comment by bob1029 9 hours ago
C#/.NET feels unreasonably effective as a target for LLMs. The reflection and compiler services are not found anywhere else and have profound effects that HN still seems to be taking massive naps on.
Comment by JFuzz 13 hours ago
Comment by zachsaw 5 hours ago
Comment by exceptione 7 hours ago
"Read the relevant design documents under docs/ before changing architecture."
makes me think that developing 'graphify the tool' and using 'graphify as a tool' are mixed up in the same document? How does an LLM keep track of both this gigantic skill and the user development problem at the same time?Comment by zachsaw 5 hours ago
Comment by exceptione 4 hours ago
Comment by thiagoc77 2 hours ago
Comment by Merad 12 hours ago
Comment by zachsaw 9 hours ago
Comment by poilcn 12 hours ago
Comment by coverband 10 hours ago
Comment by zachsaw 9 hours ago
Comment by quietraster 8 hours ago
Comment by zachsaw 5 hours ago
Comment by yodon 15 hours ago
Comment by CatsOwlsCatsOwl 13 hours ago
GitHub Copilot's semantic index can work for any SaaS repo provider (GitLab, Bitbucket, etc.) or any local repos but this requires you to opt into the feature. Repos hosted in GitHub and Azure DevOps do NOT require opting into it since Microsoft already has your code.
Comment by zachsaw 15 hours ago
Comment by jayd16 14 hours ago
Comment by gregoryl 14 hours ago
Comment by zachsaw 14 hours ago
EDIT: I think the differentiation is that this isn't MCP based. Dumping a portable json file allows much more flexibility than just having to run Rider IDE in the background with the solution loaded and indexed. e.g. the graph works with jq, CI (gates), arbitrary agents without MCP support, non MCP tools, bulk questions etc.
Comment by creatorofuniv 12 hours ago