'csharp' 검색 결과

ASP.NET Core web framework conventions: Minimal API vs MVC controllers, Program.cs composition, DI lifetimes (Scoped/Singleton/Transient), Options pattern with IOptions<T>, middleware ordering (HTTPS redirect → routing → authentication → authorization), model binding and validation (FluentValidation / DataAnnotations), ProblemDetails error handling, structured logging with ILogger<T>, configuration layering (appsettings.json + environment variables + User Secrets), and health checks. Works alongside csharp-foundation:csharp-conventions and aspnet-core-plugin:efcore-patterns. Use this skill to: - Compose Program.cs correctly — register services, configure middleware in the right order, map endpoints. - Apply the Options pattern to avoid passing raw IConfiguration into services. - Write Minimal API endpoint groups with typed results and authorization. - Handle cross-cutting errors uniformly with ProblemDetails. - Configure structured logging and health checks for production readiness. Do NOT use this skill for: - EF Core entity configuration and migrations — see aspnet-core-plugin:efcore-patterns. - C# language idioms — see csharp-foundation:csharp-conventions. - Testing — see csharp-foundation:dotnet-testing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use the open-source free `CSharpier` formatter for C# and XML. Use when a .NET repo intentionally wants one opinionated formatter instead of a highly configurable `dotnet format`-driven style model. USE FOR: the repo uses or wants CSharpier; the team prefers an opinionated formatter over many configurable style knobs. DO NOT USE FOR: repos that already standardized on dotnet format as the only formatter. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Modern C# idioms for any .NET project (C# 10+, .NET 6+): nullable reference types, records, readonly structs, primary constructors, pattern matching, async/await with CancellationToken, IDisposable/IAsyncDisposable, file-scoped namespaces, var usage, naming conventions (PascalCase members, _camelCase fields, I-prefixed interfaces), and class design rules. Apply whenever the project is a .NET 6+ project. Stack-agnostic — referenced by every .NET plugin in the marketplace. Use this skill to: - Write self-documenting immutable value types with records and readonly structs. - Handle nullable reference types explicitly to eliminate NullReferenceException at compile time. - Implement async/await correctly with CancellationToken propagation and ConfigureAwait(false) in libraries. - Dispose unmanaged resources correctly via IDisposable / IAsyncDisposable and using statements. - Apply C# pattern matching (switch expressions, property patterns, list patterns) for cleaner branching logic. Do NOT use this skill for: - Framework-specific idioms (ASP.NET Core controllers, minimal APIs, EF Core — those live in aspnet-core-plugin skills). - Build tooling (dotnet CLI, NuGet, csproj) — see csharp-foundation:dotnet-tooling. - Testing patterns — see csharp-foundation:dotnet-testing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

.NET SDK and NuGet tooling conventions: dotnet CLI commands (new/build/run/test/publish/restore/format), NuGet package management (PackageReference, Directory.Packages.props central package management, packages.lock.json), project file conventions (.csproj, .sln, global.json, Directory.Build.props), multi-targeting, and dotnet format. Stack-agnostic — referenced by every .NET plugin in the marketplace. Use this skill to: - Detect the .NET SDK version and run all commands via the dotnet CLI. - Manage NuGet dependencies safely (central package management, no floating versions). - Configure project files and solution-wide properties in Directory.Build.props. - Format code consistently with dotnet format. Do NOT use this skill for: - Framework-specific tooling (dotnet ef migrations, aspnet-codegenerator — those are in aspnet-core-plugin:aspnet-conventions). - Testing patterns — see csharp-foundation:dotnet-testing. - C# language idioms — see csharp-foundation:csharp-conventions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guidelines for introducing and using nullable reference types (NRT) and System.Diagnostics.CodeAnalysis nullable attributes in C# / .NET codebases. Covers the nullability model, flow analysis, the null-forgiving operator, API design rules, the full attribute catalog (AllowNull, DisallowNull, MaybeNull, NotNull, NotNullWhen, MaybeNullWhen, NotNullIfNotNull, MemberNotNull, MemberNotNullWhen, DoesNotReturn, DoesNotReturnIf), the C# 14 field keyword, incremental migration of legacy codebases, and a code-generation checklist.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use the open-source free `CSharpier` formatter for C# and XML. Use when a .NET repo intentionally wants one opinionated formatter instead of a highly configurable `dotnet format`-driven style model.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

xUnit, Moq/NSubstitute, FluentAssertions, and coverlet patterns for any .NET project. Covers test structure ([Fact]/[Theory]/[InlineData]), mocking discipline, fluent assertions, integration test setup with WebApplicationFactory, and coverage measurement. Stack-agnostic — referenced by every .NET plugin in the marketplace. Use this skill to: - Write clear, maintainable unit tests with xUnit [Fact] and [Theory]. - Mock dependencies with Moq or NSubstitute without overusing mocks. - Write expressive assertions with FluentAssertions. - Measure coverage with coverlet and enforce a minimum threshold. Do NOT use this skill for: - ASP.NET Core-specific integration tests (WebApplicationFactory, HttpClient — those are in aspnet-core-plugin:aspnet-conventions). - EF Core in-memory or SQL Server LocalDB test patterns (aspnet-core-plugin:efcore-patterns). - C# language idioms — see csharp-foundation:csharp-conventions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Entity Framework Core patterns for ASP.NET Core projects: DbContext design, code-first entity configuration (Fluent API via IEntityTypeConfiguration<T>), relations (HasOne/HasMany, cascade/restrict/set-null), indexes and unique constraints, projection to DTOs (Select + AsNoTracking), avoiding N+1 (Include, AsSplitQuery), transactions, parameterized raw SQL (FromSql with FormattableString), and connection string from IConfiguration. Works alongside aspnet-core-plugin:aspnet-conventions. Use this skill to: - Design a clean DbContext with ApplyConfigurationsFromAssembly for scalable entity registration. - Configure entity properties (column types, max length, precision, nullability) via Fluent API. - Avoid N+1 query problems with explicit Include / projection to DTOs. - Use transactions correctly for multi-entity operations. - Write parameterized raw SQL safely when LINQ is not expressive enough. Do NOT use this skill for: - Migration generation commands (that is efcore-specialist's job in the database extra phase). - ASP.NET Core middleware, DI, or validation — see aspnet-core-plugin:aspnet-conventions. - C# language idioms — see csharp-foundation:csharp-conventions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use the open-source free `CSharpier` formatter for C# and XML. Use when a .NET repo intentionally wants one opinionated formatter instead of a highly configurable `dotnet format`-driven style model.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Skill for csharp tasks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

