To give you a scenario that I think fits a sync of temporary files:
I have a folder c:/dev/artifacts which contains a changing set of files almost on a daily basis.
In the artifacts folder we are constantly updating the files in there that contain python packages. We want those to be temporary because we have a custom action (powershell script) that installs those files to a specific space on disk. Now in build 1 of the installer, we have python package c:/dev/artifacts/foo-1.1, in build 2 we have python package c:/dev/artifacts/ foo-1.2.
I want the advanced installer when run for build 2 to not reference foo-1.1 but foo-1.2 when its bundled up and I don't want to have to manually modify the aip project to now reference foo-1.2 as the artifacts folder contains many python packages and manually updating for version changes is impractical.
Hello, i'm facing the same issue. This feature would be a great improvement to this product. It's since 2018 that was requested and i think although there aren' t a lot of users didn't request it explicity, they faced the same limit for sure.
Internal implementation would not trivial, but it was passed 5 years.... sorry...
Thank you for reaching out and sharing your concerns. I completely understand your frustration regarding this feature request. It's clear that it's been a long-standing issue and it's disappointing that it hasn't been resolved yet.
I want to assure you that your feedback is incredibly valuable to us. I will make sure to escalate this to our development team once again, emphasizing the urgency and the impact it has on our users.
While I can't provide a specific timeline for when this feature will be implemented, please know that we are actively working towards finding a solution.
If you have any further questions or feedback, please don't hesitate to let me know. We truly appreciate your patience and your dedication to our product.