skills.rest
kierunb
kierunbCOMMUNITY
Explore all skills by this author →
GitHub

clr-activation-debugging

Analyze CLRLoad logs to diagnose CLR activation issues.

Updated Mar 19, 2026
Search Tags:#debugging#troubleshooting#logs#dotnet-framework#clr-activation#metahost#com-activation
One-click install
npx skills add https://github.com/kierunb/ReliableAppDemo --skill clr-activation-debugging-kierunb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clr-activation-debugging
Source: https://github.com/kierunb/ReliableAppDemo/tree/main/.github/skills/dotnet-diag/skills/clr-activation-debugging
Command: npx skills add https://github.com/kierunb/ReliableAppDemo --skill clr-activation-debugging-kierunb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnoses CLR activation issues by analyzing CLRLoad logs produced by mscoree.dll. It helps identify why the Shim chose the wrong runtime, failed to load any runtime, or displayed unexpected .NET 3.5 FOD dialogs, including scenarios with mixed v2/v4 runtimes.

Core Features & Use Cases

  • Analyzes CLRLoad logs to reveal activation decisions, runtime selection, and errors
  • Guides debugging for scenarios like mixed v2/v4 runtimes and COM activation paths
  • Provides actionable steps to remediate configuration or runtime installation issues

Quick Start

Analyze the provided CLRLoad logs to identify activation problems and recommended fixes.

Frequently Asked Questions about clr-activation-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug CLR activation issues from CLRLoad logs?▼

Debug CLR activation issues by analyzing CLRLoad logs produced by mscoree.dll to reveal runtime selection decisions, entry points, and version resolution errors to guide remediation.

Why does the Shim fail to load a runtime or select the wrong .NET Framework version?▼

The Shim selects the wrong runtime or fails to load due to config processing errors or mixed v2/v4 runtimes, which can be identified by interpreting CLR activation logs.

What causes unexpected .NET 3.5 FOD dialogs during COM activation?▼

Unexpected .NET 3.5 FOD dialogs during COM activation occur when the system attempts to load a missing runtime, detectable by analyzing CLR activation log outcomes.

How do I troubleshoot mixed v2 and v4 runtime loading problems?▼

Troubleshoot mixed v2/v4 runtime loading by analyzing CLRLoad logs to detect version resolution outcomes and activation decisions, providing actionable steps to remediate configuration issues.

Can I diagnose COM activation failures when the CLR shim cannot find a runtime?▼

Yes, you can diagnose COM activation failures by interpreting CLRLoad logs to detect entry points and version resolution outcomes when the Shim fails to load any runtime.

Related Skills

Explore More Software Engineering Skills→
dotnetdotnet
5.1k

clr-activation-debugging

Analyze CLR activation logs to diagnose .NET Framework runtime loading failures.

Official
Advanced
alter123-zzalter123-zz
18

qclaw-env

Diagnose and remediate missing CLI tools, runtimes, and package managers on macOS and Windows.

Community
Advanced
software-mansionsoftware-mansion
1.9k

argent-metro-debugger

Debugs React Native apps via Metro and CDP connections.

Official
Advanced
1k-off1k-off
1

clr-activation-debugging

Diagnose .NET Framework CLR activation issues from mscoree.dll CLRLoad logs.

Community
Advanced