Page 1 of 1
VirtualStore question
Posted: Mon Mar 30, 2009 7:22 pm
by PixbyteSL
Hello,
I try to move from NSIS to Installaware and I got some problems. Most are solved with the board here but the final problem I have, with any solution, is:
I use some settings files as XML. No problem at all. But while testing my setup I installed and uninstalled a couple of time. After some looping problems I found out that Vista saved a copy of the XML inside the VirtualStore. It seems it use the XML from there, not ut of the install folder.
However, what I have to do to remove the files out of the VirtualStore, too?
Ingo
Posted: Mon Mar 30, 2009 9:36 pm
by MichaelNesmith
I don't think this question is InstallAware specific.
What if not Installaware
Posted: Tue Mar 31, 2009 1:48 am
by PixbyteSL
Hi,
excuse me? A produkt is installed and control files, like XML files are stroed in virtual paths of Vista. They will not deleted after the uninstall. So what will it be,if not a part of the installation/uninstallation?
This topic is discussed in the NSIS board very much.
Fakt is that the Software tree is builded the same in the VirtualStore. A uninstall and a reinstall will cause problems. So I think it is in all cases a InstallaWare issue.
In NSIS it is solved like:
Function un.DeleteVirtualPaths
Delete "$INSTDIR\\Data\\123.db"
StrCpy $2 $INSTDIR "" 3
Delete "$LOCALAPPDATA\\VirtualStore\\$2\\Data\\123.db"
RMDir "$LOCALAPPDATA\\VirtualStore\\$2\\Data\\"
Delete "$INSTDIR\\Log\\Activation.log"
StrCpy $2 $INSTDIR "" 3
Delete "$LOCALAPPDATA\\VirtualStore\\$2\\Log\\Activation.log"
RMDir "$LOCALAPPDATA\\VirtualStore\\$2\\Log\\"
FunctionEnd
I expect from a huge authoring solution like InstallaWare a more professional solution and not to do those things for each file by hand cause it is definitly a thing of the OS.
Ingo
Posted: Tue Mar 31, 2009 9:00 am
by MichaelNesmith
Again, this is not an InstallAware issue if Vista is caching the file elsewhere - i.e., copying it somewhere extra where InstallAware is not copying it. How can you expect InstallAware to know about a copy it has not installed?
Before blaming the product, if you had taken a moment to see whether you can implement the same workaround code you're using in InstallAware, you would have found out that the answer is yes, and that we even had an NSIS import tool.
Judging from the tone of your post, I also see it fit to remind you that we do not tolerate disrespect or abuse of our support resources on these official InstallAware forums. We're all working very hard here and don't appreciate rude or unprofessional posts or rants.