Document your code
Every project on GitHub comes with a version-controlled wiki to give your documentation the high level of care it deserves. It’s easy to create well-maintained, Markdown or rich text documentation alongside your code.
Sign up for free See pricing for teams and enterprisesNuGetizer Principles
The following principles guide the NuGetizer design:
1. It should be easy to create a package from any library project. When packaging an individual project, no additional packaging projects should be necessary.
2. Creating a package that contains multiple platform-optimized implementations (such as "bait and switch" packages) should be as easy as File->New Project. This is an extremely important use case and must be first class.
3. It should be easy to add platform-specific implementations to a cross-platform package. Developers who start out creating a simple package from a netstandard project must be able to add platform-specific variants without recreating the project.
4. It should not normally be necessary for a developer to specify or override which files are included in a package, but they must be able to do so.
5. Platform-specific targets should be able to inform and override the packaging behavior to handle files specific to that platform. The Common targets should not assume all platforms work the same.
6. Projects and packages should be as interchangeable as possible. Referencing a project should be equivalent to referencing the package that it would create.
Pages 147
- Home
- 2 Factor Auth for NuGet.org sign in
- [Spec] Content v2 for project.json
- [Spec] Fallback package folders
- [Spec] FrameworkReference in NuGet
- [Spec] Managing dependency package assets
- [Spec] MSBuild restore target
- [Spec] NuGet Build Integrated Project handling of floating versions and ranges in Visual Studio Client
- [Spec] NuGet Config schema changes to enable trusted signers
- [Spec] NuGet Package Signing Client Policy
- [Spec] NuGet Package Signing Revocation Check
- [Spec] NuGet settings in MSBuild
- [spec] NuGet.org replication API
- [Spec] Package download API
- [Spec] PackageDownload support
- [Spec] Server side warnings for NuGet client
- [spec] Support organizational accounts
- [Spec] Transitive Warning Properties
- [Spec] Warnings and errors in the assets file
- Add Clear Cache button to VS Package Manager options
- Adding nuget pack as a msbuild target
- Aggressive No Caching option for nuget.exe
- Allow package authors to define build assets transitive behavior
- Allow restore to succeed for unloaded projects in Visual Studio
- Author Package Signing
- Batch Events
- Bringing back content support, September 24th, 2015
- Centrally managing NuGet package versions
- Centrally managing NuGet packages
- Centrally managing NuGet packages and versions
- Coding Guidelines
- Config Max Http Request In NuGet
- Consolidate NuGet CLIs (commands and functionality)
- Contribute to NuGet
- Contributing to NuGet
- Converting a csproj from package.config to project.json
- Converting Extension SDKs into NuGet Packages
- Cross platform authentication support
- Csproj to Xproj reference design meeting notes September 2, 2015
- Deprecate external content URLs for packages
- Deprecate packages
- Design Meeting Notes
- DevelopmentDependency support for PackageReference
- dotnet list package
- DotnetCliToolReference restore
- DotNetCliTools in VS _15_ timeframe
- Embed Interop Types with PackageReference
- Enable .NET Core 2.0 projects to work with .NET Framework 4.6.1 compatible packages
- Enable repeatable builds for PackageReference based projects
- Enable repeatable package restore using lock file
- Enhanced package upload workflow
- Filter OData query requests
- Full support of LSL
- Functional Testing
- Global Tools NuGet Implementation
- How to contribute
- Icons as part of the nupkg
- Ideas about NuGet Hierarchical Setting
- Implemented
- Improve messaging when NuGet service(s) are degraded
- Incubation
- IsLatest Duplicates
- LineUps file to manage package dependencies for a repo
- Lock file design meeting notes August 18, 2015
- Logging Guidance
- Manage allowed packages for a solution (or globally)
- MsBuild project.json xunit Design meeting notes August, 12 2015
- Multiple API Keys
- NuGet Account Deletion Workflow
- NuGet Account Deletion Workflow (deprecated)
- NuGet Account Deletion Workflow (Self Service Model)
- NuGet Account Deletion Workflow (Service Request Model)
- NuGet Client Package Debugging
- NuGet Client Test Plan
- NuGet cross plat authentication plugin
- NuGet Cross Plat Credential Plugin
- NuGet Errors and Warnings
- NuGet Gallery Test Plan
- NuGet Localization Design
- NuGet Package Debugging & Symbols Improvements
- NuGet Package Download Plugin
- NuGet Package Identity Verification
- NuGet package signing Errors and Warnings
- NuGet packages cache management
- NuGet Restore Manager
- NuGet Restore No Op
- NuGet Sign Command
- NuGet UI design meeting notes August 20 2015
- NuGet UI design meeting notes August 21, 2015
- NuGet Upgrader. Helping to move to NuGet 3.0
- NuGet Verify Command
- nuget.exe, xplat, dotnet cli commands and options planning
- NuGetGallery DB Query performance investigations
- NuGetizer 3000
- NuGetizer Core Features
- NuGetizer Core Scenarios
- NuGetizer Future Features
- NuGetizer Principles
- Nupkg Metadata File
- Organization policies and 2FA settings
- Organizations on NuGet.org
- Package applicability in NuGet package manager UI
- Package Immutability
- Package Markdown Support
- Package ownership information on nuget.org
- Package README.md support
- Package Signatures Technical Details
- Package signing
- Package Sources Diagnostics
- Package Type [Packing]
- PackageReference enhancements
- PackageReference Specification
- packages.config (PC) to PackageReference (PR) Migrator
- Packages.config SHA Validation
- PackageTargetFallback (new design for Imports)
- Packaging Documentation within the nupkg
- Packaging Icon within the nupkg
- Packaging Icon, License and Documentation within the nupkg
- Packaging License within the nupkg
- Packaging License within the nupkg (Technical Spec)
- Plugin Diagnostic Logging
- Register package signing certificates
- Release Branches
- Repeatable build using lock file implementation
- Repository Signatures
- Repository Signatures and Countersignatures Technical Specification
- Restore errors and warnings
- Roadmap
- Search by Package Type and Query Language Surfacing
- Secret Rotation
- Semver 2.0.0 Protocol
- SemVer 2.0.0 support
- SemVer2 support for nuget.org (server side)
- Setting up the NuGet Development Environment
- Show outdated packages
- Show source repository information for packages on nuget.org
- Sidebar Archive 9_14_2017
- Support dotnet add, update, remove pkg
- Support locals command in dotnet cli
- Support nuget push scenarios in dotnet CLI
- Supporting locals command in dotnet cli and VS extension
- Supporting Package Reference in UWP WPF WinForms and Classic Libraries
- Symbols Package Upload and Delete Workflow
- ToolsReference and Multi TFM Support in NuGet UI
- UWP Project Json Upgrader
- Warnings and Errors Combined Specs
- Writing and reviewing awesome specs
Home
Incubation
Reviewing
Reviewed
- Packaging Icon, License and Documentation within the nupkg
- Show outdated packages
- Enable repeatable package restore using lock file
- Packaging Icon, License and Documentation within the nupkg
- Register package signing certificates
- 2 Factor Auth for NuGet.org sign in
- Author Package Signing
- Repository Signatures and Countersignatures Technical Specification
- NuGet Verify Command
- NuGet Sign Command
- Organizations on NuGet.org
- Replication API
- NuGet Package Identity Verification
- Enhanced package upload workflow
- Package Signatures Technical Details
- NuGet Package Debugging & Symbols Improvements
- Dotnet list package
- Packages.config SHA Validation
Implemented
- NuGet Client Package Debugging
- Symbols Package Upload and Delete Workflow
- Package signing
- Repository Signatures
- Storing trusted repository
- NuGet Package Signing Client Policy