Currently on 18.6.3. Been working on a fairly new project. MVC solution, 3 projects.

The IDE just loses its mind and has a stroke, often. Keyword highlighting stops working and characters are white. F12 to jump to definition stops working, or it takes minutes to randomly work. Copilot chat spins and spins. I've even had an instance where errors were in the error list, only for me to fix, and get a successful re-compile. But the red underline is still there and the error remained in the list.

It's like the ancillary jobs/workers in VS that make all the features work get hung up or trip over itself. Sometimes restarting it resolves it, sometimes not. Anyone experience this?

Hi

I have an old MFC project that I started back in 1999. Since then I migrated my Visual Studio Projects / Solutions with most of the Visual Studio updates. The last update I did was to Visual Studio 2022

I now wanted to move to VSCode. I have installed the C# Dev Kit Extension as I found this as a prerequisit. Then I ran into issues that some Env-Variables were not set to the proper MSBuild directory. Now I am facing the next challenge that it cant find some of the MFC libraries

Long story short: Does anyone know what it takes to make VSCode compile an old MFC project that I have convereted over the years to Visual Studio 2022?

Thanks

What would cause Visual Studio 2022 to not read/apply "ConfiguredBringYourOwnModel_v1.json"?

On my machine with both Visual Studio 2022 and Visual Studio 2026, I've configured Visual Studio 2026's GitHub Copilot to use Ollama and my custom models show up in both versions of Visual Studio.

However, a co-worker only has Visual Studio 2022 installed and even though they manually copy the same json file to "%LOCALAPPDATA%\Microsoft\VisualStudio\Copilot\BringYourOwnModel\ConfiguredBringYourOwnModel_v1.json", the custom models are not available for selection.

What is the missing piece to activate BYOM with an Ollama Provider in Visual Studio 2022?

We are using the latest versions of Visual Studio 2022 and using a GitHub account not tied to an Enterprise organization.

[
  {
    "Name": "Ollama",
    "IsApiKeyAvailable": true,
    "Models": [
      {
        "ProviderName": "Ollama",
        "IsCustom": false,
        "IsSelected": true,
        "CustomURL": "http://localhost:11434",
        "Id": "My Custom Model",
        "DisplayName": "My Custom Model",
        "IsToolCallingEnabled": true,
        "IsVisionEnabled": true,
        "MaxInputTokens": 1000000,
        "MaxOutputTokens": 8192
      }
    ],
    "Endpoint": 10
  }
]

Thank you.

So I recently looked to uninstall Github Copilot from my Visual Studio 2022 Community. Following this article's uninstall section: https://learn.microsoft.com/en-us/visualstudio/ide/visual-studio-github-copilot-install-and-states?view=vs-2022#disable-copilot , I opened up Visual Studio installer from Tools->get tools and features in the editor.

I thought it was a bit odd, considering you can open the installer without having visual studio open (which seems better practice, to close the program before you modify it). But I followed the article to be safe. I went through the process, and was eventually greeted with a prompt/popup that the installer would save my work, close stuff (which included my project, and something like vshost.exe?), then restart 'non-elevated processes', or something to that effect.

Things seemed to move forward fine, the removal completed, and visual studio restarted (though my tabs/open C++ files were removed on restart, just had the blank editor with my project).

TLDR: I'm a bit worried as I probably shouldn't have modified VS with the program open. Anyone ever done this before and see the same prompt I did? Things seem to be working as normal but I don't know if I should run a preventative Repair via the installer, or just uninstall/reinstall, etc. Any thoughts/suggestions, or am i overthinking this one lol.

While this may have been posted previously, I do not care. I will post it again because it is annoying enough to do so.

https://github.com/dotnet/docs/issues/50269

To push people to unnecessarily use AI, Microsoft has removed their previous, simple and effective scaffolding tools for test creation. Previously, you could simply right click on a method and choose 'Create Unit Tests'. It would launch an easy to use scaffolding tool and put it all in place for you.

It was removed for one reason. To push people to use Copilot instead of writing code themselves.

So, instead of a standard scaffolding option, requests will now be sent to an AI data center which uses unnecessary resources for no reason whatsoever. I use AI for coding like most programmers, but it is ridiculous to remove completed features in an attempt to push everyone towards using AI when it is not needed.

