when uninstalling the SOAPUI from windows 10 or windows 7 it will uninstall the application but the smart bear folder in c:/program files is not removed.
I am uninstalling soapui with the uninstaller.exe in the smartbear folder.
can anybody help me with any suggestions as to why the smart bear folder is not being deleted when we use the uninstaller
In general, any software installation, it keeps track of the file being installed. And the same files gets removed on uninstallation.
However, some softwares installation creates new files during that process. Apart from that, if software is used, some log files are created too.
But, when the software is uninstalled, it leaves the files those files that did not track (it may think that those are user files) and leaves them as is.
Since you know now that, those are files are not persisted by you, remove the remaining files safely.
The above mentioned is not just for this software, applicable for any software installed using installer, IMO.
Related
I'm working on an old Visual Studio 2008 project which had a setup project. I have upgraded everything to VS2019 made the changes in the code, increased the version, added a few files and made the setup.
A clean install is working perfectly.
When I first install the old version using the setup build in VS2008 and then run the new setup to upgrade this, things go freaky.
The new setup will install all new files, and just before ending it removes all files that were overwritten. Only the files that did not exist will remain.
For example, the old setup places these files in the program file folder:
- program.exe v1.0
- lib.dll v1.0
Then the new setup will install these files, overwriting the old ones:
- program.exe v2.0
- lib.dll v2.0
- other.dll v1.0
- info.txt v1.0
Just before ending the install and enabling the [close] button, the folder contents changes to:
- other.dll v1.0
- info.txt v1.0
I have checked this on multiple computers (Win 10 down to Win 7) and used a filemon tool to make sure that the new files are actually installed and then removed. The Event log only shows a successful install.
Starting the new setup again and choosing 'repair' will work and leave the files. So that is a workaround, but not the nicest one for many users.
A test with two VS2019 setup builds with different versions work correctly. The old VS2008 setups also worked correctly. So it appears to be an issue when upgrading a setup build with VS2008 with a setup build with VS2019.
Does anybody know how to fix this so that installation does not remove the files?
Okay, I had seen some VS2010 questions which looked the same. Solutions there seemed to be manually editing the msi file after the build. Far from optimal and I would assume that it was fixed by MS in VS2019.
Turns out that they have not "fixed" it, but allows Backward Compatible IDs to be used. I suddenly saw this option when going through the options panel again. Change to True:
And this does solve my issue.
More info in this answer
This question can be deleted if someone thinks it's a duplicate. When you think it's helpfull I'll accept my own answer here for archive sake.
So I'm in a situation where I need to have VS2017 enterprise installed, but I so happen to have the community version installed already (also 2017 version) with all the extensions and workloads (from the modify menu of the installer) already working in that edition.
So my question is would it be possible to share these across each of the versions so that I don't need to install presumably the same things over again?
I've thought of creating hard symlinks to the folders but I don't think that will work without all the appropriate information in some other files.
Searching only gave me guides on how to import/export plugins to another computer and from what I understand, it's basically just a list of what vs will install on another computer.
I couldn't find a exact fit solution to my problem but I did find a little workaround. Turns out the installer is a little smart this time.
First I compiled vsclone, then I put the output into cmd after installing vs_enterprise.exe.
The modify window should appear and everything is selected, click modify then wait for it to finish. The thing is that the installer surprisingly detects already installed workloads although after installing, microsoft magically adds 6gb of files to the folders it installed to (still better than the 16-17 gb that it would take if it reinstalled everything).
Finally I got a program that could help run symlink /j on multiple folders that included the vs packages after transferring those folders into my d drive (I'm running a laptop so I have very limited ssd space).
Final product works with all workloads installed properly, hope I didn't miss anything important here. I unfortunately didn't analyse the filesystem before hitting modify so we may never know what used 6gb...
So I thought I'd save myself some time in moving my visual studio installation from an old drive to my C-drive. Turns out this was a very bad idea.
I ended up trying the installers to clean up some of the mess, but they won't work, since they can't find all the files they're supposed to remove. This led me to manually delete the 'Visual studio 1x.0'-folders in an attempt to have the installers show 'Install' versus 'Modify', 'Repair' and 'Uninstall'. Now I've tried to do what support suggests on this page, https://support.microsoft.com/en-us/kb/248697, but no luck...
How can I get the installers to... install.. rather than 'Modify', 'Repair' and 'Uninstall', which they won't do anyway, since some (or most) files are missing?
Suggestions appreciated.
I just want the installer to install on C-drive, and possibly overwrite any remaining trash, be it files or configurations.
Software uninstallers sometimes fail to clean up completely. In those instances, a product like Revo Uninstaller should be able to clean up any remaining files and/or registry entries. It scans for any “leftovers” from a standard uninstaller and gives you the opportunity to selectively remove those objects that are preventing you from reinstalling.
The WIX installer I'm writing needs to install several operating system files in system folder. The program I'm writing this installer for is an old program... probably 10 years. I don't want it to replace any preexisting OS files on the user's machine. To resolve this, I figured I could use "NeverOverwrite="yes"
My problem is during the uninstall. I want the installer to ONLY uninstall the files it added. I don't want it to uninstall any pre-exisitng OS files the user already had.
Thank you
The installer should not delete files that it did not install (as Natalie commented), unless you specifically tell it to.
That said, when I need to install files directly to the system folder, I mark them as permanent so they never get uninstalled. Usually it's a Mircrosoft control or some OS file for which I don't have a separate redistributable installer, but if I had I wouldn't uninstall anyway.
I installed VS2010 pro using the web installer, but now need to install it on another machine. As this new install will require the same features as my current install, is it possible to reuse the files already downloaded? And if so, how is this achieved?
You might find some tips here. This is for the older VS web installer for the express editions, but perhaps the concepts are the same.
http://vicker313.wordpress.com/2008/11/26/how-to-offline-install-visual-studio-express-without-download-the-whole-image-file/
On my machine, the setup uses files from
C:\Documents and Settings\<username>\Local settings\Temp\30319.01\1033\VS_VSTD
but I don't yet know how to reuse them, or if that directory is the result of unpacking files from somewhere else.
I used filemon to see from where the setup was reading and writing.