# .NET Framework .NET Framework is a Windows-only version of .NET for building client and server applications. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Centralize cross-account Amazon ECS telemetry with an ADOT gateway DevFeed: [Centralize cross-account Amazon ECS telemetry with an ADOT gateway]() Original publisher: [Read original article]() Author: Rahul Kumar Published: 2026-08-06T16:13:46Z Content type: tutorial Language: en Sources: [Containers]() Topics: [Amazon Elastic Container Service](), [telemetry](), [OpenTelemetry](), [SIEM, Security, Observability](), [Amazon CloudWatch](), [Amazon Web Services](), [Windows](), [.NET Framework](), [Traces](), [log management](), [Amazon Elastic Kubernetes Service]() Tags: [amazon-cloudwatch](), [amazon-eks](), [amazon-elastic-container-service](), [amazon-elastic-kubernetes-service](), [aws](), [intermediate-200](), [logs](), [metrics](), [net-framework](), [observability](), [opentelemetry](), [technical-how-to](), [telemetry](), [traces](), [windows]() ### AI overview This tutorial presents a centralized AWS Distro for OpenTelemetry gateway for collecting telemetry from Amazon ECS workloads across multiple AWS accounts. It replaces per-task sidecars, supports Windows .NET Framework tasks, receives OTLP over private connectivity, and exports traces to AWS X-Ray plus metrics and logs to Amazon CloudWatch. ### Source excerpt Running an OpenTelemetry collector as a sidecar in every Amazon ECS task does not scale across a multi-account estate, and it cannot run at all on Windows. Learn how to replace per-task sidecars with a single centralized ADOT gateway that ingests OTLP from workloads across accounts and exports traces to AWS X-Ray and metrics and logs to Amazon CloudWatch. ## Abusing .NET Core CLR Diagnostic Features (+ CVE-2023-33127) DevFeed: [Abusing .NET Core CLR Diagnostic Features (+ CVE-2023-33127)]() Original publisher: [Read original article]() Author: bohops Published: 2023-11-27T12:51:30Z Content type: article Language: en Sources: [Bohops]() Topics: [.NET](), [net core](), [.NET Framework](), [Windows](), [configuration](), [Microsoft](), [debugging](), [API]() Tags: [api](), [configuration](), [debugging](), [microsoft](), [net](), [net-core](), [net-framework](), [uncategorized](), [windows]() ### AI overview This article examines how diagnostic features of the .NET Common Language Runtime can be abused, focusing on open-source .NET on modern Microsoft Windows systems. It discusses runtime configuration knobs, registry and environment-variable settings, configuration files, and the CLR profiling API, with defensive guidance and mitigation information referenced at the end. ### Source excerpt Introduction Background .NET is an ecosystem of frameworks, runtimes, and languages for building and running a wide range of applications on a variety of platforms and devices. The .NET Framework was initially released in the early 2000s as Microsoft's implementation of the Common Language Infrastructure (CLI) specification. In 2016, Microsoft released .NET Core, the first [...] ## Windows Container on K8s Clusters DevFeed: [Windows Container on K8s Clusters]() Original publisher: [Read original article]() Author: Sebastián Gómez Published: 2021-12-03T09:27:27Z Content type: tutorial Language: en Sources: [Blog - Container Solutions]() Topics: [Kubernetes](), [Containers](), [Windows](), [.NET Framework](), [Amazon EKS](), [Docker](), [Selenium](), [Tool](), [PowerShell](), [Package manager](), [Spring Boot](), [Java]() Tags: [build](), [containers](), [docker](), [java](), [kubernetes](), [net-framework](), [nuget](), [powershell](), [selenium](), [spring-boot](), [windows]() ### AI overview This article describes a cloud migration scenario involving Windows containers and a .NET Framework 4.8 UI-testing application that uses Selenium to start a browser. It also discusses bringing Docker images into a managed Kubernetes cluster on Amazon EKS, alongside existing React/Redux and Java Spring Boot applications. ### Source excerpt I recently came across a fun and interesting challenge. In the latest project I joined, a team wanted to do a "lift & shift to the cloud". As a Cloud Native engineer I've seen this pattern fairly often, although it never means quite the same thing. ## Binding Redirects DevFeed: [Binding Redirects]() Original publisher: [Read original article]() Published: 2020-02-11T00:00:00Z Content type: tutorial Language: en Sources: [Nick Craver]() Topics: [.NET](), [net core](), [.NET Framework](), [migration](), [NuGet](), [Visual Studio]() Tags: [blog](), [compatibility](), [dependencies](), [framework](), [migration](), [net](), [net-core](), [net-framework](), [nuget](), [visual-studio]() ### AI overview This tutorial explains how .NET Framework assembly version conflicts produce load errors and build warnings. It recommends migrating to .NET Core as the long-term approach and describes binding redirects as the main fix for applications that remain on .NET Framework. ### Source excerpt This isn't part of the series on Stack Overflow's architecture, but is a topic that has bitten us many times. Hopefully, some of this information helps you sort out issues you hit. You're probably here because of an error like this: Could not load file or assembly 'System.<...>, Version=4.x.x.x, Culture=neutral, PublicKeyToken=<...>' or one of its dependencies. The system cannot find the file specified. And you likely saw a build warning like this: warning MSB3277: Found conflicts between different versions of "System.<...>" that could not be resolved. Whelp, you're not alone. We're thinking about starting a survivors group. The most common troublemakers here are: System.Memory (NuGet link) System.Net.Http (NuGet link) System.Numerics.Vectors (NuGet link) System.Runtime.CompilerServices.Unsafe (NuGet link) System.ValueTuple (NuGet link) If you just want out of this fresh version of DLL Hell you've found yourself in... The best fix The best fix is "go to .NET Core". Since .NET Framework (e.g. 4.5, 4.8, etc.) has a heavy backward compatibility burden, meaning that the assembly loader itself is basically made of unstable plutonium with a hair trigger coated in flesh eating bacteria behind a gate made of unobtanium above a moat of napalm filled with those jellyfish that kill you...that won't ever really be fixed. However, .NET Core's simplified assembly loading means it just works. I'm not saying a migration to .NET Core is trivial, that depends on your situation, but it is generally the best long-term play. We're almost done porting Stack Overflow to .NET Core, and this kind of pain is one of the things we're very much looking forward to not fighting ever again. The fix if you're using .NET Framework The fix for .NET Framework is "binding redirects". When you are trying to load an assembly (and if it's strongly named, like the ones in the framework and many libs are), it'll try to load the specific version you specified. Unless it's told to load another (likely newer) version. T ## Why you should wait on upgrading to .Net 4.6 DevFeed: [Why you should wait on upgrading to .Net 4.6]() Original publisher: [Read original article]() Published: 2015-07-27T00:00:00Z Content type: article Language: en Sources: [Nick Craver]() Topics: [.NET Framework](), [bug](), [JIT](), [Compiler](), [Microsoft](), [Stack Overflow]() Tags: [blog](), [bug](), [compiler](), [jit](), [microsoft](), [net-framework]() ### AI overview The article warns against upgrading to .NET Framework 4.6 because a bug in the 64-bit RyuJIT implementation can cause methods to receive parameter values different from those passed. Microsoft later released a patch through Security Bulletin MS15-092 and KB3086251. ### Source excerpt Update (August 11th): A patch for this bug has been released by Microsoft. Here's their update to the advisory: We released an updated version of RyuJIT today, which resolves this advisory. The update was released as Microsoft Security Bulletin MS15-092 and is available on Windows Update or via direct download as KB3086251. The update resolves: CoreCLR #1296, CoreCLR #1299, and VisualFSharp #536. Major thanks to the developers who reported these issues. Thanks to everyone for their patience. Original Post What follows is the work of several people: Marc Gravell and I have taken lead on this at Stack Overflow and we continue to coordinate with Microsoft on a resolution. They have fixed the bug internally, but not for users. Given the severity, we can't in good conscience let such a subtle yet high-impact bug linger silently. We are not upgrading Stack Overflow to .Net 4.6, and you shouldn't upgrade yet either. You can find the issue we opened on GitHub (for public awareness) here. A fix has been released, see Update 5 below. Update #1 (July 27th): A pull request has been posted by Matt Michell (Microsoft). Update #2 (July 28th): There are several smaller repros now (including a small console app). Microsoft has confirmed they are working on an expedited hotfix release but we don't have details yet. Update #3 (July 28th): Microsoft's Rich Lander has posted an update: RyuJIT Bug Advisory in the .NET Framework 4.6. Update #4 (July 29th): There's another subtle bug found by Andrey Akinshin and the F# Engine Exception is confirmed to be a separate issue. I still recommend disabling RyuJIT in production given the increasing bug count. Update #5 (August 11th): A patch for this bug has been released by Microsoft, see above. This critical bug is specific to .Net 4.6 and RyuJIT (64-bit). I'll make this big and bold so we get to the point quickly: The methods you call can get different parameter values than you passed in. The JIT (Just-in-Time compiler) in .Net (and many platfo ## Fixing Rubygems Certificates DevFeed: [Fixing Rubygems Certificates]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2013-11-28T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [.NET Framework](), [rubygems](), [SSL]() Tags: [certificates](), [error](), [issue](), [rubygems](), [ssl]() ### AI overview A brief troubleshooting post about resolving an SSL certificate error affecting a Rubygems-related development environment. ### Source excerpt Today, once again, my environment started throwing that SSL cert error. ## Apache: ograniczenie dostępu dla zalogowanych użytkowników z mod\_rewrite i mod\_auth\_basic DevFeed: [Apache: ograniczenie dostępu dla zalogowanych użytkowników z mod\_rewrite i mod\_auth\_basic]() Original publisher: [Read original article]() Author: Tom Published: 2012-09-09T00:00:00Z Content type: tutorial Language: pl Sources: [Tomasz Gągor]() Topics: [Mod\_rewrite](), [.NET Framework]() Tags: [apache](), [auth](), [debian](), [linux](), [login](), [mod-rewrite](), [rewrite](), [security](), [user]() ### AI overview This Polish tutorial explains how to use Apache mod_rewrite with mod_auth_basic to redirect authenticated users to directories named after their logins and prevent access to other users' directories. It describes comparing the URI login with the REMOTE_USER value using RewriteRule and RewriteCond backreferences. ### Source excerpt Niedawno trafiłem na ciekawy problem w mod_rewrite - by przekierowywać użytkowników logujących się jednym z modułów mod_auth_basic do dedykowanych im katalogów, równocześnie blokując dostęp do katalogów innych użytkowników. Nie brzmi to jakoś strasznie ale problem okazał się być całkiem nietrywialnym. Teoretyczne rozwiązanie sprowadzało się do wyszukania loginu użytkownika ze ścieżki URI i porównania z nazwą użytkownika ze zmiennej %{REMOTE_USER} - jeśli wartości się różnią to Forbidden. Ale szybko okazało się że w RewriteCond zmienne z dopasowań można podstawiać tylko w pierwszym parametrze i że o ile można RewriteCond'y połączyć wyrażeniami logicznymi typu AND/OR to nie ma możliwości porównania czy dopasowania z kolejnych RewriteCond'ów są identyczne. Po kilku dniach szperania w dokumentacji i różnych tutorialach udało mi się trafić na jedną wartościową wskazówkę ale tej stronki już nie ma, więc opiszę problem dla potomnych.