Specifying a version of a package in the Add Package dialog

Oct 13, 2010 at 5:59 PM
Edited Oct 13, 2010 at 10:36 PM

I just created a mock-up of how I think for v1 we should specify the version of a package when using the Add Package dialog as part of issue http://nupack.codeplex.com/workitem/185:



  • Once the list of versions hits 15 (or a certain size?), it should be scrollable.
  • The down arrow is only displayed for packages with multiple versions.
  • In all cases, clicking directly on the install button installs the current version.
  • Same UI should apply for updating a package.
Oct 13, 2010 at 6:04 PM

So clicking on a version in the dropdown will trigger installing that version right away or it just means making it the current version and requires a separate click to install?

Oct 13, 2010 at 6:07 PM

Good question. I think it should trigger the install. What do you think?

Oct 13, 2010 at 6:07 PM

If it doesn’t trigger the install, it needs to visually indicate somehow that we’re installing a specific version. Need to figure out where that info would go.

Oct 13, 2010 at 6:12 PM

I think it should trigger the install. I wonder if we should put "Install 2.1", "Install 2.0" in the dropdown to make it clear?

Oct 13, 2010 at 6:14 PM

Yes, good idea. Make it so. J

Oct 13, 2010 at 6:19 PM
How about inline progress so I can install multiple packs at once?



Daniel Cazzulino | Developer Lead | MS MVP | Clarius Consulting | +1 425.329.3471

On Wed, Oct 13, 2010 at 14:14, Haacked <notifications@codeplex.com> wrote:

From: Haacked

Yes, good idea. Make it so. J

Read the full discussion online.

To add a post to this discussion, reply to this email (nupack@discussions.codeplex.com)

To start a new discussion for this project, email nupack@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe or change your settings on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com

Oct 13, 2010 at 6:29 PM
Edited Oct 19, 2010 at 6:08 PM

Interesting idea. Probably a vNext feature, but please log an issue. J


Oct 13, 2010 at 6:30 PM

I guess the email-reply parsing could be smarter :S

Oct 13, 2010 at 9:54 PM
Are we going to see the version in the feed as well? I know I'm looking at current temporary feed though and trying to apply it to what the finished product would look like.
"Be passionate in all you do"

Oct 13, 2010 at 10:32 PM

Yes, the feed has a version field, and each version of a package has its own feed entry.

Oct 13, 2010 at 10:37 PM

Perhaps I'm looking at something old. When I browse to the feed (internet explorer), it doesn't show me a version. I just see castle.windsor in there several times.  Sure, I'm probably wrong right off for looking there.

"Be passionate in all you do"


Oct 13, 2010 at 10:41 PM

Look for a <pkg:version> tag in the current feed.

Oct 14, 2010 at 5:11 AM
It must just be an IE thing. It doesn't show up, but if I look at the actual feed itself, it's there.
"Be passionate in all you do"

Oct 15, 2010 at 7:45 PM

When the UI queries the feed will it be grouping all the versions of a package into a single entry?  How will a user check dependencies of a particular version?

One way to solve this is have the version dropdown separate from the button.  By default the UI would set the version to the latest if uninstalled.  If already installed the version would be set to the installed version.

Oct 15, 2010 at 7:49 PM

Another option would be to make installing a different version a two step process. Currently, we proposed that selecting a version in the button drop-down would launch installation.

What if instead, it merely selects that version and the details pane changes accordingly. Then when you click install, you end up installing that version.

Oct 15, 2010 at 7:57 PM

I like the first mockup. Its exactly what I envisioned with this. Didn't think about packages with more than say 10 versions. Have to take a look at how other apps handle this but I'm thinking maybe only show 5 then "..." which will launch another image. Yucky. I don't like having one dialog turn into two though...

Same with the pick a product -> pick a version. The UX makes it a bad experience. What if I want to install 5 packages and each one has multiple versions. I now have about 15 clicks (one per package, one per version, one to install).

Let see if we can UI brainstorm this a little better to get it down to a minimum set.

Oct 16, 2010 at 5:11 PM
Edited Oct 16, 2010 at 5:11 PM

How about having the Install button at the same location, and providing Next and Previous buttons on the details pane. Clicking on Next and Previous will iterate through the available versions and at the same time, the label of the Install button will change accordingly to "Install 1.0", "Install 2.0". Clicking on Install will install the currently displayed version.

Oct 18, 2010 at 7:32 PM
Edited Oct 19, 2010 at 6:08 PM

What if we put the next/prev buttons right next to the version display like so.



One thing I like about the dropdown is you get a sense of which versions are available.

We could change the drop down version to simply select the version (and not immediately install). So when you select Install 1.9, it changes the details and the version display, but you still need to click the button to perform the install. That’ll address the concern about not being able to see the dependencies and relevant information before installing.

Oct 18, 2010 at 10:24 PM

I can't see your images.

Oct 19, 2010 at 6:08 PM

OK, I fixed the images.

Oct 19, 2010 at 11:50 PM

OK, let me implement the drop down version and see if it pans out.

Oct 20, 2010 at 1:23 AM

next/prev buttons would be awesome!

Question, how much information can be added to the right-side region (above the screenshot)?  It would be nice to add (n)+ metadata fields and display the contents in a contentscrollviewer above the screenshot.


Oct 25, 2010 at 6:29 PM

I started working on this and stumbled on a design issue. Currently, we showed a checkmark image next to a package if it is already installed. So if we want to put versions into the dropdown, how are we going to show the checkmark for the installed versions? I could show it right inside the dropdown (and disable the corresponding item), but want to know how others feel about it? And when all versions are installed, should we disable the dropdown altogether?

Oct 25, 2010 at 6:52 PM

If any version is installed, the Install button should not show up. In general, you can only have one version of a package installed in a given project. However, in the Updates tab, you can show the upgrade button and in the dropdown, show which one is the current one installed (disabled).

Oct 25, 2010 at 7:02 PM

The Updates dropdown only show newer versions. We don't have to show the current one installed, do we?

Oct 26, 2010 at 6:48 PM

Right. What I meant is within the Updates tab, if we show a newer version of "FOO" is available. Do we still have the dropdown? If so, does it only show newer versions? If so, that makes sense. I wasn't sure if it was only showing newer versions or if it shows all versions allowing you to "update" it to an older version. I guess that workflow probably doesn't make sense since the Updates tab should be about "UPDATING" it to a newer version. Did that make sense?