NuGetter Wiki Rss Feed

New Comment on "Documentation"

devnetfx — Thu, 02 May 2013 02:04:53 GMT

Thanks for the awesome work. The documentation is still pointing to Version 1. I got tripped by not realizing that there is an updated version in the download along with other nugetter components. While trying to find out how multiple packages work - http://stackoverflow.com/q/16328338/198552 Can someone update this link please.

New Comment on "Documentation"

devnetfx — Thu, 02 May 2013 02:02:38 GMT

Updated Wiki: Home

marknic — Thu, 07 Feb 2013 04:31:02 GMT

Version 2.1 Released (TFS 2012)

The NuGet project was designed to provide developers with a standardized mechanism for sharing and installing code, assemblies, etc. The creation of the packages is pretty straightforward to do in a manual way but wouldn’t it be nice if it was all automated? And, not just the packaging, the versioning and deploying should be automated as well. This way, you as the developer can create a library, build it, deploy it and immediately test it.

This is the goal of NuGetter - it is an extension to the Team Foundation Server 2012 build process that will perform all of the necessary versioning, packaging and deployment functions in a customizable and completely repeatable way.

NuGetter does not require but works better and provides more robust build features when used with TfsVersioning build versioning manager (CodePlex Project)

The current version of TFS NuGetter is 2.1 and has been tested with NuGet version 2.2.

Capabilities/Features:

Includes all phases of the build process: compile, version, pre-package, package, push/deploy and publish - managed within TFS automated build
NuGet Package and deploy features for a simple to an extremely complex library package
Single or multiple solution builds
Single or multiple configuration builds
Manage versioning of the assemblies coordinated or separately from the NuGet package
Create a package, create and push a package or create a package and push and publish to a NuGet gallery
Build and have immediate access to the package in a test environment through inherent "Push/Deploy" feature
Push locations include the NuGet Gallery, a local directory, network share or web site
Use in any combination of manual, continuous integration or scheduled builds
Ability to execute PowerShell scripts prior to packaging to organize the files (e.g., lib, tools, content) for the NuGet packaging process (pre-packaging)
No requirement for NuGet.exe to be installed on the build machine – NuGet.exe can be held in source control and deployed only at the time of the build
All of the above is managed through the standard TFS Build Workflow process
Remotely store/manage package information such as version numbers, API keys, and NuSpec manifest files
All of this is managed via a Team Foundation Server automated build process
Includes updated build process template "NuGetterMultiPkgBuildVersionedTemplate20.xaml" to work with the TfsVersioning V2.0 extended versioning capabilities.
Build Number Prefix introduced in TfsVersioning has been added to NuGetter to allow identification of similar builds (i.e., daily, CI, manual, etc.)

Build Definition Sample:

Updated Wiki: Home

marknic — Thu, 24 Jan 2013 03:14:45 GMT

Version 2.0 Released (TFS 2012)

NuGetter does not require but works better and provides more robust build features when used with TfsVersioning build versioning manager (CodePlex Project)

The current version of TFS NuGetter is 2.0 and has been tested with NuGet version 2.2.

Capabilities/Features:

Includes all phases of the build process: compile, version, pre-package, package, push/deploy and publish - managed within TFS automated build
NuGet Package and deploy features for a simple to an extremely complex library package
Single or multiple solution builds
Single or multiple configuration builds
Manage versioning of the assemblies coordinated or separately from the NuGet package
Create a package, create and push a package or create a package and push and publish to a NuGet gallery
Build and have immediate access to the package in a test environment through inherent "Push/Deploy" feature
Push locations include the NuGet Gallery, a local directory, network share or web site
Use in any combination of manual, continuous integration or scheduled builds
Ability to execute PowerShell scripts prior to packaging to organize the files (e.g., lib, tools, content) for the NuGet packaging process (pre-packaging)
No requirement for NuGet.exe to be installed on the build machine – NuGet.exe can be held in source control and deployed only at the time of the build
All of the above is managed through the standard TFS Build Workflow process
Remotely store/manage package information such as version numbers, API keys, and NuSpec manifest files
All of this is managed via a Team Foundation Server automated build process
Includes updated build process template "NuGetterMultiPkgBuildVersionedTemplate20.xaml" to work with the TfsVersioning V2.0 extended versioning capabilities.

