Re: depoying an A5 application is a nightmare
Some things I just discovered about shortcuts:
1. There IS a Windows limit to the length of the shortcut "target" field. (For those who use Astrum, this is in regard to the WINDOWS "target" in the icon - not the "target" field in Astrum.)
2. The default paths for the -icon, -splash, and -include arguments are first the folder the Alpha5.exe file is in and then the folder the .adb file is in. THEREFORE, it is not necessary to include the path in these arguments if you put the file in one of those folders. (I prefer the .adb folder because it just seems more logical to me - the icons are part of the application not part of A5.)
WHY THIS IS IMPORTANT:
A. If you use an Include file (startup.txt, etc.), then you can leave off the path in those command lines and the user can install your application to any folder and the desktop icon will still work properly. Based on my limited testing, A5 includes the path by default so you will probably have to delete it manually.
B. If you don't use an Include file and simply put the arguments in the command line, leaving off the path in those arguments means that you are less likely to run into the length issue in #1 above.
(FWIW, Astrum allows you to put the actual install path into the arguments by using a variable for the <InstallDir> which is what I've been doing in the past. I won't do it that way in the future.)
Some things I just discovered about shortcuts:
1. There IS a Windows limit to the length of the shortcut "target" field. (For those who use Astrum, this is in regard to the WINDOWS "target" in the icon - not the "target" field in Astrum.)
2. The default paths for the -icon, -splash, and -include arguments are first the folder the Alpha5.exe file is in and then the folder the .adb file is in. THEREFORE, it is not necessary to include the path in these arguments if you put the file in one of those folders. (I prefer the .adb folder because it just seems more logical to me - the icons are part of the application not part of A5.)
WHY THIS IS IMPORTANT:
A. If you use an Include file (startup.txt, etc.), then you can leave off the path in those command lines and the user can install your application to any folder and the desktop icon will still work properly. Based on my limited testing, A5 includes the path by default so you will probably have to delete it manually.
B. If you don't use an Include file and simply put the arguments in the command line, leaving off the path in those arguments means that you are less likely to run into the length issue in #1 above.
(FWIW, Astrum allows you to put the actual install path into the arguments by using a variable for the <InstallDir> which is what I've been doing in the past. I won't do it that way in the future.)
Comment