Vault 2026 - .net framework debugging

[connor.ferguson]

I have a .net framework extension that still loads and run in Vault 2026 but i cant debug it because 2026 is now built on .net core runtime and i get this meesgae form Visual studio:
The debugger was configured to use the desktop CLR (.NET Framework) Managed debugger, but the target proces loaded the CoreCLR (.Net Core) runtime.

I understand i need to update the plugin to .net core but short term is there a workaround so i can debug .net framework in 2026?

[Markus.Koechl]

My personal experience during the beta phase is that, regardless of whether it is possible, don't spend time. Instead, create a fresh .NET Core project and copy (or link within the same solution) your modules to the new one. I also recommend not using the .NET FW -> .NET migration tool; I got cleaner code in a shorter time. But again, that's my personal view on it, and other professionals might see it differently. The SDK templates have been updated to create clean, working new extensions targeting .NET Core.

[connor.ferguson]

Hi Markus, 

thanks for the reply. Yes i would agree but i have a large amount of code for an application that still needs to run in 2026 and the previous two year versions. I was hoping for a quick solution for now to get a 2026 version up and running which i can use the .net framework sdk for but its risky if i cant debug it.

[egervasio]

hi, i cannot get it to load but it worked for 2025, may i ask if you changed anything in particular to make it work on 2026

[connor.ferguson]

no nothing particular, just the usual dll references to the 2026 SDK, API version and vcet.config file.

[FRFR1426 · Accepted solution]

It's because Visual Studio don't let you choose the runtime for debugging (with Rider, you can choose between .NET Framework or .NET / .NET Core). You can start your extension without debugging, then attach the debugger. When you attach, you can choose the runtime to use.

[connor.ferguson]

Simple as that. Thanks for the solution!