NuGet发布管理

Question

我第一次做了一些我想在NuGet上分享的东西,但我不确定这个"发布准备"是如何完成的.

目前我的以下步骤是:

1. 手动将主程序集(MyAssembly)的程序集版本AssemblyInfo.cs从中1.0.0.0更改为1.1.0.0
2. 在Visual Studio中构建主程序集发行版
3. 打包我的主程序集(nuget pack -prop configuration=release== MyAssembly.1.1.0.0.nupkg)
4. 将此包发布到NuGet(nuget push MyAssembly.1.1.0.0.nupkg)
5. 更新程序集引用的NuGet包MyAssembly(例如MyAssembly.Web.Mvc,MyAssembly从v1.0.0.0- > v1.1.0.0使用NuGet包管理器更新),在packages.config中定义
6. 更改版本AssemblyInfo.cs的MyAssembly.Web.Mvc到1.1.0.0,建立释放,包的NuGet和发布
7. 对所有引用程序集重复步骤6

这是PITA的一些步骤,我有一天会犯错并打破发布.

这让我想到,我错过了一个关键点,我做错了吗？

UPDATE

基于@ialekseev提供的知识,我现在创建了这个:

Build.ps1

Param(
    [Parameter(Mandatory=$true)]
    [string]$version,
    [string]$configuration = "Release",
    [boolean]$tests = $false,
    [boolean]$publish = $false,
    [boolean]$pack = $false,
    [string]$outputFolder = "build\packages"
)

# Include build functions
. "./BuildFunctions.ps1"

# The solution we are building
$solution = "NerveFramework.sln"
$assemblies = "NerveFramework", "NerveFramework.Web", "NerveFramework.Web.Mvc", "NerveFramework.Web.WebApi"

# Start by changing the assembly version
Write-Host "Changing the assembly versions to '$version'..."
$assemblyInfos = Get-ChildItem $assemblies -Filter "AssemblyInfo.cs" -Recurse | Resolve-Path -Relative
foreach ($assemblyInfo in $assemblyInfos) {
    ChangeAssemblyVersion $assemblyInfo $version
}

# Build the entire solution
Write-Host "Cleaning and building $solution (Configuration: $configuration)"
BuildSolution $solution $configuration

# Change dependency version on all depending assemblies
Write-Host "Changing the NerveFramework(s) NuGet Spec version dependencies to '$version'..."
$nuspecs = Get-ChildItem $assemblies -Filter "NerveFramework*.nuspec" -Recurse | Resolve-Path -Relative
foreach ($nuspec in $nuspecs) {
    ChangeNugetSpecDependencyVersion $nuspec "NerveFramework" $version
} 

# Pack the assemblies and move to output folder
if ($pack) {
    Write-Host "Packaging projects..."
    $projects = Get-ChildItem $assemblies -Filter "NerveFramework*.csproj" -Recurse | Resolve-Path -Relative
    foreach ($project in $projects) {
        PackProject $project $configuration $outputFolder
    } 
}

# Publish the assemblies
if ($publish) {
    Write-Host "Publishing packages..."
    $packages = Get-ChildItem $outputFolder -Filter "*$version.nupkg" -Recurse | Resolve-Path -Relative
    foreach ($package in $packages) {
        PublishPackage $package
    } 
}

BuildFunctions.ps1

Function BuildSolution() {

    Param(
        [Parameter(Mandatory=$true)]
        [string]$solution,
        [Parameter(Mandatory=$true)]
        [string]$configuration
    )

    # Set the path to the .NET folder in order to use "msbuild.exe"
    $env:PATH = "C:\Windows\Microsoft.NET\Framework64\v4.0.30319"

    Invoke-Expression "msbuild.exe $solution /nologo /v:m /p:Configuration=$configuration /t:Clean"
    Invoke-Expression "msbuild.exe $solution /nologo /v:m /p:Configuration=$configuration /clp:ErrorsOnly"
}

Function ChangeAssemblyVersion() {

    Param(
        [Parameter(Mandatory=$true)]
        [string]$filePath,
        [Parameter(Mandatory=$true)]
        [string]$publishVersion
    )

    Write-Host "-- Updating '$filePath' to version '$publishVersion'"

    $assemblyVersionPattern = 'AssemblyVersion\("[0-9]+(\.([0-9]+|\*)){1,3}"\)'
    $assemblyVersion = 'AssemblyVersion("' + $publishVersion + '")';
    $assemblyFileVersionPattern = 'AssemblyFileVersion\("[0-9]+(\.([0-9]+|\*)){1,3}"\)'
    $assemblyFileVersion = 'AssemblyFileVersion("' + $publishVersion + '")';

    (Get-Content $filePath -Encoding utf8) | ForEach-Object { 
            % { $_ -Replace $assemblyVersionPattern, $assemblyVersion } |
            % { $_ -Replace $assemblyFileVersionPattern, $assemblyFileVersion } 
    } | Set-Content $filePath
}

Function ChangeNugetSpecDependencyVersion() {

    Param(
        [Parameter(Mandatory=$true)]
        [string]$filePath,
        [Parameter(Mandatory=$true)]
        [string]$packageId,
        [Parameter(Mandatory=$true)]
        [string]$publishVersion
    )

    [xml] $toFile = (Get-Content $filePath)
    $nodes = $toFile.SelectNodes("//package/metadata/dependencies/dependency[starts-with(@id, $packageId)]")
    if ($nodes) {
        foreach ($node in $nodes) {
            $nodeId = $node.id
            Write-Host "-- Updating '$nodeId' in '$filePath' to version '$publishVersion'"
            $node.version = "[" + $publishVersion +"]"
            $toFile.Save($filePath)
        }
   }
}

Function PackProject() {

    Param(
        [Parameter(Mandatory=$true)]
        [string]$project,
        [Parameter(Mandatory=$true)]
        [string]$configuration,
        [Parameter(Mandatory=$true)]
        [string]$outputFolder
    )

    if (!(Test-Path -Path $outputFolder)) {
        New-Item $outputFolder -Type Directory
    }

    Write-Host "-- Packaging '$project'"
    Invoke-Expression ".nuget\NuGet.exe pack $project -OutputDirectory '$outputFolder' -Prop Configuration=$configuration"
}

Function PublishPackage() {

    Param(
        [Parameter(Mandatory=$true)]
        [string]$package
    )

    Write-Host "-- Publishing '$package'"
    Invoke-Expression ".nuget\NuGet.exe push $package"

}

跑得像 .\Build -version 1.2.0.0 -pack $true

Answer 1

您需要使您的过程自动化，因为，是的，手动执行此过程非常容易出错。

我通常编写可以执行以下步骤的 powershell/cmd 脚本：

1. 构建解决方案
2. 对其进行测试
3. 更新程序集版本
4. 创建 NuGet 包
5. 发布 NuGet 包

然后您可以在本地运行它来自动完成所有这些步骤。您还可以将一些任务委托给您的构建服务器（如果有的话）。例如，Teamcity 可以负责构建、运行测试，甚至将包发布到 NuGet。无论如何，我喜欢将所有这些脚本放在我的源代码管理中，以便能够在需要时在本地运行它们。如果您有兴趣，可以在GitHub上查看我为我的一个项目编写的脚本。脚本位于build文件夹中，publish_local.cmd是入口点。项目有多个 NuGet 依赖项，因此，我相信它与您想要完成的任务类似。

我知道最好直接在答案中提供示例，但是这里包含的脚本太多。如果您有任何疑问，请成为我的客人。