tizen-dotnet-debug
Tizen DotNET debug, tizen dotnet debug, 타이젠 닷넷 디버깅, netcoredbg, C# 디버깅, .NET 원격 디버깅, NUI 앱 디버그. Use this skill for automated remote debugging of Tizen .NET apps ONLY with netcoredbg — device check, on-demand debugger install, app start, PID lookup, and either an interactive CLI attach command or a VS Code DAP server. NEVER use for WebApp (.wgt) projects — web apps have no CoreCLR process and the script will refuse them.
Samsung Electronics · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add Samsung/tizen-agent-skills --skill tizen-dotnet-debugAbout this skill
name: tizen-dotnet-debug description: Tizen DotNET debug, tizen dotnet debug, 타이젠 닷넷 디버깅, netcoredbg, C# 디버깅, .NET 원격 디버깅, NUI 앱 디버그. Use this skill for automated remote debugging of Tizen .NET apps ONLY with netcoredbg — device check, on-demand debugger install, app start, PID lookup, and either an interactive CLI attach command or a VS Code DAP server. NEVER use for WebApp (.wgt) projects — web apps have no CoreCLR process and the script will refuse them. metadata: author: Samsung Electronics last-updated: "2026-07-16" keywords: - Tizen dotnet debug - netcoredbg - C# debug - .NET remote debug - 타이젠 닷넷 디버깅 - NUI 디버그 - coreclr debug
Do NOT use for Web apps (IMPORTANT)
Never run this flow for a WebApp (.wgt) project, even if the user asks to "debug the app". Web apps run inside the web runtime — there is no CoreCLR process for netcoredbg to attach to, and the script auto-detects wgt packages on the device and refuses them with an error. When the project is a WebApp:
- Do not attempt
tizen-dotnet-debugortizen-gdb-debugat all. - Use the
tizen-webapp-debugskill instead — it sets up RWI/CDP (Chrome DevTools Protocol) debugging and returns a ready CDP endpoint. - Determine the project type first (
config.xmlpresent → WebApp;tizen-manifest.xml→ Native;.csproj→ DotNET) before choosing a debug flow.
Claude Code (서브에이전트 위임)
Agent tool이 없으면 (예: Cline) 아래 "CLI Runner" 섹션으로 가세요.
- Agent tool로
tizen-dotnet-debug에이전트 호출 (개인 배포 또는tizen-sdk-skills:tizen-dotnet-debug) - 수집된 입력(App ID, 모드, 브레이크포인트)을 프롬프트로 전달
- 서브에이전트의 JSON Envelope를 그대로 사용자에게 전달 — 아래 "결과 보고" 규칙을 따른다
(fenced
json블록으로 원문을 싣고, 그 아래 요약은 1~2줄만)
CLI Runner (Cline / Claude Code)
Pick the ONE block for the shell your terminal / tool runs — the prompt tells you: $ is Bash (Linux, macOS, Claude Code's Git Bash on Windows, Codex on Linux / macOS) → Bash block; PS C:\…> is PowerShell (Codex on Windows, Cline PowerShell terminal) → PowerShell block; C:\…> is cmd.exe (Cline cmd.exe terminal) → cmd.exe block. Run that block as-is: a block pasted into another shell, or wrapped in powershell -Command "…", is a parse error.
Run the node line exactly as written and read the JSON envelope it prints to stdout. Do NOT redirect or capture the output (> file, 2>&1 | tee, Out-File, | Out-String), do NOT wrap the line in cmd /c, powershell -Command "…" or any second shell, and do NOT mix shell dialects: %TEMP% and 2>nul are cmd.exe only, $env:TEMP and Out-File are PowerShell only — in the other shell they are literal text or a parse error. A tool message that the command's completion or output "could not be observed / captured" means the terminal is still busy with an earlier command or its shell-integration hooks have broken, not that the runner failed: open a NEW terminal and re-run the SAME line unchanged. Runners that drive em-cli, sdb or a JVM can take 10–30 s and print the envelope only when they exit — wait for it rather than retrying with a redirect.
Bash — Linux / macOS / Ubuntu, and Windows Git Bash (Claude Code):
BASE="$HOME/.cline"; [ -z "${CODEX_THREAD_ID:-}${CODEX_SANDBOX_NETWORK_DISABLED:-}${CODEX_SANDBOX:-}${CODEX_VERSION:-}" ] || BASE="$HOME/.codex"; [ -z "${GEMINI_CLI:-}" ] || BASE="$HOME/.gemini"; [ -z "${CLAUDECODE:-}" ] || BASE="$HOME/.claude"
_tz_o=; [ -z "${ZSH_VERSION:-}" ] || { [[ ! -o nomatch ]] || _tz_o=1; unsetopt nomatch; }; _tz_s=; CLI=; for _tz_d in "$BASE" "$HOME"/.claude "$HOME"/.cline "$HOME"/.codex "$HOME"/.gemini; do [ "$_tz_d" != "$BASE" ] || [ -z "$_tz_s" ] || continue; _tz_s=1; for _tz_f in "$_tz_d"/plugins/cache/tizen-platform/tizen-sdk-skills/*/lib/cli/dotnet-debug-cli.js; do [ -f "$_tz_f" ] || continue; _tz_v=${_tz_f#"$_tz_d"/plugins/cache/tizen-platform/tizen-sdk-skills/}; _tz_v=${_tz_v%%/*}; case $_tz_v in *[!0-9.]*|.*|*.|*..*|*.*.*.*) continue ;; *.*.*) ;; *) continue ;; esac; _tz_a=${_tz_v%%.*}; _tz_c=${_tz_v##*.}; _tz_b=${_tz_v#*.}; _tz_b=${_tz_b%.*}; if [ -z "$CLI" ] || [ "$_tz_a" -gt "$_tz_A" ] || { [ "$_tz_a" -eq "$_tz_A" ] && { [ "$_tz_b" -gt "$_tz_B" ] || { [ "$_tz_b" -eq "$_tz_B" ] && [ "$_tz_c" -gt "$_tz_C" ]; }; }; }; then CLI=$_tz_f; _tz_A=$_tz_a; _tz_B=$_tz_b; _tz_C=$_tz_c; fi; done; [ -z "$CLI" ] || break; done; unset _tz_s _tz_d _tz_f _tz_v _tz_a _tz_b _tz_c _tz_A _tz_B _tz_C; [ -z "$_tz_o" ] || setopt nomatch; unset _tz_o
node "$CLI" <appId> [launch|attach|-] "File.cs:line" <port> <serial>
PowerShell (Codex CLI on Windows, Cline PowerShell terminal) — prefers this harness's own cache, then the newest version. Run all three lines below, in order, in the SAME PowerShell session: the node line needs the $CLI the lookup line sets (on its own, node "$CLI" … becomes node <first-arg> and fails with a misleading MODULE_NOT_FOUND), so it carries a guard that stops with a clear message when $CLI is empty. Never wrap the lines in powershell -Command "…" (PowerShell and Git Bash expand $h, $CLI and $env:… before the inner shell runs, so the lookup arrives empty):
$h = ".cline"; if ($env:CODEX_THREAD_ID -or $env:CODEX_SANDBOX_NETWORK_DISABLED -or $env:CODEX_SANDBOX -or $env:CODEX_VERSION) { $h = ".codex" }; if ($env:GEMINI_CLI) { $h = ".gemini" }; if ($env:CLAUDECODE) { $h = ".claude" }
$CLI = $null; foreach ($d in @($h, ".claude", ".cline", ".codex", ".gemini")) { $CLI = Get-ChildItem "$env:USERPROFILE\$d\plugins\cache\tizen-platform\tizen-sdk-skills\*\lib\cli\dotnet-debug-cli.js" -ErrorAction SilentlyContinue | Sort-Object { [version]$_.Directory.Parent.Parent.Name }, FullName | Select-Object -Last 1 -ExpandProperty FullName; if ($CLI) { break } }
if (-not $CLI) { throw 'tizen-sdk-skills runner not found: $CLI is empty. Run the two lookup lines above in THIS PowerShell session first; if they still find nothing, the tizen-sdk-skills plugin is not installed.' }; node "$CLI" <appId> [launch|attach|-] "File.cs:line" <
Read the complete source ↗