'dotnet' 검색 결과

Build .NET workflows that extract text, tables, and fields from invoices, receipts, and other documents using Azure AI Document Intelligence. Covers prebuilt models, custom model creation, document classification, authentication, and result handling.

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

• Extract vendors, line items, and totals from invoices
• Read merchants, dates, and totals from receipts
• Extract text and table cells from documents

Build and review C#/.NET APIs and business backends using concrete implementation patterns. Cover asynchronous operations, service dependencies, database access, configuration, caching, and tests to structure application code and examine quality and performance issues.

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

• Designing a new .NET Web API
• Reviewing asynchronous C# code
• Improving database access and caching

Review C#/.NET code for design patterns, separation of responsibilities, and common implementation issues. Receive actionable recommendations covering maintainability, testing, performance, and security without changing the code.

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

• Review design patterns in C#/.NET code
• Check separation of responsibilities before refactoring
• Identify dependencies that make testing difficult

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

Get C# examples for timezone conversion, location lookup, and scheduling in .NET applications. The skill explains Windows and IANA timezone identifiers, daylight saving changes, and suitable libraries for different platforms and scheduling needs.

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

• Find timezone identifiers for cities and addresses
• Convert between UTC and local time in C#
• Handle timezones across Windows and Linux

Provides prompts for assessing and planning .NET upgrades across multiple projects. Helps identify compatibility issues, order migration work, propose code and build pipeline changes, and prepare testing checklists, review guidance, and release documentation.

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

• Assessing project structure and dependency compatibility
• Planning an incremental upgrade with rollback checkpoints
• Reviewing deprecated APIs and NuGet package replacements

Review and improve .NET/C# code against project conventions. Cover public API documentation, dependency injection for supplying services to classes, asynchronous operations, tests, configuration, logging, and input validation, including guidance for Semantic Kernel integrations.

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

• Review C# code against project conventions
• Improve XML documentation for public APIs
• Review asynchronous operations and dependency injection

Plan and configure command and control (C2) systems for red team exercises. Covers major frameworks, communication methods, relay servers, certificate management, and the network or endpoint signals defenders use to detect these systems.

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

• Compare C2 frameworks for a red team exercise
• Plan communication methods and relay infrastructure
• Review C2 detection signals from a defender's perspective

Identify repeated NuGet package restores across .NET build, test, and publish steps. Check whether earlier restores cover each later step, apply targeted changes, and validate the pipeline without removing required dependency restoration.

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

• Remove repeated package restores from CI pipelines
• Check where --no-restore can safely be added
• Investigate NETSDK1004 or NETSDK1047 after skipping restore

Assess whether tests detect the wrong behavior relevant to a specific change, PR, or commit. Link findings to exact revisions, compare faulty and correct behavior when execution is authorized, and distinguish observed results from predictions.

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

• Check whether a regression test detects the original bug
• Assess tests for a new feature
• Review behavior preservation during a refactor

Use the new Process APIs in .NET 11 applications to run external commands, capture output and errors, and manage child processes. Guidance covers waiting for completion, reading output, and controlling whether processes survive their parent.

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

• Capturing output and errors from external commands
• Stopping child processes when the parent exits
• Reading process output one line at a time

Add, repair, and strengthen tests for existing code using the project's testing framework. Covers regression cases, boundary conditions, flaky tests, and coverage gaps, with validation that links requested behaviors to specific tests.

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

• Add unit tests for existing code
• Repair failing or flaky tests
• Cover regression cases, boundaries, and error paths

Create VS Code custom agents for roles such as planning or code review. It builds .agent.md files with role instructions, permitted tools, and optional handoffs that let users move work to another agent.

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

• Creating an agent dedicated to planning
• Defining a code review agent
• Restricting tools to match an agent's role

Write and review GitHub Actions workflows for syntax and structural correctness. Check quoting around expressions and special characters, then validate with actionlint, a workflow checker, to catch errors that ordinary YAML parsing can miss.

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

• Reviewing new or edited GitHub Actions workflow files
• Checking quotes around expressions containing special characters
• Investigating workflow failures before any jobs start

Route GitHub Agentic Workflows requests to the appropriate task guide. It selects prompts for design, creation, updates, debugging, or upgrades, with additional guidance for specialized tasks and repository-specific instructions when available.

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

• Starting workflow design through an interview
• Selecting guidance for creating or updating workflows
• Finding debugging or upgrade procedures

Correct and improve existing MSTest tests using APIs supported by the installed version. Refine assertions and failure messages, update data-driven tests, fix setup and cleanup, and address MSTest diagnostics while preserving the project's established conventions.

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

• Making assertion failures easier to understand
• Correcting expected and actual argument order
• Improving existing data-driven tests

Apply the System.Text.Json APIs introduced in .NET 11 to produce PascalCase JSON names and retrieve typed serialization metadata, the information used to convert objects. Create runnable examples and check metadata availability without exception-based probing.

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

• Produce PascalCase JSON property names
• Convert dictionary keys to PascalCase
• Retrieve typed serialization metadata without casts

Introduce nullable reference types into an existing C# project, making explicit which references may be null. Plan a staged migration, resolve compiler warnings, and clarify public API annotations while preserving runtime behavior.

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

• Adopting nullable reference types in an existing C# project
• Migrating a large codebase file by file
• Clarifying nullability in public APIs

Classify existing tests with standard tags for success cases, errors, boundaries, and other behaviors. Get a per-test mapping and distribution summary, or apply tags using supported framework syntax and verify compilation and test discovery.

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

• Comparing success-case and error-case test counts
• Adding standard tags to existing tests
• Reviewing the mix of boundary and integration tests

Replace C# static calls for time, files, or environment values with existing abstractions that tests can substitute. Update construction and affected tests within a defined scope, while preserving read counts, evaluation order, date-time semantics, and existing static callers.

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

• Migrating DateTime.UtcNow calls to TimeProvider
• Replacing File calls with an existing IFileSystem
• Replacing disk or environment access in unit tests with fakes

Interpret .NET coverage reports, which show code exercised by tests, to explain missing coverage and stalled progress. Calculate the gains needed to reach a target and, when requested, combine coverage with complexity to rank risk.

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

• Explain Cobertura reports and partially covered conditions
• Find the code keeping coverage from improving
• Calculate line gains needed to reach a coverage target

Find changes in observable behavior that existing tests could miss. Map public results to test assertions, identify gaps in boundaries, permissions, and calculations, and propose focused tests, with optional verification when requested.

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

• Check whether existing tests would catch a bug
• Find missing boundary and permission-denial tests
• Review exact amounts and rounding in financial calculations

Create, modify, debug, and review Windows Forms applications while preserving their editable layouts in Visual Studio Designer. Covers resizing, data binding, asynchronous UI behavior, and checks that distinguish successful builds from actual screen and designer verification.

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

• Fixing forms that fail to open in Visual Studio Designer
• Resolving clipped controls after resizing or DPI changes
• Repairing bound lists that do not refresh

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