Build Definition Sample:

Updated Wiki: Home

marknic — Wed, 23 Jan 2013 05:31:45 GMT

Version 2.0 Released (TFS 2012)

NuGetter does not require but works better and provides more robust build features when used with TfsVersioning build versioning manager (CodePlex Project)

The current version of TFS NuGetter is 2.0 and has been tested with NuGet versions 2.2.

Capabilities/Features:

Includes all phases of the build process: compile, version, pre-package, package, push/deploy and publish - managed within TFS automated build
NuGet Package and deploy features for a simple to an extremely complex library package
Single or multiple solution builds
Single or multiple configuration builds
Manage versioning of the assemblies coordinated or separately from the NuGet package
Create a package, create and push a package or create a package and push and publish to a NuGet gallery
Build and have immediate access to the package in a test environment through inherent "Push/Deploy" feature
Push locations include the NuGet Gallery, a local directory, network share or web site
Use in any combination of manual, continuous integration or scheduled builds
Ability to execute PowerShell scripts prior to packaging to organize the files (e.g., lib, tools, content) for the NuGet packaging process (pre-packaging)
No requirement for NuGet.exe to be installed on the build machine – NuGet.exe can be held in source control and deployed only at the time of the build
All of the above is managed through the standard TFS Build Workflow process
Remotely store/manage package information such as version numbers, API keys, and NuSpec manifest files
All of this is managed via a Team Foundation Server automated build process
Includes updated build process template "NuGetterMultiPkgBuildVersionedTemplate20.xaml" to work with the TfsVersioning V2.0 extended versioning capabilities.

Build Definition Sample:

Updated Wiki: Home

marknic — Wed, 23 Jan 2013 05:19:27 GMT

Version 2.0 Released

NuGetter does not require but works better and provides more robust build features when used with TfsVersioning build versioning manager (CodePlex Project)

The current version of TFS NuGetter is 2.0 and has been tested with NuGet versions 2.2.

Capabilities/Features:

Includes all phases of the build process: compile, version, pre-package, package, push/deploy and publish - managed within TFS automated build
NuGet Package and deploy features for a simple to an extremely complex library package
Single or multiple solution builds
Single or multiple configuration builds
Manage versioning of the assemblies coordinated or separately from the NuGet package
Create a package, create and push a package or create a package and push and publish to a NuGet gallery
Build and have immediate access to the package in a test environment through inherent "Push/Deploy" feature
Push locations include the NuGet Gallery, a local directory, network share or web site
Use in any combination of manual, continuous integration or scheduled builds
Ability to execute PowerShell scripts prior to packaging to organize the files (e.g., lib, tools, content) for the NuGet packaging process (pre-packaging)
No requirement for NuGet.exe to be installed on the build machine – NuGet.exe can be held in source control and deployed only at the time of the build
All of the above is managed through the standard TFS Build Workflow process
Remotely store/manage package information such as version numbers, API keys, and NuSpec manifest files
All of this is managed via a Team Foundation Server automated build process
Includes updated build process template "NuGetterMultiPkgBuildVersionedTemplate20.xaml" to work with the TfsVersioning V2.0 extended versioning capabilities.

Build Definition Sample:

New Comment on "Documentation"

AmyDudley — Tue, 17 Jan 2012 11:55:13 GMT

Hi, nice work! I was about to go and develop my own activities when I came across this project. I would like to use just the build activities in my own, heavily customized process templates. While I could certainly work my way through your work using reflector and your templates as examples to figure out exactly what each property is, some documentation on the activities and their properties would be very much appreciated and would save me and others a whole lot of time. Any chance of this happening soon?

Updated Wiki: Home

marknic — Wed, 21 Dec 2011 20:03:34 GMT

Project Description

This is the goal of NuGetter - it is an extension to the Team Foundation Server 2010 build process that will perform all of the necessary versioning, packaging and deployment functions in a customizable and completely repeatable way.

NuGetter does not require but works better and provides more robust build features when used with TfsVersioning build versioning manager (CodePlex Project)

The current version of TFS NuGetter is 1.2.0.0 and has been tested with NuGet versions 1.3, 1.4 and 1.5. Preliminary testing of the latest NuGet version 1.6 has not discovered any issues but testing continues.

