Mike Temporale
04-07-2005, 05:15 PM
<div class='os_post_top_link'><a href='http://msdn.microsoft.com/smartclient/default.aspx?pull=/library/en-us/dnnetcomp/html/instnetcfapp.asp' target='_blank'>http://msdn.microsoft.com/smartclient/default.aspx?pull=/library/en-us/dnnetcomp/html/instnetcfapp.asp</a><br /><br /></div><i>"There are many stages to a mobile project (and any project in general), from getting a project sponsor, gathering business requirements, development, deployment, support, and so on. One stage that often is overlooked is the support stage, including designing your application for instrumentation while your mobile application is out in the field. What happens when you have released your application to the field, there is a problem, and the response you get from the user is "It doesn't work!" or "I click the button and nothing happens." This is a support person's and developer's nightmare because no one knows where to start to attempt to find a solution. You could have the user retrace their steps but that usually doesn't help. I hope that, by using the techniques discussed in this article and the library provided, the pain of supporting mobile applications in the field will be alleviated."</i><br /><br />There is a new MSDN article that talks about how to correctly handle and log any errors that might arise in your application once it has been released. Mark Arteaga, the articles author, has even included a library for you to use, or extend upon in your apps. :D