Search existing Visual Studio feedback
VS 17.9 changed the “style” of the collapse/expand for outlining regions. It now uses a very ugly and not very intuitive “v” instead of the previous “+” in a box. The former was not only visually better it was more informative. Worse, we have no option to restore the original form.
[severity:It’s more difficult to complete my work]
I asked this question to copilot in VS2022: what is difference between TestInitialize and classinitialize. And the response is, “The response is redacted to meet Responsible AI policies. If this was unexpected, please give feedback.”.
I don’t know why this violates Responsive AI policy. I would like to suggest to provide more details about why it is blocked by Responsive AI policy, maybe a URI may provide the details.
[regression] [worked-in:Visual Studio 2022 17.13.0 preview 3.0]
20250123-0216-47.2514693.mp4
[severity:I’m unable to use this version]
I am unable to connect to my Apple ID account from Visual Studio 2022. The login credentials are correct. When I try logging in from my MacBook (Xcode), everything works fine, but logging in from VS 2022 fails. I receive the error message: “Authentication service is unavailable.” I tried uninstalling and reinstalling VS, but that did not resolve the issue. I also found the following error in the log:
Xamarin.Messaging.Client.MessagingClient Error: 0 : An error occurred on client privateb4f986e140 while executing a reply for topic xvs/idb/add-developer-account
Xamarin.Messaging.IDB.Contracts.AppleProvisioningException: Authentication service is unavailable.
at Xamarin.Messaging.IDB.AppleProvisioningManager.<GetUpdatedAccountAsync>d__13.MoveNext() in D:\a_work\1\s\src\Messaging\Xamarin.Messaging.IDB.Local\AppleProvisioningManager.cs:line 129
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Xamarin.Messaging.IDB.Local.AddDeveloperAccountHandler.<ExecuteAsync>d__4.MoveNext() in D:\a_work\1\s\src\Messaging\Xamarin.Messaging.IDB.Local\Handlers\AddDeveloperAccountHandler.cs:line 27
Describe your issue here
===DO NOT EDIT BELOW THIS LINE===
PackageId:GitV2; PackageAction:Install; PackageVersion:2.45.2.1; ReturnCode:1;
[regression] [worked-in:Version 17.12.0 Preview 3.0]
Since version 17.12.0 Preview 4.0, private Unity messages (Awake, Start, etc.) are incorrectly marked as unused IDE0051.
Copy and Paste Files or Folders Failed : (Visual Studio Enterprise 2022 (64-bit) - Preview) (Version 17.11.0 Preview 5.0)
Environment:
- Microsoft Visual Studio Enterprise 2022 (64-bit) - Preview
- Version 17.11.0 Preview 5.0
Issue Description:
Copying and pasting files or folders is not working, specifically the paste function is not working.
Similar issues have been reported by other users, and I have tried all suggested methods without success.
A Visual Studio ran into an unexpected problem, and may affect some project system functions. Open log file
- I encountered a failure when moving a file. The specific steps are as follows:
For example, when I tried to move the file FrameworkUser.cs from project A to project B, an exception occurred.
-
project A to project B within the same solution
-
I will upload this failure log. I suspect this problem caused the copy, paste, move and other operations.
Similar Issues:
I have found similar issues reported by other users. I have tried various methods, but the issue persists.
Many developers just hit F5 or the main “Play” icon to start their apps, thus always starting with debugging. There is a significant startup cost to running the debugger for many app types, especially web projects, and many developers think this is “just how it is” and don’t realize that Start Without Debugging exists. The addition of the hollow play icon to the main UI buttons no doubt helps this, but the language used in the menus is still not ideal. Folks think they need to Start the app so they go to the first Start they find.
I propose changing the menu from Start Debugging to Debug.
I propose changing the menu from Start Without Debugging to Run (or Start but Run is better).
This is shorter, simpler, and clearer. It should help more developers discover the “right” thing and will dramatically improve app start times for loads of developers without you having to make any performance improvements in Visual Studio or dotnet.
I have a few references with real customer data you may wish to check out:
https://twitter.com/ardalis/status/1780291326099050908
Poll - Should we make the change described here:
https://twitter.com/ardalis/status/1780290422213915131
VisualStudio ask me to re-login to Githaub. After that VisualStudio service locate at https://localhost:58183/ was crushed after login to github. TCPView show that port 58183 was closed and process stoped. Do you have some ideas?
Hello,
Since updating to Visual Studio 2022 version 17.12, IntelliSense has been reporting errors throughout my C++ files. Rolling back to version 17.11.5 resolves the issue, and everything works as expected. I have also tried modifying my header files to address the issues reported by IntelliSense, but this did not help.
Does anyone have any ideas on why this issue is occurring with version 17.12 and how I can fix IntelliSense to work as it did before?
Thanks,
Guillaume Lauriol
[severity:I’m unable to use this version]
trying to execute this command on VS command prompt but getting this error:
Tools.NewDataComparison /SrcServerName . /SrcDatabaseName DBNAME/SrcDisplayName V1 /TargetServerName . /TargetDatabaseName DBName2 /TargetDisplayName V2
A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.)
A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.)
The certificate chain was issued by an authority that is not trusted
[severity:I’m unable to use this version] [regression] [worked-in:17.10.0 preview 2.0]
Create MFC user dll and set CLR option, linker will report:
error LNK2001: unresolved external symbol "public: __cdecl PostDllMain::PostDllMain(void)" (?? 0PostDllMain@@$$FQEAA@XZ)
error LNK2001: unresolved external symbol "public: __cdecl PostRawDllMain::PostRawDllMain(void)" `(?? 0PostRawDllMain@@$$FQEAA@XZ)`
With no CLR set dll builds.
[regression] [worked-in:17.10.0 Preview 2.0]
In a .NET 8 Blazor application using VS 17.10.0 Preview 3.0, I’m seeing TS1109 (TS) Expression expected errors in Razor files. I do not have any TypeScript files in my project.
I did not see these errors using 17.10 Preview 1.0 or 2.0.
This seems to be a recurring issue in Blazor/Razor:
- https://developercommunity.visualstudio.com/t/Blazor-server-razor-TS1109-errors/10346821?ref=native&refTime=1712755642333&refUserId=aa8031b5-7fbb-6676-945f-31ef50738611
- https://developercommunity.visualstudio.com/t/NET-MAUI-Blazor-Hybrid-project-randoml/10522090
- https://developercommunity.visualstudio.com/t/razor-code-assigned-to-javascript-variable-still-g/6492
Describe your issue here
===DO NOT EDIT BELOW THIS LINE===
PackageId:AndroidPlatformMAUI2; PackageAction:Install; PackageVersion:1.0.6; ReturnCode:10;
[severity:I’m unable to use this version]
We have 2 Apple Silicon Mac Mini machines set up with dotnet and visual studio. We use these machines to pair to mac from VS on windows. Today randomly when we try to pair to mac we get this error.
I tried updating xcode, restarting the machines, and nothing fixed the issues. All developers are experiencing the same issue in our team.
[severity:Other] [regression] [worked-in:N/A]
I am trying to use the new Multiple Startup Projects feature where you can have multiple launch profiles, but I am unable to reliably have any of them save other than the launch profile existing. Not sure if it’s related, but one of the projects is 32 bit for driver compatibility reasons, and doesn’t offer any “Debug Target” options, and if I select it and try to move it with the up/down arrows, it causes VS to freeze and then crash completely a few seconds later.
Steps to reproduce not saving issue:
- Open Configure Startup Projects window for project with a combination of 32 and 64 bit ASP.NET projects (.NET8)
- Select “Multiple Startup Projects”
- Click on create new profile button and give it a name
- Create profile launching 64 bit project with debugging and a kestrel debug target
- Click Apply then OK
- Re-open the window, and create another profile and give it a name
- Select “Start” for the action and the same debug target for same project as in the previous profile, and then select any action and debug target for any other project (32 bit or 64 bit)
- Click “Apply” and then “OK”
- Re-open the window, the second profile will not have retained the second (or any subsequent) startup project configurations
Steps to reproduce 32 bit project crash issue:
- Open Configure Startup Projects window for project with a combination of 32 and 64 bit ASP.NET projects (.NET8)
- Select “Multiple Startup Projects”
- Click on create new profile button and give it a name
- Create profile launching 32 bit project with debugging (no debug target was available for me on this project, despite having 4 configured)
- Select the name of the DB2 project to enable the up/down arrows
- Click on either the up or down arrow to change order
- VS will freeze immediately, and then crash
Adding syntax coloring to the Immediate Window would improve readability and make debugging more efficient by aligning its appearance with the main editor.
This request is filed to document a feature suggestion raised by a user in a Twitter thread.
[severity:I’m unable to use this version] [regression] [worked-in:17.11]
Microsoft Visual Studio Enterprise 2022
Version 17.12.0
Create a new project.
C++
CLR Class Library (.NET)
Write the following code.
// ClassLibrary1.h
public ref class Class Class1
{
void Test()
{
System::String::Format( "{0}{1}{2}", 1, 2, 3 );
System::String::Format( "{0}{1}{2}{3}", 1, 2, 3, 4 );
}
};
Build results in an error.
fatal error C1001 INTERNAL COMPILER ERROR
[severity:I’m unable to use this version]
Good morning (at least it is morning here on the east coast of australia).
Attempting to connect to a mac to build a .net maui project for iOS, it reported object not found. Examining the logs, revealed:
Xamarin.VisualStudio.Services.ProductsService Error: 0 : The Products Service response was not successfull. Service URL: https://software.xamarin.com/service/products
With the subsequent downstream errors and eventual failure.
This has previously been reported and apparently resolved in May 2024.
https://developercommunity.visualstudio.com/t/VS-Pair-to-mac-gives-Object-reference-no/10670625
As there does not appear to be an ability to log this issue anywhere else, or to indicate the issue previously reported has reoccurred, I am logging this issue here.
Can somebody please reestablish the software.xamarin.com service.
I hope you all have a wonderful day.
Kind regards,
Paul
[severity:I’m unable to use this version] [regression] [worked-in:17.8.7]
After upgrading to Visual Studio 2022 17.9.0 database projects that reference system databases fail to build with the following error:
Error: SQL72025: No file was supplied for reference master.dacpac; deployment might fail. When package was created, the original referenced file was located MASTER.DACPAC.
See the sample project SQL72025.ZIP.
It would be nice to have the ability to add markdown files to solutions/projects instead of creating a different file and renaming the type. It would be helpful.
Microsoft, using an adjunct specialized team in coordination with the Visual Studio team should create a universal UI builder that is equal to, or superior to, the functionality in the WinForms designer in order to reduce initial development time, support time, and lowering total SDLC costs and driving more use of Azure to increase revenue and stave off decreasing revenue from Visual Studio and consequently Azure.
Business case:
Microsoft’s revenue depends largely on Azure, which means Azure developers (as .NET developers) are the key to creating Azure apps, as well as desktop apps (still used broadly as internal apps in organizations).
In order to have .NET developers producing apps on a scale large enough to maintain and increase Azure usage, their employers must choose to use the .NET family of products.
The key to Visual Basic’s and Visual Studio’s initial success at dominating the developer market for Windows users was the forms designer that allow rapid application development (RAD). The UI designer worked, generated good code with rarely ever a bug, reducing the time to create a UI, and virtually eliminating bugs from trying to manually code a UI. Microsoft’s customers using Visual Basic/Visual Studio saw reduction in time to get an app to QA, and a reduction in how many UI bugs QA would find, allowing better testing on business logic and data access. Microsoft’s business grew, fueling the growth in SQL Server and Windows. Microsoft understood the necessity to generating revenue of having a highly performant and functional “Visual” in “Visual Basic/Studio”.
Today, aside from WinForms, still used a lot internally, but supplanted by mobile apps and web apps externally, Microsoft has arrived at a place where there is no “Visual” in “Visual Studio”. The “Visual” has always related to the visual UI designer for building front ends. But there is no productive equivalent to the WinForms UI designer for MAUI (XAML), Blazor (HTTP/CSS), WinUI (XAML), nor WPF (XAML). And all three XAML-based UI formats use different, incompatible, XAML formats and values. Microsoft no longer just concerns itself with Windows, but with developing software for numerous operating systems, platforms, and devices.
Hand-coding MAUI, Blazor, WinUI, and WPF (the WPF designer is a bit buggy) takes much longer and is given to being buggy until it finished. Then, when it is time to extend or update, more hand-coding time and bug-fixing time. That costs the employer time, delays release dates, and increases support costs to fix and extend.
By using a small, dedicated team (similar in process and capabilities that Alan Cooper and his team were when they created the UI designer paradigm, and developed in a short time, used from the days of VB through today in WinForms), Microsoft puts the “Visual” back in “Visual Studio”, and can hype that capability in marketing to open more revenue doors for Microsoft.
Artificial Intelligence (AI, e.g. CoPilot, etc.) cannot handle the complexity that goes through a UI developer’s mind, looking ahead to both the user experience, as well as the necessary code (to meet requirements) for validation logic, business logic, and data logic. Nor will it be able to at a reliable, marketable, level anytime in the foreseeable future.
Hiring the right person to lead and manage the project, who in turn chooses the team members, can create and execute a Microsoft UI Designer “Skunkworks” team that can deliver a lot, with excellent quality, in a short time.
The downside to continuing down the same path is where customers are beginning to abandon .NET, over a transition time, for other tools that are not Azure, and not Visual Studio, where development and delivery is improved. Microsoft Visual Studio competitors are starting to pick up on the market for UI designers, which would help with the exodus. And with the exodus from .NET and Visual Studio comes an exodus from Azure.
Technical case: (see attached image)
They key to creating the proposed UI designer is to keep it to one level of abstraction, where one code base can manage the code generation and the designer UI for whichever UI format is chosen for a project (WinForms, MAUI, Blazor, WinUI, WPF). The code generated would not contain anything special related to the UI designer, no special tags or keys. Just the code understood by the UI format, the same as it does handwritten code.
UI controls are a defined set, regardless of language or format. Not all possible UI controls exist in all formats. By having a single list of all UI control types, cross-referenced to which ones exist in each UI format, with each generic UI type/UI format combination having a unique set of properties, methods, and events, the UI designer code then generates the code-behind unique to that combination, with a default set of values and settable by the developer or by code. That comes down to only one level of abstraction.
The team would consist of one project leader who is also a software engineer on the UI designer. The leader is the single direct contact from the business side and the Visual Studio team. The leader, with input from the team, designs and architects the UI designer. The leader and the team will work hand-in-hand daily to make progress.
The team would consist of software engineers, picked by the lead, subject to Microsoft employee requirements, for one each:
- WPF and WinUI expertise
- Blazor/HTTP/CSS expertise
- WinForms expertise
- MAUI expertise
- QA, Azure DevOps, and general .NET/C# development
The process would take:
- Lead hired, from first day to initial mid-level design - 3 months
- Team selection, hiring, provisioning, and internal training - 2 to 3 months
- Product from first team day to delivered to QA for testing - 12 to 18 months
- Product from end of QA testing to delivery to Visual Studio team - 1 month
There would be monthly deliverables, and where possible beta versions released as Visual Studio extensions to engage the existing Visual Studio customer base and benefit from feedback.
Conclusion
It is unthinkable that in the 21st century, after Microsoft having proven the value of a UI designer in gaining marketshare and generating profits, that there would be no “Visual” in “Visual Studio”. The technical challenge is not as great as some might assert, particularly if they are used to command line usage and hand-coding applications. The damage to Microsoft by not starting now to return to being the king of rapid application development could ripple beyond just the Visual Studio team.
[severity:It’s more difficult to complete my work] [regression] [worked-in:17.12.0 Preview 1 or maybe earlier]
Just hit CTRL-T to open up code search.
Searched for one term “CohereHelpers”, and hit enter to find that class.
I re-opened code search, and I started typing “AnthropicHelpers”, and it hung after three chars (“Ant”).
This is typical of the problem - it always hangs after 3 or 4 chars.
When it hangs, and I check task manager, it’s consuming a decent amount of CPU while unresponsive. 10% of my 22 vCPU on my laptop.
BTW, when I recorded that test, I had two other instances of VS running, but I just reproduced it again with only the first instance running. Only took typing one character to hang it this time.
[severity:It’s more difficult to complete my work]
In Visual Studio when you debug an access violation in a C++ project, you can normally see the call stack correctly:
For example:
Asan1.exe!f() Line 6
Asan1.exe!main() Line 11
Asan1.exe!invoke_main() Line 79
Asan1.exe!__scrt_common_main_seh() Line 288
Asan1.exe!__scrt_common_main() Line 331
Asan1.exe!mainCRTStartup(void * __formal=0x00000004bbfff000) Line 17
kernel32.dll!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()
As soon as you activate ASan (Address Sanitizer) in the same project, during debugging, the call stack does not show much useful info to find the correct source location:
KernelBase.dll!00007ffd59cf837a()
clang_rt.asan_dynamic-x86_64.dll!ShadowExceptionHandler(_EXCEPTION_POINTERS * exception_pointers=0x000000028975f1e0) Line 336
00000141493e001e()
This makes working with ASan very difficult as you may not always be able to run the same scenario again in a non ASan build.
Please fix it that we can see the same correct source location of the access violation in Visual Studio.
Additional notes: Symbols were loaded for the call stacks. Visual Studio versions tested: 17.12.3 & 17.13.0 Preview 2.0
I also added a sample Project with an intentional Access violation for testing purpose. With for example Debug x64 configuration you see the full call stack. With DebugASan x64 configuration you see the incomplete call stack.
Every time I share the paste special -> ‘Paste JSON As Classes’ feature, devs really love it and many are discovering it for the first time. It meets a lot of needs but many devs desire the ability to control the output a little more like we can do using online JSON to C# convertors such as https://json2csharp.com/ to increase the utility of this feature in VS.
The items in particular that get mentioned as lot are the ability to set the casing, the Json property name and whether to use records instead of classes. Please consider adding these.
Screenshot of the settings available on json2csharp.com ⬇️
[severity:It bothers me. A fix would be nice] [regression] [worked-in:17.12.0 Preview 3.0]
I have the following Rule for C#:
This got broken in Version 17.12.0 Preview 3.0
or so.
The init.ps1 included in the NuGet package is a script that automatically executes arbitrary processes during package installation. Although the NuGet team deprecated the use of init.ps1 in 2017, it still executes in Visual Studio as of 2025. There are limited ways to stop the execution of init.ps1, especially as there is no setting within Visual Studio to do so. Attacks using init.ps1 have occurred in the past, posing significant security risks.
Given the current situation, I believe that explicit user opt-in should be required rather than implicit execution in Visual Studio.
Proposal:
- Add a setting in Visual Studio options:
Add a “NuGet Package Manager” section to the Visual Studio options menu, with a checkbox to disable the automatic execution of the init.ps1 script.
This setting will allow users to prevent the init.ps1 script from running during package installation.
- Display a warning message:
When attempting to install a package containing an init.ps1 script, display a warning message.
Explain the script’s contents and risks to the user, and provide an option to choose whether or not to execute it.
from last week none of my accounts would associate app with store. Personal (dev account associated with company partner portal, global manager). company account(dev account), and company owner (partner program owner) account. For years i have been using my personal account to build and upload games for our company. IF that for some reason from time to time would not associate app with store then owner account would always do so. Now personal account says “your developer account is inactive” though i can still log onto partner center and manage everything there and shows i have dev account. Company account says “The store blocked this account”… but can use it on partner center as usual. Company owner account just says “An unexpected network error has occurred”. Have tried on two separate computers Windows 10 and 11, both VS2019 and 2022. Have updated everything, uninstalled everything, reinstalled everything, logged in and out a 100 times.
We would like to request the ability to set the “Use custom path to clang-format.exe” option individually for each solution in Visual Studio, instead of only being able to set it globally.
We are very happy that there is built-in clang-format in Visual Studio these days, and we are in the process of deploying it on multiple projects, but this feature would ensure we can have a much more solid deployment.
Current Situation: At the moment, we deploy this configuration to all users in production using a script that reads the CurrentSettings.vssettings, checks if it contains the correct values, and then applies the required settings using the Tools.ImportandExportSettings command. However, this approach has a significant limitation: it enforces a single global path to clang-format.exe across all projects.
Problem Statement: In our organization, many developers work on multiple projects, each of which may have different formatting requirements and might need to use different versions or paths for clang-format.exe. As a result, the global configuration does not meet our needs and requires manual intervention, which is both inefficient and prone to errors.
Furthermore, changing these Visual Studio settings for the entire production environment is cumbersome and requires checking for active Visual Studio instances on developers machines to avoid conflicts. This complexity increases the risk of errors and makes managing different configurations across projects difficult.
Proposed Solution: We propose adding the ability to override the global clang-format.exe path setting on a per-solution basis. The implementation could allow a setting within the solution that, when defined, takes precedence over the global Visual Studio setting. This would provide much-needed flexibility while still maintaining the global configuration as a fallback.
Business Impact: As a large company with a significant number of developers working on diverse projects, this feature would streamline our development process and improve the working conditions of thousands of developers. It would help reduce the need for custom scripting and manual adjustments, allowing teams to focus on development instead of environment setup.
We believe that implementing this feature would not only benefit our organization but also provide value to many other development teams working with multiple projects in Visual Studio.
Thank you for considering this request.
[severity:I’m unable to use this version] [regression]
Once again, after upgrading to the latest version of Visual Studio 2022 (v17.9.3), a system that was fairly consistently succeeding to pair to a Mac for iOS development suddenly stopped being able to pair to the Mac it was previously connecting to. Xamarin IDE log attached. Tagging Mauro Agnoletti [MSFT] and Bret Johnson [MSFT] in this post as they previously worked on this issue with me.
Deleting the ~/Library/Caches/Xamarin/XMA/SDKs/dotnet/
folder on the mac does NOT solve the issue, like it did with previous issues. I am now completely stuck with no way to move forward.
During the paring process, error messages are displayed in a larger format than displayed in previous versions of VS, but in a way that obscures the rest of the Pair to Mac window if the error message is too large. You need to resize the window to even know it’s the Pair to Mac window. Here is the error message that I experienced during the several attempts I made to pair:
[severity:Multiple people on my team are impacted (internal MSFT only)] [regression] [worked-in:17.11.5]
The upgrade made several code rules that used to be informational required, blocking me from development.
For example, ide0090 is now blocking my build and it wasn’t before.
I didn’t see any mention of code rules being promoted in the release notes, so I’m not sure why the upgrade caused this issue.
[severity:I’m unable to use this version] [regression] [worked-in:17.10.0]
Hi all,
After upgrading today to version 17.10.2, I can no longer authenticate to an extension (XRMToolkit) using Visual Studio anymore.
I get the following error message:
It did still work with version 17.10.0 which I have upgraded from today. I just did a rollback to version 17.10.0 and it is working now again.
I don’t know if this is a problem of Visual Studio or XRMToolkit, but as this was a minor version update, it should have probably not broken this extension.
Best regards,
Florian
[severity:I’m unable to use this version] [regression] [worked-in:17.1]
I’ve updated from VS 17.1 to VS 17.10, and all my projects can not build right now. It shows following error in the Microsoft.CSharp.Core.targets
file
Unhandled Exception: System.MissingMethodException: Method not found: ‘System.Collections.Generic.IEnumerator
1<Microsoft.CodeAnalysis.NodeStateEntry
1<System.ValueTuple2<System.__Canon,System.__Canon>>> Microsoft.CodeAnalysis.NodeStateTable
1.GetEnumerator()’. axshare_mvc.Core, Axure.Atlassian.Connect, Axure.Cloud.Mailer.Templates, Axure.Mailer.Templates C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Current\Bin\Roslyn\Microsoft.CSharp.Core.targets
[severity:I’m unable to use this version] [regression] [worked-in:17.11]
Installed VS2022 professional latest version, now getting the following error when VS starts up and forces me to sign-in on first usage:
Only loopback redirect uri is supported, but urn:ietf:wg:oauth:2.0:oob was found. Configure http://localhost or http://localhost:port both during app registration and when you create the PublicClientApplication object. See https://aka.ms/msal-net-os-browser for details
After upgrading to Visual Studio 2022 version 17.12, while Copilot now allows switching between language models, only gpt-4o, o1, and o1-mini are available as options.
I have confirmed that the ‘Anthropic Claude 3.5 Sonnet in Copilot’ option is enabled in GitHub Copilot settings, and Claude 3.5 Sonnet works properly in VS Code.
However, the new version of VS 2022 still doesn’t show this option. I’m not sure if this should be considered a missing feature or a bug.
Here are the settings in GitHub Copilot:
Here are the model options in VS Code’s Copilot:
Here are the model options in VS 2022 17.12’s Copilot:
Visual Studio’s Git integration has features that depend on where the remote repository lives, like Pull-Request integration and Copy Permalink. These features only support GitHub and Azure DevOps.
This request is for VisualStudio.Extensibility to expose a way for extension authors to provide additional support to other hosting providers like GitLab and BitBucket, expanding the capabilities of these hosts without the need for new UI.
After updating the Visual Studio to version 17.9, I can’t open any .sql files.
It shows me these errors.
Report: Visual Studio 2013 .sln File Causes Windows Explorer to Crash
Issue Description
On Windows 11 Pro, saving and downloading Visual Studio 2013 format .sln
files causes Windows Explorer (explorer.exe) to crash. Specifically, after extracting a compressed package containing a .sln
file, simply clicking to open the folder containing this file causes the system’s File Explorer to freeze and crash.
Error Information
The following error logs were retrieved from the Event Viewer:
Faulting application name: explorer.exe, version: 10.0.22621.3733, time stamp: 0xc47c2769
Faulting module name: SHELL32.dll, version: 10.0.22621.3733, time stamp: 0x8ec472d1
Exception code: 0xc0000005
Fault offset: 0x0000000000032fb6
Faulting process id: 0x0x476C
Faulting application start time: 0x0x1DABDB675F13596
Faulting application path: C:\Windows\explorer.exe
Faulting module path: C:\Windows\System32\SHELL32.dll
Report Id: 758c3fdd-bec2-4af9-a496-c2313b70dda9
System Information
- Edition: Windows 11 Pro
- Version: 23H2
- Installed on: 4/26/2024
- OS build: 22631.3737
- Experience: Windows Feature Experience Pack 1000.22700.1009.0
- Visual Studio: Visual Studio 2022 Preview Release Version 17.11
Possible Causes
- File System or Hardware Issues:
- Disk or file system corruption might cause problems when accessing specific files.
- File Association Issues:
- The system’s default program or association settings for
.sln
files might have issues, causing File Explorer to crash when attempting to parse the file.
- System Preview Functionality Issues:
- Certain system configurations or preview handlers might have trouble parsing
.sln
files, leading to high resource consumption or crashes.
Thank you.
[severity:It bothers me. A fix would be nice]
Visual Studio 2022 Preview Version 17.12.0, Github Copilot with .razor pages duplicating characters when Copilot Completions is enabled. When I disable Copilot Completions I no longer have this issue. It seems to be only happening on the .razor forms.
[regression] [worked-in:17.9.6]
After installing a Visual Studio update (17.10.34916.146), when trying to start Visual Studio it gets into a restart loop with this message box:
The following extension is disabled because the installed version is not compatible with Visual Studio Enterprise 17.10.34916.146.
- GitHub Copilot Chat
To update this extension go to Tools, Extensions and Updates and look for available updates on the Updates tab.
Click OK to restart Visual Studio for the disable to take effect.
[OK]
After Visual Studio restarts, the same message is displayed over and over (presumably the extension is not actually getting disabled). The only way to stop the cycle was to manually kill the DEVENV.EXE process.
Rebooting the computer did not solve the problem.
I have rolled back to release 17.9.6.