NuGet Version 1.5 introduced new XML namespaces within the NuSpec file. This caused a problem with version 1.1.0.0 of NuGetter. That issue has been resolved with version 1.2.0.0. Note: This update/"fix" effects the custom activity assembly only - no changes or updates to existing TFS build templates is necessary.

Capabilities/Features:

Includes all phases of the build process: compile, version, pre-package, package, push/deploy and publish - managed within TFS 2010 automated build
NuGet Package and deploy features for a simple to an extremely complex library package
Single or multiple solution builds
Single or multiple configuration builds
Manage versioning of the assemblies coordinated or separately from the NuGet package
Create a package, create and push a package or create a package and push and publish to a NuGet gallery
Build and have immediate access to the package in a test environment through inherent "Push/Deploy" feature
Push locations include the NuGet Gallery, a local directory, network share or web site
Use in any combination of manual, continuous integration or scheduled builds
Ability to execute PowerShell scripts prior to packaging to organize the files (e.g., lib, tools, content) for the NuGet packaging process (pre-packaging)
No requirement for NuGet.exe to be installed on the build machine – NuGet.exe can be held in source control and deployed only at the time of the build
All of the above is managed through the standard TFS Build Workflow process
Remotely store/manage package information such as version numbers, API keys, and NuSpec manifest files
All of this is managed via a Team Foundation Server automated build process
Includes updated build process template "NuGetterVersioningBuildTemplate15.xaml" to work with the TfsVersioning v1.5 extended versioning capabilities.

Build Definition Sample:

Updated Wiki: Home

marknic — Wed, 21 Dec 2011 20:01:01 GMT

Project Description

NuGetter does not require but works better and provides more robust build features when used with TfsVersioning build versioning manager (CodePlex Project)

The current version of TFS NuGetter is 1.2.0.0 and has been tested with NuGet versions 1.3, 1.4 and the latest NuGet version 1.5.

NuGet Version 1.5 introduces new XML namespaces within the NuSpec file. This caused a problem with version 1.1.0.0 of NuGetter. That issue has been resolved with version 1.2.0.0. Note: This update/"fix" effects the custom activity assembly only - no changes or updates to existing TFS build templates is necessary.

Capabilities/Features:

Includes all phases of the build process: compile, version, pre-package, package, push/deploy and publish - managed within TFS 2010 automated build
NuGet Package and deploy features for a simple to an extremely complex library package
Single or multiple solution builds
Single or multiple configuration builds
Manage versioning of the assemblies coordinated or separately from the NuGet package
Create a package, create and push a package or create a package and push and publish to a NuGet gallery
Build and have immediate access to the package in a test environment through inherent "Push/Deploy" feature
Push locations include the NuGet Gallery, a local directory, network share or web site
Use in any combination of manual, continuous integration or scheduled builds
Ability to execute PowerShell scripts prior to packaging to organize the files (e.g., lib, tools, content) for the NuGet packaging process (pre-packaging)
No requirement for NuGet.exe to be installed on the build machine – NuGet.exe can be held in source control and deployed only at the time of the build
All of the above is managed through the standard TFS Build Workflow process
Remotely store/manage package information such as version numbers, API keys, and NuSpec manifest files
All of this is managed via a Team Foundation Server automated build process
Includes updated build process template "NuGetterVersioningBuildTemplate15.xaml" to work with the TfsVersioning v1.5 extended versioning capabilities.

Build Definition Sample:

Updated Wiki: Home

marknic — Wed, 21 Dec 2011 20:00:06 GMT

Project Description

NuGetter does not require but works better and provides more robust build features when used with TfsVersioning build versioning manager (CodePlex Project)

The current version of TFS NuGetter is 1.2.0.0 and has been tested with NuGet versions 1.3, 1.4, 1.5 and the latest NuGet version 1.6.

Capabilities/Features:

