Author Topic: Installation Gripes  (Read 2442 times)

mark0978

  • Community Member
  • Posts: 98
  • Hero Points: -2
Installation Gripes
« on: August 25, 2011, 01:19:50 am »
When I install a product it creates a folder, when I install an update, it should overwrite the original folder and update my existing program.  Slickedit seems to think it more useful to create another folder (meaning my shortcut in the start menu no longer works!

Not only that, but the folks in the installation department can't even really decide how to name the folder

05/12/2011  12:46 PM    <DIR>          SlickEditV16.0.0x64
08/24/2011  07:58 PM    <DIR>          SlickEditV16.0.2 x64

Why does slickedit fly in the face of industry standards?

I might also ask WHY 16.0.0 didn't bother to alert me to the fact that there was an update, but since I'm not on 16.0.2, maybe that bug has been fixed?

ExtremeXS

  • Senior Community Member
  • Posts: 108
  • Hero Points: 6
Re: Installation Gripes
« Reply #1 on: August 25, 2011, 10:47:10 am »
Slick edit update always install on a per version/revision basis.  I remove older versions when I no longer need them.

For me I find that keeping the old version is really important, as updates do not always run as anticipated at first, which means I can just go back to the previous version without re-installing and tyring to reverse configuration files bumped to the new version.

vivitron

  • Senior Community Member
  • Posts: 162
  • Hero Points: 10
Re: Installation Gripes
« Reply #2 on: August 25, 2011, 11:07:28 am »
When I install a product it creates a folder, when I install an update, it should overwrite the original folder and update my existing program.  Slickedit seems to think it more useful to create another folder (meaning my shortcut in the start menu no longer works!

I have to disagree here... While that is common practice for many applications, you can also only run version one of those applications.  With Slickedit you can install multiple versions side by side which is nice if a feature has changed or there is a regression. Personally, I support this behavior.

mark0978

  • Community Member
  • Posts: 98
  • Hero Points: -2
Re: Installation Gripes
« Reply #3 on: August 25, 2011, 12:33:57 pm »
I don't remember any previous minor revisions do this.  Major revisions yes, but minor revisions always seemed to update my existing installation.

But after the last several hours, I have to admit you guys may be right, considering how badly 16.0.2 is hosing my C++ code last night and this morning, I'm regretting installing it.

I expect new versions of a program to be regression tested and behave better than the version they are replacing.

If Chrome behaved this poorly, I'd quit using it as a browser.  I used to think that slickedit was pretty complicated because of all the settings, but having done a lot of work with CSS3 and HTML in the last year, I think the layout engine of a browser is FAR MORE complex because its behavior is completely programmed by the content, and the combinations of options and possibilities are far more numerous.  Yet, they seem to be able to turn out improvement after improvement without breaking so many things that used to work.

I think this sums it up pretty well:

Quote
as updates do not always run as anticipated at first, which means I can just go back to the previous version without re-installing and tyring to reverse configuration files bumped to the new version.

This (installing minor releases into a new folder) is obviously the mechanism used to prevent needless testing of the product prior to release on unsuspecting victims customers.