You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The .NET Core framework has a dotnettools plug-in system where toolsmiths can plug their tools easily into a .NET solution's build pipeline. The C# ".NET SDK" csproj new file format also adds common metadata used to publish nuget packages; this same metadata can be used for chocolatey since much of what chocolatey uses for metadata is based off nuget nuspec metadata.
Related helpful features: #602 - MSBuild already provides some schema validation ability, so while this won't serve whole community, will help C# developers maintaining executable projects, like:
#522 - Adding variable substitution becomes less important if .NET developers can choco pack their bin directories as part of their MSBuild, since MSBuild can take care of the substitution. The variable substitution then is only useful if trying to manage packages you don't have a C# sln for/control over.
The text was updated successfully, but these errors were encountered:
This may require uplifting Chocolatey to .Net Core, since it currently is on .Net 4.0 (to be moved to 4.8 in the midterm future), and I don't know what the plug in system requires with regard to .Net version.
The .NET Core framework has a dotnettools plug-in system where toolsmiths can plug their tools easily into a .NET solution's build pipeline. The C# ".NET SDK" csproj new file format also adds common metadata used to publish nuget packages; this same metadata can be used for chocolatey since much of what chocolatey uses for metadata is based off nuget nuspec metadata.
Related helpful features:
#602 - MSBuild already provides some schema validation ability, so while this won't serve whole community, will help C# developers maintaining executable projects, like:
#522 - Adding variable substitution becomes less important if .NET developers can choco pack their bin directories as part of their MSBuild, since MSBuild can take care of the substitution. The variable substitution then is only useful if trying to manage packages you don't have a C# sln for/control over.
The text was updated successfully, but these errors were encountered: