This post is very closely related to my previous post about the lessons I’ve learned while developing CaseDetective 1.3, as it’s also about my reliance on eSellerate’s tools. It’s therefore going to be a short post.
In the previous post I mentioned that with the change from Integrated eSeller to Embedded Web Store imposed by eSellerate when supporting Universal Binaries, it effected how CaseDetective checked for updates. If I’d had my own check for update code independent from eSellerate, I’d not have had any problems when eSellerate changed how they set up SKUs (Stock Control Units).
Lesson Learned: Develop your own check for update mechanism from end to end, or use an open source solution that you have full source for and control over.
