Infra, Ops & WorkflowSûr100100/100

Vsintegration Ide Debugging (.NET)

Fix F# debugging issues (breakpoints, .pdb, sequence points). Build, run VS integration tests, inspect IL/PDB.

ou envoie-le directement à ton agent.

Installer dans ton projet

$ curl -fsSL https://arboristhree.xyz/cli/install-skill.mjs -o /tmp/arboris-install-skill.mjs && node /tmp/arboris-install-skill.mjs vsintegration-ide-debugging__dotnet-dotnet__src-fsharp-github-skills-9ddd30eb8427
.NET
dotnet/dotnet
Contenu à copier
---
name: vsintegration-ide-debugging
description: Fix F# debugging issues (breakpoints, .pdb, sequence points). Build, run VS integration tests, inspect IL/PDB.
metadata:
  origin: .NET
---

# VS Integration Debugging

## Build
`.\Build.cmd -c Debug`

## Run tests
xUnit2 VS Extensibility — not `dotnet test`.
```powershell
$runner = (Get-ChildItem "$env:NUGET_PACKAGES\xunit.runner.console" -Recurse -Filter xunit.console.exe | Where-Object { $_.FullName -like '*net472*' } | Select-Object -First 1).FullName
& $runner artifacts\bin\FSharp.Editor.IntegrationTests\Debug\net472\FSharp.Editor.IntegrationTests.exe -parallel none -nologo
```

## Key paths
- Tests + infra: `vsintegration/tests/FSharp.Editor.IntegrationTests/`
- Sequence point emit: `src/Compiler/CodeGen/IlxGen.fs` → `EmitDebugPoint`, `EnsureNopBetweenDebugPoints`
- PDB writer: `src/Compiler/AbstractIL/ilwritepdb.fs`
- Collection lowering: `src/Compiler/Optimize/LowerComputedCollections.fs`
- Local compiler setup: `UseLocalCompiler.Directory.Build.props`

## Core rule
VS debugger binds breakpoints only at **stack-empty** IL offsets. Move the sequence point — never add runtime instructions.
Colle ce Markdown dans ton agent ou utilise les boutons ci-dessus pour l’écrire dans ton projet.

Ce que fait Vsintegration Ide Debugging (.NET)

Tests + infra: `vsintegration/tests/FSharp.Editor.IntegrationTests/`
Sequence point emit: `src/Compiler/CodeGen/IlxGen.fs` → `EmitDebugPoint`, `EnsureNopBetweenDebugPoints`
PDB writer: `src/Compiler/AbstractIL/ilwritepdb.fs`
Collection lowering: `src/Compiler/Optimize/LowerComputedCollections.fs`

Comment utiliser Vsintegration Ide Debugging (.NET)

1
Copie le prompt
Un clic copie le prompt packagé (ou l'envoie à ton agent).
2
L'agent installe le skill
Il ajoute le SKILL.md et ses ressources à ton projet.
3
Activation automatique
Le skill s'active dès que le contexte correspond.

Déclencheurs pour Vsintegration Ide Debugging (.NET)

Dis simplement à ton agent quelque chose comme :

Applique le skill vsintegration-ide-debugging__dotnet-dotnet__src-fsharp-github-skills-9ddd30eb8427 à cette tâche
Utilise vsintegration-ide-debugging__dotnet-dotnet__src-fsharp-github-skills-9ddd30eb8427 pour améliorer cette implémentation
Passe en revue ce sujet avec vsintegration-ide-debugging__dotnet-dotnet__src-fsharp-github-skills-9ddd30eb8427

Skills liés à Vsintegration Ide Debugging (.NET)

Add CLI Command (.NET)
Add or change a dotnet CLI command, subcommand, or option across the relevant CLI projects. USE FOR: adding or changing a dotnet CLI command/subcommand, adding a new Option<T> or Argument<T>, registering a subcommand in the command tree, changing an option's help description or a command's runtime message, wiring a command parser, or updating --help output.
Add Dotnet Aot Command (.NET)
Add, enable, or review a dotnet CLI command or feature in the Native AOT CLI (src/Cli/dotnet-aot) and prove its compatibility. USE FOR: migrating a command or option to AOT, reviewing an AOT migration PR, defining conservative eligibility and managed fallback, changing AotSourceFiles.props or AotDependencies.props, validating AOT/managed parity, NativeAOT-publishing tests, checking binary-size impact, or using the dn harness and separated SDK layout. DO NOT USE FOR: resolving IL trim/AOT analyzer warnings alone (use dotnet-aot-compat), running dotnet.Tests incrementally (use incremental-test), or pure managed CLI work.
Add Net Analyzer (.NET)
Add, port, or change a .NET code analysis rule (CA####) under src/Microsoft.CodeAnalysis.NetAnalyzers. USE FOR: implementing a new CA analyzer and its code fixer, porting a rule or PR from the retired dotnet/roslyn-analyzers repo, allocating a diagnostic ID from DiagnosticCategoryAndIdRanges.txt, choosing RuleLevel/severity/category, wiring resx + xlf strings, recording the rule in AnalyzerReleases.Unshipped.md, regenerating the analyzer documentation/sarif files, and writing MSTest analyzer/code-fix tests with the VerifyCS/VerifyVB harness. DO NOT USE FOR: NETSDK#### MSBuild diagnostics (src/Tasks), CS####/BC#### compiler diagnostics or IDE#### analyzers (dotnet/roslyn), or CONTAINER#### diagnostics (src/Containers).