# C# Published articles for C#. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Modernize your .NET apps for Windows Arm64 with GitHub Copilot DevFeed: [Modernize your .NET apps for Windows Arm64 with GitHub Copilot]() Original publisher: [Read original article]() Author: Mika Dumont Published: 2026-11-05T18:05:00Z Content type: tutorial Language: en Sources: [.NET Blog]() Topics: [.NET](), [GitHub Copilot](), [Windows]() Tags: [agent](), [ai](), [arm64](), [c-sharp](), [github-copilot](), [migration](), [modernization](), [modernize](), [net](), [upgrade](), [windows]() ### AI overview The GitHub Copilot upgrade agent assesses .NET projects migrating from Windows x64 or x86 to Windows Arm64, identifies architecture-specific code, unsupported native dependencies, package compatibility issues, and configuration blockers, then proposes a codebase-specific plan and helps update code, dependencies, and project settings with developer review. It can build migrated components; runtime testing depends on access to matching Arm64 hardware or CI runners. A successful build alone does not validate runtime behavior, so validation on Windows Arm64 is still needed. The scenario targets portability and correctness, not Arm64 performance tuning; performance can be measured separately after validation. ### Source excerpt Modernize your .NET apps for Windows Arm64 with the GitHub Copilot upgrade agent, from identifying migration blockers to planning and making code changes. The post Modernize your .NET apps for Windows Arm64 with GitHub Copilot appeared first on .NET Blog. ## GPT-6 Cyber Security Evaluation: CodeRabbit's Results DevFeed: [GPT-6 Cyber Security Evaluation: CodeRabbit's Results]() Original publisher: [Read original article]() Author: Rohit Khanna Published: 2026-11-05T12:00:00Z Content type: news Language: en Sources: [CodeRabbit]() Topics: [ai code review](), [AI in cybersecurity](), [Static code analysis](), [Security]() Tags: [authorization](), [benchmark](), [bypass](), [c-sharp](), [cases](), [cross-site-scripting](), [cyber-security](), [cybersecurity](), [daybreak](), [daybreak-defense-network](), [deep](), [denial-of-service](), [english](), [evaluation](), [exploited](), [featured](), [go](), [gpt-6-cyber](), [idor](), [model-evaluation](), [results](), [security]() ### AI overview In CodeRabbit Secure's comparison on the same 33 cases, adding GPT-6 Cyber increased known-issue catches from 19 to 22 (a 15.8% relative gain) and raised high- and medium-severity findings in final reports by 65.6%, rounded to 66%. The net gain reflects five additional catches and two baseline catches lost; nine selected issues remained undetected by both configurations. Cases covered nine programming languages, and only issues present in final reports with an explanation received catch credit. The extra findings have not yet been assessed for validity, so report accuracy and prioritization remain open questions. Investigation used high reasoning effort, but no lower-effort run was compared, leaving its effect on coverage, time, and cost unknown. ### Source excerpt Across 33 benchmark cases, CodeRabbit's ensemble with GPT-6 Cyber caught 22 known issues versus 19 without it and reported 66% more high- and medium-severity findings. ## CodeQL 2.27.4 improves accuracy and query metadata DevFeed: [CodeQL 2.27.4 improves accuracy and query metadata]() Original publisher: [Read original article]() Author: Allison Published: 2026-11-04T20:04:52Z Content type: release Language: en Sources: [GitHub Changelog]() Topics: [Static code analysis](), [GitHub]() Tags: [analysis](), [application-security](), [arithmetic](), [blog](), [c](), [c-c-plus-plus](), [c-plus-plus](), [c-sharp](), [changelog](), [changes](), [code-scanning](), [codeql](), [engine](), [github](), [improvement](), [improvements](), [metadata](), [post](), [query](), [security](), [static](), [static-analysis]() ### AI overview CodeQL 2.27.4 improves analysis accuracy across several languages: Java/Kotlin queries recognize more sanitizers and path guards; Rust queries have fewer false positives; and C/C++ queries suppress reports for intentional `std::byte*` pointer arithmetic and variables marked `[[maybe_unused]]`. It also removes CWE-730 metadata from specified regex-related queries across C#, Java/Kotlin, JavaScript/TypeScript, Python, Ruby, and Swift. The CLI sends JVM warnings and initialization errors to stderr, preserving machine-readable output. When bundling or publishing packs, it omits files whose resolved symbolic links point outside the pack root and warns about them. GitHub deploys new CodeQL versions automatically for code scanning on github.com; this release is slated for GHES 3.24, while older GHES versions can be upgraded manually. ### Source excerpt CodeQL is the static analysis engine behind GitHub code scanning, which finds and remediates security issues in your code. We've recently released CodeQL 2.27.4 with query accuracy improvements across several... The post CodeQL 2.27.4 improves accuracy and query metadata appeared first on The GitHub Blog. ## Building Windows C# Tools and Payloads from Kali Linux DevFeed: [Building Windows C# Tools and Payloads from Kali Linux]() Original publisher: [Read original article]() Published: 2026-11-04T00:00:00Z Content type: tutorial Language: en Sources: [Kali Linux]() Topics: [Cross-Compilation](), [builds](), [Windows](), [WINE](), [.NET Framework](), [console](), [Process]() Tags: [advanced](), [c-sharp](), [clm](), [compile](), [distribution](), [kali](), [kali-linux](), [kalilinux](), [linux](), [penetration](), [penetration-testing](), [testing](), [tools](), [windows]() ### AI overview The article shows how Kali Linux can build and run Windows C# artifacts for penetration-testing exercises. Install `mono-devel` and use `mcs` to compile C# into a Windows executable or DLL; `wine` with `wine-mono` can run ordinary binaries on Kali. A Constrained Language Mode bypass example additionally requires Microsoft PowerShell and installer DLLs, which the article locates in files downloaded by configuring `powershell-empire`. It also describes using the `csharp` interpreter with a shell function to transform `msfvenom` output, and compiling Rubeus with `dotnet publish` using a patch for a self-contained build. For DotNetToJScript, the authors use repository binaries because they could not compile them; that workflow requires `wine` and `dotnet35`, since `wine-mono` alone did not work. These are article-specific procedures; the supplied text does not establish broader compatibility or current package availability. ### Source excerpt One of our team members recently took (and passed!) OffSec's advanced penetration testing course & exam, PEN-300/OSEP. Whilst it focuses a lot on Microsoft Windows, there were a few extra places where Linux could be used to complete the same task... just quicker! Compiling C# code in Kali In general, what you need for compiling CSharp (C#) code in Kali is mono-devel : kali@kali:~$ sudo apt install mono-devel Now we need some code to compile. Here's a very basic way of executing a program (process): using System; using System.Diagnostics; namespace Exec { class Program { static void Main() { Process proc = new Process(); ProcessStartInfo procInfo = new ProcessStartInfo("cmd.exe", "/T:09 /K systeminfo"); procInfo.CreateNoWindow = false; procInfo.UseShellExecute = false; proc.StartInfo = procInfo; proc.Start(); } } } If you would like some more examples to get you going, try a Shellcode Launcher or a Simple Reverse Shell. All that is left is to compile: kali@kali:~$ TERM=linux mcs -out:exec.exe exec.cs kali@kali:~$ kali@kali:~$ file exec.* exec.cs: C++ source, ASCII text exec.exe: PE32 executable for MS Windows 4.00 (console), Intel i386 Mono/.Net assembly, 3 sections kali@kali:~$ How to run these binaries from Kali Linux Simple: just install wine and wine-mono. It's really handy, as you can test your Windows binaries (even reverse shells) directly from Kali: kali@kali:~$ sudo dpkg --add-architecture i386 kali@kali:~$ sudo apt update [...] kali@kali:~$ sudo apt -y install wine32 [...] kali@kali:~$ # Install wine-mono kali@kali:~$ wget https://dl.winehq.org/wine/wine-mono/11.3.0/wine-mono-11.3.0-x86.msi [...] kali@kali:~$ kali@kali:~$ wine msiexec /i wine-mono-11.3.0-x86.msi [...] kali@kali:~$ And now, to run your freshly built .exe binary, just use: kali@kali:~$ wine exec.exe Constrained Language Mode Bypass It's not always that easy -- sometimes things get a bit trickier. For example, for compiling the Constrained Language Mode (CLM) bypass section, we need some DLL libr ## How Ares Interactive runs live ops without waiting on client updates DevFeed: [How Ares Interactive runs live ops without waiting on client updates]() Original publisher: [Read original article]() Author: Adam Axler Published: 2026-11-04T00:00:00Z Content type: article Language: en Sources: [Unity]() Topics: [CI/CD](), [mobile devops](), [Continuous Delivery (CD)](), [firebase-remote-config](), [mobile-app-performance](), [Production Engineering]() Tags: [a-b-testing](), [assets](), [backend](), [balance](), [branch](), [build](), [build-times](), [builds](), [c-sharp](), [caching](), [calendar](), [call](), [ci](), [config](), [live](), [ops](), [release](), [remote](), [remote-config](), [ship]() ### AI overview Ares Interactive keeps many live changes independent of client releases, with different pipelines in its two games. Baseball Hits 26 uses a custom backend and remote configuration across more than 50 domains; validated, versioned changes reach servers within seconds, with staging, rollback, scheduling, segmentation, and A/B testing. Addressables deliver optional stadium bundles on demand, while a default stadium ships in the app. The Walking Dead: Aftermath carries forward proven live-service systems and keeps frequently changed content in platform-specific AssetBundles, separate from Addressables, which handle loading and memory. Bundles include compatibility metadata; configuration and balance can change remotely, while new art and code require a build. Spreadsheets feed designer-authored content, enabling some fixes in about 15 minutes. CI checks environment configuration and prevents uploads when required settings are missing. Both teams emphasize early device testing and designing for failures; Swift Games also advises proving the core loop with a small amount of content before expanding live-service features. ### Source excerpt How Baseball Hits 26 and The Walking Dead: Aftermath use remote config, versioned bundles, and CI to ship live ops changes without a client release. ## Get Ready for .NET Conf 2026! DevFeed: [Get Ready for .NET Conf 2026!]() Original publisher: [Read original article]() Author: .NET Team Published: 2026-11-03T17:30:00Z Content type: news Language: en Sources: [.NET Blog]() Topics: [.NET Conf](), [.NET](), [Developer Events](), [ASP.NET Core](), [ASP.NET](), [.NET MAUI](), [C#]() Tags: [agentic-ui](), [agents](), [ai](), [asp-net-core](), [aspire](), [blazor](), [c-sharp](), [c-sharp-dev-kit](), [community](), [conference](), [copilot](), [debugging-and-diagnostics](), [developer-workflow](), [dotnet-cli](), [net](), [net-11](), [net-conf](), [net-conf-2026](), [net-maui](), [virtual-event](), [visual-studio]() ### AI overview .NET Conf 2026 is a free virtual event running November 10-13, with the official .NET 11 launch and two days each of Microsoft and community-led sessions. Microsoft sessions begin November 10 at 8 AM PST with a keynote on .NET 11 and Copilot and agents in .NET development; November 11 focuses on Visual Studio and developer deep dives. Topics include C#, ASP.NET Core and Blazor, .NET MAUI, AI tooling, debugging, and modernization. The November 12-13 Community Days are organized by volunteers and feature developers' project experiences; their agenda and viewing details are on dotnetconf.net. Microsoft's agenda and conference information are at dot.net/conf, where attendees can select a time zone and add sessions to their calendars. ### Source excerpt .NET Conf is one week away! Join us November 10-13 for the launch of .NET 11, two days of Microsoft sessions, and two days of Community Days. The post Get Ready for .NET Conf 2026! appeared first on .NET Blog. ## CVE-2026-63346 - Refitter: C# source injection through OpenAPI header parameter names DevFeed: [CVE-2026-63346 - Refitter: C# source injection through OpenAPI header parameter names]() Original publisher: [Read original article]() Author: CVEFEED.io; github.com Published: 2026-10-30T23:17:14Z Content type: news Language: en Sources: [Latest High/Critical Vulnerabilitiy Feed]() Topics: [C#](), [OpenAPI Specification](), [client library]() Tags: [2026](), [api](), [application](), [assembly](), [behavior](), [c-sharp](), [class](), [client](), [code](), [cve](), [cve-2026-63346](), [header](), [interface](), [library](), [name](), [net](), [net-8](), [openapi](), [parameter](), [source]() ### AI overview Before Refitter 2.1.2, an OpenAPI header parameter name was inserted unescaped into a Refit `[Header("")]` attribute. An attacker-controlled description could therefore inject valid C# into generated code; a `[ModuleInitializer]` could run the injected code when the compiled assembly loads at startup, even if the API client is never called. The excerpt says default validation does not block this path and notes that query `AliasAs` and enum/default value sinks are escaped. The behavior was verified with Refitter 2.0.0 and .NET 8; the issue is fixed in 2.1.2. ### Source excerpt CVE ID :CVE-2026-63346 Published : Oct. 30, 2026, 11:17 p.m. | 39 minutes ago Description :Refitter is a tool for generating a C# REST API client using the Refit library. Prior to 2.1.2, the header parameter name in `parameters[].name` with `in: header` is emitted verbatim into a Refit `[Header("")]` attribute string without escaping quotation marks. An attacker-influenced OpenAPI description can pass default validation without `--skip-validation` and break out from the parameter-list position by closing the parameter and method syntax, attribute, interface, and namespace. The generated file can remain valid C# while containing a top-level file class with a `[ModuleInitializer]` method, which executes attacker code when the compiled assembly is loaded at application startup, even if the client is never called. Query `AliasAs` and enum/default value sinks are escaped; this flaw is in header-name attribute-string emission. The behavior was verified with Refitter 2.0.0 and .NET 8. This issue is fixed in version 2.1.2. Severity: 8.6 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more... ## CVE-2026-63345 - Refitter: C# source injection through OpenAPI path keys DevFeed: [CVE-2026-63345 - Refitter: C# source injection through OpenAPI path keys]() Original publisher: [Read original article]() Author: CVEFEED.io; github.com Published: 2026-10-30T23:17:13Z Content type: news Language: en Sources: [Latest High/Critical Vulnerabilitiy Feed]() Topics: [OpenAPI Specification](), [REST API](), [Compilers and Linkers](), [Boilerplate](), [client library]() Tags: [2026](), [c-sharp](), [cve](), [cve-2026-63345](), [openapi]() ### AI overview Before Refitter 2.1.2, OpenAPI `paths` keys were inserted verbatim into generated C# Refit route attributes. An attacker-controlled, single-line slash-prefixed path can survive default validation and inject a `[ModuleInitializer]` that runs when the generated assembly is compiled and loaded at startup, without the client being called. The excerpt says enum and default-value output is escaped and is not the vulnerable sink. The behavior was verified on Refitter 2.0.0 with .NET 8; the issue is fixed in 2.1.2. The excerpt does not identify affected products in the catalog table. ### Source excerpt CVE ID :CVE-2026-63345 Published : Oct. 30, 2026, 11:17 p.m. | 39 minutes ago Description :Refitter is a tool for generating a C# REST API client using the Refit library. Prior to 2.1.2, OpenAPI `paths`-object keys are emitted verbatim into Refit route attributes such as `[Get("")]` without escaping quotation marks or restricting characters. An attacker-influenced single-line, slash-prefixed path survives default validation without `--skip-validation` and can close the attribute string, interface, and namespace while introducing a top-level file class and reopening the generated structure to keep valid C#. A `[ModuleInitializer]` method executes attacker code when an application compiles and loads the generated assembly at startup, even without calling the generated client. The enum and default value sinks are escaped and are not the vulnerable path-emission sink. The behavior was verified on Refitter 2.0.0 with .NET 8. This issue is fixed in version 2.1.2. Severity: 8.6 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more... ## From GDScript to GDExtensions: One IDE for Your Godot Code DevFeed: [From GDScript to GDExtensions: One IDE for Your Godot Code]() Original publisher: [Read original article]() Author: Anna Ruban Published: 2026-10-29T13:00:44Z Content type: article Language: en Sources: [JetBrains]() Topics: [Godot](), [Tool](), [CMake](), [Test-driven development](), [smolagents]() Tags: [2025](), [c-plus-plus](), [c-sharp](), [code](), [content](), [content-creation](), [foundation](), [free](), [game-development](), [gdscript](), [godot](), [godot-engine](), [godot-engine-2](), [godot-foundation](), [godotcon](), [godotfest](), [hobby](), [ide](), [it-s](), [jetbrains](), [learning](), [one](), [open](), [open-source](), [over](), [rider]() ### AI overview Rider brings Godot's GDScript, C#, and C++ GDExtension work into one IDE, with free non-commercial use. Its GDScript support includes completion, refactoring, inspections, and scene-aware navigation; an official Godot addon connects Rider with the editor. Developers can debug GDScript, C#, or both together, run C# tests, and use C++/CMake templates for native extensions and addons. The 2026.3 EAP adds scene-node navigation and signal tracing for GDScript, live scene inspection while debugging C#, and separate ports to reduce conflicts across multiple Godot projects. These are preview features, while 2026.2 is the current stable release described. JetBrains also contributed Godot debugger protocol support for scene selection and command-line arguments. ### Source excerpt JetBrains has been a Platinum sponsor of the Godot Foundation since August 2025, and we've renewed our sponsorship into 2027. Over the past year, Rider has expanded its Godot support to cover GDScript, C#, and C++ GDExtensions in one place. It's free for non-commercial use, including hobby projects, learning, open source, and content creation. At [...] ## SKIP LOCKED vs. Redis: When Should You Use a Database Queue? DevFeed: [SKIP LOCKED vs. Redis: When Should You Use a Database Queue?]() Original publisher: [Read original article]() Author: Vasyl Vdovychenko Published: 2026-10-28T07:52:57Z Content type: comparison Language: en Sources: [HackerNoon]() Topics: [PostgreSQL](), [Database](), [Redis](), [Transactions]() Tags: [api](), [at-least-once-delivery](), [backend](), [background](), [background-job-processing](), [c-sharp](), [database](), [database-row-locking](), [distributed-systems](), [for-update](), [idempotency](), [jobs](), [postgres-job-queue](), [postgresql](), [queue](), [queues](), [redis](), [skip](), [tokens]() ### AI overview `SKIP LOCKED` lets concurrent workers atomically claim different queued rows without waiting, but it only protects the claim: a crash after commit can leave a job stuck as `running`. Recovery needs leases, while heartbeats help slow workers retain a lease; timeouts can still create overlapping owners. Increasing fencing tokens let the database reject stale workers' final writes, and idempotency keys can make repeated external calls, such as payments or emails, harmless. The article describes tradeoffs of a database queue: PostgreSQL update bloat and vacuum work, reliance on the primary, no strict processing order, worker connection use, and limits at very high throughput. For a single-worker side project, the author instead uses a PostgreSQL advisory lock plus an alert for long-running jobs, noting that a dropped database connection loses the lock. The approach fits when its recovery and operational costs are understood; it is not a silver bullet. ### Source excerpt Is SKIP LOCKED enough for reliable background jobs? Explore leases, heartbeats, fencing tokens, and idempotency in PostgreSQL queues. ## Qt Bridges Technology Preview: Qt Quick UIs for Rust and C# Developers DevFeed: [Qt Bridges Technology Preview: Qt Quick UIs for Rust and C# Developers]() Original publisher: [Read original article]() Author: bruno.vunderl@qt.io (Bruno Vunderl) Published: 2026-10-27T08:59:12Z Content type: release Language: en Sources: [Qt]() Topics: [Qt](), [Rust](), [Visual Studio Code](), [VS Code Extension](), [Programming languages & frameworks](), [Tokio]() Tags: [2025](), [backend](), [bridges](), [c-sharp](), [csharp](), [feedback](), [interfaces](), [net](), [preview](), [qt](), [qt-bridge](), [qt-bridge-for-c-sharp](), [qt-bridge-for-rust](), [qt-bridges](), [qt-quick](), [rust](), [technology]() ### AI overview Qt Bridges let developers pair Qt Quick/QML interfaces with Rust or C# backends by exposing selected backend types, properties, methods, signals and collections to QML, without hand-written glue. The bridges focus on the UI connection rather than binding the full Qt API; developers continue using their language ecosystem's libraries for tasks such as networking and file I/O. The Rust bridge uses attribute macros and traits, maps QML objects to Rc> with Rust borrow rules across the boundary, and can coexist with CXX-Qt. For C#, Visual Studio offers project templates and automatic NuGet references, while the VS Code extension supports project discovery, Qt installation lookup, QML tooling and debugging; projects need one build to generate QML tooling metadata. This Technology Preview is suitable for prototypes and evaluation, but APIs, platforms and requirements may change before stable release. ### Source excerpt When we announced Qt Bridges at Qt World Summit 2025, we had a simple goal: let developers build Qt Quick user interfaces with a backend written in their favorite programming languages. This year, the C# and Rust bridges went through several public betas. Thank you to everyone who tried them and sent feedback. It shaped every release. ## Terminus-4B: Can a Smaller Model Replace Frontier LLMs at Agentic Execution Tasks? DevFeed: [Terminus-4B: Can a Smaller Model Replace Frontier LLMs at Agentic Execution Tasks?]() Original publisher: [Read original article]() Author: Spandan Garg, Vikram Nitin, Yufan Huang Published: 2026-10-27T04:00:00Z Content type: article Language: en Sources: [arXiv: Software Engineering]() Topics: [agentic-coding](), [hierarchical agent systems](), [Large Language Model](), [Fine-tuning](), [LLM evaluation / benchmarking](), [llm-reasoning](), [Frontier AI]() Tags: [abstract](), [agent](), [agentic](), [agents](), [arxiv](), [based](), [bench](), [benchmark](), [benchmarks](), [build](), [but](), [c-sharp](), [can](), [claude](), [claude-sonnet](), [cs-ai](), [cs-se](), [execution](), [frontier](), [llms](), [model](), [tasks]() ### AI overview Terminus-4B is a Qwen3-4B model post-trained with supervised fine-tuning and reinforcement learning using rubric-based LLM-as-judge rewards for agentic terminal execution. In the reported evaluations, using it as a subagent reduced the main agent's token use by up to about 30% versus using no subagent, without reducing performance on SWE-Bench Pro or the authors' internal, execution-heavy SWE-Bench C# benchmark. The abstract also reports greater reliance on subagent outputs and fewer terminal tasks handled by the main agent; Terminus-4B closed the gap with vanilla Qwen and frontier models such as Claude Sonnet/Opus and GPT-5.3-Codex, sometimes exceeding them. These are claims from the supplied abstract, which does not provide detailed methods or results. ### Source excerpt arXiv:2605.03195v3 Announce Type: replace-cross Abstract: Modern coding agents increasingly delegate specialized subtasks to subagents, which are smaller, focused agentic loops that handle narrow responsibilities like search, debugging or terminal execution. This architectural pattern keeps the main agent's context window clean by isolating verbose outputs (e.g. build logs, test results, etc.) within the subagent context. Typically when agents employ subagents for such tasks, they use frontier models as these subagents. In this paper, we investigate whether a finetuned small language model (SLM) can achieve comparable performance to frontier models in the task of agentic terminal execution. We present Terminus-4B, which is a post-trained Qwen3-4B model via Supervised Finetuning (SFT) and Reinforcement Learning (RL) using rubric-based LLM-as-judge reward, specifically for this task. In our extensive evaluation spanning various frontier models, training ablations and main agent configurations, we find that Terminus-4B is able to reduce the token usage of the main agent by up to ~30% compared to the No Subagent baseline with no impact to agent performance on benchmarks like SWE-Bench Pro and our internal SWE-Bench C# benchmark, which tends to be heavy in verbose execution tasks. Furthermore, Terminus-4B improves key metrics showing the main agent relying on the outputs of the subagent and doing fewer terminal execution tasks by itself. We see that our model not only closes the gap between the Vanilla Qwen model and frontier models like Claude Sonnet / Opus / GPT-5.3-Codex, but often even exceeds their performance. ## GPT-6.1 Terra in GitHub Copilot DevFeed: [GPT-6.1 Terra in GitHub Copilot]() Original publisher: [Read original article]() Author: Allison Published: 2026-10-26T19:15:53Z Content type: release Language: en Sources: [GitHub Changelog]() Topics: [GitHub Copilot](), [agentic-coding](), [GitHub Copilot CLI]() Tags: [agentic](), [agentic-coding](), [billing](), [c-sharp](), [cli](), [cloud-agent](), [coding](), [copilot](), [cost](), [everyday](), [github](), [github-copilot](), [github-copilot-app](), [gpt-6-1](), [gpt-6-1-sol](), [gpt-6-1-terra](), [model](), [openai](), [release](), [terminal](), [terra]() ### AI overview GPT-6.1 Terra is generally available in GitHub Copilot for everyday agentic coding and terminal work, with focused steps for well-scoped tasks. Early testing found it solved noticeably more terminal and C# coding tasks than GPT-5.6 Terra; the excerpt gives no metrics. It costs less than GPT-6.1 Sol and uses provider list pricing under usage-based billing. It is offered to Pro, Pro+, Max, Business, and Enterprise users across the listed Copilot interfaces, with gradual rollout. Business and Enterprise administrators can manage access through model policy settings; new models are enabled by default unless the global default is off or Terra is explicitly disabled. ### Source excerpt GPT-6.1 Terra, OpenAI's newest model, is now generally available in GitHub Copilot. It is designed for everyday agentic coding and terminal work at a lower cost than GPT-6.1 Sol. In... The post GPT-6.1 Terra in GitHub Copilot appeared first on The GitHub Blog. ## MCP C# SDK 2.0 Makes HTTP Stateless by Default and Adds Multi Round-Trip Requests DevFeed: [MCP C# SDK 2.0 Makes HTTP Stateless by Default and Adds Multi Round-Trip Requests]() Original publisher: [Read original article]() Author: Edin Kapić Published: 2026-10-26T08:00:00Z Content type: release Language: en Sources: [InfoQ]() Topics: [MSP MCP](), [SDK](), [HTTP]() Tags: [2026](), [c-sharp](), [context](), [development](), [discovery](), [headers](), [http](), [mcp](), [mcp-csharp-sdk-stateless](), [microsoft](), [model](), [model-context-protocol](), [model-context-protocol-mcp](), [net](), [news](), [oauth](), [protocol](), [releases](), [revision](), [routing](), [sdk](), [servers](), [stateless](), [subscriptions](), [version]() ### AI overview MCP C# SDK 2.0 adopts the 2026-07-28 protocol revision, making Streamable HTTP stateless by default and replacing the initialization handshake and session ID with per-request protocol metadata. Standardized routing headers let infrastructure route calls without inspecting bodies, while the body remains authoritative and mismatches return `HeaderMismatch`. Multi Round-Trip Requests let tools request client input and resume calls with responses; `McpClient` handles this automatically when handlers are registered. Stateful sessions can bridge older clients, while stateless connections to older clients surface an `McpException`. Stateful servers must opt out of the new default. Later 2.1-2.3 releases added hybrid session modes, an optional notification-stream handler, and discovery, OAuth, and shutdown fixes. The excerpt also notes a compatibility break for Tasks, moved to an opt-in package, and warns that `McpClient.ServerInfo` is now nullable; self-reported identity should not inform security decisions. Silent long-running handlers may need progress output or longer HTTP timeouts. ### Source excerpt Microsoft announced version 2.0 of the official MCP C# SDK, which implements the 2026-07-28 revision of the Model Context Protocol with stateless HTTP servers by default, standardised routing headers and Multi Round-Trip Requests. Releases 2.1 to 2.3 have since added hybrid session serving, a subscriptions/listen handler and a series of discovery, OAuth and shutdown fixes. By Edin Kapić ## Setting up Swamp in a C# and Unity shop - reset.dev DevFeed: [Setting up Swamp in a C# and Unity shop - reset.dev]() Original publisher: [Read original article]() Author: reset Published: 2026-10-23T23:14:07Z Content type: tutorial Language: en Sources: [Swamp Club Feed]() Topics: [developer setup](), [Developer experience](), [workflow automation](), [TypeScript](), [C#](), [Unity]() Tags: [agent-harness](), [ai-tool](), [api-key](), [audit](), [auth](), [automation](), [behavior](), [behaviors](), [browser](), [building](), [c-sharp](), [cli](), [game](), [setup](), [swamp](), [telemetry](), [tools](), [transparency](), [typescript](), [unity](), [workflow]() ### AI overview In a C# and Unity studio, Swamp provided auditable behavior runs that retain results and record who initiated them, with workflow runs tagging records by run. Setup had practical friction: Homebrew 7 required trusting the tap, browser sign-in needed a real terminal, and workflow examples needed object-form `dependsOn` entries and an `expr` assert field; validation returned a Zod stack trace where run gave clearer feedback. Because `swamp repo init` can install skills globally and configure an agent, the author used `--tool none` and kept skills in one repository. A blocked-command telemetry check found command path, argument names, result metadata, version and environment details, but no file contents or stdout. The studio keeps Swamp in an operations repository and is building extensions for game and studio tools. These are first-day findings from the supplied excerpt. ### Source excerpt A developer documents the first-day experience configuring Swamp, a TypeScript-based automation CLI, in a C# and Unity game studio, covering installation quirks, behavior and workflow setup, agent scoping with --tool none, and telemetry transparency. ## JetBrains GameDev Day 2026: Watch the Recordings DevFeed: [JetBrains GameDev Day 2026: Watch the Recordings]() Original publisher: [Read original article]() Author: Anna Ruban Published: 2026-10-23T15:04:27Z Content type: news Language: en Sources: [JetBrains](), [TeamCity]() Topics: [Game Development](), [Developer Events](), [Tool](), [Learning]() Tags: [2026](), [agentic](), [ai](), [ai-generated-code](), [automation](), [aws](), [c-plus-plus](), [c-sharp](), [conference](), [development](), [game-developement](), [gamedev](), [gamedev-day](), [jetbrains](), [net-tools](), [open-source](), [recordings](), [rider](), [sessions](), [talks](), [teamcity-2](), [technical](), [tools](), [watch](), [youtube]() ### AI overview Recordings from JetBrains GameDev Day 2026 are available on YouTube, with sessions covering production workflows across Unreal Engine, Unity, Godot, and game infrastructure. Examples include migrating a live game toward a hybrid ECS and legacy engine, profiling Unreal performance with Unreal Insights and Rider, and using an AI agent over MCP to automate parts of Figma-to-Unity UI integration while identifying tasks that still need human input. Other talks demonstrated TeamCity CI workflows from the development environment, prompt-driven Godot world generation that combines AI configurations with procedural techniques, agentic Unreal development, and debugging C# and C++ runtimes together. Epic's open-source Lore VCS was presented as splitting large assets into content-addressable fragments so only changed portions need to move; the speakers also covered on-demand edge caches and self-deployment through AWS tooling. ### Source excerpt Missed JetBrains GameDev Day 2026, or want to revisit your favorite sessions? All the recordings are now available on YouTube! On September 28, we brought together game developers, engineers, and industry experts for a full day of technical talks, live demos, and discussions about the tools and challenges shaping modern game development. From Epic's open-source [...] ## What Is the Python Global Interpreter Lock (GIL)? DevFeed: [What Is the Python Global Interpreter Lock (GIL)?]() Original publisher: [Read original article]() Author: Abhinav Ajitsaria Published: 2026-10-23T14:00:00Z Content type: article Language: en Sources: [Real Python]() Topics: [locking](), [Python](), [Process](), [scheduling]() Tags: [acquisition](), [architecture](), [argument](), [bugs](), [build](), [bytecode](), [c](), [c-sharp](), [code](), [collection](), [compilers](), [core](), [cpu](), [cpython](), [gil](), [interpreter](), [mutex](), [performance](), [python](), [thread]() ### AI overview CPython's GIL protects shared reference counts with one interpreter-wide lock, but it allows only one thread to execute Python bytecode at a time. That makes CPU-bound multithreaded work unable to use multiple cores and can add lock overhead; I/O-bound threads are less affected, though older GIL scheduling could starve them. The text compares multiprocessing, which enables parallel execution at the cost of process overhead and separate memory, with subinterpreters, which provide per-interpreter GILs and isolation within one process. It also notes that GIL behavior differs among Python implementations. Free-threaded CPython builds are available from Python 3.13 and officially supported in 3.14, but remain optional, and extensions must declare compatibility or the GIL is re-enabled. The default CPython build still uses the GIL. ### Source excerpt The Python GIL is a mutex that lets only one thread control the interpreter at a time. Learn how it shapes your program's performance. ## Skipping domain reload: faster iteration using the MethodReload feature DevFeed: [Skipping domain reload: faster iteration using the MethodReload feature]() Original publisher: [Read original article]() Author: Théo Richart; Mike Geig Published: 2026-10-22T00:00:00Z Content type: article Language: en Sources: [Unity]() Topics: [Programming](), [Tool](), [iteration](), [Framework](), [CI/CD]() Tags: [agent](), [api](), [apis](), [applications](), [arrays](), [asset](), [assets](), [await](), [backend](), [build](), [builds](), [bytecode](), [c-sharp](), [domain](), [faster](), [feature](), [iteration](), [net](), [reload](), [unity]() ### AI overview MethodReload speeds iteration by interpreting updated bodies of tagged methods in a running Unity Editor or development player, including IL2CPP builds, avoiding a full domain reload for those edits. The experimental package requires Unity 6.0+; tagged public methods must return void or IEnumerator, with tags present before Play Mode or player build. Its interpreter supports a C# subset, cannot alter fields, call sites, or type layout, and runs slower than compiled code during development. On devices, reloaded code can call only APIs retained in the build. Existing Asset Store hot reload tools offer full C# and a mature Mono Editor workflow, but cannot patch IL2CPP; .NET Hot Reload targets CoreCLR, not Unity Mono or IL2CPP. Larger changes still require normal compilation and reload. ### Source excerpt Stop waiting on domain reloads! Learn how MethodReload speeds up Unity iteration time, explore its limitations, and compare it to existing hot reload tools. ## C# 15 Union Types for API Results: Examples, Trade-Offs, and Migration DevFeed: [C# 15 Union Types for API Results: Examples, Trade-Offs, and Migration]() Original publisher: [Read original article]() Author: Arunachalam Kandasamy Raja Published: 2026-10-21T14:17:46Z Content type: article Language: en Sources: [Syncfusion]() Topics: [union types](), [ASP.NET]() Tags: [api](), [asp-net-core](), [business](), [c-sharp](), [c-sharp-15](), [c-sharp-15-union-types](), [c-sharp-discriminated-unions](), [c-sharp-result-pattern](), [c-sharp-union-types](), [c-sharp-union-types-in-asp-net-core](), [cases](), [compare](), [compatibility](), [compilation](), [compiler](), [examples](), [microsoft](), [migration](), [net-11](), [net-development](), [net-development-asp-net-core-c-sharp-software-architecture-web-platform-apis-what-s-new](), [net-sdk](), [results](), [software-architecture](), [software-development](), [types](), [union](), [union-types](), [web-api](), [web-platform-apis](), [what-s-new]() ### AI overview C# 15 union types represent a fixed set of result cases and let the compiler flag unhandled cases in switch expressions. In the ASP.NET Core example, a service returns distinct order outcomes while a controller maps them to HTTP responses, keeping business logic separate from HTTP handling. Unions suit closed sets of expected outcomes; interfaces better fit extensible implementations, and an established Result may already meet a project's needs. Generated unions store cases through object?, so value types may box; the text recommends measuring performance-sensitive use. JSON deserialization can be ambiguous when structural case shapes overlap, and explicit polymorphic serialization may suit APIs needing a stable discriminator. Because unions are preview features in the C# 15/.NET 11 development cycle, migration guidance is to update internal consumers first and check response contracts, OpenAPI, generated clients, and serialized or persisted data before removing an old result model. ### Source excerpt Learn how C# 15 union types simplify ASP.NET Core API results, compare with existing C# patterns, and help you decide when to adopt them. ## RocketWerkz' C# framework 'BRUTAL' is now available to all developers DevFeed: [RocketWerkz' C# framework 'BRUTAL' is now available to all developers]() Original publisher: [Read original article]() Author: Bryant Francis Published: 2026-10-19T20:57:38Z Content type: news Language: en Sources: [Game Developer]() Topics: [Game engine](), [Minetest]() Tags: [c-plus-plus](), [c-sharp](), [game](), [godot](), [net]() ### AI overview RocketWerkz and Ahwoo have released BRUTAL, an open-source C# and .NET framework with C++ libraries and low-level graphics access for developers building their own game development tools or engines. It is free for commercial games, with attribution and an in-game logo required. The article discusses the appeal and added complexity of this approach compared with third-party engines, and cites Rimworld's port to a custom engine powered by BRUTAL. ### Source excerpt Developers who want to complete control over their game's code have a new framework to lean on. ## Get Your .NET MAUI App Ready for Xcode 27 DevFeed: [Get Your .NET MAUI App Ready for Xcode 27]() Original publisher: [Read original article]() Author: Gerald Versluis Published: 2026-10-19T16:05:00Z Content type: tutorial Language: en Sources: [.NET Blog]() Topics: [.NET MAUI](), [Xcode](), [.NET](), [Agent Skills](), [XcodeGen](), [Continuous Delivery (CD)]() Tags: [activation](), [agent](), [agent-skill](), [agent-skills](), [apple](), [authentication](), [build](), [c-sharp](), [cli](), [code](), [coding-agent](), [command-line](), [content](), [ios](), [lifecycle](), [mac-catalyst](), [net](), [net-10](), [net-for-ios](), [net-maui](), [net-maui-cli](), [net-sdk](), [scene-lifecycle](), [uikit](), [xcode](), [xcode-27]() ### AI overview This tutorial explains how to migrate an existing .NET MAUI app for Xcode 27's UIKit scene lifecycle requirement. It covers matching SDK and workload versions, adding scene delegates and plist configuration, preserving custom lifecycle behavior such as authentication and deep links, adjusting deployment targets, and testing the migration on iOS 27 and Mac Catalyst. ### Source excerpt Use an agent skill to prepare your existing .NET MAUI app for Xcode 27, with the scene lifecycle changes and manual migration steps explained. The post Get Your .NET MAUI App Ready for Xcode 27 appeared first on .NET Blog. ## Bring Your Own Model to the GitHub Copilot SDK with C# DevFeed: [Bring Your Own Model to the GitHub Copilot SDK with C#]() Original publisher: [Read original article]() Author: Bruno Capuano Published: 2026-10-19T16:00:00Z Content type: tutorial Language: en Sources: [.NET Blog]() Topics: [GitHub Copilot SDK](), [SDK](), [GitHub Copilot](), [Chat completions endpoints](), [litellm]() Tags: [agent-harness](), [agent-harnesses](), [ai](), [api](), [azure](), [azure-openai](), [byok](), [c-sharp](), [copilot](), [csharp](), [dotnet](), [github-copilot-sdk](), [microsoft-foundry](), [net](), [runtime]() ### AI overview This tutorial shows how to use the GitHub Copilot SDK runtime with a model provider you control. Its .NET 10 sample configures Microsoft Foundry or Azure OpenAI, supports Microsoft Entra ID or an API key, and demonstrates a minimal session that sends a model request. ### Source excerpt The GitHub Copilot SDK gives your application an agent runtime. BYOK lets you keep that runtime while sending model requests to your own Microsoft Foundry or Azure OpenAI deployment. Here is the complete C# setup. The post Bring Your Own Model to the GitHub Copilot SDK with C# appeared first on .NET Blog. ## JetBrains .NET Day Online 2026: Watch the Recordings DevFeed: [JetBrains .NET Day Online 2026: Watch the Recordings]() Original publisher: [Read original article]() Author: Mehul Harry Published: 2026-10-19T08:00:00Z Content type: news Language: en Sources: [JetBrains]() Topics: [deveco](), [.NET](), [AI Chat](), [LLM security](), [Legacy Modernization](), [Container Image Building](), [Deployment Strategies](), [asyncapi supply chain attack](), [native aot]() Tags: [2026](), [agent](), [agents](), [ai](), [ai-development](), [api](), [blog-post](), [build](), [c-sharp](), [container](), [container-apps](), [containers](), [dashboard](), [data-api-builder](), [deployment](), [events](), [jetbrains](), [net](), [net-days-online](), [resharper](), [rider]() ### AI overview JetBrains .NET Day Online 2026 recordings are available on YouTube. The event recap highlights sessions on AI-assisted development with JetBrains tools, distributed .NET patterns, C# performance, AI development workflows, software supply-chain security, modular monoliths, .NET interoperability, SQL MCP Server, and scaling Blazor workloads with .NET Aspire and Azure Container Apps. ### Source excerpt Every session from October 7 is now on YouTube. .NET Day Online 2026 took place on October 7. Thanks to everyone who watched the livestream and asked questions in the chat! If you missed a session, or want to watch one again, all of them are now online. Watch the full playlist Here's a quick [...] ## .NET 11 Release Candidate 2: Go-Live License and Updates Across Libraries, F#, MAUI, and WinForms DevFeed: [.NET 11 Release Candidate 2: Go-Live License and Updates Across Libraries, F#, MAUI, and WinForms]() Original publisher: [Read original article]() Author: Almir Vuk Published: 2026-10-19T08:00:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [.NET](), [version](), [Cryptography](), [Continuous Delivery (CD)](), [C#](), [.NET MAUI](), [WinForms]() Tags: [c-sharp](), [candidate](), [cryptography](), [development](), [dotnet-11-rc-2](), [libraries](), [net](), [net-10](), [net-11](), [net-9](), [net-maui](), [news](), [nuget](), [post-quantum](), [quantum](), [release](), [visual-studio](), [winforms]() ### AI overview Microsoft released .NET 11 Release Candidate 2 under a go-live license, with support in Visual Studio 2026 Insiders and VS Code with the C# Dev Kit. The release includes library, runtime, SDK, NuGet, F#, ASP.NET Core, .NET MAUI, and Windows Forms changes, including experimental post-quantum cryptography APIs, file-based app directive improvements, NuGet package cooldowns, and a C# UI option for MAUI. ### Source excerpt Microsoft has released .NET 11 Release Candidate 2 under a go-live license, supported in Visual Studio 2026 Insiders. The release adds incremental CBOR reading, experimental post-quantum cryptography APIs, file-based app directive improvements, NuGet package cooldowns, F# runtime async building blocks, a C# UI option for .NET MAUI, and refined Windows Forms visual styles. By Almir Vuk [Next page]()