Visual Studio - Faz Business | فاز الأعمال

Visual Studio Code 1.120

Posted on May 7, 2026 by faz_business

Last updated: May 7, 2026

Welcome to the 1.120 release of Visual Studio Code.

Happy Coding!

May 7, 2026

Group chat sessions by recency by default in the sessions Quick Pick. #314965
Add a context size picker to the model picker. #314814

May 6, 2026

Hide archived sessions by default in the chat sessions Quick Pick to reduce visual clutter. Searching in the Quick Pick still matches archived sessions, so you can revive one by title. #297421
Surface GitHub metadata, including a pull request button, in the agent host UI for sessions backed by a GitHub repository. #314811
Detect password and passphrase prompts in chat agent terminal commands and show a confirmation dialog that focuses the terminal so you can enter the secret directly. The prompt is announced to screen readers, and secrets are never routed through the model. #314796
Discover Copilot CLI user-installed plugins from ~/.copilot/installed-plugins/. #302152

May 5, 2026

Agent host terminals respect the user’s preferred shell from

terminal.integrated.defaultProfile

instead of hardcoding the platform default. #313160
Add support for custom diff editors with the new customDiffEditorProvider proposed API. Extensions that implement resolveCustomDiffEditor can render a unified diff in a single webview with access to both the original and modified documents, instead of two side-by-side custom editor webviews. #298924
Restore the ability to select and copy code in chat edit suggestions that the agent proposes to remove. #252762

May 4, 2026

Add a custom duration option to the Snooze Inline Suggestions Quick Pick. #288770
Reduce the CSS context attached when adding a DOM element to chat. The attachment only includes modified computed styles and CSS rules and variables that actually affect the element. #314188

We really appreciate people trying our new features as soon as they are ready, so check back here often and learn what’s new.

Visual Studio Code 1.119

Posted on May 1, 2026 by faz_business

Last updated: April 30, 2026

Welcome to the 1.119 release of Visual Studio Code.

Happy Coding!

April 30, 2026

Add a preview button for Markdown files. #312425
Allow hiding the update notification button in the title bar. #311929

April 29, 2026

Organize Markdown settings into subcategories for better discoverability. #313363
Add support for indexing external ingest in virtual file systems for chat codebase context. #313281
Add support for attaching browser tabs to chat to share page snapshots as context. #312169
Add support for Copilot CLI plan mode in AHP. #312050
Allow agents to request access to browser tabs through a permission dialog. #297372

We really appreciate people trying our new features as soon as they are ready, so check back here often and learn what’s new.

TypeScript 7 Beta Now Enabled by Default in Visual Studio 2026 18.6 Insiders 3

Posted on April 30, 2026 by faz_business

TypeScript 7 Beta Now Enabled by Default in Visual Studio 2026 18.6 Insiders 3

In Visual Studio 2026 18.6 Insiders 3 we have updated the built-in TypeScript SDK to TypeScript 7 Beta (native preview). The TypeScript SDK provides the compiler and language service used for TypeScript and JavaScript support in Visual Studio. This update impacts any project that uses the built-in SDK, including TypeScript projects, ASP.NET Core projects with npm packages, and any TypeScript or JavaScript files you are editing. If your project doesn’t have a specific TypeScript version installed, Visual Studio will use the new native compiler by default. In this post we will go over what this change means for you, how to use a different version of TypeScript if needed, and the known issues we are currently working on. You can download the latest Insiders release with the link below.

Download Visual Studio 2026 Insiders

What is the TypeScript 7 native preview?

TypeScript 7 is a native port of the TypeScript compiler and tools. This is a significant change that brings native execution speed and shared-memory parallelism to the TypeScript compiler and language service. We have seen compile time improvements of up to 10x for large code bases, along with substantially reduced memory usage. If you are working with large TypeScript or JavaScript projects, you should see a noticeable improvement across your entire development experience.

