detection, GitHub submission client
- **`src/WingetCreatePackage`** - MSIX packaging project for distribution
- **`src/WingetCreateTests`** - Unit and E2E tests
## Building, Testing, and Running
### Initial Setup
Configure your system using `.config/configuration.winget` (`winget configure .config/configuration.winget
Extensionless `go build` output named after its source directory
(for example, `examples/02-agents/agents/step10_as_mcp_tool/step10_as_mcp_tool`).
- `go test -c` binaries (`*.test`) and coverage output (`*.out`, `coverage.html`).
- Platform executables and libraries (`*.exe`, `*.dll`, `*.so`, `*.dylib
solution that works.
Self-verify before destructive or irreversible actions. Plan before complex tasks. Test-first when possible.
At task boundaries: compact with key decisions preserved.
After 2 failed corrections
Copilot Instructions for Azure Industrial-IoT
## Build and Test
The repo uses `.slnx` solution files (not legacy `.sln`).
```shell
# Restore (CI uses public nuget.org; local dev uses the Azure Artifacts
Commands and usage
- Configuration options
- Installation instructions
- Prerequisites
- Known issues or limitations
### Code Quality & Testing
Before submitting any changes or pushing code, **always run the following checks** to avoid pipeline
Windows Protocol Test Suites - Copilot Instructions
## Project Overview
Windows Protocol Test Suites provide interoperability testing for Windows open specifications across multiple protocol families (File Services, Identity Management, RDP, Kerberos
status rtk git status
git log -10 rtk git log -10
cargo test rtk cargo test
docker ps rtk docker ps
kubectl get pods rtk kubectl get pods
```
## Meta commands
have added new files, make sure to `git add` them first.
## Building and Testing
The following commands are commonly used for building and testing the project. See `docs/quickstart.md` for more
systems that external contributors cannot access. Contributions must be
reviewable from public sources alone.
- **Test coverage and consistency** — ask whether the tests would fail if this behavior regressed.
Failure, retry
annotations
- **Tutorial Content**: Place in `docs/` with proper markdown formatting
- **Code Examples**: Include practical, tested examples
- **Screenshots**: Use for UI changes and place in `docs/static/`
- **Breaking Changes**: Document breaking changes
licenses` enforces it, and anything adapted
from another project is recorded in `THIRD-PARTY-NOTICES.md` first.
- **Tests are `npm test` (Vitest).** New behaviour needs a test; the suite
runs offline
container that copies agent + bundled Python into any user image via emptyDir volume
## Build, Test, and Lint
```bash
# Install (editable, from the repo root)
pip install -e "orchard