Copilot works great in VS Code but does almost nothing in VS 2022

[Kugelhaufen]

When I edit files (C#) in VS Code, Copilot is very responsive and makes lots of good suggestions.
However, when I open the same files in VS 2022, Copilot does almost nothing except maybe add a semicolon or brackets here and there.

Even when I try very simple things like writing a comment that says "//A method that adds two numbers" Copliot doesn't give any suggestions most of the time.

Sometimes it works, but that's rare

(No errors are shown in the console or anywhere else)

[kzu]

Please make sure you're at least on version 1.40.0.1. You can see your current version in Help | About.

[Kugelhaufen]

I'm on version 1.40.0.2

[jamesgurung]

Same issue here on 1.40.0.2 with VS2022. The "Trigger inline Suggestion" and "Open GitHub Copilot" options are greyed out after signing in and it doesn't work at all.

[anthonyy41]

same problem (version is 1.40.0.2 )

[Kugelhaufen]

Quick update:
For the last two days, Copilot worked way better in VS 2022. I didn't change anything tho. Still on version 1.40.0.2. (Same C# Project as well).
Copilot in VS Code is still a bit more responsive but not by much.

[jamesgurung]

Still not working in VS for me.

[Bortronx]

same here @jamesgurung

[EvaisaDev]

For me it is even worse, every 5 minutes I get a popup that says
"thank you for using github copilot, your extended access ends in one day"
I tried signing out and signing back in and it keeps happening.

[gabrielDenilson]

I have the same problem, I made several configurations and even installed ReSharper (On the GitHub website it is said that GitHubCopilot works better with this tool) but I have not achieved any efficiency. Any suggestion is appreciated.

Edit: Version 1.42.0.0

[jamesgurung]

I raised a GitHub support ticket and have been advised that they're aware of this Copilot issue in VS 2022 17.4 Preview 1. For now, the workaround is to install the non-preview 17.3.2 release of Visual Studio.

[annieorben]

I am using visual studio 2022 17.32 community with GitHub Copilot 1.42.0.0 installed. I have the same issue of little to no suggestions and have been waiting for the Copilot busy animation to stop for over 10 minutes now. I've also tried to use the same examples shown in the documentation and did not receive suggestions.

[Kugelhaufen]

I'm also using version 17.3.2 community

[Bortronx]

Same here

[MulleDK19]

Yes, it's extremely broken in VS 2022, to the point it's unusable. I'm working on a post about this.

[Bortronx]

Provide link to the post thank you

[MulleDK19]

Provide link to the post thank you

https://github.com/orgs/community/discussions/31404

[drizztdourden08]

@MulleDK19 if you wish to participate, Please scroll down this post and record the test I posted and add the video here so we can gather data.

[Matt-17]

I was using Copilot in VS 2022 (17.3.x) and thought every person is overreacting the usefulness. Last days I tried in VS Code and am blasted. How is it possible to differ so much? First it seems stable and fast in VSCode while it's buggy and slow in VS2022. Even the suggestions (if there are any) are worse in VS2022.

[Kugelhaufen]

Exactly

[MulleDK19]

https://github.com/orgs/community/discussions/31404

[drizztdourden08]

@Matt-17 if you wish to participate, Please scroll down this post and record the test I posted and add the video here so we can gather data.

[doanamo]

Still a problem. VS Code works completly different (as in working at all) while VS IDE is unusable.

[Eptagone]

Same problem. And even sometimes Copilot stops working in VS IDE. With VS Code, it works much better.

[chenhw]

Is anyone working on these issues? After all this time, it's still the same problem

[chenhw]

This product had a lot of problems in the preview stage, and more than a year later, it still does. This extension performs very well in other ides, but poorly in VS

[JoeTomkinson]

I've just popped a reply to my comment above, have a look and see if that is a workable solution for your use case. It's done the trick for me, for the time being.

[drizztdourden08]

A workaround isn’t and never was the goal. We are paying customer for a product that doesn’t work as advertised.

even if it can give suggestions, they absolutely suck in comparison to what i get in VsCode regularly. And most of the time, I just don’t produce anything. If it won’t do it on it’s own, then the tool is useless, shortcut or not.

the minimum is not to support your product but ensure it actually works to begin with.

[JoeTomkinson]

Just trying to help. I don't disagree with your sentiment however.

[drizztdourden08]

Sorry. Didn’t mean too. It’s been so long and no one is really trying to fix it. That’s definitely all on Microsoft, not you.

[NickMaczk]

I'm not sure if that's the right place to talk about this, but I have no idea if I'm still a copilot user. When I first tried copilot with VS, well, it barely ever worked, and since then, it never did anything more than suggest bad code, I never really used it for more than some auto completion that I have to correct myself 99% of the time. I got the point of thinking that it's the free version of copilot that only ends your lines and throws bad code all over the place. Is copilot supposed to work still even if the plan is canceled, or am I still paying for this, I can't tell?

[ayim]

If you've cancelled Copilot, you're using IntelliCode's whole-line autocomplete that runs locally on your machine.
You'll not see more than a line of code from IntelliCode ever, whereas Copilot adds the comment based and multi-line functionality

[chenhw]

What puzzles me most is why this tool can be used normally in vscode and jb series ides, such as dg,idea,rider, the same solution, when opened in VS, almost no hint, but when opened in rider, the vast majority of cases can provide effective code hints

[NickMaczk]

I'm using GPT4, I believe it's the true copilot, you can discuss strategies and throw ideas at each other, it can spit out full classes after a good talk, I don't understand why GHCP doesn't use the same principles.

[chenhw]

understand these questions? Is anyone fixing these issues? Or are there any plans to fix these issues? After all, developers are paying for a tool that doesn't work every day

[chenhw]

Can anyone at Microsoft tell me if any of you are following or dealing with these issues? I gave up vs and went to use rider. Your copilot plugin performs much better on third-party ides than on your own vs. When I ask a question to copilot chat, the answer given by vs's copilot chat is useless, while vscode gives the correct solution. What are your vs version copilot guys doing? Did you see everyone's feedback? Or are you going to let it go?

[MulleDK19]

It's a fucking mystery. I first reported serious issues with the VS version like 2 years ago, and nothing has changed. It's still useless. It doesn't work; when it works, it suggests garbage. Switch to VS Code, and it works without issue.

It's absolutely ridiculous that it's been years, and the basics still aren't working..

[chenhw]

It seems that their team is not going to give any response and feedback, let alone solve it, so that's it

[chenhw]

Disappointing issue

[chenhw]

Now I am using Rider as the main development tool. Copilot performs quite well in Rider. This is a strange phenomenon. Is it intentional by Microsoft to promote Rider?

[chenhw]

It's been a year, it's been a whole year

[chenhw]

I understand, github copilot has two versions, the vs version and other versions. When I asked a question in coplit chat in vs, he told me 'Sorry, I only answer development related questions.’, but when I asked the same question in vscode, he gave me a complete answer. Do you dare to imagine that copilot performs a hundred times better in any other development tool than in vs2022? This is so unbelievable. What are product managers and developers doing?

[fubaduba]

Hey @chenhw! We have had some team re-shuffling that happened and have some new faces on the product team. So, Hi!👋🏽 I would love to dig into your issues here, and I appreciate your continued voicing of concerns. Its absolutely unacceptable for us to have an inferior experience with Copilot in VS and are committed to unblocking you and others.

I want to dig in a bit deeper on when you experience Copilot most likely to give you 'Sorry, I only answer development related questions.’

• How do you iterate when that happen?
• Have you used the newly available /commands and additional way to refer to context with #? This should greatly reduce that from happening

It seems that you've had a bunch of issues since last year. I want to reset and categorize if you're seeing the same issues with-

• Copilot Completions in VS 2022
• Copilot Chat in VS 2022

I'm nothing that this thread: https://github.com/orgs/community/discussions/29843#discussioncomment-7277987 and the experience limitations you mentioned here are still unresolved. I will take a look at the error logging and output issues you mentioned, but I wanted to ask you specifically- "Configuring copilot for VS is, honestly, horrible. There are clearly things that the user expect to work and options that needs to be set for this to properly work and the information is scattered everywhere and or unclear."
We're making a push towards making the two Copilot experiences work well together, especially when it comes to setting up, proof of life and knowing what something has fired or not.

I would love to get on a call with you to resolve this issue and just generally understand your experience frustrations compared to VS Code, Rider etc. What is the best way to sync up? I can setup a call whenever you're available.

Thank you, hoping to start anew here! 

[Matt-17]

Right now Copilot feels really weird. Sometimes it works good but and then it's giving really dumb suggestions, where not even variables or parameters exist in this method. There seems to be something like a caching problem I think. As soon it provides such a mess, it makes no sense to try getting better results (at least by getting code through comments). Sometimes when I write my own code, Copilot figures out what I want and returns back to good answers. I could never replicate this behaviour in VS Code.
Please, finally fix it. Also use Copilot. It's already more than a year in production and very little changed. It's not stopping at all anymore, this is great though... or better a minimal request for a paid product.

[ghost]

I just decided to try the GHCP trial because it was free and promptly cancelled. It actually slowed me down and is in no way useful or intuitive to use.

Using vs2022/c#/.net 8

You'd think Microsoft would support their own product better on their flagship IDE...

I just want it to help work through a slog of fixing code errors in a ui refactor I am doing. Basically renaming abcCheckbox123 to xyzCheckbox123. It seems utterly incapable though, in many areas intellisense is more helpful.

[chenhw]

Any progress? Is anyone following up? As a paid commercial product, simply unacceptable

[drizztdourden08]

if you go further down this thread, the only way I was able to get anyone to even look at this is to open a ticket with them, and then basically force them to read it and do something about, refusing any kind of half assed answer. it worked and they did make a fix at the times, which wasn't very good to start with and rapidly went south and not working again.

So yeah, spamming here won't do anything. Open a ticket. that's what I did but I'm tired to fight with them.

[Matt-17]

Good idea. Whenever you open a ticket, provide a link, so we can upvote at least.

[ayim]

Hey - I work on this product.

@Matt-17 @chenhw @drizztdourden08 hardest part is getting a good repro (sometimes it's even where your cursor goes before and after you try to get a prompt). Screen recordings, a sample file, or even a live demo along with the output file is the most effective way - ayim@github.com

[drizztdourden08]

@ayim this is probably the most frustrating issue I’ve participated in for any product. This is the kind of answer we always get no matter how much effort we put into helping you guys.

all we ask is that it’s the same level of performance as any other editor. Right now, it’s at the stupid level. Read the thread in its entirety, not just the last posts. We have literally provided dozens of examples, step by steps. Proof right here on this thread. Full video: https://github.com/orgs/community/discussions/29843#discussioncomment-5495371

last support guy, I asked him that he gives us a video of the same thing in HIS visual studio to prove that it can work. I have never seen a VS that has a performing copilot so far. We received nothing but an update that wasn’t really doing anything different.

[ayim]

Saw your message there, my repro looks a bit different but we'll look into it.

Since April, we've released two major updates:

1. Behaviour for pinging Copilot for a prediction now occurs on every keystroke (used to be different from other editors)
2. Since releasing IntelliSense driven completions for C# and C++, we've seen accept rates increase in a significant way.

The remaining problems we're chasing down are quite a bit more difficult in nature to resolve.
Have a couple hypotheses but need more customer examples to validate - still going to need the recordings/sample file/live demo

[Matt-17]

Right now, Copilot got really worse in VS. For example I'm trying to add documentation for both of those methods:

public A LoadA() 
{
   ...
}
public B LoadB() 
{
   ....
}

It worked for LoadA "Loading A from service.". Then I tried on LoadB and it just hallucinated "Loading A from service asynchronously.".

Stuff like this happen so often right now. And even Triggering again or open copilot window does not help anything. I couldn't reproduce this issue once in VS Code.

[ayim]

Got a sample file or View > Output > Copilot logs that I can look at?
Would love to try to repro - even cursor location and other files open can influence the response we get back from Copilot so the more info we can get, the better.

Feel free to email me at anytime with the Copilot logs & some file context for repro if we've run into a buggy state.... ayim@github.com. Hope to hear from ya

[fubaduba]

Were you able to talk to @ayim at all @Matt-17?

[redaezziani]

i can help you

[ayim]

@redaezziani we're deeply interested in improving the product.

The hardest part is getting a good repro (sometimes it's even where your cursor goes before and after you try to get a prompt).
Two ways we can do this...

1. Screen recordings, a sample file, or even a live demo along with the output file.
2. Let's get in touch and do a code along session with you where we can observe/have ya point out issues. I'm generally happy to be interrupted my workday if you've entered an error/buggy state in the product.

Email: ayim@github.com / aayim@microsoft.com. Hope to hear from you.

[Matt-17]

After I used version 129 for several week now and since yesterday 133, I must admit it's working much better. Copilot still has some issues with not producing anything or gives totally wrong output but usually start typing what I want seems to work pretty good now. At least the quality is much better than one month ago in my opinion - or at least my current projects.

[fubaduba]

Hey @Matt-17! Our team is just jumping on this thread and catching up on the feedback.
I'm happy to know the quality of answers seems to be improving for you.

I want to dig in a bit deeper on when you experience Copilot most likely to give you nothing at all or completely wrong answers.

• How do you iterate when that happen?
• Have you used the newly available /commands and additional way to refer to context with #?

[stgaup]

It's still not working in VS2022... In the demos they are be able to type a comment and then CoPilot will suggest something when they hit enter, but this very rarely happens. In VS Code it works a lot better. Been a long time, and it's still not fixed. I am able to pop up the helper inside the code, but it does not look at where my cursor is (right the next line after my comment), so I have to type a lot of text to explain that it should do what the comment says... is this how it's supposed to work?

[stgaup]

I installed the latest update for VS2022 and now it seems to be working better.

[ghost]

I installed the latest update for VS2022 and now it seems to be working better.

That's my experience as well.

[ayim]

You can also use the Alt + , shortcut to try triggering a grey text suggestion if one didn't appear

--
Aaron Yim
Product Manager for GitHub Copilot in Visual Studio

[Matt-17]

I'm using VS 17.10.1 now and Alt+. is declared as Edit.NextSuggestion but it does not even adds a new line to Github Copilot output. Alt+# works so far, it's opening a chat window but loading progress bar does not stop and no answer is ever shown. At least it sends something to Copilot.

[ayim]

That's correct, although the Alt + , shortcut is declared as Edit.NextSuggestion, it explicitly requests a prediction from Copilot if there isn't already one. We're really just trying to cut down on the # of shortcuts that you need to remember/use.

In some scenarios, Copilot just doesn't have anything to suggest, you can validate this using the View > Output window to see if any prediction was returned.