Comment by neutronicus
2 days ago
It definitely seems like Visual Studio is no longer feeling the love.
IMO Visual Studio presented an incredible opportunity to sell Copilot. Implement a MCP server, give the LLMs in Copilot all the tools available to a human developer to analyze and debug a codebase. Instead it's just a shitty autocomplete you have to turn off in order to get the good, IntelliSense autocomplete working.
Our parent company went hilt-deep into Copilot and ... now they're backing off, because nobody likes it!
I just don't get it. They couldn't get the AI people and the Visual Studio people in a room together? I guess, cynically, probably not, because the AI people aren't on the same continent as the Visual Studio people?
Very frustrating.
You need to jump into VS 2026 for those goodies.
It was so rushed out, that many of the dialog windows on the new settings pane show tiny VS 2022 settings dialogs as popups.
Wait, can VS2026 Copilot make tool calls to bring only relevant type and function definitions into Context?
If yes, that would be great! I've been trying to bodge that together with clangd and emacs LSP, but the amount of yak shaving to get clangd actually working on our codebase (on which Visual Studio just works for the most part) is prohibitive for actually accomplishing anything.
Our codebase is millions of line of very non-standard C++ (some automatically translated from Pascal years ago), and single files can get up to 50,000 lines.
So a LLM really needs (just like us human developers!) the ability to skip around and only read the parts that matter.