I would like to be able to send all FF generated files to a FF_Output subdirectory but the created EXE to my main project directory.
I think that my option would be to implement this kind of thing via a user defined tool. The tool would run on post-compile and simply copy the created EXE to the project directory.
BTW, I got the private email from you regarding the Tab Control questions. I just sent you a reply. Please let me know if you get it. I originally sent the reply on May 22nd but I fear that email sent from my home account to you is getting filtered. I have sent you several emails from home and never heard anything from you (regarding that COM browser problem you experienced on one of your computers).
Quote from: TechSupportI think that my option would be to implement this kind of thing via a user defined tool. The tool would run on post-compile and simply copy the created EXE to the project directory.
Ok, that's one way to do it ... I have found out that if I set the Output Directory to <my project directory>\FF_Output that it FF creates everything, including the EXE, in that directory when using F5 ... which causes errors for me because I have data in <my project directory>\Data ... but if I use Ctrl-F5 then the EXE is created in my project directory but the FF stuff is correctly put into \FF_Output.
Quote from: TechSupportBTW, I got the private email from you regarding the Tab Control questions. I just sent you a reply. Please let me know if you get it. I originally sent the reply on May 22nd but I fear that email sent from my home account to you is getting filtered. I have sent you several emails from home and never heard anything from you (regarding that COM browser problem you experienced on one of your computers).
Well, this would explain why you are ignoring me then :D. I have had a few people get caught in my anti-spam stuff lately ... I will see if I can locate your email(s) and put your address in my whitelist.
Thanks,
This morning even Ctrl-F5 is putting the EXE in the FF_Output directory.
Quote from: TechSupportI think that my option would be to implement this kind of thing via a user defined tool. The tool would run on post-compile and simply copy the created EXE to the project directory.
I definitely want to see this post-compile option take place.
I protect my applications using Armadillo. Problem is that occasionally the behaviour changes before/after Armadillo processing - which I don't see until way later in the development cycle.
I really want to be able to send the EXE to Armadillo each time I run the application.
Andrew