NuGetter Discussions Rss Feed

New Post: Using nugetter with a hosted build controller.

0v3rCl0ck — Sun, 12 May 2013 14:21:44 GMT

I have the same problem explained in this post, could marknic please checkin the fix to the codeplex source control?

Thanks!

New Post: Suggestions on how to support .csproj Nuget pack targets?

jonstelly — Mon, 06 May 2013 20:36:34 GMT

Understood. Following your suggestion, I tried something a bit different: Tackle some missing pieces in the core nuget project to make this easier. I'm posting it here in case it's helpful. In the end, I ended up with couple simple modification to the TFS 2012 Build Template:

Add 3 arguments to the build template for NuGet OutputPath (My local NuGet Repository), A path to a powershell script to run, and my nuget version info (minus the build part, which I pull out of the build name)
Add an activity after build/test execution that checks to see if the powershell script was specified. If so, execute the powershell script which does all of the packaging and pushing.

I've submitted a pull request, available HERE for the NuGet project. The second part of that pull request is to fix BasePath support for packing project files, which is what makes things so simple.

Here's the powershell script I mention above (It's still pretty hack-y, but is functioning):

Script:

Param([string]$basePath, [string]$outPath, [string]$version, [string]$buildName)
Process
{
    [string[]]$projectFiles = @(
"Source\ProjectA\ProjectA.csproj",
"Source\ProjectB\ProjectB.csproj",
"Tests\ProjectA.Tests\ProjectA.Tests.csproj",
"Tests\ProjectB.Tests\ProjectB.Tests.csproj")

    function Get-ScriptDirectory
    {
        $Invocation = (Get-Variable MyInvocation -Scope 1).Value
        Split-Path $Invocation.MyCommand.Path
    }

    $scriptDir = Get-ScriptDirectory

    $nuget = 'nuget.exe'
    
    $solution = $buildName.Split('.')[0].Split('_')[0]
    $revision = $buildName.Split('.')[1]
    $verpart = [System.String]::Format('{0:yyMMdd}{1:00}', [System.DateTime]::Now, $revision)
    $version = "$version.$verpart"
        
    $outPath = "$outPath\$solution-$version"
    $outDir = New-Item -ItemType directory -Path $outPath

    Write-Output "Packaging $buildName ($version) from $basePath to $outPath"

    foreach($projectFile in $projectFiles)
    {
        $arguments = "pack `"$scriptDir\$projectFile`" -IncludeReferencedProjects -Version $version -BasePath `"$basePath`" -OutputDirectory `"$outPath`" -Prop Configuration=Debug"
        $proc = Start-Process -FilePath $nuget -ArgumentList (,$arguments) -NoNewWindow -Wait
    }
}

New Post: Suggestions on how to support .csproj Nuget pack targets?

cpedros — Fri, 03 May 2013 22:34:43 GMT

The problem here is that the Nuget specific operations happening in the NuGetter template are post build of the project and operate on the outputs in the drop location. At this point you do not have access to the project source and therefore there is no csproj. I think it would take a fairly substantial rework of the workflow steps to achieve this, but I could be wrong.

You could perhaps hack some way around this by using powershell in a pre-packaging step as this has access to the sources through the $tfsSourcesFolder variable. You could get the source into a pre-package folder in the drop location and then configure nuget through the template to execute against the csproj file, passing in the -Build switch as an additional command line option.

New Post: Multiple packages per build

tragichip — Wed, 24 Apr 2013 15:23:11 GMT

did you create one that works with TFS 2010? If so could you share it please?

New Post: Using nugetter with a hosted build controller.

MrHinsh — Fri, 12 Apr 2013 19:07:19 GMT

I have downloaded your source code an made a simple change to fix this...

New Post: Multiple packages per build

rushfrisby — Fri, 12 Apr 2013 13:11:56 GMT

I ended up just creating my own build template to handle it. It is pretty easy once you get the hang of it.