Includes all phases of the build process: compile, version, pre-package, package, push/deploy and publish - managed within TFS 2010 automated build
NuGet Package and deploy features for a simple to an extremely complex library package
Single or multiple solution builds
Single or multiple configuration builds
Manage versioning of the assemblies coordinated or separately from the NuGet package
Create a package, create and push a package or create a package and push and publish to a NuGet gallery
Build and have immediate access to the package in a test environment through inherent "Push/Deploy" feature
Push locations include the NuGet Gallery, a local directory, network share or web site
Use in any combination of manual, continuous integration or scheduled builds
Ability to execute PowerShell scripts prior to packaging to organize the files (e.g., lib, tools, content) for the NuGet packaging process (pre-packaging)
No requirement for NuGet.exe to be installed on the build machine – NuGet.exe can be held in source control and deployed only at the time of the build
All of the above is managed through the standard TFS Build Workflow process
Remotely store/manage package information such as version numbers, API keys, and NuSpec manifest files
All of this is managed via a Team Foundation Server automated build process
Includes updated build process template "NuGetterVersioningBuildTemplate15.xaml" to work with the TfsVersioning v1.5 extended versioning capabilities.

Build Definition Sample:

Updated Wiki: Home

marknic — Sat, 10 Sep 2011 20:58:34 GMT

Project Description

NuGetter does not require but works better and provides more robust build features when used with TfsVersioning build versioning manager (CodePlex Project)

The current version of TFS NuGetter is 1.2.0.0 and has been tested with NuGet versions 1.3, 1.4 and the latest NuGet version 1.5.

Capabilities/Features:

Includes all phases of the build process: compile, version, pre-package, package, push/deploy and publish - managed within TFS 2010 automated build
NuGet Package and deploy features for a simple to an extremely complex library package
Single or multiple solution builds
Single or multiple configuration builds
Manage versioning of the assemblies coordinated or separately from the NuGet package
Create a package, create and push a package or create a package and push and publish to a NuGet gallery
Build and have immediate access to the package in a test environment through inherent "Push/Deploy" feature
Push locations include the NuGet Gallery, a local directory, network share or web site
Use in any combination of manual, continuous integration or scheduled builds
Ability to execute PowerShell scripts prior to packaging to organize the files (e.g., lib, tools, content) for the NuGet packaging process (pre-packaging)
No requirement for NuGet.exe to be installed on the build machine – NuGet.exe can be held in source control and deployed only at the time of the build
All of the above is managed through the standard TFS Build Workflow process
Remotely store/manage package information such as version numbers, API keys, and NuSpec manifest files
All of this is managed via a Team Foundation Server automated build process
Includes updated build process template "NuGetterVersioningBuildTemplate15.xaml" to work with the TfsVersioning v1.5 extended versioning capabilities.

Build Definition Sample:

Updated Wiki: Home

marknic — Fri, 09 Sep 2011 23:06:27 GMT

Project Description

NuGetter does not require but works better and provides more robust build features when used with TfsVersioning build versioning manager (CodePlex Project)

The current version of TFS NuGetter is 1.2.0.0 and has been tested with NuGet versions 1.3, 1.4 and the latest NuGet version 1.5.

Capabilities/Features:

Includes all phases of the build process: compile, version, pre-package, package, push/deploy and publish - managed within TFS 2010 automated build
NuGet Package and deploy features for a simple to an extremely complex library package
Single or multiple solution builds
Single or multiple configuration builds
Manage versioning of the assemblies coordinated or separately from the NuGet package
Create a package, create and push a package or create a package and push and publish to a NuGet gallery
Build and have immediate access to the package in a test environment through inherent "Push/Deploy" feature
Push locations include the NuGet Gallery, a local directory, network share or web site
Use in any combination of manual, continuous integration or scheduled builds
Ability to execute PowerShell scripts prior to packaging to organize the files (e.g., lib, tools, content) for the NuGet packaging process (pre-packaging)
No requirement for NuGet.exe to be installed on the build machine – NuGet.exe can be held in source control and deployed only at the time of the build
All of the above is managed through the standard TFS Build Workflow process
Remotely store/manage package information such as version numbers, API keys, and NuSpec manifest files
All of this is managed via a Team Foundation Server automated build process
Version 1.1 includes updated build process template "NuGetterVersioningBuildTemplate15.xaml" to work with the TfsVersioning v1.5 extended versioning capabilities.

Build Definition Sample:

Updated Wiki: Home

marknic — Fri, 02 Sep 2011 22:43:17 GMT

Project Description

NuGetter does not require but works better and provides more robust build features when used with TfsVersioning build versioning manager (CodePlex Project)

