Just wanted to get some of this detail down, for those interested.
We have been planning the new release (v.220.127.116.11) of NuPattern to be as soon as possible. We are currently waiting to resolve one last dependency issue. After which, the release will go out, and we can then start to tackle our backlog of new features
and issues in subsequent (significantly shorter) release cycles.
We will need to change how and where we host the deliverables to maximize user experience and minimize complexity and management.
Since the new release (v.18.104.22.168) includes two separate versions of the deliverables (one for VS2010 and one for VS2012) we have needed to change our strategy on where to host the releases. In the previous version of VSPAT (v.22.214.171.124) we had a VSIX
for the Pattern Toolkit Builder and a VSIX for the Hands On Labs. We host all the released deliverables (VSIXes, HOL, docs) on this site ('Downloads' tab) AND the VSIXes on the VSGallery. The VSGallery provides the most integrated option for people to discover,
download and install the VSIX extensions. And this codeplex site provides the best option for hosting documentation, and tracking the project.
However, in the new release we will need to host 4 separate VSIXes: NuPattern Toolkit Builder for VS2010, NuPattern Toolkit Builder for VS2012, Hands On Labs for VS2010, and Hands On Labs for VS2012. They are all separate packages.
It seems a waste to (and overly complex to manage) 4 separate pages on the VS Gallery for what amounts to two of the same deliverables (albeit targeted at different version of VS). Especially because at some point in the future we may be able to consolidate
the differences between VS versions into the same deliverable that works in both versions of VS.
A different hosting strategy might now be employed that removes the immediate confusion and management complexity, but that can be improved over time should it be possible.
The VSGallery supports hosting a redirection URL instead of a VSIX binary, and that URL can redirect to the latest version of the deliverables in the 'Downloads' page on this site. And users can see the obvious distinction between which version they need
to download for their version of VS.
In this way, we can maintain the current VSGallery pages (there are currently two), persist their feedback and ratings there, and consolidate the hosting to one authoratative site.
We will not lose any ability to browse, download and install the VSIXes from within Visual Studio, althought the experience is slightly different, and to be fair a bit downgraded. But still more acceptable than having 4 different sites on the VSGallery,
4 sets of feedback, confusion and complexity etc.
The only challenge is whether we can keep the existing two VSGallery pages, and revert them back to hosting a redirection URL, since they are already configured to host a VSIX. We are investigating that issue now with the VSGAllery owners. If we cannot
revert, then we may have to abandon the existing pages, delete them and create new ones, losing our ratings, history and feedback! which is not desirable.