npe Discussions Rss Feed

New Post: Add support for deleting NuGet packages from feed

dotnetjunky — Tue, 30 Apr 2013 05:02:23 GMT

This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.

New Post: Add support for deleting NuGet packages from feed

dotnetjunky — Tue, 30 Apr 2013 05:01:45 GMT

Great suggestion. Will do it in the next release.

New Post: Add support for deleting NuGet packages from feed

PombeirP — Fri, 26 Apr 2013 09:34:53 GMT

It would be very useful to allow NPE to delete packages present in the NuGet feed (nuget delete command).

New Post: Connect connect using NPE 3.3 to private NuGet feed running NuGet.Server v1.6.0.0

dotnetjunky — Fri, 22 Mar 2013 15:16:43 GMT

Yes, please upgrade NuGet.Server to the latest version and try again. Let me know if it still doesn't solve your problem.

New Post: Connect connect using NPE 3.3 to private NuGet feed running NuGet.Server v1.6.0.0

seandockery — Thu, 21 Mar 2013 19:36:17 GMT

I can view the packages in the feed from within Visual Studio via the NuGet Package Manager, but NuGet Package Explorer complains "an error occurred while processing this request" for the same package source (internal IIS serving over HTTP). I tried NPE 3.0 and had the same result. I looked for NPE 2.7 but could not find it anywhere to download and try. How can I troubleshoot the problem? Is NPE 3.3 incompatible with NuGet.Server 1.6.0.0? Is upgrading necessary?

New Post: Publish to local share

dotnetjunky — Mon, 19 Nov 2012 20:59:26 GMT

To publish to a local share, simply copy the .nupkg files into it.

New Post: Publish to local share

HawgJohnsonCOP — Mon, 19 Nov 2012 20:44:05 GMT

I've noticed that we can have a source for nuget packages to be a local share for our company. However, when I'm trying to publish to a local share it won't let me. Is there some trick for being able to do this?

New Post: Generate NuSpec file ?

eferreyra — Tue, 06 Nov 2012 18:11:51 GMT

Hi, im starting with NuGet, i have set up a local (network share) repository and i have looked for the third party libraries we use, and then have opened with NPE and Save As.. in the local repository, is this ok?

To sync my local repository with the latest versions i need to do it manually ?

I also have libraries of my own that i need to put in the local repository, can i generate (and keep sync on each build) the NuSpec file inside the VS2010 project ?

Thanks for any help.

New Post: Better symbol package support

onovotny — Sun, 07 Oct 2012 15:30:44 GMT

Along with this, it becomes more important to have wildcard support in the <Files> element and preserve the original. It's far easier to specify:

<file src="..\**\*.cs" target="src" />

And not have to manually add/remove files from the Nuspec. Today, NPE reads that element, but upon save, it saves the fully expanded list.

New Post: Better symbol package support

TripleEmcoder — Sat, 29 Sep 2012 10:29:22 GMT

I think we're in agreement here :) Where does this fit on your roadmap? Will you be looking into it anytime soon? Would you like any help with it?

New Post: Better symbol package support

dotnetjunky — Wed, 19 Sep 2012 09:53:21 GMT

Good idea. I like to add support for symbol packages myself too. Here's my thinking:

When saving a .nuspec, if the symbols are included, automatically save the symbol package at the same location as the regular package, perhaps with the convention packageName.symbols.nuspec. There will be a global setting to disable this behavior.
When pushing a package, I like your suggestion of checking for the existing .symbols.nupkg file in the same directory and showing it in the publish dialog. There will be perhaps a checkbox to disable publishing symbol package.
I like your idea of showing warning when saving a modified package too.

New Post: Better symbol package support

TripleEmcoder — Sat, 04 Aug 2012 18:53:40 GMT

I would like to start a discussion on how we could enhance NPE to better support symbol packages.

The good:

NPE treats packages as-is, so you can open, edit, save and push regular and symbol packages without any issues.
Opening a .nuspec and the saving it creates a .nupkg file, which is a nice UI-based way of doing nuget.exe pack .nuspec.

The bad:

There's no way to do nuget.exe pack -symbols with NPE.
NPE will not automatically push (autodetect) a symbols package like nuget.exe does.

I tried looking at the codebase to implement a proof-of-concept of some kind that would address these issues, but got stuck at the concept level.

My ideas so far are:

Saving a .nuspec could result in 2 file dialogs popping up - one for the regular package and one for symbols. Perhaps it could be intelligent and skip the second step if no symbols are included.
Pushing a package would check if .symbols.nupkg exists in the same directory and present an additional "Symbols Publish Url" textbox and then push both accordingly. Same thing would happen when pushing a .nuspec directly.
Saving a modified package would issue a warning if a symbol package also exists on disk, something like: "This package has a corresponding symbol package, be sure to update it as well."

What do you think?

New Post: Update nuget package using explorer

dotnetjunky — Fri, 03 Aug 2012 19:03:30 GMT

What package source did you publish to? If you go to the website of the gallery, do you see your package listed there?

New Post: Transforming MVC3 .cshtml files

dotnetjunky — Fri, 03 Aug 2012 19:02:41 GMT

You're correct. .pp is meant for new file only.

There is currently no support in nugget to add code to non-XML file.

New Post: Update nuget package using explorer

zoho — Mon, 04 Jun 2012 21:50:44 GMT

I update new package using nuget explorer .But I am not able to see it in repository .

What I did is

1.created metadata file

2.Added dlls in lib folder

3.Published it to reposiroty.It says successfully publiched , but I don;t see the package in repository.

Same happenned with updating the exisiting package.

Could you guys tell what I am missing here?

Thanks

New Post: Transforming MVC3 .cshtml files

lordofscripts — Sat, 26 May 2012 16:40:31 GMT

I created a new package and needed to add some code to the _Layout.cshtml file and the _ViewStart.cshtml files. I proceeded to create the files with the same names but with .pp extension (.transform is only for web.config as I understand, the site does not clarify).

I noticed upon deploying the package that none of these transformations were performed. Then I also read in STackOverflows that the .pp are meant for new files???

New Post: Dependency Management Suggestion

KjWhal — Tue, 24 Apr 2012 01:17:26 GMT

It would be useful if there was an icon next to each dependency that allowed you to quickly update it to latest, or provided a list of newer package version for that package; instead of having to search for a later one, add it, and delete the prior one.

New Post: Name Origin

dotnetjunky — Tue, 06 Sep 2011 17:22:27 GMT

AFAIK, it came from the Nu project, which was a community project that attempted to do the same thing as NuGet. The 'Get' part was come up by Phil Haack, so you may want to ask him directly. :)

New Post: Name Origin

Arcond — Tue, 06 Sep 2011 17:18:41 GMT

Where did the NuGet name come from? I'm assuming the Get part stems from similar package managers like Debian's apt-get. Just curious.