Files not copied to the target folder on Windows 2008 R2 DE
Posted: Thu Sep 02, 2010 9:10 am
Hello,
I have noticed that on the Windows 2008 R2 DE system, when the user chooses the "Program Files" (not "Program Files (x86)") as the target folder for the installation (in the 32-bit compatibility mode installer), the files are not copied correctly during the installation. And the installer claims that the installation was successful... What is more - when you use the localized version of the "Program Files" folder, everything is fine.
I am pasting the results of my tests with the screenshots and the detailed description.
The test environment:
1. Windows 2008 R2 DE (fresh installation)
2. "Creating IIS Websites and Virtual Folders" sample project, without any modifications.
3. The initial folder structure as in the screenshot below:
The test
1. Start the installer
2. Go to the "destination" dialog
3. On the destination dialog the target folder proposal is set to "C:\Program Files (x86)\Creating IIS Websites and Virtual Folder". This should be correct (despite the fact, that it's the DE system and the 'Program Files' should be displayed as 'Programme'). The installer is running in the 32-bit compatibility mode, that's why the (x86).
4. Change the proposed target folder to "C:\Program Files\test". I know that the 'Program Files' (without x86) is not a standard path for 32-bit applications, but this is exactly what our customers are doing. Please note that in the "Browse for Folder" modal windows the folder name is "Programme", but after clicking on "OK" it is changed to "Program Files" in the "destination" dialog. 5. Proceed with the installation
6. The results:
- The "C:\Program Files\test" folder was created, but it is empty
- The files were installed to the "C:\Program Files (x86)\test" instead... I consider this as a bug. If the redirection was done, why wasn't I (as a user) warned about it? And why wasn't the path corrected in the "destination" dialog?
Second - it doesn't look good when on one dialog you see "Program Files", and on the other "Programme" at the same time.
But now comes the most interesting part - it works correctly when you use the localized folder names (continuation in the next post because of the attachments limit).
I have noticed that on the Windows 2008 R2 DE system, when the user chooses the "Program Files" (not "Program Files (x86)") as the target folder for the installation (in the 32-bit compatibility mode installer), the files are not copied correctly during the installation. And the installer claims that the installation was successful... What is more - when you use the localized version of the "Program Files" folder, everything is fine.
I am pasting the results of my tests with the screenshots and the detailed description.
The test environment:
1. Windows 2008 R2 DE (fresh installation)
2. "Creating IIS Websites and Virtual Folders" sample project, without any modifications.
3. The initial folder structure as in the screenshot below:
The test
1. Start the installer
2. Go to the "destination" dialog
3. On the destination dialog the target folder proposal is set to "C:\Program Files (x86)\Creating IIS Websites and Virtual Folder". This should be correct (despite the fact, that it's the DE system and the 'Program Files' should be displayed as 'Programme'). The installer is running in the 32-bit compatibility mode, that's why the (x86).
4. Change the proposed target folder to "C:\Program Files\test". I know that the 'Program Files' (without x86) is not a standard path for 32-bit applications, but this is exactly what our customers are doing. Please note that in the "Browse for Folder" modal windows the folder name is "Programme", but after clicking on "OK" it is changed to "Program Files" in the "destination" dialog. 5. Proceed with the installation
6. The results:
- The "C:\Program Files\test" folder was created, but it is empty
- The files were installed to the "C:\Program Files (x86)\test" instead... I consider this as a bug. If the redirection was done, why wasn't I (as a user) warned about it? And why wasn't the path corrected in the "destination" dialog?
Second - it doesn't look good when on one dialog you see "Program Files", and on the other "Programme" at the same time.
But now comes the most interesting part - it works correctly when you use the localized folder names (continuation in the next post because of the attachments limit).