Yashi,
Keep in mind that the installation of an add-on in SBO is a totally "different animal", than regular Windows installation. If you are a VB.NET programmer there is very useful sample in the SBO SDK. The best approach IMHO is to write an add-on as a single-file EXE (e.g. myaddon.exe) along with the Interop.SAPbouiCOM.dll (I'm a C# developer and I'm not sure if a VB.NET project needs this dll to interoperate with the SBO API). Write a separate installer (myinstaller.exe) which includes myaddon.exe and Interop.SAPbouiCOM.dll as embedded resources (that is embedded as binary data in the myinstaller.exe). When you register your addon, actually you register the installer. SBO stores the installer file in its database as a binay data. Next time you or any other client restarts SBO, SBO detects that the add-on has not been installed on that particular client computer, then SBO copies the (single-file) installer program into a temporary folder and launches it. When the installer is started from this temporary folder, SBO provides the destination folder as a command line argument. The installer copies the add-on files (myaddon.exe and Interop.SAPbouiCOM.dll) to the destination folder as demonstrated by the c:\Program Files\SAP Manage\SAP Business One SDK\Samples\COM UI\VB.NET\14.AddOnInstaller sample.
Let us know how are you progressing.
Miki
Add a comment