New Post: Multiple packages per build

mcmcod120 — Fri, 12 Apr 2013 08:04:23 GMT

Hi,

I came one step further after finding the right place of the documentation (in the download package, which contains the newest doc version).

Maybe you want to update the outdated link on the Codeplex "Documentation" Tab, which points to an old doc version of 2011, and made me get confused :-)

So I will try my luck! Thanks for providing a good peace of software!

Cheers from Austria!

New Post: Suggestions on how to support .csproj Nuget pack targets?

jonstelly — Fri, 12 Apr 2013 04:21:15 GMT

I've currently got a batch file that builds all of my packages. I use the NuGet functionality that lets me have a .nuspec sitting next to a .csproj file, and specify the .csproj file as my pack target instead of the .nuspec file.

In trying to get nugetter set up on my Team Build server, I can't do this. I've dug into the workflow a bit, and the primary issue seems to be that there are 2 activities that try to read the id element out of the .nuspec xml, and they fail if you specify the .csproj.

I see a couple ways of solving this and wanted some advice on the best way to do it so that my patch would be applied.

1) Add a boolean property to the process, something like "Pack project files if available" where the user configuring the build would still specify the .nuspec files in the multi-package list, etc... but for the last step where we invoke nuget to pack, we would check for the existence of a .csproj next to the .nuspec and use that if found.
2) Automatically detect if a .csproj file is specified as the pack target. If so, transparently open/read the .nuspec file sitting next to it.

I think #1 is the better option, as it doesn't rely on "magic" functionality that the user doesn't know about, but at the same time, #2 is similar to what nuget does itself when packaging.

I'd like to start making the changes, any preference on which direction to head? Any warnings on things I haven't mentioned that might be problematic?

New Post: Problem updating to 2012

jonstelly — Wed, 10 Apr 2013 15:54:06 GMT

Installing PowerShell 3 on the controller from Joe's link fixed the problem for me.

New Post: Multiple packages per build

mcmcod120 — Wed, 10 Apr 2013 14:52:24 GMT

I am in the same or similar situation that I want to create multiple nuget packages, but with only 1 build definition.

I am not sure how to accomplish this. Above, you point to a section "Multiple Package Build" in the documentation, but I am not sure which part you mean, because I did not find this section, I have searched in this doc:

http://download.codeplex.com/download?ProjectName=nugetter&DownloadId=251922

Did I understand right, that in the property "NuSpec File Path" of the build template ("NuGetterMultiPkgBuildVersionedTemplate20.xaml"), I can use a wildcard expression (e.g. "**.*.nuspec"), and the build template will pack one nuget package for each nuspec file it has found (in the droplocation)? (According to this thread).

Trying to use a wildcard expression "**.*.nuspec", I get an FileNotFoundException in activity "Get the file path to the NuSpec file/Get NuGetterVPackageId".

I do not know whether I am on the right way, I appreciate it to be pointed to the proper direction, thank you.

PS: I am using VS2012 and TFS2012

New Post: Using nugetter with a hosted build controller.

marknic — Fri, 05 Apr 2013 14:15:38 GMT

That information definitely helps. I haven’t had time recently to look at the code or reply because of several large projects consuming all of my time. I tried to grant someone else access to the code on CodePlex once and it turned into more than it was worth at the time. Microsoft legal thing I guess.

I am going to try to create a GitHub repo today and get the code pushed there.

I will let you know.

Thanks,

Mark

New Post: Using nugetter with a hosted build controller.

MrHinsh — Thu, 04 Apr 2013 17:07:47 GMT

If you have a local build server plugged into the cloud TFS then you can debug... however all that needs to happen is that the packaging happens against "c:\b\binaries\" rather than the Drop Location.... simples...

Would it be possible to give me access to your repository and I can fix it :) saves me from downloading the source seperatly...

New Post: Using nugetter with a hosted build controller.

