{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"vscode-awwsky-csharpfixformatfixed","slug":"cnet-compiler-aio-toolkit","name":"C#/.NET Compiler + AIO Toolkit","type":"extension","url":"https://marketplace.visualstudio.com/items?itemName=awwsky.csharpfixformatfixed","page_url":"https://unfragile.ai/cnet-compiler-aio-toolkit","categories":["code-editors"],"tags":["C#","csharp","format","sort","using"],"pricing":{"model":"freemium","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"vscode-awwsky-csharpfixformatfixed__cap_0","uri":"capability://code.generation.editing.using.directive.sorting.and.deduplication","name":"using directive sorting and deduplication","description":"Automatically organizes C# using statements in alphabetical order with configurable namespace grouping and duplicate removal. The extension parses the using block at the top of C# files, applies deterministic sorting rules based on the `dotnetaio.sort.usings.order` configuration (defaulting to System namespaces first), and optionally inserts blank lines between namespace groups when `dotnetaio.sort.usings.splitGroups` is enabled. This operates as a static text transformation without AST parsing, making it fast but limited to simple reordering.","intents":["I want to enforce consistent using statement ordering across my C# codebase to match team style guidelines","I need to remove duplicate using directives that accumulate during refactoring","I want using statements grouped by namespace (System first, then third-party, then project-specific) with visual separation"],"best_for":["C# developers working in teams with strict code style requirements","developers maintaining legacy C# codebases with inconsistent using statements","teams using VS Code without access to enterprise C# tooling like Resharper"],"limitations":["No AST-based understanding — cannot distinguish between using statements and using declarations (C# 8+)","Custom ordering requires manual configuration of namespace prefixes; no automatic detection of project-specific namespaces","Does not handle conditional using directives (#if/#endif) intelligently","Sorting is purely alphabetical; cannot implement semantic grouping (e.g., by assembly or dependency graph)"],"requires":["VS Code (version compatibility UNKNOWN due to deprecation status)","Active C# file (.cs extension) in editor","Setting `dotnetaio.sort.usings.enabled` must be true (default)"],"input_types":["C# source code (text)"],"output_types":["C# source code with reordered using statements (text)"],"categories":["code-generation-editing","code-formatting"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-awwsky-csharpfixformatfixed__cap_1","uri":"capability://code.generation.editing.indentation.normalization.and.fixing","name":"indentation normalization and fixing","description":"Scans C# source files line-by-line and corrects indentation levels based on code structure (blocks, nested scopes, preprocessor directives). The extension applies configurable rules via `dotnetaio.style.indent.*` settings to determine whether to indent preprocessor directives, region blocks, and switch-case labels. It operates as a regex or line-based transformation (not AST-aware), making it fast but unable to handle complex nesting or mixed-indentation scenarios accurately. Wrapped lines are processed with special handling to preserve logical continuation.","intents":["I want to fix inconsistent indentation across an entire C# file or project folder","I need to enforce a specific indentation style (e.g., 4 spaces vs tabs) consistently","I want to exclude preprocessor directives or region blocks from indentation to match legacy code style"],"best_for":["developers cleaning up indentation in legacy C# codebases with mixed styles","teams enforcing consistent indentation without relying on Roslyn or OmniSharp","developers who need lightweight, fast indentation fixes without full-project compilation"],"limitations":["Line-based processing cannot understand nested scope depth from AST; may produce incorrect indentation in complex scenarios (e.g., nested lambdas, LINQ chains)","No support for custom indentation rules beyond the predefined settings (preprocessor, region, switch-case)","Cannot detect or fix tab-vs-space inconsistencies within the same file","Wrapped lines are handled heuristically; may not preserve intended alignment for multi-line method calls or array initializers","No awareness of C# language features like expression-bodied members or pattern matching that affect logical indentation"],"requires":["VS Code (version compatibility UNKNOWN)","Active C# file (.cs extension)","Setting `dotnetaio.style.enabled` must be true (default)"],"input_types":["C# source code (text)"],"output_types":["C# source code with normalized indentation (text)"],"categories":["code-generation-editing","code-formatting"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-awwsky-csharpfixformatfixed__cap_10","uri":"capability://code.generation.editing.net.compilation.support.mechanism.unknown","name":".net compilation support (mechanism unknown)","description":"The extension claims to provide '.NET Compilation Support,' but the architectural analysis explicitly states 'This extension is not a compiler itself,' creating ambiguity about what compilation capability actually exists. The documentation does not specify whether the extension invokes an external compiler, provides compilation diagnostics, or merely claims compatibility with .NET projects. No configuration for targeting specific .NET versions or SDKs is documented, suggesting this capability may be aspirational or limited to project file recognition.","intents":["I want to compile C# code directly from VS Code using this extension","I need compilation diagnostics and error reporting integrated into the editor","I want to target specific .NET versions or frameworks (Unity, Godot, .NET Core, .NET Framework)"],"best_for":["developers who want lightweight compilation without external build tools","teams using VS Code who need basic compilation support"],"limitations":["Actual compilation capability is UNKNOWN; extension may not invoke a compiler at all","No configuration for .NET version targeting despite claims of .NET Core and .NET Framework support","No documented integration with MSBuild, dotnet CLI, or other compilation tools","Claims of Unity and Godot framework support are UNKNOWN in scope and reliability","No error reporting or diagnostics documented","Likely does not support incremental compilation or caching"],"requires":["VS Code (version compatibility UNKNOWN)","C# project files (.csproj, .sln) in workspace (UNKNOWN if extension reads these)",".NET SDK or runtime installed (UNKNOWN if required)"],"input_types":["C# source code and project files (text)"],"output_types":["Compilation diagnostics or compiled artifacts (UNKNOWN)"],"categories":["code-generation-editing","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-awwsky-csharpfixformatfixed__cap_2","uri":"capability://code.generation.editing.brace.style.reformatting.k.r.vs.allman","name":"brace style reformatting (k&r vs allman)","description":"Transforms opening brace placement in C# code between K&R style (opening brace on same line as declaration) and Allman style (opening brace on new line). Controlled by `dotnetaio.style.braces.onSameLine` (true = K&R, false = Allman) and `dotnetaio.style.braces.allowInlines` (permits single-line expressions like `if (x) { return; }`). The extension uses line-based pattern matching to detect brace positions and relocate them, without full AST parsing, making it fast but potentially fragile on complex or malformed code.","intents":["I want to enforce K&R brace style (opening brace on same line) across my C# project","I need to convert legacy Allman-style code to K&R to match team standards","I want to allow or disallow single-line brace expressions (e.g., `if (x) { return; }`) based on team preference"],"best_for":["C# teams with strict brace-style guidelines enforced via code review","developers migrating codebases between organizations with different style standards","teams using VS Code without access to Resharper or other enterprise formatters"],"limitations":["Regex-based brace detection may fail on edge cases: braces in strings, comments, or complex expressions","No understanding of context (e.g., cannot distinguish between method braces and lambda braces for different rules)","Single-line brace allowance is global; cannot apply different rules to different statement types (if vs for vs method declarations)","Does not handle brace placement in LINQ expressions, anonymous types, or other C# 3.0+ syntax correctly","May corrupt code if braces are malformed or nested in unexpected ways"],"requires":["VS Code (version compatibility UNKNOWN)","Active C# file (.cs extension)","Setting `dotnetaio.style.enabled` must be true (default)"],"input_types":["C# source code (text)"],"output_types":["C# source code with reformatted brace placement (text)"],"categories":["code-generation-editing","code-formatting"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-awwsky-csharpfixformatfixed__cap_3","uri":"capability://code.generation.editing.empty.line.cleanup.and.normalization","name":"empty line cleanup and normalization","description":"Removes excessive blank lines from C# source files and normalizes spacing to a configurable maximum (controlled by `dotnetaio.style.newline.*` settings, though specific setting name is UNKNOWN). The extension scans the file for consecutive blank lines and collapses them to the configured limit, improving code density and readability. This is a simple line-based transformation that does not understand code structure, making it fast but unable to preserve intentional spacing around logical sections.","intents":["I want to remove excessive blank lines that accumulate in C# files during development","I need to enforce a maximum number of consecutive blank lines (e.g., max 2) across my codebase","I want to clean up spacing to improve code density without manual editing"],"best_for":["developers cleaning up whitespace in legacy or rapidly-evolving C# codebases","teams enforcing consistent spacing conventions without manual code review","developers using VS Code who want lightweight whitespace normalization"],"limitations":["No semantic understanding of code structure; cannot distinguish between intentional spacing (e.g., separating logical sections) and excessive blank lines","Configuration is global; cannot apply different rules to different file regions or statement types","Does not handle trailing blank lines at end-of-file separately from internal spacing","May remove intentional blank lines used for visual organization or readability in complex methods"],"requires":["VS Code (version compatibility UNKNOWN)","Active C# file (.cs extension)","Setting `dotnetaio.style.enabled` must be true (default)"],"input_types":["C# source code (text)"],"output_types":["C# source code with normalized blank-line spacing (text)"],"categories":["code-generation-editing","code-formatting"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-awwsky-csharpfixformatfixed__cap_4","uri":"capability://code.generation.editing.preprocessor.directive.indentation.control","name":"preprocessor directive indentation control","description":"Allows selective indentation of C# preprocessor directives (#if, #endif, #define, etc.) based on the `dotnetaio.style.indent.preprocessorIgnored` setting (default: true, meaning preprocessor directives are NOT indented). When disabled, the extension applies indentation rules to preprocessor lines as if they were regular code, improving visual alignment with surrounding blocks. This is a line-based filter applied during indentation normalization, not a separate pass.","intents":["I want to keep preprocessor directives at column 0 to match legacy C# style conventions","I need to indent preprocessor directives to align with surrounding code blocks for readability","I want to enforce a consistent preprocessor indentation style across my codebase"],"best_for":["developers maintaining legacy C# codebases with strict preprocessor formatting conventions","teams with platform-specific code using #if directives that need consistent indentation","developers who prefer visual alignment of preprocessor blocks with surrounding code"],"limitations":["Boolean toggle only; no granular control over different preprocessor directive types (#if vs #define vs #pragma)","No understanding of preprocessor nesting depth; indentation is applied uniformly","Cannot handle conditional compilation scenarios where preprocessor directives span multiple logical blocks","Does not validate preprocessor syntax or detect mismatched #if/#endif pairs"],"requires":["VS Code (version compatibility UNKNOWN)","Active C# file (.cs extension) containing preprocessor directives","Setting `dotnetaio.style.enabled` must be true (default)"],"input_types":["C# source code with preprocessor directives (text)"],"output_types":["C# source code with indentation applied or skipped for preprocessor directives (text)"],"categories":["code-generation-editing","code-formatting"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-awwsky-csharpfixformatfixed__cap_5","uri":"capability://code.generation.editing.region.block.indentation.control","name":"region block indentation control","description":"Allows selective indentation of C# region and endregion directives (#region, #endregion) based on the `dotnetaio.style.indent.regionIgnored` setting (default: false, meaning regions ARE indented). When enabled, region directives are indented to match surrounding code blocks; when disabled, they remain at column 0. This is a line-based filter applied during indentation normalization, similar to preprocessor directive handling.","intents":["I want to indent #region blocks to align with surrounding code for visual consistency","I need to keep #region directives at column 0 to match legacy code organization style","I want to enforce consistent region indentation across my codebase"],"best_for":["developers organizing large C# classes with multiple #region blocks","teams with legacy codebases using regions for code organization who need consistent formatting","developers who prefer visual alignment of region blocks with surrounding code"],"limitations":["Boolean toggle only; no granular control over nested regions or region-specific rules","No understanding of region nesting depth; indentation is applied uniformly","Cannot validate matching #region/#endregion pairs or detect orphaned directives","Does not provide region-based code folding or navigation (VS Code handles that separately)"],"requires":["VS Code (version compatibility UNKNOWN)","Active C# file (.cs extension) containing #region directives","Setting `dotnetaio.style.enabled` must be true (default)"],"input_types":["C# source code with region directives (text)"],"output_types":["C# source code with indentation applied or skipped for region directives (text)"],"categories":["code-generation-editing","code-formatting"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-awwsky-csharpfixformatfixed__cap_6","uri":"capability://code.generation.editing.switch.case.indentation.control","name":"switch-case indentation control","description":"Allows selective indentation of switch-case labels (case and default keywords) based on the `dotnetaio.style.indent.switchCaseIgnored` setting (default: false, meaning case labels ARE indented). When enabled, case and default labels are indented to align with the switch statement body; when disabled, they remain at the same indentation level as the switch keyword. This is a line-based filter applied during indentation normalization, targeting a specific C# language construct.","intents":["I want to indent case labels inside switch statements for visual clarity","I need to keep case labels at the same level as the switch keyword to match legacy style","I want to enforce consistent switch-case indentation across my codebase"],"best_for":["C# developers working with large switch statements who need consistent indentation","teams with legacy codebases using non-standard switch-case indentation who need to enforce a style","developers who prefer visual alignment of case labels with switch body statements"],"limitations":["Boolean toggle only; no granular control over different case types or nested switches","No understanding of switch expression syntax (C# 8+) vs traditional switch statements","Cannot handle complex case patterns (when guards, relational patterns) intelligently","Does not validate switch statement completeness or detect unreachable cases"],"requires":["VS Code (version compatibility UNKNOWN)","Active C# file (.cs extension) containing switch statements","Setting `dotnetaio.style.enabled` must be true (default)"],"input_types":["C# source code with switch statements (text)"],"output_types":["C# source code with indentation applied or skipped for case labels (text)"],"categories":["code-generation-editing","code-formatting"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-awwsky-csharpfixformatfixed__cap_7","uri":"capability://automation.workflow.batch.file.formatting.via.explorer.context.menu","name":"batch file formatting via explorer context menu","description":"Enables formatting of multiple C# files in a folder or project by right-clicking a folder in the VS Code Explorer and selecting a batch-format option. The extension applies all enabled formatting rules (using sorting, indentation, brace style, etc.) to every .cs file in the selected folder and its subfolders. This is a convenience wrapper around the single-file formatting logic, executed sequentially on each file without parallelization or progress reporting.","intents":["I want to format all C# files in a folder or project at once to enforce consistent style","I need to apply formatting rules to a large codebase without manually opening each file","I want to batch-format a newly-cloned repository to match team style guidelines before starting work"],"best_for":["developers working on large C# projects who need to enforce style across many files","teams onboarding new developers or integrating legacy code that needs style normalization","developers who want to batch-format a codebase before committing changes"],"limitations":["No progress reporting or cancellation mechanism; large projects may appear to hang during batch processing","Sequential processing (not parallelized); performance on large codebases is UNKNOWN but likely slow","No dry-run or preview mode; changes are applied immediately without review","No filtering options; all .cs files in the folder tree are formatted regardless of relevance","No integration with version control; formatted files are not automatically staged or committed","Batch operation scope is UNKNOWN — does it respect .gitignore or other exclusion patterns?"],"requires":["VS Code (version compatibility UNKNOWN)","Folder or project containing C# files (.cs extension)","All formatting settings enabled as desired (using sort, indentation, brace style, etc.)"],"input_types":["C# source code files (text, multiple files)"],"output_types":["C# source code files with formatting applied (text, multiple files)"],"categories":["automation-workflow","code-generation-editing"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-awwsky-csharpfixformatfixed__cap_8","uri":"capability://code.generation.editing.on.demand.code.formatting.via.vs.code.format.document.command","name":"on-demand code formatting via vs code format document command","description":"Integrates with VS Code's standard 'Format Document' command (typically Shift+Alt+F on Windows/Linux, Shift+Option+F on macOS) to apply all enabled formatting rules to the currently-active C# file. The extension registers itself as a formatter provider in the VS Code formatting pipeline, allowing it to be invoked on-demand or automatically (if `editor.formatOnSave` is enabled, though explicit compatibility is UNKNOWN). Formatting is applied in-place to the active editor buffer without creating backups or requiring file saves.","intents":["I want to quickly format the current C# file using a keyboard shortcut","I need to format code automatically when I save a file to maintain consistent style","I want to format code on-demand during editing without leaving the editor"],"best_for":["C# developers using VS Code who want lightweight, fast formatting without external tools","teams enforcing code style through editor-level formatting rather than CI/CD pipelines","developers who prefer keyboard-driven workflows with minimal UI interaction"],"limitations":["Formatting is applied to the entire file; no support for formatting selected text or ranges","No undo history integration; formatted changes cannot be easily reverted through standard VS Code undo (UNKNOWN if extension respects undo stack)","Compatibility with `editor.formatOnSave` is UNKNOWN; may not work reliably with auto-save workflows","No conflict detection if multiple formatters are registered for C# files (e.g., OmniSharp, C# Dev Kit)","Formatting is synchronous; large files may cause UI freezing (performance characteristics UNKNOWN)","No error reporting or validation; malformed code may be silently corrupted"],"requires":["VS Code (version compatibility UNKNOWN; extension is deprecated and may not work with latest versions)","Active C# file (.cs extension) in the editor","All formatting settings configured as desired"],"input_types":["C# source code (text, single file)"],"output_types":["C# source code with formatting applied (text, single file)"],"categories":["code-generation-editing","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-awwsky-csharpfixformatfixed__cap_9","uri":"capability://code.generation.editing.error.detection.and.auto.fixing.mechanism.unknown","name":"error detection and auto-fixing (mechanism unknown)","description":"The extension claims to detect errors in C# code and apply automatic fixes 'on the fly,' but the documentation does not specify what types of errors are detected, how detection works, or what fixes are applied. This capability is mentioned in the marketplace description but lacks implementation details. It may refer to simple pattern-based fixes (e.g., missing semicolons) or more sophisticated analysis, but without architectural documentation, the actual scope and mechanism are UNKNOWN.","intents":["I want the editor to automatically detect and fix common C# syntax errors","I need quick fixes for simple mistakes like missing semicolons or incorrect indentation","I want real-time error detection without running a full compiler"],"best_for":["developers who want lightweight error detection without full compilation","teams using VS Code who need basic syntax error catching"],"limitations":["Scope of error detection is UNKNOWN; may be limited to simple syntax errors or formatting issues","Auto-fix mechanism is UNKNOWN; may corrupt code or apply incorrect fixes","No error reporting or logging; users cannot see what errors were detected or fixed","Likely does not support semantic error detection (type mismatches, undefined symbols) without compiler integration","Trigger mechanism is UNKNOWN ('on the fly' may mean on-save, on-demand, or real-time)","No configuration options for error types or fix behavior documented"],"requires":["VS Code (version compatibility UNKNOWN)","Active C# file (.cs extension)","Setting for error detection/auto-fix (name and default value UNKNOWN)"],"input_types":["C# source code (text)"],"output_types":["C# source code with errors fixed (text)"],"categories":["code-generation-editing","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":52,"verified":false,"data_access_risk":"moderate","permissions":["VS Code (version compatibility UNKNOWN due to deprecation status)","Active C# file (.cs extension) in editor","Setting `dotnetaio.sort.usings.enabled` must be true (default)","VS Code (version compatibility UNKNOWN)","Active C# file (.cs extension)","Setting `dotnetaio.style.enabled` must be true (default)","C# project files (.csproj, .sln) in workspace (UNKNOWN if extension reads these)",".NET SDK or runtime installed (UNKNOWN if required)","Active C# file (.cs extension) containing preprocessor directives","Active C# file (.cs extension) containing #region directives"],"failure_modes":["No AST-based understanding — cannot distinguish between using statements and using declarations (C# 8+)","Custom ordering requires manual configuration of namespace prefixes; no automatic detection of project-specific namespaces","Does not handle conditional using directives (#if/#endif) intelligently","Sorting is purely alphabetical; cannot implement semantic grouping (e.g., by assembly or dependency graph)","Line-based processing cannot understand nested scope depth from AST; may produce incorrect indentation in complex scenarios (e.g., nested lambdas, LINQ chains)","No support for custom indentation rules beyond the predefined settings (preprocessor, region, switch-case)","Cannot detect or fix tab-vs-space inconsistencies within the same file","Wrapped lines are handled heuristically; may not preserve intended alignment for multi-line method calls or array initializers","No awareness of C# language features like expression-bodied members or pattern matching that affect logical indentation","Actual compilation capability is UNKNOWN; extension may not invoke a compiler at all","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.9,"quality":0.32,"ecosystem":0.3,"match_graph":0.25,"freshness":0.9,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:34.118Z","last_scraped_at":"2026-05-03T15:20:29.937Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=cnet-compiler-aio-toolkit","compare_url":"https://unfragile.ai/compare?artifact=cnet-compiler-aio-toolkit"}},"signature":"UFmcqv2W+xW2EGCsz1zsiKcqIwIT3cSKHGMlFx2hTGXyXLLNDZUcWabGMG9prA9bv3FI3rrLwa5bnMhmXp2gDA==","signedAt":"2026-06-15T08:20:49.716Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/cnet-compiler-aio-toolkit","artifact":"https://unfragile.ai/cnet-compiler-aio-toolkit","verify":"https://unfragile.ai/api/v1/verify?slug=cnet-compiler-aio-toolkit","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}