Posted by: laurentl in tasklet, best practices on
Jan 11, 2008
I will try in this article(s) to give you my view on some best practices when developing Tasklets.
So the first thing about designing a Tasklet is that it is supposed to do only one task. By creating multiple Tasklets you will add configurability and the flexibility. It will allow you to replace very easily your components and use them in different places in your application. For example, a customer search and a customer overview are related to each other, you would usually use first the search and then view the overview of the selected customer. But these 2 "tasks" could work independently; you could from a Tasklet showing a contact navigate to the customer overview of this contact. So it would be a good design to keep these functionalities in 2 different Tasklets.
Do not use orchestration actions (the ones defined in UserRole.xml) for Tasklet internal logic. If you need to have a menu item in your Tasklet that will just do something that is internal to the Tasklet, add the menu item using the Tasklet.MainMenuManager.
For instance, let's say that you are creating a Tasklet that shows a list of contacts and you want to have a menu item "Select all" to select all the contacts in the list. The "Select all" is something that belongs to the logic of the current Tasklet so we need to add a menu item from the Tasklet code. You can add the code in the OnStarted as it is called only once when creating the Tasklet.
Posted by: laurentl in Untagged on
Jan 08, 2008
Finally I pulled myself together to start my own blog!
I'm a Microsoft Developer working in Denmark in Copenhagen. I started a few month ago as .net consultant and before that I worked for about 2 years at Microsoft in the Dynamics Mobile Team where I worked on the Microsoft Dynamics Mobile Development Tools which will be the main subject of my blog. I'll try to give some examples and some tips about the mobile part of the framework.
So if there is anything topic you would like me to explore, send me a mail and I'll try to post something about it.
I saw today (which pushed me to finally start mine) that the my former colleagues from the Dynamics Mobile Team created their own blog (http://blogs.msdn.com/dynamicsmobile). :)