Visual Studio AI-Assistance: A Developer’s Best Friend

Peter Groenewegen

Senior Software Engineer

The Visual Studio family leverages AI to help you stay focused on the creative tasks that get the core logic of your application built.

For Visual Studio and VS Code, IntelliCode is free and assists with writing, editing and understanding code in popular languages. With IntelliCode, models run locally, meaning that none of your code leaves your machine. This blogpost will focus on IntelliCode.

For users desiring even more AI capabilities, Copilot and Copilot for Business are also supported by Visual Studio and VS Code. Copilot’s models are cloud based.

Tips, tricks, and engineering story behind IntelliCode.

Whether you’re a newer developer or experienced, consider this blogpost your jumping off point to get the most from IntelliCode. The team is excited to share tips, tricks and engineering stories that we’ll link to below – content to come soon!

Writing code

IntelliSense list: Instead of exploring an unsorted list of methods and members, IntelliCode uses AI to place what we believe is most relevant to your code context at the top and places a ⭐ symbol next to item.
Gray text: To help increase productivity and reduce errors, IntelliCode can suggest up to a whole line of code in grey text. Your code context and code style are used to help generate these suggestions.

Editing code

Repeated edits: Making several similar but slightly different edits? IntelliCode can detect the pattern and apply the change to other locations – saving you keystrokes and navigation.
Intent Detection: IntelliCode has learned to assist with common edit patterns such as creating a constructor after creating parameters, or even with editing code that’s just been pasted.

Navigating code

API Usage Example: Making a round trip to the browser and fiddling with search to figure out how to use an API is a common workflow. This feature can save you from that by presenting examples of how an API is commonly used.

Navigating Packages

Most Common NuGet Packages: This feature helps you find and use the most used NuGet packages, streamlining the process of finding and adding packages to your projects.

Reviewing code

The Visual Studio family is excited to explore AI-assistance for workflows that start with preparing a pull request and end with a successful merge.

The IntelliCode team is not only excited to help improve your productivity, but also to learn about your scenarios that could be improved with AI.

Topics

Author

Peter Groenewegen

Senior Software Engineer

Peter is a Software Engineer on the Visual Studio IDE team, where he's been integrating ML and AI in developer tools. He currently working on AI tools for developers.

27 comments

Discussion is closed. Login to edit/delete existing comments.

Dandy February 22, 2023

For me, this sort of assistance has now reached the point where it's just trying too hard and I now spend more time undoing what it does, than I would have spent had it not inserted anything at all.

I'm getting increasing frustrated lately just making corrections to some of the auto-suggest things that the editor is adding as I'm typing; for example, if I'm entering a ")" and the editor can't figure out where the matching "(" is, it'll insert it where my cursor is (the "(" it couldn't find, that is, not the ")" I just typed), shuffle some...
Read more
For me, this sort of assistance has now reached the point where it’s just trying too hard and I now spend more time undoing what it does, than I would have spent had it not inserted anything at all.

