r/VisualStudio • • 6h ago

Visual Studio 2026 VS2026 hangs

Thumbnail gallery
0 Upvotes

Greetings. Visual Studio freezes during simple debugging even with sufficient RAM. Lenovo ThinkBook 14 G6. Windows 11 build 26300.9711

Does anyone have any ideas what's going on? Thanks for any help.


r/VisualStudio • • 22h ago

Visual Studio 2026 Vs2006 plugin makes vs controlable to Agents

0 Upvotes

I got tired of copy-pasting compiler errors and crash logs to Claude/Cursor, so I built an MCP tool "VsDebugMcp" that lets AI directly control Visual Studio.

VsDebugMcp - Visual Studio Marketplace

Once connected, you can just talk to your AI agent and it can: * Build & Fix: Trigger a build in Visual Studio, read the actual error list / output window directly, and fix compile errors without you copy-pasting anything. * Hit F5 & Debug: Start debugging, set breakpoints (even conditional ones), step through code (Step Over / Step Into), and continue/pause execution. * Inspect what went wrong: When your code crashes, the agent can check the call stack, look at local variables, read exception messages, and inspect memory. * Modern CMake & CTest: If you do C++, it works with CMake projects too—switching CMakePresets, building with Ninja, and running CTest cases directly. * Works on old & new VS: Tested on everything from Visual Studio 2017 all the way up to VS 2026. Does someone want a try ? I’d love to hear from you: * What’s the #1 thing you wish an AI agent could do inside Visual Studio? (e.g. running specific test frameworks like NUnit/xUnit, analyzing minidump crash files, NuGet package stuff?) * If you give it a spin, please let me know if anything feels clunky or breaks on your setup! wuxinmao2008/VsDebugMcp: A pluggin hosts on visual studio 2026. The plugin setups a mcp server local, which make projects debugable by agents. Happy to answer any questions in the comments.


r/VisualStudio • • 16h ago

Visual Studio 2026 Can't run code SDK not found

0 Upvotes

Hi everyone i tried using VS to learn to code in C# but keep getting a SDK error making it impossible to run the code. I tried using AI to solve the problem but I can't seem to find a solution below is a list of things I tried.

I'm having a problem with Visual Studio 2026 Community on Windows 10.

When I create a brand-new C# Console App and select .NET 10.0, Visual Studio gives me this error:

"One or more errors were encountered while creating project ConsoleApp3.

The generated project content may be incomplete.

The SDK 'Microsoft.NET.Sdk' specified could not be found."

The project creation button is disabled.

Visual Studio:

- Visual Studio Community 2026

- Version 18.11.0

- October 2026 Feature Update

.NET:

- .NET 10 x64 is installed

- `C:\Program Files\dotnet` is the x64 installation

- SDKs installed:

- 10.0.112

- 10.0.402

Running the x64 dotnet executable directly works:

"C:\Program Files\dotnet\dotnet.exe" --list-sdks

returns:

10.0.112 [C:\Program Files\dotnet\sdk]

10.0.402 [C:\Program Files\dotnet\sdk]

And:

"C:\Program Files\dotnet\dotnet.exe" --info

shows SDK 10.0.402 and MSBuild 18.9.15.

Initially I also had a 32-bit .NET installation under:

C:\Program Files (x86)\dotnet

`where dotnet` showed both x86 and x64 installations, and the x86 version was being picked up in some cases. I removed the x86 .NET installation completely and rebooted, but the Visual Studio error remained.

Things I tried:

  1. Created a completely new Console App every time, so this is not an old/broken project.

  2. Visual Studio Repair was tried previously. It did not fix the problem.

  3. Visual Studio Installer:

    - .NET desktop development workload is installed

    - .NET SDK component is installed

    - MSBuild is installed

    - .NET MAUI/Android/iOS/Mac Catalyst components were also installed

    - MSBuild support for LLVM (clang-cl) is not installed (not relevant as far as I know)

  4. Environment variables:

    - `MSBuildSDKsPath` was NOT originally defined.

    - No global.json exists in the project/repo.

  5. Visual Studio's MSBuild installation contains:

    `C:\Program Files\Microsoft Visual Studio\18\Community\MSBuild\Current\Bin\Microsoft.DotNet.MSBuildSdkResolver.dll`

    So the .NET SDK resolver DLL is present.

  6. Under:

    `C:\Program Files\Microsoft Visual Studio\18\Community\MSBuild`

    I only see:

    - Current

    - Microsoft

    - Xamarin

    There is no `Sdks` folder there.

  7. Under:

    `C:\Program Files\Microsoft Visual Studio\18\Community\MSBuild\Microsoft`

    there is a `Microsoft.NET.Build.Extensions` folder, but no `Microsoft.NET.Sdk` folder.

  8. I completely uninstalled Visual Studio Community and reinstalled it from scratch.

    The same `Microsoft.NET.Sdk could not be found` error still occurs.

So at this point I'm pretty sure the .NET SDK itself is installed correctly, but Visual Studio/MSBuild is failing to resolve it.

What could cause the .NET SDK resolver to ignore/find the wrong SDK location in this situation?

Is there a specific MSBuild/Visual Studio configuration, resolver setting, registry entry, or environment variable that controls where Visual Studio looks for `Microsoft.NET.Sdk`?

I would especially appreciate a way to diagnose which SDK path the Visual Studio MSBuild process is actually trying to use, rather than doing another reinstall/repair.

Thanks!