NuGet Packages

New Post: NHibernate package dependencies

PandaWood — Tue, 04 Dec 2012 01:06:27 GMT

Ignore me, I only just realized that that latest version of nhibernate doesn't require this proxy factory packages anymore

Commented Issue: EFCodeFirst.SqlServerCompact can't be installed via Add Library Package Reference dialog [9]

sp2432 — Wed, 12 Sep 2012 08:08:49 GMT

When trying to install EFCodeFirst.SqlServerCompact via the Add Library Package Reference dialog, I get the following Operation Failed message:

"This package (or one of its dependencies) contains PowerShell scripts and needs to be installed from the Package Manager Console."

I would expect any library that can be added via the console should be able to be installed via the dialog.

(NuGet Package Manager installed is version 1.0.11217.102)
Comments: I had to install the package by specifying the version number Install-Package EFCodeFirst.SqlServerCompact -Version 0.8.8482.1

New Post: Visualizers in NuGet?

JBranders — Sat, 30 Apr 2011 16:13:04 GMT

Thanks, Haacked!

New Post: Visualizers in NuGet?

Haacked — Wed, 27 Apr 2011 04:40:18 GMT

Can they be deployed as part of a solution? My assumption is no and that they actually extend VS itself in which case you’re better off deploying them via the VS Extension gallery as a VSIX.

New Post: Visualizers in NuGet?

jbranders — Tue, 26 Apr 2011 21:14:49 GMT

Can debugger visualizers be packaged through NuGet?

Commented Issue: EFCodeFirst.SqlServerCompact can't be installed via Add Library Package Reference dialog [9]

BitStar — Tue, 12 Apr 2011 11:39:13 GMT

When trying to install EFCodeFirst.SqlServerCompact via the Add Library Package Reference dialog, I get the following Operation Failed message:

"This package (or one of its dependencies) contains PowerShell scripts and needs to be installed from the Package Manager Console."

I would expect any library that can be added via the console should be able to be installed via the dialog.

(NuGet Package Manager installed is version 1.0.11217.102)
Comments: I can't install EFCodeFirst at all because of this. So how exactly is the impact 'Low'?

Source code checked in, #a5c1bc67ab8f

davidebbo — Thu, 20 Jan 2011 20:31:26 GMT

nuget.exe update

Source code checked in, #6beb7c6e3991

davidebbo — Thu, 20 Jan 2011 19:09:57 GMT

New nuget.exe

Source code checked in, #329a39a15745

davidebbo — Thu, 20 Jan 2011 19:09:32 GMT

SQLCE Eula

Source code checked in, #c89146325c49

davidebbo — Tue, 18 Jan 2011 02:18:53 GMT

T4MVC 2.6.41

New Post: Dependency in different repo?

palelocust — Fri, 14 Jan 2011 16:19:45 GMT

That worked, thanks

New Post: Dependency in different repo?

dfowler — Fri, 14 Jan 2011 15:05:45 GMT

You need to select the "All" node.

New Post: Dependency in different repo?

palelocust — Fri, 14 Jan 2011 14:48:55 GMT

We have created some NuGet packages for our internal assemblies, and have also created our own repository out on our internal network.

Recently, I tried to add a new NuSpec that had a dependency on EFCodeFirst, which according to the NuGet gallery is the correct ID.

The problem is, when I try to install this in another project I get an error that NuGet can't find EFCodeFirst.

Is this because EFCodeFirst and our internal assemblies are in separate repos?

Source code checked in, #9cc7dbcbd9e5

davidebbo — Fri, 14 Jan 2011 02:07:09 GMT

NuGet.CommandLine 1.1.2113.118

Updated Wiki: Home

davidebbo — Wed, 12 Jan 2011 01:59:47 GMT

This site is now obsolete! Please use http://nuget.org to submit packages now!

Read this post for details.

Old content follows, only for reference

Welcome to the temporary NuGet package repository site

This is a temporary repository for NuGet packages while NuGet is in a pre-release state. By the time it reaches RTM, we’ll have a nice Gallery site with all the bells and whistles, but for now this is what our public feed is driven off.

Here is what you need to do to contribute packages:

Fork the nupackpackages repository

Note that this is a different repository from the NuGet repository, which has the sources for the NuGet engine. This one just contains packages.

Just go to the Source Code repository and create a fork. If you’re unfamiliar with Mercurial, start here. See all this page.

You will then make your changes in your fork

Add your new package files into the PackageSources folder

Packages live under the PackageSources folder. Specifically, you need to create a [PackageName]\[PackageVersion] under that. e.g. Elmah 1.1. is under PackageSources\elmah\1.1. I’ll refer to this as your root package folder.

Tip: the best way to learn the correct layout is to look through existing packages. Also, please read through this page for info on creating packages. Here are the basics:

