Skip to content

Latest commit



70 lines (31 loc) · 3.29 KB


File metadata and controls

70 lines (31 loc) · 3.29 KB
comments date layout slug title wordpress_id tags
2011-09-12 21:11:56 +0000
Trying out OpenWrap 2.0

[Update 3: github is not pushing the changes to properly, I’ve updated the link to the shell in the post to point to the correct file.]

[Update 2: The problems with side-by-side of 2.0 and 1.0 seem to be mostly resolved. Do not install 2.0 in your system repository just yet, keep it in a test project, and please update OpenWrap to the newly released 1.0.1 version which solves some of those issues.]

[Update: I’ve temporarily removed the 2.0 packages from the beta server due to unforeseen 1.0.0 / 2.0 side-by-side execution due to a bug in 1.0.0. Expect a new set of packages soon.]

We’ve come a long way since the initial work started on OpenWrap 1.1 that turned into 2.0.

We now have ReSharper 6 support and a whole lot of new features, and we’re 50 open issues from being feature complete. Still, it’s time to announce a few things.

First, the shell has been updated to 2.0, and bring back the possibility of deleting your /wraps folder when something goes bad to force an update, as well as fix a bunch of bugs that existed in the 1.1 release. Go download it now.

The second thing is that test packages of OpenWrap 2.0 are available for testing, but not on the main repository. If you have OpenWrap 1.0 installed, you can upgrade a specific project to OpenWrap 2.0 by adding the beta repository.

C:\src> o add-remote beta
# OpenWrap Shell
# Copyright © naughtyProd Limited 2009-2011
# Using C:\Users\sebastien.lambla\AppData\Local\openwrap\wraps\_cache\openwrap-\bin-net35\OpenWrap.dll (
Remote repository 'beta' added.

<font color="#444444" face="Georgia" size="3">Then you can update your project to the new test version.</font>

<font color="#444444" face="Georgia" size="3"></font>

C:\src\myProject> o update-wrap openwrap -project

If you want to install 2.0 in your system repository, and at this stage it is not recommended as those are early previews that do not guarantee that side-by-side execution will work, then any 1.0 project may fail with noun not found errors. If this is your case:

  • Change your wrap descriptor to force 1.0, so “depends: openwrap content” should be changed to “depends: openwrap = 1.0 content”

  • Force an update to 1.0.1 by doing “o update-wrap openwrap –proj –usesystem”

  • If this fails, let us know how, then simply reset your system repository to a known state using the –shellpanic flag before executing your update-wrap command.

In the next couple of weeks there will be very long blog posts about all the new features we have in there for you, but if you’ve been dying to test out the alpha releases, now you know how.

As usual, contributors are welcome, bug reports should be filled on If you’ve not involved yourself in real open source, by the people, for the people, in the open and in all honesty, now is the time.

OpenWrap is the longest running and most open package manager on .net, come and have a look.