If you can run your app on the full Framework on your desktop PC, you may be
able to get useful info this way. The tools for the desktop of course are
very good. Unless you are doing a whole bunch of P/Invoke stuff or have lots
of CF-only calls, getting a CF app to work with the 1.1 desktop Framework
can often be pretty straightforward and can be worth the effort just to be
able to use the tools alone. Some caveats to consider are that the graphics
system on desktop hardware is often very different as is file I/O, so it
won't help you with all classes of problems.
When you say I/O, are you referring to flash storage? In general, writing to
flash storage will be slower than say a hard drive on a PC because flash
must erase a sector before writing. The obvious and simplest ways to improve
flash I/O are to minimize I/O access and write in fewer, larger writes at a
time. A desktop profiler would give you these kind of statistics. Often a
simple code inspection can expose these type of problems. This would be
generally true if you're writing to the in-memory file system as well.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.