The current version of TFS NuGetter is 1.1.0.0 and has been tested with NuGet versions 1.3, 1.4 and the latest NuGet version 1.5.

Capabilities/Features:

Includes all phases of the build process: compile, version, pre-package, package, push/deploy and publish - managed within TFS 2010 automated build
NuGet Package and deploy features for a simple to an extremely complex library package
Single or multiple solution builds
Single or multiple configuration builds
Manage versioning of the assemblies coordinated or separately from the NuGet package
Create a package, create and push a package or create a package and push and publish to a NuGet gallery
Build and have immediate access to the package in a test environment through inherent "Push/Deploy" feature
Push locations include the NuGet Gallery, a local directory, network share or web site
Use in any combination of manual, continuous integration or scheduled builds
Ability to execute PowerShell scripts prior to packaging to organize the files (e.g., lib, tools, content) for the NuGet packaging process (pre-packaging)
No requirement for NuGet.exe to be installed on the build machine – NuGet.exe can be held in source control and deployed only at the time of the build
All of the above is managed through the standard TFS Build Workflow process
Remotely store/manage package information such as version numbers, API keys, and NuSpec manifest files
All of this is managed via a Team Foundation Server automated build process
Version 1.1 includes updated build process template "NuGetterVersioningBuildTemplate15.xaml" to work with the TfsVersioning v1.5 extended versioning capabilities.

Build Definition Sample:

Updated Wiki: Home

marknic — Fri, 02 Sep 2011 16:44:06 GMT

Project Description

This is the goal of NuGetter. It is an extension to the Team Foundation Server 2010 build process that will perform all of the necessary versioning, packaging and deployment functions in a customizable and completely repeatable way.

NuGetter does not require but works better and provides more robust build features when used with TfsVersioning build versioning manager (CodePlex Project)

Current version is 1.1.0.0. This is the initial release.

Version 1.1.0.0 has been tested with NuGet versions 1.3, 1.4 and the newest 1.5 release.

Note: Disregard any previous message about NuGet 1.5 not working with NuGetter 1.1.0.0 - it was retested and worked as expected.

Capabilities/Features:

Includes all phases of the build process: compile, version, pre-package, package, push/deploy and publish - managed within TFS 2010 automated build
NuGet Package and deploy features for a simple to an extremely complex library package
Single or multiple solution builds
Single or multiple configuration builds
Manage versioning of the assemblies coordinated or separately from the NuGet package
Create a package, create and push a package or create a package and push and publish to a NuGet gallery
Build and have immediate access to the package in a test environment through inherent "Push/Deploy" feature
Push locations include the NuGet Gallery, a local directory, network share or web site
Use in any combination of manual, continuous integration or scheduled builds
Ability to execute PowerShell scripts prior to packaging to organize the files (e.g., lib, tools, content) for the NuGet packaging process (pre-packaging)
No requirement for NuGet.exe to be installed on the build machine – NuGet.exe can be held in source control and deployed only at the time of the build
All of the above is managed through the standard TFS Build Workflow process
Remotely store/manage package information such as version numbers, API keys, and NuSpec manifest files
All of this is managed via a Team Foundation Server automated build process
Version 1.1 includes updated build process template "NuGetterVersioningBuildTemplate15.xaml" to work with the TfsVersioning v1.5 extended versioning capabilities.

Build Definition Sample:

Updated Wiki: Home

marknic — Fri, 02 Sep 2011 16:37:20 GMT

Project Description

NuGetter does not require but works better and provides more robust build features when used with TfsVersioning build versioning manager (CodePlex Project)

Current version is 1.1.0.0. This is the initial release.

Version 1.1.0.0 has been tested with NuGet versions 1.3, 1.4 and the newest 1.5 release.

Note: Disregard any previous message about NuGet 1.5 not working with NuGetter 1.1.0.0

Capabilities/Features:

