At 4:16 PM -0800 2/23/07, Wade Little wrote: >It appears that the old eSellerate plugin I used just for validating >my registration code they provided will no longer work. I have had >to move to the EWS plugin with some very minor code modifications. >This plugin will work with UB apps for mac so that I can release apps >for PPC or Intel. The problem is that it appears that I can no >longer do a Windows appliation. I used to include the eSellerate dll >file with my windows applications. > >Can anyone who has used the eSellerate plugins with RB2007 on intel >Mac verify that my UB apps will work fine with the new EWS >plugin....also how do I now do a Windows application????
eSellerate is lagging behind on fully updating their plugin, but with a little jockeying around you can make everything work. The new eSellerate plugin works with the 2007 IDE and can create Mac Intel Mach-O, Mac PPC Mach-O and Mac UB Mach-O apps. But not Mac PEF nor Windows apps. And note that the class names have changed slightly. The old eSellerate plugin can be made to work with the new 2007 IDE, but you have to use the plugin converter to update their previous plugin to the new rbx format. You can find the plugin converter in the IDE Extras folder in the full download. The converted version of their old plugin can be used to create PEF and Windows versions of your apps. BUT since it doesn't contain an Intel part, it is not recognized at all if the IDE is running on Intel. SOoooo you have to run the 2007 IDE on a PPC or using Rosetta to build eSellerate apps for PEF or Windows. As you probably already know, you can either download the PPC version of the IDE or you can use the UB version of the IDE by using GetInfo and enabling the Open Using Rosetta checkbox. In any case, the eSellerate class names are different in the two plugins so a little bit of #IF work is required too. You can keep both plugins in the same RB plugin folder and they don't conflict with each other. It's actually simpler than it might sound, but you do need to keep two versions of the IDE around and make separate builds. I use an IDE Script to switch the build mode and build only the appropriate versions so I can use the same project file for everything. BTW If you're just using the eSellerate ValidateSerialNumber call there's no reason to ship their DLL. Hope this helps, Joe Huber _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
