This is an issue that has been discussed a few times before - in most depth here.
Presently ebfs cannot be applied to installs made by custom installers or those created through the Deployment Wizard. This means that for every ebf that might be needed, new installers have to be created, tested etc when only the Sybase components are changing. For some users this does not present much difficulty, but for those with large distributed install bases it does. Also, as we know in support cases, the first question is always (and reasonably), have you installed the latest ebf? Again on these occasions new installers have to be built speculatively.
Although re-building an installer after applying an ebf on the originator machine is not that great an undertaking, then testing it say XP, Vista, Windows 7, Server 2003, Server 2008, with 32 and 64 bit flavours certainly is!
Of course if one wanted to have a custom installer be capable of having an ebf applied, one would have to accept restrictions about how one installed the Sybase components and probably do some extra work, but for many that would be a price worth paying for the ability to quickly apply an ebf when that is required.
asked 29 Dec '11, 08:21
Following this question, the truly non-official description might simply say: Use the official ProductCode when generating your setup with the help of the Deployment Wizard. - Not recommendable for a few very good reasons, particularly as this will pretend your custom setup as an official one.
As long as you can assure your customers (or better: your in-house users) do not use "official SQL Anywhere setups" on their boxes, it even may work:) - However, for such cases, deplyoing a re-run Deployment Wizard'ed setup will usually be the safer alternative and won't require much more work...