BUG: InstallAware vs (Lack of) Short File Name
Posted: Mon Sep 08, 2014 10:58 pm
Apparently InstallAware cannot be installed on a disk volume that does not support Short File Name (8.3 format). Otherwise when you perform a build, it will complain:
This is regardless of what path you set in the File Bag statement. (And yes, the application runtimes ARE installed correctly.)
Since I'm trying to install InstallAware on a build server with very long paths, enabling Short File Name is not an option. So how should I get around this problem?
P.S. I reckon that future versions of Windows will completely remove support of it as well. Even right now Microsoft's Best Practices of setting up Windows Server discourages the use of Short File Names. So it will be useful if InstallAware can remove this limitation in the future.
InstallAware File Bag Plug-In
WARNING!
No files matching wildcard pattern C:\Program
If you were trying to build application runtimes, run InstallAware setup again, and add all optional features.
This is regardless of what path you set in the File Bag statement. (And yes, the application runtimes ARE installed correctly.)
Since I'm trying to install InstallAware on a build server with very long paths, enabling Short File Name is not an option. So how should I get around this problem?
P.S. I reckon that future versions of Windows will completely remove support of it as well. Even right now Microsoft's Best Practices of setting up Windows Server discourages the use of Short File Names. So it will be useful if InstallAware can remove this limitation in the future.