NuGet Download for NUnit?

[Charlie Poole]

Hi All,

I invited folks on the altnetseattle google group to try out the 2.6
release candidate and got pretty strong pushback for there not being a
NuGet package. I was surprised, because this group has really not made
much of an issue of it. Do you use NuGet? If so, have you been using
the (3rd party) NuGet package for NUnit?

There are some obstacles to creating an official package: primarily
that a package called nunit already exists and (I believe) the person
doing it has different ideas than I do about what should be in it. But
if there's a general desire for such a package, I'll try to overcome
the obstacles.

Of course, if there's going to be a package anyway, I'd rather it be
an "official" one. We had lots of trouble in the past with various 3rd
party versions - some with code changes, some without - of NUnit,
where reported bugs turned out to be due to the package rather than
the NUnit code itself. A lot of time was wasted. I'd rather not repeat
that experience. :-( Nevertheless, your response will determine what
sort of priority it gets.

Charlie

[Peter Gfader]

Hi Charlie

>>Do you use NuGet? 

yes

>>If so, have you been using the (3rd party) NuGet package for NUnit?

yes, if you mean this one http://nuget.org/packages/NUnit

I didnt realize that this one is not an "official" nuget nunit "thing"...

Keep up your great work!!

  .peter.gfader.

  http://blog.gfader.com/

Charlie

--
You received this message because you are subscribed to the Google Groups "NUnit-Discuss" group.
To post to this group, send email to nunit-...@googlegroups.com.
To unsubscribe from this group, send email to nunit-discus...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/nunit-discuss?hl=en.

--

[Al Gonzalez]

I have begun to use NuGet recently.
I've used it primarily for libraries and not tools as much.
I'm not using the current NuGet package because I was aware that it was not the official one. I would prefer the packages to be from an official source.

Some concerns/pain points I've had with NuGet that I'm trying to overcome or wrap my head around:

• Still not sure if the PowerShell scripts that are included can be used for malicious means or are they sand-boxed?
• NuGet places the files in a folder with a version number. This makes it difficult to have script/batch files that reference tools, since they will break if you move to a different version of the package.
• I've never really found it that hard to get the libraries that I want to use from their respective official sites, and I like to know what configuration changes are needed.

A couple of things I see as a plus:

• Larger companies can host a NuGet repo internally with all the accepted versions of libraries and tools. Developers can then install from that repo knowing that they are getting the correct version that has already been tested and approved. Any libs/tools not there would have to go through the approval process.
• For those with an experimental bent, it does make it easier to discover and try new libraries.

[Charlie Poole]

Hi Al,

Thanks. Those are good points to keep in mind.

Regarding your third bullet, I think the NuGet advocates oversell by
making the "traditional" approach of downloading seem way harder
than it really is to anyone with experience. That has put me off a bit,
but maybe I should just ignore it like I do most marketing and look
at what the tool does. ;-)

Charlie