In addition to faster compile times, the TypeScript language service has significant performance improvements as well. We have seen that the time to load projects has decreased roughly 8x. The improvements are not limited to load times; you should see a general speed improvement across the board with any features which interact with the TypeScript language service. Some of the Visual Studio features that benefit from these improvements include.

IntelliSense and completions. Code completions and parameter info should appear faster, especially in large projects where you may have previously noticed a delay.
Find All References. Searching for references across your solution is significantly faster.
Go to Definition. Navigating to definitions is more responsive.
Error diagnostics. Squiggles and error lists update more quickly as you type.
Project load times. Opening TypeScript and JavaScript projects in Visual Studio should be noticeably faster, with load times decreasing by roughly 8x.

If you are working with large code bases, you should see a noticeable improvement to your entire development experience. You will spend less time waiting for the IDE to respond and more time being productive working on your applications.

For more details on TypeScript 7 and the performance improvements, see the Announcing TypeScript 7.0 Beta blog post.

Using a different TypeScript version

Visual Studio ships with a built-in version of the TypeScript compiler and language service for cases where the project doesn’t specify a specific version to be used. Starting with this release, that built-in version is TypeScript 7 Beta. If you prefer to use a different version, you can install it in your project and Visual Studio will always use the project-local version over the built-in one.

Disabling TypeScript 7 native preview

If you want to go back to using the previous TypeScript language service, you can disable the native preview in Visual Studio. Go to Tools > Options > Preview Features and search for “native preview”. Uncheck the Enable JavaScript/TypeScript Native Language Service Preview option and restart Visual Studio.

Using TypeScript 6.x (GA)

To use the current stable release, install the typescript package in your project.

npm install -D typescript@^6.0.0

Using a specific TypeScript 7 native preview version

If you want to pin to a specific version of the native preview, install the @typescript/native-preview package.

npm install -D @typescript/native-preview@beta

In both cases, Visual Studio will detect the version in your node_modules and use that instead of the built-in SDK.

Known issues

TypeScript 7 brings significant performance improvements to Visual Studio, and we are continuing to refine the experience. Below are the known issues that we are actively working on. This is not an exhaustive list.