xUnit 등의 구현 예제로 C#과 .NET 테스트를 작성하고 검토합니다. 단위 테스트, API·데이터베이스 통합 테스트와 테스트 데이터 및 배치를 다룹니다.

• C# 서비스에 테스트를 추가할 때
• ASP.NET Core API 응답 검증
• 데이터베이스 저장 결과 확인

Build cryptocurrency exchange integrations in C# and .NET with CCXT. Get guidance on setup, market data, orders, authentication, and error handling, using REST for individual requests and WebSocket connections for live price and order book updates.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding cryptocurrency prices to a C# application
• Implementing order placement and cancellation
• Monitoring live prices and order books

Review C# asynchronous code and get suggestions for method names, return types, exception handling, concurrent tasks, and cancellation. Identify blocking calls and missing awaits, and choose patterns for long operations or sequences processed asynchronously.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing async/await usage
• Finding blocking calls and missing awaits
• Planning concurrent tasks and cancellation

Write and improve C# unit tests with MSTest 3.x/4.x. Covers assertions that check expected results, tests with multiple input sets, asynchronous setup, cleanup, and test organization, with guidance on APIs that differ between versions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create a C# unit test project
• Test multiple input sets with DataRow or DynamicData
• Update exception checks to modern assertion APIs

Write focused C# unit tests with XUnit, including tests that run against multiple input datasets. Apply consistent naming, setup, assertions, shared fixtures, and mock dependencies to keep tests readable, independent, and organized.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Set up an XUnit test project for C#
• Test multiple input cases with Theory and data attributes
• Check exceptions and isolate dependencies with mocks

Write consistent XML documentation comments for C# types and public members. Follow specific rules for summaries, parameters, return values, properties, exceptions, examples, and inherited documentation so API behavior and usage are clearly described alongside the code.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding documentation to public APIs
• Standardizing parameter and return value descriptions
• Documenting exception conditions and usage examples

Write C# unit tests with TUnit using clear test structure, asynchronous checks, and multiple input cases. Get guidance on setup and cleanup, execution controls, test organization, and converting existing xUnit tests to TUnit.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Setting up a TUnit test project
• Testing one behavior with multiple input cases
• Organizing test setup and cleanup

Write C# unit tests with NUnit using clear naming, focused assertions, and independent test cases. Covers project setup, testing with multiple input values, exception checks, and replacing dependencies with mocks to test components in isolation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Setting up an NUnit test project
• Testing the same behavior with multiple inputs
• Checking exceptions and collection contents

Build C# applications with .NET 8+, including ASP.NET Core APIs and Blazor interfaces. Get models, endpoints, services, and configuration, with guidance on database access, asynchronous operations, cancellation, authentication, performance tuning, and tests.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Build a REST API with ASP.NET Core
• Implement database access with Entity Framework Core
• Create Blazor components and manage application state

Match C# and .NET tasks to the appropriate specialist skill using the request and project evidence. Invoke available specialists, explain how to obtain missing plugins, and complete suitable tasks with standard tooling when possible.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing a specialist for a C# or .NET task
• Finding the plugin needed for a missing specialist
• Restoring discovery of already installed skills

Move existing .NET 9 projects to .NET 10 by updating project settings and dependencies, fixing build errors, and reviewing behavior changes. Includes CI and Docker updates, followed by builds, tests, and security checks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Upgrading an existing .NET 9 project to .NET 10
• Fixing build errors and warnings after an SDK upgrade
• Reviewing ASP.NET Core and EF Core behavior changes

Migrate legacy .NET project files to SDK-style format, reducing repetitive XML and explicit file lists. Convert package references, move assembly metadata into project settings, and consolidate shared build and package settings across multiple projects.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Convert legacy .csproj or .vbproj files to SDK-style
• Migrate packages.config to PackageReference
• Replace AssemblyInfo.cs with generated assembly metadata

Refactor C#/.NET code through renaming, extraction, consolidation, and other structural changes while preserving behavior. Check compatibility beyond code references, including public APIs and serialized names, then validate with builds and relevant tests.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Rename C# members and update their references
• Extract shared logic from duplicate code
• Reorganize code while preserving public API compatibility

Run small C# apps without creating a project, using the .NET CLI, its command-line tool. Use it to test language features, explore APIs, or prototype utilities with helper files and NuGet packages.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Trying C# language features or APIs
• Prototyping logic before project integration
• Building a small utility with helper files