Windows installer problems whne previous versions are not uninstalled

[ajj]

First reported as "menu items and desktop shortcut labeled as 2.2.1" during testing of 3.0 release. However see below for real issue.

[butler]

What platforme was this tested on. The PC version has 3.0 on both the welcome and about page and is the name of the desktop shortcut. Is this a problem with the mac bundler? On the other hand it is always build 1 which makes it really annoying to figure out what version is being run from inside the application. The welcome page used to capture the build number. What happened and is that still possible?

[ajj]

As per title, it was windows. Win7

I was mistaken about desktop icon (cluttered desktop), but start menu seemed to have only sasview entry, so can't have two versions in menu? Had to change install path to avoid overwriting previous. Likely not a problem for most users.

Can probably close this?

[butler]

After more experimentation the problem seems to be the following:

1. If you install a new version without uninstalling the previous version but choose to install in the existing sasview directory, the start menu items do not change their name (but point to the new place) and any desktop icons is not removed (so now you have two) but the old one still points to the new version.
2. If you install a new version without unistalling the old BUT use a different directory then most things work as expected (you have two versions) except that the start menu folder is only one and has the label of the old install. Also because only one .sasview folder is created the configurations are shared.
3. Interestingly if you uninstall before running anything then .sasview directory is removed when running uninstall. As soon as one runs sasview a .matplotlib directory is created and neither it nor the .sasview are removed during uninstall.

[butler]

The first issue stated is probably the most problematic but even that is not likely to be a huge problem for our users. We should think carefully about the install for next release though and how it should behave. Thus as agreed at fortnightly meeting of May 20, 2014 am moving this to next release tickets. Meantime we will add this as a known issue.