Skip to content

Documentation

Kyaa Dost edited this page Sep 23, 2020 · 3 revisions
  • DO NOT expect that your API is so well designed that it needs no documentation. No API is that intuitive.
  • DO provide great documentation with all APIs.
  • DO use readable and self-documenting identifier names.
  • DO use consistent naming and terminology.
  • DO provide strongly typed APIs.
  • DO use verbose identifier names.

Files and Folders

  • DO associate no more than one class per file.
  • DO use folders to group classes based on features.

About Windows Community Toolkit

Usage

Contribution

Development/Testing

Project Structure

Clone this wiki locally