Comments on: Dependency Management in .Net: Get http://lostechies.com/derekgreer/2011/09/21/dependency-management-in-net-get/ pursuing well-crafted software Wed, 12 Jun 2013 15:15:00 +0000 hourly 1 http://wordpress.org/?v=3.4.2 By: AnikaBlair http://lostechies.com/derekgreer/2011/09/21/dependency-management-in-net-get/#comment-424 AnikaBlair Wed, 07 Nov 2012 06:23:00 +0000 http://lostechies.com/derekgreer/?p=554#comment-424 Recently, I did not give whole lot thought to commenting on weblog articles and have left feedback even less. Viewing your useful piece of writing, might inspire me to do this again. Recently, I did not give whole lot thought to commenting on weblog
articles and have left feedback even less. Viewing your useful piece of
writing, might inspire me to do this again.

]]> By: The Morning Brew - Chris Alcock » The Morning Brew #942 http://lostechies.com/derekgreer/2011/09/21/dependency-management-in-net-get/#comment-275 The Morning Brew - Chris Alcock » The Morning Brew #942 Wed, 21 Sep 2011 07:50:39 +0000 http://lostechies.com/derekgreer/?p=554#comment-275 [...] Dependency Management in .Net: Get - Derek Greer follows on from his previous post on making use of NuGet without using Visual Studio, sharing a simple tool that can be used from any build process to easily fetch specific NuGet Packages. [...] [...] Dependency Management in .Net: Get – Derek Greer follows on from his previous post on making use of NuGet without using Visual Studio, sharing a simple tool that can be used from any build process to easily fetch specific NuGet Packages. [...]

]]> By: Derek Greer http://lostechies.com/derekgreer/2011/09/21/dependency-management-in-net-get/#comment-273 Derek Greer Wed, 21 Sep 2011 04:30:00 +0000 http://lostechies.com/derekgreer/?p=554#comment-273 Yep, I took a look at this the other day.  Unfortunately, there seems to be some issues with it at the moment:  https://github.com/davidfowl/NuGetPowerTools/issues/8#issuecomment-2144527 Issues aside, this only deals with updating, not with providing application-level dependency management.  It also takes the same approach as OpenWrap in that it modifies your project files to hook in its custom MSBuild files.  I prefer to keep things clean and separate.  Who knows, I might want to do something crazy one day like completely abandon MSBuild in favor of some Albacore csc.exe tasks. Bailey, you got that done yet? :) Yep, I took a look at this the other day.  Unfortunately, there seems to be some issues with it at the moment:  https://github.com/davidfowl/NuGetPowerTools/issues/8#issuecomment-2144527

Issues aside, this only deals with updating, not with providing application-level dependency management.  It also takes the same approach as OpenWrap in that it modifies your project files to hook in its custom MSBuild files.  I prefer to keep things clean and separate.  Who knows, I might want to do something crazy one day like completely abandon MSBuild in favor of some Albacore csc.exe tasks.

Bailey, you got that done yet? :)

]]> By: Derek Greer http://lostechies.com/derekgreer/2011/09/21/dependency-management-in-net-get/#comment-274 Derek Greer Wed, 21 Sep 2011 04:30:00 +0000 http://lostechies.com/derekgreer/?p=554#comment-274 Yep, I took a look at this the other day.  Unfortunately, there seems to be some issues with it at the moment:  https://github.com/davidfowl/NuGetPowerTools/issues/8#issuecomment-2144527 Issues aside, this only deals with updating, not with providing application-level dependency management.  It also takes the same approach as OpenWrap in that it modifies your project files to hook in its custom MSBuild files.  I prefer to keep things clean and separate.  Who knows, I might want to do something crazy one day like completely abandon MSBuild in favor of some Albacore csc.exe tasks. Bailey, you got that done yet? :) Yep, I took a look at this the other day.  Unfortunately, there seems to be some issues with it at the moment:  https://github.com/davidfowl/NuGetPowerTools/issues/8#issuecomment-2144527

Issues aside, this only deals with updating, not with providing application-level dependency management.  It also takes the same approach as OpenWrap in that it modifies your project files to hook in its custom MSBuild files.  I prefer to keep things clean and separate.  Who knows, I might want to do something crazy one day like completely abandon MSBuild in favor of some Albacore csc.exe tasks.

Bailey, you got that done yet? :)

]]> By: Derek Greer http://lostechies.com/derekgreer/2011/09/21/dependency-management-in-net-get/#comment-272 Derek Greer Wed, 21 Sep 2011 04:19:00 +0000 http://lostechies.com/derekgreer/?p=554#comment-272 Yeah, there's likely a few more solutions like this floating around out there.  I just took a look at it, but I find all the powershell stuff and the usage a bit off-putting.  To each his own I suppose. I did get this error when trying to run it from a 'powershell' shell though: PS C:TemptestProjChewie.0.0.5> .chewie.ps1The term 'install-package' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.At line:1 char:16+ install-package <<<<  machine.specifications    + CategoryInfo          : ObjectNotFound: (install-package:String) [], CommandNotFoundException    + FullyQualifiedErrorId : CommandNotFoundException Not sure what's going on there, but the funny thing is that it executed fine when I ran it from my bash shell via 'powershell chewie.ps1'.  Perhaps I haven't flipped all the switches correctly to make powershell 'go' :) Yeah, there’s likely a few more solutions like this floating around out there.  I just took a look at it, but I find all the powershell stuff and the usage a bit off-putting.  To each his own I suppose.

I did get this error when trying to run it from a ‘powershell’ shell though:

PS C:TemptestProjChewie.0.0.5> .chewie.ps1The term ‘install-package’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.At line:1 char:16+ install-package <<<<  machine.specifications    + CategoryInfo          : ObjectNotFound: (install-package:String) [], CommandNotFoundException    + FullyQualifiedErrorId : CommandNotFoundException

Not sure what's going on there, but the funny thing is that it executed fine when I ran it from my bash shell via 'powershell chewie.ps1'.  Perhaps I haven't flipped all the switches correctly to make powershell 'go' :)

]]> By: Jeff Schumacher http://lostechies.com/derekgreer/2011/09/21/dependency-management-in-net-get/#comment-271 Jeff Schumacher Wed, 21 Sep 2011 03:03:00 +0000 http://lostechies.com/derekgreer/?p=554#comment-271 Nuget also has similar functionality... http://docs.nuget.org/docs/workflows/using-nuget-without-committing-packages Good to have variations though! :D Nuget also has similar functionality… http://docs.nuget.org/docs/workflows/using-nuget-without-committing-packages

Good to have variations though! :D

]]> By: Jeff Schumacher http://lostechies.com/derekgreer/2011/09/21/dependency-management-in-net-get/#comment-270 Jeff Schumacher Wed, 21 Sep 2011 03:00:00 +0000 http://lostechies.com/derekgreer/?p=554#comment-270 This already exists in the form of Chewie: http://nuget.org/List/Packages/Chewie This already exists in the form of Chewie:
http://nuget.org/List/Packages/Chewie

]]>