I am trying to take an existing addon developed by my predecessor internally and enhance it. Making the necessary changes are not a problem, but I want to test them before deployment to the server so as to not disrupt our active business operations. Due to the nature of the environment, I was hoping to be able to create a second testing version of this addon, with a new name to allow for testing against a test company while normal work goes on uninterrupted.
I am having trouble with deploying the addon. I have changed the name of the executable for the addon, and I have modified the ARD file to support generating a unique addon registration. The revised ARD file is generated successfully, and the installer builds as I would expect. However, the installation of the addon fails because the addon installer (derived from the SDK sample) as it is trying to create the in-memory buffer for extracting the addon EXE file to a .tmp file before renaming it.
Am I missing something incredibly obvious here? I have been working on this problem for quite some time, and I was hoping that the wisdom of the folks on here would be able to assist. What common troubles do developers have when deploying versions of addons during their development?
One short item of note, we are running SAP B1 2007A (we area hoping to upgrade to the 8.8.x version of B1 after the beginning of the new year, during our slow period).
Thanks,
Rob