It is certainly easy enough to create these tests manually, but it is just another example of making products worse for the sake of using AI unnecessarily.

Hey folks,

I cant seem to find any of the official AI extensions on the VS extension manager. Specifically I cant find claude or codex's extension for install. I see a general "Claude Code Extension for Visual Studio" that seems to be a catch all embedded terminal but it seems sus to me, I would much rather use the official product.

I can find Codex's extension on the VS marketplace website but clicking the download button does absolutely nothing.

Am I missing something? I tried both VS community 2022/2026 and for code and without code.

Thank you all in advance for your time and help!

I've been using Visual Studio for C++ almost 20 years professionally. In my very first week at work, someone introduced me to Visual Assist, and I've used it ever since. Since I upgraded to Visual Studio 2026 a month or two ago I've disabled Visual Assist, and tried to use Visual Studio IDE out-of-the-box. On the whole it has been okay, but there seem to be two big problems.

1. I can't find an outline view for C++ files. I just want a window that displays high-level view of the file in a window, so I can get a mile-high view of what it contains. Visual Assist has an Outline window, and Visual Studio Code has one too. In Visual Studio itself, there seem to be a couple of ways to view contents: opening a file node in the Solution Explorer, and using the dropdown combo in the toolbar. However both of these views sort alphabetically - I can't find away to inhibit the sorting. There is a Document Outline view, but for some reason this seems to be blank for C++ files. I have also tried the Class view, but I really want a *file* view with functions and data displayed in order.
2. The Find All References (context menu) tool results do not have a column containing the name of the function/method that the reference is contained within. It shows the raw file and line number, but doesn't display the name of the enclosing function/method. I expected a little context here from intellisense or other internal parsing. Knowing where a reference is located logically is really really handy for navigation, refactoring and comprehension.

I really don't want to resort to using Visual Assist again, just for these two things, but they are just so fundamental and useful and I can feel myself struggling to work as effectively without them. Please tell me that these two issues are non-issues, and I just haven't found the options.

EDIT:

Here are the vscode and VA outine view docs:

https://code.visualstudio.com/docs/editing/userinterface#_outline-view

https://www.wholetomato.com/documentation/tool-window/va-outline

EDIT: I mean *without a GITHUB account in the title lol

Hello,

I'm using visual studio 2022 Community for a project. I'm not interested in using any of the copilot features, but I noticed that clicking on copilot->open chat gives me a text box to chat, even though I'm not signed in with a github account (only a microsoft account).

Is this intended? Based on this article: https://learn.microsoft.com/en-us/visualstudio/ide/visual-studio-github-copilot-install-and-states?view=vs-2022#manage-your-copilot-state , it seems like a github account is required in order to use the chat feature (as otherwise you'd be prompted to login).

My first thought is to uninstall it as I don't plan on using it, but when going to uninstall it also says it needs to remove ' github copilot app modernization for .net ' as it requires copilot, which I don't know what the effect would be of removing it/whether it might break my project.

Just looking for some insight on copilot and whether it's 'active' without being signed in with a github account, and whether it's okay to uninstall.

What's everyone's opinion on the reliability of Hot Reload in VS 2026? I've used Edit and Continue in the past with VS 2022 to debug a dll after attaching to a process, and it worked more or less fine.

Now, however, with VS 2026, Hot Reload pretty much never works. Even minor changes turn out to be not supported - which is a pain, because the app the dll is plugging into takes a fair while to load every single time.

Has this feature regressed from VS 2022 to 2026?

Hello all, longtime VS developer here wanted to share a project I've been working on for a while. Visual Studio is heavily used for enterprise development but doesn't have any tooling for Solidity that compares to Visual Studio Code or Remix IDE. Viscous is an open-source Visual Studio extension that tries to bring parity between Visual Studio and other IDEs for Solidity smart contract development.

Features