I’m getting increasing frustrated lately just making corrections to some of the auto-suggest things that the editor is adding as I’m typing; for example, if I’m entering a “)” and the editor can’t figure out where the matching “(” is, it’ll insert it where my cursor is (the “(” it couldn’t find, that is, not the “)” I just typed), shuffle some of the nearby code inside that opening parens, then follow that with the closing parens (which is the only character that ultimately should’ve been added). God help me if I’m working on skeleton code, typing in class names that I haven’t defined yet (but intend to soon) – then it starts making all sorts of bad suggestions and inserts bad stuff that I have to delete.

I’m told there’s options to disable that. A one-click button needs to be given prominence; hiding it 7 levels deep in an options tree isn’t going to incite me to turn it off only temporarily.

Read less
- Aaron Yim February 27, 2023
  
  That sounds really frustrating. There should be a purple lightbulb in the bottom left of your editor window that should make it easily to temporarily disable the feature. There’s also an option to wait for pauses in typing before showing a completion that should help you with the bouncing suggestions as you type.
Dave Bacher February 21, 2023

1. In a .NET 7 Blazor project, the AI is prioritizing deprecated features with stars pretty consistently.
2. In a .NET 7 Blazor project, the AI needs a higher repetition penalty because it's suggesting the previously typed line of code more often than not, particularly in the builder.Services.Add section of program.cs (this happens with Generic Host applications as well)
3. When adding Entity Framework, it will never suggest data annotations.
4. When defining POCO's, it will suggest the same handful of properties - which are often irrelevant to the specific class being defined, but common in Microsoft demonstration code.
5....
Read more
1. In a .NET 7 Blazor project, the AI is prioritizing deprecated features with stars pretty consistently.
2. In a .NET 7 Blazor project, the AI needs a higher repetition penalty because it’s suggesting the previously typed line of code more often than not, particularly in the builder.Services.Add section of program.cs (this happens with Generic Host applications as well)
3. When adding Entity Framework, it will never suggest data annotations.
4. When defining POCO’s, it will suggest the same handful of properties – which are often irrelevant to the specific class being defined, but common in Microsoft demonstration code.
5. When defining POCO’s, it will never suggest data annotation attributes or other useful things.
6. It often suggests things like – and this is real – “int intintintint(int intint) {get; set;}” that aside from being comically repetitive – also is simultaneously comically wrong.
7. It suggests a lot of anti-pattern and other code smells, presumably because of the training material.
8. I also can’t recall a single occurrence of it generating code that is both correct and compilable. It occasionally generates near miss code that only needs minor correction.
9. Due to C# file structure, it doesn’t have enough context in most cases to generate proper in-context code. Things like using many smaller classes aren’t good for the Open AI models – they want large, monolithic anti-patterns to have a shot at having enough context to point at the right spot. The typical taking C# and breaking it into classes and components makes it less likely Open AI’s models can generate good code.
10. Every Open AI generation has a token [AB] that exists in corpus and a token [BC] – for any arbitrary ABC adjacent in output, both [AB] and [BC] must have non-zero occurrence. This is what gives coherence – [ABC] very likely exists in corpus for any given training data. This is why Chat GPT is useful to Bing. What this means is that every “generated” code fragment is made up of chains of tokens that appeared in the corpus, and it’s an open question how long the chains can get, but assuming it’s Open AI’s model – which it is – we know they can stretch 200+ tokens, in some cases, over on the GPT side. We also know that this varies with diversity of context, etc. and we know the code is less diverse than the English language model.
I’m just saying – this feature is genuinely bad in its current state. Not only is it sometimes copying identifiable code from the corpus, but its also nearly never right on its suggestions and has a focus on deprecated features when writing .NET Core apps using MVC or Blazor. I don’t understand how Microsoft isn’t running into this constantly internally – it’s almost as if since your management sunk billions into Open AI, you’re trying to integrate it to earn points with them or something. Meanwhile, for most common coding things, I find Code Rush or similar tools are more useful than the AI model at reducing replicated code. And some of this could be done at a C# level, when you look at add ins.
Just as an example, there are plenty of tools for automating INotifyPropertyChange and IObservable – since the AI never suggests plausible, compilable or executable code for these major patterns, these other tools add way more value. But as with Sydney / Bing, Microsoft’s focus isn’t on generating correct information – working, viable code – their focus is on recouping senior management’s investment in Open AI.
But at a least, you should be able to negatively reinforce deprecated code in most Open AI models and ramp up the repetitition penalty, also – you need some more diversity in the entity framework scenarios that you’re training on so that the model can at least plagiarize more correct code. It appears the WPF and UWP code also isn’t very well trained, as well, and has similar issues but I don’t use it as often. On the JavaScript side, I’m also getting wrong and bad suggestions more often than correct ones – it’s also favoring deprecated properties in some libraries.
It is the single largest source of instability in the analyzers when I am on a shakey network – bar none.
Also, the feature does not stay off – turning it off disables it for some period of time, but it always eventually turns itself back on. I’m working on nailing down the condition, but it appears it might be when Visual Studio Installer pickes up a new version of the IDE. If I turn this feature off, I would very much appreciate it staying off. I’m less annoyed by some of the other stuff – but it genuinely appears, in this case, you toggle the setting back to on intentionally periodically as a “hey, I know you didn’t like this, but what about now” sort of a test. That’s fine, but as it does actively crash Roslyn regularly when your calls out to the API fail, I would really appreciate it if you’d leave the feature off until I intentionally re-activate it.

Read less
- Aaron Yim February 27, 2023
  
  Hi Dave,
  
  I'm hearing a couple things:
  
  1) That we should improve our performance for .NET 7 Blazor / EntityFramework; hang tight here - we're working on it.
  Other than .NET7 Blazor / EntityFramework (web app work) is there any other type of code that you write?
  Curious what kinds of scenarios we're doing poorly in (we know niche codebases to be more problematic).
  
  2) That you're running into repetition - we've done a fair bit of work here... but helpful to hear that it's still occurring to you in the real world for ya :( You're always welcome to tweet me or...
  Read more
  Hi Dave,
  
  I’m hearing a couple things:
  
  1) That we should improve our performance for .NET 7 Blazor / EntityFramework; hang tight here – we’re working on it.
  Other than .NET7 Blazor / EntityFramework (web app work) is there any other type of code that you write?
  Curious what kinds of scenarios we’re doing poorly in (we know niche codebases to be more problematic).
  
  2) That you’re running into repetition – we’ve done a fair bit of work here… but helpful to hear that it’s still occurring to you in the real world for ya 🙁 You’re always welcome to tweet me or email me at aayim @ microsoft . com if you see something that’s just bad.
  
  3) RE: re-enabling, please file a bug the next time you run into this. Settings state should be retained between versions.
  
  Read less
