(Intro Note from Alan: for those who don't really *get* why would I want package management and is this workshop really for me? Basically ... it's like this... Openwrap(package management) is for .NET as Rails sugar is for Ruby coffee? ( get it? No.. .ok... well, in the .NET world, if you're sitting with some mates, and say, hey I got an idea for a "blah thingy", and want to quickly build a test, you'll go... ok .. we'll need to use the library xyz,which we'll need to download from ..er... where exactly, and then configure it for our own use, (er, this new version is configured slightly differently, so we have to read the manuals, (which are where?) ... ok, few hours later, and we're busy installing the correct version, when we discover that when we finally get our app running that it now depends on the GrokFooJQuery UI library, without which it gives us a runtime error... so... we head off to GrokFooJquery library website and start reading their "install" docs.... after several hours go by, your mates have already gone home and you decide to abandon your great idea that you thought you could build in 10 minute!
(27.01.11 5:28pm correction, after some compaints: OpenWrap is for .NET ... like jems is for Ruby! )
In the ruby world, you'd simply decide on what "packages (gems)" you're going to need ... as you realise you need them, and simply issue a 1 line command at the command prompt, which goes away and fetches the latest release of that package, and updates your currently project and makes sure that it has all the required settings for you to instantly be able to use it... all part of that 1 line command.
OpenWrap does the same thing for .NET! If you're not using a package management tool for .NET... then you're an {come attend the workshop and when you're finished insert your own suitable adjective or expletive}!!! ;-p) there... hopefully that's clear now!

Official intro to OpenWrap lifted from OpenWrap Website
If you are part of a team delivering complex software then this is a "Not to be missed" must attend workshop: Any .NET project beyond "hello world" is going to require external libraries and tools. There's an abundance of free, open source libraries out there, but how do you get what you need? Manually searching, downloading (and in some cases building from source) is not a productive use of your time. It's even worse when one library depends on another and you have to manage dependency chains!
GeekBeers Openwrap pre-event drinks: Please see the calendar for the Friday afternoon GeekBeers (pre-event) drinks get-together and RSVP for that as well if you can make it! Here we can discuss pre-requisites and any other pre-event questions. The pre-events are extremely valuable and will help you get the most out of the workshop the next day.
10:00 - 10:30 ( Coffee outside + sexy swag giveaway!)
10:30 - 12:00 ( Session 1)
12:00 - 13:00 ( lunch and general package management discussion)
13:00 - 14:00 (Session 2)
Date now "officially" confirmed with Seb as 5th November!
pre-requisites for this workshop
(TBA)
Date 29th October is currently tentative: I will send out an email to everyone as soon as Sebastian confirms the date is suitable.
(More info coming shortly )
If you're running or part of a team delivering complex .NET software, or moving from Java to .NET, then this is a must-not miss event! Spaces are limited, so RSVP now to reserve your spot.
For more information, please checkout http://www.openwrap.org/
I've install openwrap (really wonderfully simple) and have started a test project of my own following the "getting started" here... http://www.openwrap.org/get-started.html![]()
![]()
Recommended link from Seb, understand versioning, http://semver.org/![]()
Instructions to try out the 2.0 beta version are on Seb's blog
http://codebetter.com/sebastienlambla/2011/09/12/trying-o...![]()
![]()
Some of the helpful changes are scoped package dependencies and a new caching mechanism that speeds up NuGet repositories.
The date clashes with GiveCamp, so I can't make it. Don't know how many other members are involved with GiveCamp, though.