Skip to main content

Discovering Visual Studio 2026–Adaptive paste

Yes! The new Visual Studio 2026 edition is available in preview (now called Insiders). I'll take some time this week to walk through some of the features I like and maybe some of the rough edges I discover along the way.

Let’s be honest. Every developer copy and pastes other code. Typically after pasting there is some cleanup left to do; correcting styles, adapt to your naming conventions, fixing small errors. process often comes with extra steps. What if the pasted code is automatically adapted incorporating one or more of the following actions

  • Aligning syntax and styling with the document
  • Inferring parameter adjustments
  • Fixing minor errors
  • Supporting language translation, human and code-based
  • Completing patterns or filling in blanks

Wouldn’t that be great? Enter adaptive paste.

Adaptive paste

The adaptive paste UI appears when you do a regular paste (CTRL-V). Press the TAB key afterwards to get an Adaptive Paste suggestion.

You can also trigger Adaptive paste by using the (ALT-SHIFT-V) combination:

Remark: This feature is also available as part of the 17.14 update of Visual Studio 2022.

Let’s try a few scenario’s and see how the Adaptive paste handles it.

Code translation

Let’s take a piece of Python code and paste it in a C# file and see how it adapts the syntax, variable declarations, and idioms.

I take this simple Python method that checks if a number is prime number

and paste it into a PrimeService.cs C# class. Copilot rewrites the code to the following:

Maybe not perfect. But it does the trick... 1 point for Copilot!

Changing naming conventions

I tale some that uses a mix of naming conventions (camelCase, …) and paste it into  a PascalCase project. Here is the example I use:

After some thinking, Copilot transforms it to the following:

Great! Another point for Copilot.

Test framework adaption

A third scenario I wanted to give a try was to take an MSTest unit test example and paste it into an XUnit project.

I copied the following example from Microsoft Learn about MSTest:

And pasted it in a C# XUnit test project

GitHub Copilot thinks a while but in the end no code was changed.

2 out of 3 points, that is not so bad….

First conclusions

These were only some simple scenario’s I could think of but they are a good indication on what it possible. It is certainly a great improvement and takes away some of the annoyances when doing copy/paste operations in your code base.

Nice!

More information

Effortless adjustments with an adaptive paste - Visual Studio Blog

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...