Zak Dwyer February 21, 2023

Despite the negativity surrounding IntelliCode, I think it does more help than harm. Sometimes I'll get a brain fart and the AI suggestion will help jog my memory. Often it has saved me a huge amount of time - main examples are when I've written properties and then it suggests a fully-formed constructor. Another example is changing references from one property/variable to another - navigate to the variable, change it once, and then every time you go to the next change it will automatically suggest it. Once in a while it comes up with a solution that was even more...
Read more
Despite the negativity surrounding IntelliCode, I think it does more help than harm. Sometimes I’ll get a brain fart and the AI suggestion will help jog my memory. Often it has saved me a huge amount of time – main examples are when I’ve written properties and then it suggests a fully-formed constructor. Another example is changing references from one property/variable to another – navigate to the variable, change it once, and then every time you go to the next change it will automatically suggest it. Once in a while it comes up with a solution that was even more ingenious than I would have came up with, and other times it suggests things like “List UsersUsers = new List()”.

Read less
- Aaron Yim February 27, 2023
  
  Zak,
  
  Thanks for taking the time to leave a comment, glad we’re of help.
  Two trains of thought here:
  
  1) RE: navigating to the next variable & changing it, we’re working on a new experience that makes it easier to navigate to next location & apply (i.e. tab to go to next location, tab to apply, etc.)
  
  2) RE: goofy suggestions, feel free to tweet the bad (and the good) to me @aaronyim. Love hearing how we can better help.
Stevie White (Dragnilar) February 18, 2023 · Edited

Hi Peter,

I appreciate the work MS is continuing to do to enhance the Intellisense and developer experience in Visual Studio. However, I am at the point where I think MS' experiment with using AI in VS may require rethinking. To date, I have not had any positive experiences with Intellicode versus using JetBrains' famous extension.

I will have to echo the feedback provided by Chuck Ryan, Henry B and Andreas S. Franci Gonçalves. And to add to their lists of problems I have with Intellicode, it also causes a lot of intermittent errors in Visual Studio. I tried to be...
Read more
Hi Peter,

I appreciate the work MS is continuing to do to enhance the Intellisense and developer experience in Visual Studio. However, I am at the point where I think MS’ experiment with using AI in VS may require rethinking. To date, I have not had any positive experiences with Intellicode versus using JetBrains’ famous extension.

I will have to echo the feedback provided by Chuck Ryan, Henry B and Andreas S. Franci Gonçalves. And to add to their lists of problems I have with Intellicode, it also causes a lot of intermittent errors in Visual Studio. I tried to be more diligent about reporting them in the past, but eventually I got to the point where I gave up on Intellicode and uninstalled it.

Another way to look at it: I really do not like the way Intellicode’s suggestions integrates into the VS workflow. It would be so much more helpful, but I am at a loss as to how you could improve it so that it integrates better into the general usage patterns that which people use for VS. This part of the extension is its most problematic, since it feels like it adds an extra “burden” on top of the work we do inside of the application. Your team may need to do some broader studies to set up requirements and/or get inspiration on how to better smooth out a developer adopting intellicode into their workflow.

Read less
- Aaron Yim February 27, 2023
  
  Hey Stevie, thanks for taking the time to leave a comment.
  
  I hear you! Although we do careful user research studies/sensemaking, it’s a fine line between being useful and being disruptive. We’re excited about improvements to stability and being in the user's flow in version 17.5 of VS (more refinement to come in version 17.6 - available for Public Preview here).
  
  Thanks for your patience while we pioneer new ways of using an IDE… and feel free to tweet me @aaronyim or email us at aayim at microsoft dot com with more detail/examples… love hearing about where we can do better.
  
  Appreciate...
  Read more
  Hey Stevie, thanks for taking the time to leave a comment.
  
  I hear you! Although we do careful user research studies/sensemaking, it’s a fine line between being useful and being disruptive. We’re excited about improvements to stability and being in the user’s flow in version 17.5 of VS (more refinement to come in version 17.6 – available for Public Preview here).
  
  Thanks for your patience while we pioneer new ways of using an IDE… and feel free to tweet me @aaronyim or email us at aayim at microsoft dot com with more detail/examples… love hearing about where we can do better.
  
  Appreciate you.
  
  Read less