Accepted Solutions (1)
Hi Leon,
The Screen Painter is merely a tool to design forms. It will allow you to create a form using a visual editor and then save to an xml (or srf) file. You can't really develop an entire addon just with Screen Painter. But it is a great tool to assist in quickly creating your forms.
The B1DE is a set of tools that allows you to create your addon from scratch. The good thing about B1DE is that it's easy to use and integrated with Visual Studio. However this tool is no longer under active development by the original authors. Still, you can develop your addon and create your installer using the several wizards available. Another advantage is you can modify the source code because it's available to everyone.
B1 Studio is the "next generation" development environment. It's fairly recent compared to the other too, but it integrates well into visual studio and there is also a standalone version that you can launch from B1. However, because it's recent it still has some issues (several threads on the forum have shown that). But all of them actually have some issue. A great advantage is that B1 Studio is trying to close the gap between the way you develop Windows Forms applications and a B1 Addon. It uses familiar elements like double clicking an event name generates the method that handles that event.
Could anyone explain to me which method is best for developing and registering add-ons in SAP B1?
There isn't a best approach. All these things are just tools to help you build your addon (the SDK alone allows you to build a full addon without any of these tools).
It will always depend on what you intend to do. And all we can offer is advantages and disadvantages based on the situation. For example, if I was building a single screen addon to be used by 1 or 2 users tops, I'd go with B1 Studio. It will be fairly fast and since this is a very small application not many problems will be expected. If I need a bigger addon, but I need to do it very fast but also for a small set of users I'd go with B1DE. However, if I'm building a huge addon to be used by multiple users, and to be used in multiple versions and localizations, I'd go with the basic SDK (merely because everything would be under our own control and not some framework).
Conclusion:
Try them all, build some spike solutions to check their advantages and disadvantages and then decide based on real experiences.
Good luck.
Best regards,
Pedro Magueija
Hi Leon,
For generated code you can change it. But for code which is locked away in some dll that the environment uses (e.g.: B1 Studio uses some Framework dll) you won't be able to do anything. You can use the SDK to try and work around whatever the "framework" is doing, but this is just unnecessary work.
I'm also a bit cautious when changing code that is "expected" by some framework since we can really say what will be the effect.
Best regards,
Pedro Magueija
Answers (0)
| User | Count |
|---|---|
| 99 | |
| 12 | |
| 11 | |
| 6 | |
| 6 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.