dotnet / dotnet/msbuild

Better support for MSBuild extensibility delivered via nugetss

Open
#9,926 1 comment 1 reaction 0 assignees View on GitHub
Area: BuildCheck needs-design Priority:2 triaged
Dominant language
C#
Stars
5.5k
Forks
1.5k
Avg merge
1d 8h
Merged PRs (30d)
141

Description

### Context

There are some existing extensibility that users might want to deliver via nugets:
* loggers
* tasks
* sdks/sdkresolvers

There are talks on possible future extensibility that might want to be delivered via nugets:
* BuildCheck / Analyzers
* Project Archetypes

Some of those can already be delivered via nugets, some are complex or near impossible to achieve

### Sample usage scenarios:
* Engineering teams wanting to run builds with custom loggers - this currently requires standalone setup step (to have the logger locally available in known location)
* Custom BuildCheck packages that would require early evaluation access or a initial build access (solution processing etc.)

### Requirements

* Ability to reference versioned nuget packages from commandline (injecting loggers, global BuidChecks etc.)
* Ability to reference nugets within projects (sdks, bildchecks, tasks) and have those resolved during the restore phase and have some metadata available as input into other build phases - so that magic nuget properties or naming doesn't have to be used.

### Goals of initial investigation
* Summarize the scenarios and their requirements
* Define if/what support from nuget side would simplify the scnearios - and negotiate creation of workitem(s) with nuget team
* Propose and prototype solutions without additional nuget support.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.