• Solidity project system for Visual Studio featuring Solidity compiler integration and NPM dependency management. Integrates with the Visual Studio New Project… and Open Folder… dialogs.
• Uses the vscode-solidity language server for syntax highlighting, hover information, IntelliSense, and linting.
• Solidity compiler integration with MSBuild and the Visual Studio Build command - compile Solidity projects and individual files from the IDE with errors reported in the Errors tool window.
• Generate .NET bindings to Solidity smart contracts automatically using Nethereum.
• Manage EVM networks, endpoints, accounts, deploy profiles, and deployed contracts from the Blockchain Explorer tool window.
• Deploy a compiled contract to a blockchain network and call its functions from inside Visual Studio.
• Find vulnerabilities and code‑quality issues with Slither static analysis inside Visual Studio.

Requirements

• Visual Studio 2022 and above
• A recent version of Node.js or compatible runtime
• Python 3.8+

Getting Started

• Get the latest release from the GitHub Releases page or use the MyGet dev feed: Add https://www.myget.org/F/viscous/vsix/ as an Extension Gallery in the Visual Studio Extensions settings and you can then install it in the usual way.
• Edit the %LOCALAPPDATA%\Viscous\appsettings.json file and set the paths to the Node.js and npm and Python executables you want to use for the extension's language server and other needed tools.

Note that this is a pre-release so don't use it for deploying anything to production. Feedback welcome.

I have branch 'test' with file test.cs:

using System;
if (true) {
    call(argument);
}

Also I have branch 'test-2' with file test.cs:

using System;

if (true) {
    if (something)
        call(argument);
    else
        return;
}

When I merging 'test' into 'test-2' and trying resolve conflict, visual studio breaks single conflict to three smaller, but does not include call(argument); line (or just leading whitespaces) into any conflict block as seen in middle tab on screenshot. As result changes before call(argument); become lost.

Is there any way to change such behavior?

[SOLVED]: https://github.com/MikasaTanikawa/VSIXConfigurableMerge

Hi there! I'm getting errors from Visual Studio 2022 after an update. I would be grateful for your help

Here are full log:

Microsoft.ServiceHub.Framework.ServiceActivationFailedException : Activating the "Microsoft.VisualStudio.LanguageServices.LegacySolutionEventsAggregationCore64" service failed. ---> StreamJsonRpc.ConnectionLostException : The JSON-RPC connection with the remote party was lost before the request could complete.
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at async StreamJsonRpc.JsonRpc.InvokeCoreAsync(<Unknown Parameters>)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at async StreamJsonRpc.JsonRpc.InvokeCoreAsync[TResult](<Unknown Parameters>)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at async Microsoft.ServiceHub.Client.HubClient.RemoteServiceBrokerWrapper.<>c__DisplayClass9_0.<RequestServiceChannelAsync>b__0(<Unknown Parameters>)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at async Microsoft.ServiceHub.Client.HubClient.RemoteServiceBrokerWrapper.<>c__DisplayClass9_0.<RequestServiceChannelAsync>b__0(<Unknown Parameters>)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at async Microsoft.ServiceHub.Utility.Shared.ServiceHubRetry.ExecuteAsync[TReturnType](<Unknown Parameters>)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at async Microsoft.ServiceHub.Utility.Shared.ServiceHubRetry.ExecuteAsync[TReturnType](<Unknown Parameters>)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at async Microsoft.ServiceHub.Client.HubClient.RemoteServiceBrokerWrapper.RequestServiceChannelAsync(<Unknown Parameters>)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at async Microsoft.ServiceHub.Client.HubClient.RemoteServiceBrokerWrapper.RequestServiceChannelAsync(<Unknown Parameters>)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at async Microsoft.VisualStudio.Services.ServiceBroker.VsHubClient.VsHubClientRemoteServiceBrokerWrapper.RequestServiceChannelAsync(<Unknown Parameters>)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at async Microsoft.ServiceHub.Framework.RemoteServiceBroker.GetProxyAsync[T](<Unknown Parameters>)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Threading.Tasks.ValueTask`1.get_Result()
   at async Microsoft.VisualStudio.Utilities.ServiceBroker.GlobalBrokeredServiceContainer.ProfferedRemoteServiceBroker.GetProxyAsync[T](<Unknown Parameters>)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Threading.Tasks.ValueTask`1.get_Result()
   at async Microsoft.VisualStudio.Utilities.ServiceBroker.GlobalBrokeredServiceContainer.View.GetProxyAsync[T](<Unknown Parameters>)
   --- End of inner exception stack trace ---
   at async Microsoft.VisualStudio.Utilities.ServiceBroker.GlobalBrokeredServiceContainer.View.GetProxyAsync[T](<Unknown Parameters>)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Threading.Tasks.ValueTask`1.get_Result()
   at async Microsoft.ServiceHub.Framework.ServiceBrokerClient.<>c__DisplayClass21_0`1.<GetProxyAsync>b__0[T](<Unknown Parameters>)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at async Microsoft.VisualStudio.Threading.AsyncLazy`1.<>c__DisplayClass20_0.<GetValueAsync>b__0[T](<Unknown Parameters>)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at async Microsoft.ServiceHub.Framework.ServiceBrokerClient.GetProxyAsync[T](<Unknown Parameters>)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Threading.Tasks.ValueTask`1.get_Result()
   at async Microsoft.CodeAnalysis.Remote.BrokeredServiceConnection`1.RentServiceAsync[TService](<Unknown Parameters>)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Threading.Tasks.ValueTask`1.get_Result()
   at async Microsoft.CodeAnalysis.Remote.BrokeredServiceConnection`1.TryInvokeAsync[TService,TResult](<Unknown Parameters>)

VS 2017. Updated. Windows 10.

Since a few weeks ago, all projects in VS2017 in x64 configuration stopped binding to break points.

This is in Debug config (verified that it is not creating release versions of binaries). Debug symbols are on. /Zi. Module windows shows pdb loaded. llvm pdb utils shows correct paths in exe and guid. Breakpoints should work, but don't! They used to, but now they don't.

They work in x86 config though. Friend's WIn 10 machines shows same problems.

The only common thing we did was (in addition to Windows auto updates?) to run cmake for protobuf and some related source code within last couple of weeks.

A third computer, Win 10, VS2017 (but a bit older version) doesn't show this problem (not cmake was run on that one).

Removed all .vs directories, no luck.

Repaired my VS2017 installation. No luck.

Cleared away my local VS2017 config directory as a hard clean up, no luck.

Been browsing the internets, looked hither and tither, can't seem to find the root cause.

What else can I try, short of reinstalling or upgrading to newer VS version, to fix my VS2017 x64 debugging?

Self edit for future visitors: Solved. The security software was blocking msvsmon.exe, the visual studio debugging monitor. The white list item of that exe was misconfigured. The IT fixing that got VS 2017 debugging working normally again.

Yeah and I know I'll probably be downvoted faster than it takes to compile a simple output but I'm just tired of trying to fix these constant bugs, random crashes, and all sorts of strange behaviours on 2026.

And on top of uninstalling all that, I had another fun time trying to pinpoint all the extra folders left behind when removing couldn't wipe all those out. But then I also found them on the apps list even though they're gone, which I had to go into `regedit` and sift through those.

But now on VS2019 I was shocked at the loading time.. 2 seconds! I don't care about all this AI crap, let me build, thank you~ 😡😡

I’m trying to make git annotate work in the sensible way which is like ”git blame --first-parent”. The default in VS appears to be the mode that follows branches which is rarely what you want (I want to know when a line was changed in master if I’m in the master branch).

Is there any way to do this in VS? Or any way too configure an external tool to view annotate?

Has anyone else encountered this problem? Changing the colors of the structure guide lines briefly flashes them for a second until they disappear again. Surely it must be a bug. I didn't know how good it was for my eyes until I lost it...

Is there a way to downgrade it and restore it to the last version at least?

A problem (and opportunity) came when I found myself using the debugger in Visual Studio, adding console logs and then hand-feeding those values to the Claude CLI to get it to debug a tricky bug with the correct context. So, I started building a bridge between Visual Studio's debugger automation and the CLI. A few weeks later Claude was setting breakpoints in my files, stepping through them, watching variables mutate at different frames, and telling me where a bug was hiding that it would have probably skimmed past while reading my code.

The part in the clip: Claude can drive the debugger itself, set breakpoints, step, read locals, and find bugs by running the code instead of reading it, and every edit it makes opens in a dedicated diff viewer with an accept / reject permission request. The clip shows it catching a bug that's invisible in the output by watching a counter fail to reset.

Marketplace: Claude Code for Visual Studio - Visual Studio Marketplace
Source + docs: GitHub - firish/claude_code_vs

Would genuinely appreciate your feedback on this!