MrHinsh — Mon, 01 Apr 2013 03:38:25 GMT

marknic wrote:

This is going to be harder than I thought. In VS2012 you can't see the "Copy build output to the following Source Control folder:" option. In VS2010 you can see it however you can't use it. Apparently, it is really only an option in a hosted environment so I won't be able to reproduce the situation in a controlled environment. Uggh.

Do you have an update?

New Post: Versioning of Dependend Packages

biohazard999 — Fri, 22 Mar 2013 08:45:36 GMT

Hi!

First of all, thank you for this project! It saved me a lot of work! :)

We build a "Core" that is used by a number of projects. We use NuGetter to arrange multiple packages out of this solution. However some of the packages depend on other packages in the core:

So we have such a structure:

Common
Helper
SystemModule

We build 3 different packages:

Core.Common
Core.Helper
Core.SystemModule

The nuget package specs are like this:

Core.Common
No Dependencies

-Core.Helper

Depends on Core.Common ("2.0.0.0")

-Core.SystemModule

Depends on Core.Helper ("2.0.0.0")

However building of the packages work, but if i update the package Core.SystemModule in another solution (speeking from 2.0.0 to 2.0.1) the references to Helper and Common are not updated. I guess this happens cause the dependency gets not updates cause of the "2.0.0.0" part in the dependency part in the spec files.

So my question is, is there a way to update the dependency version of some packages? (or use variables in the spec files?)

Thanks, Manuel.

New Post: Using nugetter with a hosted build controller.

MrHinsh — Tue, 19 Mar 2013 19:56:12 GMT

The drop folder is only in source control. You would need to do the packaging pre-drop on the build server...

New Post: Using nugetter with a hosted build controller.

MrHinsh — Tue, 19 Mar 2013 18:29:05 GMT

Is there a solution for this? I am running into it now as well...

New Post: Nugetter versioning question

osikes — Tue, 19 Mar 2013 18:00:14 GMT

Thank you so much, that completely solves my problem. :)

New Post: Nugetter versioning question

marknic — Tue, 19 Mar 2013 13:50:22 GMT

osikes,

I appreciate the compliment, thanks!

What you are trying to do is easy to set up. The "b" pattern takes its value from the build number that gets set as a result of the Build Number Format in the Build Definition. The default configuration for that is "$(BuildDefinitionName)_$(Date:yyyyMMdd)$(Rev:.r)" where the "$(Rev:.r)" is the build number. Any time the non-build number value changes, the build number resets. Because it has $(Date:yyyyMMdd) in it, it will change every night at midnight and the build number goes back to 1.

So, if you modify the Build Number Format to haves a "more static value" in it, the build number will simply continue to increment on every build. When you want the build number to reset, just modify the Build Number Format. You could put a name in there or a high level version number - anything you want really. Just make sure the "$(Rev:.r)" is at the end so NuGetter will have a value to work with.

Regards,

Mark

New Post: Nugetter versioning question

osikes — Mon, 18 Mar 2013 21:42:54 GMT

To start off, I love nugetter. At my office we're able to support multiple internal nuget packages with tfs builds because of this.

I have ran into an issue that I would really appreciate some clarification/ help on. I have tfs build definition using the nugettermultipkgbuildversionedtemplate20.xaml. My goal is to kick off a build, and then let the template create the nuget package with an auto incremented version number. Currently I have set the version patter to 1.0.b. This appears to work great as it is auto-incrementing on any given day, but it seems every night that this resets. Back to 1.0.0. So essentially each day the version number has reset.

What mechanism or concept am I missing to allow tfs to maintain the current nuget version number?

Any help or comments would be greatly appreciated thanks.

New Post: Multiple packages per build

marknic — Tue, 12 Mar 2013 18:59:53 GMT

The build template is specific to 2012. There are a couple additional workflow arguments that are used as part of an updated build process. The activity could be used in 2010 but an "older" base build template would be needed.

Mark