1.1.1 vs 1.11

Topics: Project Management Forum
Coordinator
Apr 7, 2007 at 11:08 PM
Do you mind if I rename the 1.11 release to 1.1.1 since 1.11 would appear to be newer than a future 1.2 release? I would also like to tweak the setup to make this an upgrade. I don't think we should require folks to uinstall 1.1 in order to install this patched version.
Developer
Apr 8, 2007 at 3:51 PM
I think that's exactly the right thing. If you bump the 1.1 to 1.1.1 in the setup project, it will automatically do an in-place upgrade of the 1.1. I tested this myself (I built a 1.1.1 beta installer for MOW as he was having problems with the tab-expansion bug)
Coordinator
Apr 9, 2007 at 5:06 AM
OK I bumped the version number in the setup project to 1.1.1. I also bumped the AssemlbyInfo.Shared.cs version numbers to 1.1.1.
Developer
Apr 10, 2007 at 3:09 PM
Edited Apr 10, 2007 at 3:10 PM
I noticed in the check-in comment for this wi that you "didn't change any guids" - when you change the version in the setup project, it will prompt you to let it change the productcode guid. IIRC, you must let it change it or else the in-place upgrade doesn't work properly (e.g. you have to uninstall/reinstall). Conversely enough, I believe the "upgradecode" gui remains the same, and this is how it knows that it is the same product.

Test it out without and without the product guid changed.
Developer
Apr 10, 2007 at 11:41 PM
and while we're on versioning, I checked in a get-pscxversion cmdlet into 1.2 - should I backport it to 1.1.1 ?

Coordinator
Apr 11, 2007 at 5:37 AM
Do you think we need this considering that we have the $PscxVersion variable?

11> $pscxversion
 
Major  Minor  Build  Revision
-----  -----  -----  --------
1      1      1      -1
Developer
Apr 11, 2007 at 1:09 PM
Never noticed that. I see it has the -1 problem too. I noticed that when I tried to parse the version string in assemblyinfo.shared. If it's not a full dotted quad, it puts in -1's where the zeros should be...

sorry keith, getting ahead of myself. I'll remove it.
Coordinator
Apr 11, 2007 at 8:33 PM
No problem. Perhaps we should fill in the full version number in the AssemblyInfo.Shared.cs file to get rid of the stupid -1?
Developer
Apr 12, 2007 at 9:37 PM
I had done that for 1.2 anyway (i think), so go for it.
Coordinator
Apr 13, 2007 at 6:47 AM
Done. Now I've just got to figure out why Pscx.dll isn't getting re-registered. Grrr.