We have an installer that installs to "[AppData]\[Manufacturer]\[ProductName]". During the installation it looks like it extracts the files/folders into "[AppData]\[Manufacturer]\[ProductName] [ProductVersion]". Once the installer finishes, it attempts to clean up, but the "[AppData]\[Manufacturer]\[ProductName] [ProductVersion]" folder remains with one subfolder that is empty.
This is fairly benign, but very confusing for the user when they look at "[AppData]\[Manufacturer]" in Windows Explorer and see two entries for our product, one with no version where the real install is and one with the version appended which is effectively empty. How can we properly clean up that empty one with the version appended that the installer is using as a temporary directory during the install? If it's not easy to do that, is there any way I can tell the installer to use some other temp dir that the user has access to where the left-behind empty folder won't pollute the "[AppData]\[Manufacturer]" folder and confuse the user?
FOLLOW US
Get the latest news in Application Packaging