Includes all phases of the build process: compile, version, pre-package, package, push/deploy and publish - managed within TFS 2010 automated build
NuGet Package and deploy features for a simple to an extremely complex library package
Single or multiple solution builds
Single or multiple configuration builds
Manage versioning of the assemblies coordinated or separately from the NuGet package
Create a package, create and push a package or create a package and push and publish to a NuGet gallery
Build and have immediate access to the package in a test environment through inherent "Push/Deploy" feature
Push locations include the NuGet Gallery, a local directory, network share or web site
Use in any combination of manual, continuous integration or scheduled builds
Ability to execute PowerShell scripts prior to packaging to organize the files (e.g., lib, tools, content) for the NuGet packaging process (pre-packaging)
No requirement for NuGet.exe to be installed on the build machine – NuGet.exe can be held in source control and deployed only at the time of the build
All of the above is managed through the standard TFS Build Workflow process
Remotely store/manage package information such as version numbers, API keys, and NuSpec manifest files
All of this is managed via a Team Foundation Server automated build process
Version 1.1 includes updated build process template "NuGetterVersioningBuildTemplate15.xaml" to work with the TfsVersioning v1.5 extended versioning capabilities.

Build Definition Sample:

Updated Wiki: Home

marknic — Fri, 02 Sep 2011 15:51:51 GMT

Project Description

NuGetter does not require but works better and provides more robust build features when used with TfsVersioning build versioning manager (CodePlex Project)

Current version is 1.1.0.0. This is the initial release.

Version 1.1.0.0 has been tested with NuGet versions 1.3 and the latest 1.4 release.

Sept 2, 2011: Please note: NuGetter V1.1.0.0 appears to have a problem with creating a package with the newly updated NuGet version 1.5. I am aware of it and will be generating an update shortly. As stated above, versions 1.3 and 1.4 have been tested and work.

Capabilities/Features:

Includes all phases of the build process: compile, version, pre-package, package, push/deploy and publish - managed within TFS 2010 automated build
NuGet Package and deploy features for a simple to an extremely complex library package
Single or multiple solution builds
Single or multiple configuration builds
Manage versioning of the assemblies coordinated or separately from the NuGet package
Create a package, create and push a package or create a package and push and publish to a NuGet gallery
Build and have immediate access to the package in a test environment through inherent "Push/Deploy" feature
Push locations include the NuGet Gallery, a local directory, network share or web site
Use in any combination of manual, continuous integration or scheduled builds
Ability to execute PowerShell scripts prior to packaging to organize the files (e.g., lib, tools, content) for the NuGet packaging process (pre-packaging)
No requirement for NuGet.exe to be installed on the build machine – NuGet.exe can be held in source control and deployed only at the time of the build
All of the above is managed through the standard TFS Build Workflow process
Remotely store/manage package information such as version numbers, API keys, and NuSpec manifest files
All of this is managed via a Team Foundation Server automated build process
Version 1.1 includes updated build process template "NuGetterVersioningBuildTemplate15.xaml" to work with the TfsVersioning v1.5 extended versioning capabilities.

Build Definition Sample:

Updated Wiki: Home

marknic — Thu, 04 Aug 2011 14:10:14 GMT

Project Description

NuGetter does not require but works better and provides more robust build features when used with TfsVersioning build versioning manager (CodePlex Project)

Current version is 1.1.0.0. This is the initial release.

Version 1.1.0.0 has been tested with NuGet versions 1.3 and the latest 1.4 release.

Capabilities/Features:

Includes all phases of the build process: compile, version, pre-package, package, push/deploy and publish - managed within TFS 2010 automated build
NuGet Package and deploy features for a simple to an extremely complex library package
Single or multiple solution builds
Single or multiple configuration builds
Manage versioning of the assemblies coordinated or separately from the NuGet package
Create a package, create and push a package or create a package and push and publish to a NuGet gallery
Build and have immediate access to the package in a test environment through inherent "Push/Deploy" feature
Push locations include the NuGet Gallery, a local directory, network share or web site
Use in any combination of manual, continuous integration or scheduled builds
Ability to execute PowerShell scripts prior to packaging to organize the files (e.g., lib, tools, content) for the NuGet packaging process (pre-packaging)
No requirement for NuGet.exe to be installed on the build machine – NuGet.exe can be held in source control and deployed only at the time of the build
All of the above is managed through the standard TFS Build Workflow process
Remotely store/manage package information such as version numbers, API keys, and NuSpec manifest files
All of this is managed via a Team Foundation Server automated build process
Version 1.1 includes updated build process template "NuGetterVersioningBuildTemplate15.xaml" to work with the TfsVersioning v1.5 extended versioning capabilities.

