My installer has to copy certain 32-bit and 64-bit communication DLLs to both Windows\System32 and Windows\SysWow64 when we run installer on Windows 64-bit. Then, at <postinstall>, I have to explicitly remove them from uninstaller, so that they remain on user machine, for the use by other applications in our "family" of products. When I install those files on 64-bit system, I specify destination using BitRock's built-in variable "windows_folder_system" to copy 64-bit DLLs to Windows\System32, and then use the same built-in variable "windows_folder_system" in combination with "<wow64FsRedirection>enable</wow64FsRedirection>" to place 32-bit DLLs into Windows\SysWOW64. At <postinstallation> step I need to somehow, using "windows_folder_system", tell uninstaller to not remove files in both Windows\System32 and Windows\SysWow64. I hesitate to use hard-coded path of "C\Windows\...", but rather use built-in vars. What would be the best approach to accomplish this, please?

Note: I read your post at http://answers.bitrock.com/questions/293/how-can-i-point-to-windows-specific-folders,

but

  1. the link to msn article did not lead where intended
  2. I was not able to find CLSID for system32 and syswow64 folders

Thanks.

asked 13 Dec '12, 19:50

Sasha's gravatar image

Sasha
6222323
accept rate: 0%


I believe your solution about using <wow64fsredirection>enable</wow64fsredirection> should work fine. What I would recommend to avoid removing the libraries from the uninstaller would be to unpack the libraries to a temporary directory (either a subdirectory under ${system_temp_directory} or under the ${installdir}) and then manually copy to the final destination using the <copyFile> action (or move them using <renameFile>). The uninstaller will not try to uninstall the libraries placed under the final destination because they were not put there by the unpacking process. Would that work for you?

We have also fixed the link to the csidl page. Thanks for reporting it.

link

answered 14 Dec '12, 04:40

juanjo's gravatar image

juanjo ♦♦
5.8k413
accept rate: 23%

I will try this apporach and will let you know if that worked out. Thank you for the idea.

(14 Dec '12, 11:56) Sasha
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×176
×12
×8

Asked: 13 Dec '12, 19:50

Seen: 2,154 times

Last updated: 14 Dec '12, 11:56