What winds me up is the need to write to the registry, or all over the bloody hard drive wherever they fancy.
I love nice clean software that sits in a folder and does its work there and if you want to uninstall it you could, quite literally, delete the folder and "Bobs 'yer Uncle."
A reboot after installing software should be required under the following circumstances: 1) static kernel-level code has been changed 2) err... 3) that's it
And ACO, I'm not sure that being an ASP programmer bolsters your case.
Steve Tierney - I have a few "portable" versions of freeware programmes that work very well without any installation. Some times they don't offer all the features, but it's rarely that important. One of them is an Un-installer that I've used to get rid of the crap others leave behind...
6 comments:
And the software was?
There's no justification for the reboot*, but there's no justification either for tarring all windows programmers (well I do ASP) as ijits either.
*Unless a DLL file was locked by another application and could only be replaced on reboot.
DLL hell, static linkage FTW.
What winds me up is the need to write to the registry, or all over the bloody hard drive wherever they fancy.
I love nice clean software that sits in a folder and does its work there and if you want to uninstall it you could, quite literally, delete the folder and "Bobs 'yer Uncle."
A reboot after installing software should be required under the following circumstances:
1) static kernel-level code has been changed
2) err...
3) that's it
And ACO, I'm not sure that being an ASP programmer bolsters your case.
Steve Tierney - I have a few "portable" versions of freeware programmes that work very well without any installation. Some times they don't offer all the features, but it's rarely that important. One of them is an Un-installer that I've used to get rid of the crap others leave behind...
Post a Comment