Build Definition Sample:

Updated Wiki: Home

marknic — Tue, 28 Jun 2011 12:45:00 GMT

Project Description

NuGetter does not require but works better and provides more robust build features when used with TfsVersioning build versioning manager (CodePlex Project)

Current version is 1.0.0.0. This is the initial release.

Version 1.0.0.0 has been tested with NuGet versions 1.3 and the latest 1.4 release.

Capabilities/Features:

Includes all phases of the build process: compile, version, pre-package, package, push/deploy and publish
NuGet Package and deploy features for a simple to an extremely complex library package
Single or multiple solution builds
Single or multiple configuration builds
Manage versioning of the assemblies coordinated or separately from the NuGet package
Create a package, create and push a package or create a package and push and publish to a NuGet gallery
Build and have immediate access to the package in a test environment through inherent "Push/Deploy" feature
Push locations include the NuGet Gallery, a local directory, network share or web site
Use in any combination of manual, continuous integration or scheduled builds
Ability to execute PowerShell scripts prior to packaging to organize the files (e.g., lib, tools, content) for the NuGet packaging process (pre-packaging)
No requirement for NuGet.exe to be installed on the build machine – NuGet.exe can be held in source control and deployed only at the time of the build
All of the above is managed through the standard TFS Build Workflow process
Remotely store/manage package information such as version numbers, API keys, and NuSpec manifest files
All of this is managed via a Team Foundation Server automated build process

Build Definition Sample:

Updated Wiki: Home

marknic — Tue, 28 Jun 2011 12:44:18 GMT

Project Description

NuGetter does not require but works better and provides more robust build features when used with TfsVersioning build versioning manager (CodePlex Project)

Current version is 1.0.0.0. This is the initial release.

Version 1.0.0.0 has been tested with NuGet versions 1.3 and the latest 1.4 release.

Capabilities/Features:

Includes all phases of the build process: compile, version, pre-package, package, push/deploy and publish
NuGet Package and deploy features for a simple to an extremely complex library package
Single or multiple solution builds
Single or multiple configuration builds
Manage versioning of the assemblies coordinated or separately from the NuGet package
Create a package, create and push a package or create a package and push and publish to a NuGet gallery
Build and have immediate access to the package in a test environment through inherent "Push/Deploy" feature
Push locations include the NuGet Gallery, a local directory, network share or web site
Use in any combination of manual, continuous integration or scheduled builds
Ability to execute PowerShell scripts prior to packaging to organize the files (e.g., lib, tools, content) for the NuGet packaging process (pre-packaging)
No requirement for NuGet.exe to be installed on the build machine – NuGet.exe can be held in source control and deployed only at the time of the build
All of the above is managed through the standard TFS Build Workflow process
Remotely store/manage package information such as version numbers, API keys, and NuSpec manifest files
All of this is managed via a Team Foundation Server automated build process

Build Definition Sample:

Updated Wiki: Home

marknic — Thu, 23 Jun 2011 12:57:52 GMT

Project Description

NuGetter does not require but works better and provides more robust build features when used with TfsVersioning build versioning manager (CodePlex Project)

Current version is 1.0.0.0. This is the initial release.

Capabilities/Features:

Includes all phases of the build process: compile, version, pre-package, package, push/deploy and publish
NuGet Package and deploy features for a simple to an extremely complex library package
Single or multiple solution builds
Single or multiple configuration builds
Manage versioning of the assemblies coordinated or separately from the NuGet package
Create a package, create and push a package or create a package and push and publish to a NuGet gallery
Build and have immediate access to the package in a test environment through inherent "Push/Deploy" feature
Push locations include the NuGet Gallery, a local directory, network share or web site
Use in any combination of manual, continuous integration or scheduled builds
Ability to execute PowerShell scripts prior to packaging to organize the files (e.g., lib, tools, content) for the NuGet packaging process (pre-packaging)
No requirement for NuGet.exe to be installed on the build machine – NuGet.exe can be held in source control and deployed only at the time of the build
All of the above is managed through the standard TFS Build Workflow process
Remotely store/manage package information such as version numbers, API keys, and NuSpec manifest files
All of this is managed via a Team Foundation Server automated build process