Comments on: Dependency Management in .Net: install2 http://lostechies.com/derekgreer/2011/09/27/dependency-management-in-net-install2/ pursuing well-crafted software Tue, 14 May 2013 13:08:00 +0000 hourly 1 http://wordpress.org/?v=3.4.2 By: Anonymous http://lostechies.com/derekgreer/2011/09/27/dependency-management-in-net-install2/#comment-298 Anonymous Wed, 05 Oct 2011 18:44:00 +0000 http://lostechies.com/derekgreer/?p=570#comment-298 The intent of this extension is to use it as part of your CI build process, so I don't see OpenWrap or NuGet Powertools presenting any advantages over this from a CI perspective.  This solution does have its own advantages, however, in that it isn't tied to any particular build tool (OpenWrap and NuGet Powertools both rely upon custom MSBuild tasks and modification of your project files to work) and it allows you to maintain a simple solution-wide manifest to denote your project's dependencies. The intent of this extension is to use it as part of your CI build process, so I don’t see OpenWrap or NuGet Powertools presenting any advantages over this from a CI perspective.  This solution does have its own advantages, however, in that it isn’t tied to any particular build tool (OpenWrap and NuGet Powertools both rely upon custom MSBuild tasks and modification of your project files to work) and it allows you to maintain a simple solution-wide manifest to denote your project’s dependencies.

]]> By: Chris Pont http://lostechies.com/derekgreer/2011/09/27/dependency-management-in-net-install2/#comment-297 Chris Pont Wed, 05 Oct 2011 16:12:00 +0000 http://lostechies.com/derekgreer/?p=570#comment-297 Good work, and a nice simple solution. Similar to OpenWrap, but NuGet Powertools does this too, as described here... http://bit.ly/n79hA0 The advantage is that if you build using CI such as Jenkins, the dependencies will be resolved every time, and NuGet will keep the configs up to date if you decide to upgrade any packages. Good work, and a nice simple solution.

Similar to OpenWrap, but NuGet Powertools does this too, as described here… http://bit.ly/n79hA0
The advantage is that if you build using CI such as Jenkins, the dependencies will be resolved every time, and NuGet will keep the configs up to date if you decide to upgrade any packages.

]]> By: Todd Edwin King http://lostechies.com/derekgreer/2011/09/27/dependency-management-in-net-install2/#comment-293 Todd Edwin King Wed, 28 Sep 2011 18:14:00 +0000 http://lostechies.com/derekgreer/?p=570#comment-293 Project file modification notwithstanding, we use MSBuild and find that convenient.  I'm sure OpenWrap's goal is to have no specific build tool dependency. As to "magical" referencing of assemblies, that is what enables the system we have built to manage cross-team dependencies.  Dependencies are not kept with source code (except where necessary) and are pulled during build process. This goes well beyond NuGet and OpenWrap purview, but our needs go well beyond just making it easy to get and maintain open source dependencies. Cheers  Project file modification notwithstanding, we use MSBuild and find that convenient.  I’m sure OpenWrap’s goal is to have no specific build tool dependency.

As to “magical” referencing of assemblies, that is what enables the system we have built to manage cross-team dependencies.  Dependencies are not kept with source code (except where necessary) and are pulled during build process.

This goes well beyond NuGet and OpenWrap purview, but our needs go well beyond just making it easy to get and maintain open source dependencies.

Cheers 

]]> By: Anonymous http://lostechies.com/derekgreer/2011/09/27/dependency-management-in-net-install2/#comment-292 Anonymous Wed, 28 Sep 2011 15:12:00 +0000 http://lostechies.com/derekgreer/?p=570#comment-292 The advantage of this approach is that it provides solution-level dependency management independent of any particular build tool.  One of the things I don't like about OpenWrap is the modification of project files to insert hooks to OpenWrap's custom MSBuild tasks.  I'm also not sure I like the "magical" referencing of all assemblies. The advantage of this approach is that it provides solution-level dependency management independent of any particular build tool.  One of the things I don’t like about OpenWrap is the modification of project files to insert hooks to OpenWrap’s custom MSBuild tasks.  I’m also not sure I like the “magical” referencing of all assemblies.

]]> By: Todd Edwin King http://lostechies.com/derekgreer/2011/09/27/dependency-management-in-net-install2/#comment-291 Todd Edwin King Wed, 28 Sep 2011 14:39:00 +0000 http://lostechies.com/derekgreer/?p=570#comment-291 OpenWrap solves this problem pretty well now, and I hope better in the next version(s).  These build time objectives are what led me to OpenWrap after I determined that NuGet's scope/objectives aren't as powerful/useful as I was hoping. It's good to see extensions like this though, as it looks like there is hunger for more advanced usages of NuGet. OpenWrap solves this problem pretty well now, and I hope better in the next version(s).  These build time objectives are what led me to OpenWrap after I determined that NuGet’s scope/objectives aren’t as powerful/useful as I was hoping.

It’s good to see extensions like this though, as it looks like there is hunger for more advanced usages of NuGet.

]]> By: Anonymous http://lostechies.com/derekgreer/2011/09/27/dependency-management-in-net-install2/#comment-290 Anonymous Tue, 27 Sep 2011 13:27:00 +0000 http://lostechies.com/derekgreer/?p=570#comment-290 This isn't supported right now since the install command, which my extension relies upon, doesn't appear to currently support ranges.  I'll see what I can do though. ==EDIT== This turned out to be pretty easy, so its there now in version 1.0.0.1. This isn’t supported right now since the install command, which my extension relies upon, doesn’t appear to currently support ranges.  I’ll see what I can do though.

==EDIT==
This turned out to be pretty easy, so its there now in version 1.0.0.1.

]]> By: Jack Ryan http://lostechies.com/derekgreer/2011/09/27/dependency-management-in-net-install2/#comment-289 Jack Ryan Tue, 27 Sep 2011 08:21:00 +0000 http://lostechies.com/derekgreer/?p=570#comment-289 This looks excellent, we've been struggling with the best way to incorporate NuGet into our builds. Is there any support for (or planned support for) specifying an allowed version range? Or is the source available somewhere? This looks excellent, we’ve been struggling with the best way to incorporate NuGet into our builds. Is there any support for (or planned support for) specifying an allowed version range? Or is the source available somewhere?

]]> By: The Morning Brew - Chris Alcock » The Morning Brew #946 http://lostechies.com/derekgreer/2011/09/27/dependency-management-in-net-install2/#comment-288 The Morning Brew - Chris Alcock » The Morning Brew #946 Tue, 27 Sep 2011 07:52:11 +0000 http://lostechies.com/derekgreer/?p=570#comment-288 [...] Dependency Management in .Net: install2 - Derek Greer shares a NuGet Extension for retrieving application level build time external dependencies and transitive dependencies, neatly illustrating how extensions can be added to NuGet to extend the tool. [...] [...] Dependency Management in .Net: install2 – Derek Greer shares a NuGet Extension for retrieving application level build time external dependencies and transitive dependencies, neatly illustrating how extensions can be added to NuGet to extend the tool. [...]

]]>