IntelliSense. You may notice completions not appearing in some cases. In .cshtml files, the TypeScript completion list may not appear inside a <script> tag. When accepting a completion for the last argument of a function, the closing parenthesis may be removed. Pressing Ctrl+Space can work around this.
Code Actions & Refactoring. Quick fixes (Ctrl+.) are not available yet. Only Copilot AI-based suggestions may appear. The Organize Imports command (Ctrl+R, Ctrl+G) is also not available.
Navigation & Search. The navigation bar dropdowns at the top of the editor do not show document symbols. Find All References (Shift+F12) shows a flat list without semantic grouping (read/write/declaration), and cross-file references may be incomplete. Code search results may show mismatched titles and descriptions.
CodeLens. Reference counts (e.g., “19 references”) do not appear above interface and class declarations.
Hover tooltips. Hover tooltips are missing the symbol icon and have different text coloring compared to the previous language service.
Snippets. Insert Snippet (Ctrl+K, Ctrl+X) does not work in JavaScript files.
JSDoc. Typing /** above a function with parameters does not auto-generate the JSDoc template with @param entries.
Formatting. Unchecking “Format on open block {” in Tools > Options > Text Editor > JavaScript/TypeScript > Formatting does not take effect.
Task List. If a TypeScript file contains both a TODO comment and a variable named “TODO”, the Task List may incorrectly show duplicate tasks.
File and folder rename. Renaming a file or folder in a TypeScript project does not consistently update import paths in other files.
File watching. When files are modified outside of Visual Studio, changes are not detected until the file is opened and modified inside the IDE. Errors from external edits will not appear in the Error List.

We appreciate your feedback as we work toward full parity.

Reporting feedback

If you have feedback on the TypeScript compiler, or language service, the best place to file feedback is the typescript-go GitHub repo.

If you are running into an issue that is specific to Visual Studio, you can share feedback with us via Developer Community: report any bugs or issues via report a problem and share your suggestions for new features or improvements to existing ones.

We would love if you could try out the new experience and let us know how it’s working for you. Please try it out and share your feedback with us.

SDK-Style Support for Extension Projects

Posted on April 30, 2026 by faz_business

Starting in Visual Studio 18.5, you can create and build Visual Studio extensions (VSIX) using an officially supported SDK-style project. This brings VSIX projects into the modern build and deployment pipeline, improving incremental build performance and making the build → deploy → debug workflow more reliable. Install the Visual Studio extension development workload to get the templates and tooling and try it out for yourself!

Note: Extensions written using the modern VisualStudio.Extensibility framework already supports SDK-style projects today. This update extends the same SDK-style experience to VSSDK-based Visual Studio extensions.

What We Are Adding:

Official SDK-style support for projects that produce VSSDK-based extensions.
Build time reductions of up to 75%! We’ve added end-to-end incremental build support including Fast Up To Date Check and up to date deployment logic. Through internal adoption, we see a reduction of up to 75% in build time in large solutions for small changes or changes confined to a single sub project.
Updated in-box templates: SDK-style by default, with the familiar project items (tool windows, classifiers, commands, etc.).

Project Usage

Creating a project is done the same way you are used to, using the “VSIX Project” or “Empty VSIX Project” template:

This will yield a much more compact csproj than before: only 20 lines:

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <TargetFramework>net472</TargetFramework>
    <Nullable>enable</Nullable>
    <LangVersion>14</LangVersion>

    <!-- VSIX settings -->
    <VSSDKBuildToolsAutoSetup>true</VSSDKBuildToolsAutoSetup>
    <VsixDeployOnDebug>true</VsixDeployOnDebug>
    <GeneratePkgDefFile>true</GeneratePkgDefFile>
  </PropertyGroup>
  <ItemGroup>
    <ProjectCapability Include="CreateVsixContainer" />
  </ItemGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.VisualStudio.SDK" Version="17.14.40265" ExcludeAssets="runtime" />
    <PackageReference Include="Microsoft.VSSDK.BuildTools" Version="18.5.38461" />
  </ItemGroup>
</Project>

Does it impact my extension?

If you create a new extension, you will automatically get full SDK-Style support.
Your existing MPF style extension will continue to work should you choose not to migrate. This update adds an official SDK-style option; it doesn’t force a conversion.
You can update your project to an SDK-style project file to take advantage of these features.
Vsixmanifest files included in SDK-style projects now open by default in the XML editor. The old designer is still available through the ‘Open With’ menu.

Migration In Brief

When available, you can do this in the project configuration:

<VSSDKBuildToolsAutoSetup>true</VSSDKBuildToolsAutoSetup> will setup most sensible defaults for you and reduce the size of your csproj. This will setup options like CreateVsixContainer as true, and the legacy DeployExtension to false.
<VsixDeployOnDebug>true</VsixDeployOnDebug> Should be added to your csproj if you will add it to other solution files to ensure the deploy checkbox is set automatically.

Agentic conversion

We’re experimenting with ways of making this as easy as possible for you. To that end, we’ve added an agent skill to the vs-agent-plugins repository you can use in conjunction with the Modernize agent. Let us know whether this workflow is helpful, or if you have a different agentic workflow in mind for extension development.

Reference projects

Here are a few extensions that are already converted, so you can use them as references.

We want to hear from you!

Please send us feedback and issues you encounter in Developer Community. Thank you, and happy extending!

Visual Studio Code 1.118

Posted on April 24, 2026 by faz_business

Last updated: April 24, 2026

Welcome to the 1.118 release of Visual Studio Code.

Happy Coding!

April 23, 2026

Adopt the Copilot CLI SDK session-title APIs as the source of truth for session names. #311535
Add keybindings such as Ctrl+1 and Ctrl+2 to quickly switch between sessions in the Agents app. #310992
Add auto model support to the Copilot CLI agent. #311299

April 22, 2026

Add descriptions to the chat customization creator menu, helping users understand which skill location to use for each type of customization. #295151
Let users opt in to testing the TypeScript 7.0 nightlies. #311966
Copilot CLI responses in the chat panel show a model badge indicating which model handled the request. #303960
Add support for auto model selection in Copilot CLI. #311779

April 21, 2026

The Copilot CLI SDK resolves node-pty from VS Code via hostRequire, eliminating the need to copy node-pty binaries into the SDK’s prebuilds folder at build time or runtime. #307746

We really appreciate people trying our new features as soon as they are ready, so check back here often and learn what’s new.

Stop Hunting Bugs: Meet the New Visual Studio Debugger Agent Workflow

Posted on April 18, 2026 by faz_business

We’ve all been there: a bug report lands in your inbox with a title like “App crashes sometimes” and zero reproduction steps. Your morning, which was supposed to be spent building new features, is now a forensic investigation. You’re setting scattershot breakpoints, staring at the call stack, and trying to guess what the original reporter was thinking.

Debugging isn’t just about fixing code; it’s about reducing uncertainty. Today, we’re taking a massive leap toward solving that problem by introducing a new, upgraded, guided workflow within our exiting Debugger Agent in Visual Studio.

Ending the “Guessing Game” with a Guided Debugger Loop

Let’s be honest: traditional debugging is full of friction. You manually parse a vague report, hunt for the right file, and spend twenty minutes just trying to see if you’re in the right ballpark. This new workflow flips the script, transforming the Debugger Agent from a chatbot into an interactive partner plugged directly into your live runtime.

To get started, simply open your solution in Visual Studio, switch to Debugger mode in Copilot Chat, and point it to the problem with a GitHub/ADO URL or a quick sentence like:

“The app crashes when saving a file.”

The workflow is interactive and powered by runtime debugging, meaning the Agent doesn’t just read your code; it feels how it’s running. It immediately builds a mental model of the failure and walks you through a structured, real-time process:

Hypothesis & Preparation: The Agent analyzes the issue and proposes a root cause. If the reasoning looks solid, it sets intelligent breakpoints and prepares to launch your project.

Note: If your project can’t be started automatically, just manually start your code, attach the debugger, and tell the Agent you’re ready.

Active Reproduction: The Agent stays “on the line” while you trigger the bug, watching the runtime state as you move through the repro steps.

Real-Time Validation: As breakpoints hit, the Agent evaluates variables and the call stack to systematically confirm its hypothesis or eliminate potential causes.

The Final Fix: Once the root cause is isolated, the Agent proposes a solution. If you approve, it applies the fix and reruns the session to validate the resolution.

This iterative flow is designed to keep you “in the zone.” By handling the manual setup and state analysis, the Agent lets you move from a bug report to a verified fix with significantly less mental context switching.

Our Vision: Foundational Quality and Beyond

18.5 GA releases deliver the foundational experience of the guided workflow, specifically optimized for high-value, reproducible scenarios like exceptions, logic inconsistencies, and state corruption.

As we look forward, we are already evolving this foundation to be even more robust. Our goal is to progressively automate the end-to-end workflow, maturing the Debugger Agent into a comprehensive, seamless debugging companion that anticipates your needs.

Debug Smarter, Not Harder

The new workflow in the Debugger Agent represents a fundamental shift in how we think about IDEs. We’re excited to see how you use this in your own workflows whether you’re untangling a complex race condition in a multi-threaded service or simply trying to figure out why a UI element isn’t updating as expected.

Stay connected with the Visual Studio team by following us on Twitter @VS_Debugger, Twitter @VisualStudio, YouTube, and LinkedIn.

From AI to .NET: 20 VS Live! Las Vegas Sessions You Can Watch Now

Posted on April 17, 2026 by faz_business

In March 2026, developers came together at VS Live! Las Vegas for a full week of technical learning, hands-on exploration, and a lot of great conversations about where software development is headed next. From AI-assisted development to modern .NET, cloud-native apps, and developer productivity, one thing was clear: the pace of change is not slowing down.

If you were not able to attend, or if you want to revisit some of the strongest content from the event, we are now publishing 20 sessions from VS Live! Las Vegas on the Visual Studio YouTube channel.

We are releasing about two sessions per day, so you can watch them at your own pace and jump into the topics that matter most to you.

What you’ll find in this series

These sessions reflect the topics developers are focused on right now, including:

AI and Copilot-powered development
Modern .NET and C#
Cloud-native apps and Azure
Developer productivity and tooling
Real-world architecture and engineering

You’ll hear directly from Microsoft engineers helping build these tools, along with industry experts who are using them to solve real problems and ship real applications.

A few sessions to check out

This lineup includes a strong mix of practical guidance, technical depth, and forward-looking keynotes.

Keynotes

The Road to Visual Studio 2027: Building a Faster, Smarter IDE – Mads Kristensen
Knowledge is the Key: The Path for AI Applications – Jerry Nixon and Drew Skwiers-Koballa

Featured sessions

AI’s Not Magic: A Developer’s Guide to Using AI Tools Without the Hype – Brian A. Randell
Building an AI Agent to Work with Your Own Data – Jerry Nixon
Building Intelligent .NET Applications: From AI to Implementation – Jon Galloway
What’s New in C# – Jason Bock
Building RESTful Services with ASP.NET Core – Philip Japikse
GitHub Actions in Action – Marcel de Vries
The Forgotten Features of Visual Studio You NEED In Your Life! – Mads Kristensen
Fast Focus: Caching Options in .NET – Jason Bock
VS Code and Visual Studio, Better Together – Brian A. Randell
Modernizing .NET Applications Faster with Visual Studio – Jon Galloway

What I like about this set of sessions is that it is not just theory. These talks focus on real-world scenarios, whether you are exploring AI in existing apps, modernizing older .NET solutions, improving performance, or just looking for better ways to work day to day.

Start watching

Whether you are catching up on what you missed or diving in for the first time, this is an easy way to experience some of the best content from VS Live! Las Vegas on your own schedule.

VS Live! Las Vegas YouTube Playlist

We will continue publishing sessions daily, so check back often and subscribe to the Visual Studio YouTube channel to stay up to date.

Want the full VS Live! experience? Attend in person

Watching online is a great way to learn, but there is still nothing like attending a VS Live! event in person. You get the sessions, the hands-on labs, the hallway conversations, and direct access to speakers, product experts, and fellow developers.

If you are a Visual Studio subscriber, you may already have access to exclusive event pricing through my.visualstudio.com. Just sign in, head to the Benefits page, and look for the Visual Studio Live! Events tile to get your priority code. Depending on the event, that can save you up to $900 on registration.

If you are not a subscriber, you can still save. As a Visual Studio Blog reader, use priority code VSLMS at checkout to save up to $600.

Each event includes a full week of expert-led sessions and hands-on labs, plus the chance to connect directly with the people behind Visual Studio, .NET, Azure, and GitHub Copilot.

Upcoming VS Live! events

Microsoft HQ (Redmond) | July 27 to 31, 2026
San Diego | September 14 to 18, 2026
Live! 360 Orlando | November 15 to 20, 2026
Las Vegas | March 22 to 26, 2027

Explore All VS Live Events

Visual Studio Code 1.117

Posted on April 17, 2026 by faz_business

Last updated: April 16, 2026

Welcome to the 1.117 release of Visual Studio Code.

Happy Coding!

April 15, 2026

Add support for self-updating the Agents app on macOS. #308646
Copilot CLI sessions indicate whether they were created by VS Code or externally. #308543
In package.json files, the dependency hover now shows the currently installed version alongside the latest published version of a package. #307648
Images in JSDoc comments, including <img> HTML tags, now render correctly in hovers, completion details, and signature help for JavaScript and TypeScript files. #231792

April 14, 2026

The Autopilot permission mode now persists across sessions. You can configure the default permission level with the

chat.permissions.default

setting. #309562
When an agent sends input to a terminal, the terminal output is now automatically included in the result after a brief delay, saving an extra agent turn. #309509
Agent Host now supports auto-approve session configuration with three modes: Default Approvals, Bypass Approvals, and Autopilot (Preview). #309337
You can now switch back to the main window from auxiliary (floating) windows. #306571
Agent Host Protocol now supports subagents and agent teams. #305755

April 13, 2026

Agent Host sessions now support worktree and git isolation. #305325
Copilot CLI, Claude Code, and Gemini CLI are now recognized as shell types in the terminal. #290830

April 12, 2026

Copilot CLI now generates meaningful branch names based on the user’s prompt when creating worktrees for background agent sessions. #306191

We really appreciate people trying our new features as soon as they are ready, so check back here often and learn what’s new.

Visual Studio Code 1.116

Posted on April 9, 2026 by faz_business

Last updated: April 8, 2026

Welcome to the 1.116 release of Visual Studio Code.

Happy Coding!

April 8, 2026

Add dedicated commands and keybindings to the Agents app to focus the Changes view (), the files tree within the Changes view, and the Chat Customizations view, enabling full keyboard navigation. #308327, #308322, #308265
Add an accessibility help dialog (⌥F1 (Windows Alt+F1, Linux Shift+Alt+F1)) to the Agents app chat input box that displays available commands and keybindings for screen reader users, with an option to control announcement verbosity. #308259
Add support for CSS @import link node_modules resolution, allowing you to Ctrl+click through imports like @import "some-module/style.css" when using bundlers. #295074

April 7, 2026

Add #-triggered file-context completions to the Agents app, scoped to the workspace chosen in the picker. #299057

We really appreciate people trying our new features as soon as they are ready, so check back here often and learn what’s new.

Take full control of your floating windows in Visual Studio

Posted on April 7, 2026 by faz_business

If you work with multiple monitors like I do, you’ve probably grown to love floating tool windows and documents in Visual Studio. Being able to pull out Solution Explorer, the debugger, or your code files onto a second (or third) screen can be a huge productivity boost.

But there’s always been a bit of friction with how these floating windows behave.

By default, floating windows are “owned” by the main Visual Studio window. That means they don’t show up as separate buttons in your Windows taskbar, they disappear when you minimize the main IDE, and they always stay on top of everything else — even when you don’t want them to.

For some workflows that’s exactly what you want. For others, it gets annoying fast.

Fortunately, there’s a little-known setting that lets you decide exactly how much control Visual Studio has over your floating windows.

The setting is here: Tools > Options > Environment > Windows > Floating Windows

You’ll see this dialog:

The dropdown is labeled “These floating windows are owned by the main window” and gives you three choices:

None
Tool Windows (the default)
Documents and Tool Windows

Changing this one setting can completely transform how you work with floating windows.

My favorite scenario: PowerToys FancyZones

This setting really shines when you combine it with Microsoft and its excellent FancyZones feature.

I like to set it to None and then use FancyZones to create custom layouts across my monitors. Suddenly all my floating tool windows and documents behave like normal application windows — they appear in the taskbar, stay visible even if I minimize the main Visual Studio window, and I can snap them perfectly into my FancyZones layouts without them forcing themselves to the front all the time.

It feels much more natural and gives me the clean multi-monitor setup I’ve always wanted.

When to choose each option

None: Maximum independence. Everything gets its own taskbar entry and full window behavior. Perfect for heavy multi-monitor users with PowerToys.
Tool Windows: A nice middle ground — keep your documents floating freely while tool windows stay tied to the IDE.
Documents and Tool Windows: The classic Visual Studio behavior.

Pro tip: Combine this with the Ctrl + double-click trick on any tool window title bar (see our earlier post on easily docking and floating tool windows) for lightning-fast layout switching. No restart required.

Have you played with this setting before? What option do you prefer: None, Tool Windows, or the default? Let me know in the comments. I’m always curious how other developers set up multi-monitor workspaces.

Happy coding!