Directly in your root package folder, create a [PackageName].nuspec file (e.g elmah.nuspec). Start by copying one from another package!
Make sure you specify all your dependencies in the nuspec files. e.g. you at sparkmvc.nuspec. Please avoid including your dependencies inside your own package, as that defeats the purpose of dependencies. e.g. if your package uses Castle.Core, don’t include those dlls in your package, but take a dependency on the Castle.Core package!
Put your assembly references under a lib folder. They can either be directly under lib, or in a subfolder if they’re framework version specific. e.g. folders can be names ‘2.0’, ‘3.5’, ‘4.0’, ‘SL4’ (for Silverlight).
You don’t need to add any entries into your NuSpec file to point to those lib files. Being in lib is all it takes to have them treated as references.
Put your content files in the Content folder. These are files that will get copied into the project when the package is installed.
If your package contains tools, put then in the Tools folder. If you include .exe files, they’ll end up being on the path in the NuGet console.

Build the packages and test your package

Go to the root of the NuPackPackages repo and run RebuildPackages.cmd. This will build all the .nupkg files into a NuPackPackages folder (i.e. NuPackPackages\NuPackPackages).
In VS, go to the NuGet console (aka Package Manager Console), and click the icon to the right of the Package Source to add a new Package source
Add a new Package Source using the local path to the folder that has the .nupkg files. e.g. D:\NuPackPackages\NuPackPackages
You can now use NuGet to try installing your package. Test it well to make sure it works the way you want!

Send a pull request

When you’re happy with your package, push your changes to your fork and send a pull request
Important: you don't need to merge with main. Many people do it in the wrong direction, which then needs to be fixed. We'll do the merge when we accept the pull request
In the pull request, please include your twitter name so we can easily ping you. Also include some info about what you’re adding.
If all goes well, your package will be in the feed in a few hours

Updated Wiki: Home

davidebbo — Wed, 12 Jan 2011 01:59:20 GMT

This site is now obsolete! Please use http://nuget.org to submit packages now!

Read this post for details.

Welcome to the temporary NuGet package repository site

Here is what you need to do to contribute packages:

Fork the nupackpackages repository

Note that this is a different repository from the NuGet repository, which has the sources for the NuGet engine. This one just contains packages.

Just go to the Source Code repository and create a fork. If you’re unfamiliar with Mercurial, start here. See all this page.

You will then make your changes in your fork

Add your new package files into the PackageSources folder

Tip: the best way to learn the correct layout is to look through existing packages. Also, please read through this page for info on creating packages. Here are the basics:

Directly in your root package folder, create a [PackageName].nuspec file (e.g elmah.nuspec). Start by copying one from another package!
Make sure you specify all your dependencies in the nuspec files. e.g. you at sparkmvc.nuspec. Please avoid including your dependencies inside your own package, as that defeats the purpose of dependencies. e.g. if your package uses Castle.Core, don’t include those dlls in your package, but take a dependency on the Castle.Core package!
Put your assembly references under a lib folder. They can either be directly under lib, or in a subfolder if they’re framework version specific. e.g. folders can be names ‘2.0’, ‘3.5’, ‘4.0’, ‘SL4’ (for Silverlight).
You don’t need to add any entries into your NuSpec file to point to those lib files. Being in lib is all it takes to have them treated as references.
Put your content files in the Content folder. These are files that will get copied into the project when the package is installed.
If your package contains tools, put then in the Tools folder. If you include .exe files, they’ll end up being on the path in the NuGet console.

Build the packages and test your package

Go to the root of the NuPackPackages repo and run RebuildPackages.cmd. This will build all the .nupkg files into a NuPackPackages folder (i.e. NuPackPackages\NuPackPackages).
In VS, go to the NuGet console (aka Package Manager Console), and click the icon to the right of the Package Source to add a new Package source
Add a new Package Source using the local path to the folder that has the .nupkg files. e.g. D:\NuPackPackages\NuPackPackages
You can now use NuGet to try installing your package. Test it well to make sure it works the way you want!

Send a pull request

When you’re happy with your package, push your changes to your fork and send a pull request
Important: you don't need to merge with main. Many people do it in the wrong direction, which then needs to be fixed. We'll do the merge when we accept the pull request
In the pull request, please include your twitter name so we can easily ping you. Also include some info about what you’re adding.
If all goes well, your package will be in the feed in a few hours

Source code checked in, #8ac0ae52389c

davidebbo — Tue, 11 Jan 2011 07:52:54 GMT

SQLCE 4.0.8482.1

Source code checked in, #fd2140f9f8d0

JamesNK — Sat, 08 Jan 2011 04:22:43 GMT

-Json.NET 4.0 Release 1

New Post: Blueprint Package?

davidebbo — Fri, 07 Jan 2011 19:42:53 GMT

Filed http://nuget.codeplex.com/workitem/543

New Post: Blueprint Package?

nkirkes — Fri, 07 Jan 2011 19:31:45 GMT

(I'm not a contributer but) As a consumer, it makes sense to me.