Bundling third party package

[k4ml]

Is it a common practice in asp.net development to include third party packages in the project repo rather than just somehow declared what dependencies it need and then let the build process pull it in ?

[ikhwanhayat]

It's common. .NET devs are rather late at adopting central package/library management like cpan or gems. But we got NuGet now and it's been growing rapidly and already have most important libs in it. In fact all the dependencies in this project are from NuGet.

NuGet is quite different though. Library files are downloaded into a "package" folder in the solution folder, rather than installed into the whole environment (we call it GAC).

Automatically downloading packages in build script is rather rare though.

[k4ml]

NuGET sound like virtualenv in python world where packages get installed into specific environment, usually created specifically for that particular project.

[ikhwanhayat]

I see, so that's what virtualenv is... So do you think virtualenv is useful
in python dev?

Microsoft use to "advocate" (at least in the way they do the tooling etc)
to put all things in GAC. But it doesn't really work, to much dependency
hell since you have to be explicit whenever you want to add reference to
certain libs. Instead of just the DLL name, you need to specify exact
version number and a unique id we call public key token of that DLL.

Getting it in and out of the GAC is another hurdle too. It's easier to put
the DLL in the working directory Deployments are easier too, just
copy/paste the whole junk :)

On Mon, May 14, 2012 at 10:15 AM, k4ml <
reply@reply.github.com

wrote:

NuGET sound like virtualenv in python world where packages get installed
into specific environment, usually created specifically for that particular
project.

---

Reply to this email directly or view it on GitHub:
#1 (comment)