学习Windows Phone 7 编程时的主要痛点是什么?
我想知道其他开发者在学习 Windows Phone 7 编程时的痛点是什么.对我来说是在应用程序页面和 MVVC 之间切换.如果您有任何有助于克服这些痛点的提示或资源，请分享.
I was wondering what are the pain points for other developers when learning Windows Phone 7 programming. For me is switching between application pages and the MVVC. If you have any hints or resources helping to overcome these pain points, please share it.
当切换到一个新的开发平台时，必然会有新的东西需要学习.
When switching to a new development platform there are bound to be new things to learn.
如果您来自网络背景，请务必注意，您不再与网络处于同一个无国籍世界.还有一个不同的导航模型.(特别是如果您在 XNA 中进行开发！)
If you're coming from a web background it's important to note that you're no longer in the same stateless world as the web. There is also a different navigation model. (Especially if you're developing in XNA!)
在转向手机(或任何移动平台)开发方面，最大的，也是我认为最重要的区别是以下 6 点.
The biggest, and in my opinion, most important difference in moving to developing for the phone (or any mobile platform) are teh follwoing 6 points.
使用移动"应用程序与台式机不同.——期望用户有更少的时间花在应用程序上并成为同时做其他事情.
"Mobile" applications are used differently to desktops ones. - Expect users to have less time to spend with the application and be doing other things at the same time.
输入不同.- 考虑[多]触摸以及语音，位置和传感器，而不是鼠标和键盘.
Input is different. - Consider [multi-]touch as well as voice, location and sensors rather than mouse and keyboard.
输出不同.- 即使只是考虑输出到屏幕，这是非常不同的发展比大屏幕小.
Output is different. - Even if just considering output to the screen, it's very different developing for a small screen than a large one.
无法保证连接性.——创建离线工作的应用程序偶尔连接.别假设网络连接是保证或快速.
Connectivity is nott guaranteed. - Create apps which work offline and are occassionaly connected. Don't assume a network conneciton is guaranteed or fast.
性能很重要.- 部分移动"应用程序的方式与他们的用法不同桌面同行创建了一个来自用户的不同期望和他们的容忍度要低得多正在显示的应用程序相当于一个等待游标.做不超过你必须并确定使应用程序/设备保持响应尽可能.
Performance is important. - Partt of the way that"mobile" applications are used differently to their desktop counterparts creates a different expectation from users and they are much less tollerant of applications which are displaying the equivalent of a wait cursor. Do no more than you have to and be sure to keep the app/device as responsive as possible.
资源有限.- 这最重要的后果就是不做你必须做的事情，所以您可以延长电池寿命.毕竟，如果你耗尽了用户电池他们感到沮丧和无法使用您的应用.
Resources are constrained. - The most important consequence of this is to do no more than you must, so you can preserve battery life. Afterall, if you run down the users battery they get frustrated and can't use your app.
不幸的是，避免遇到问题的最佳方法是对平台有详细的了解和了解.
考虑到这一点，我建议使用以下资源:
Unfortunately the best way to avoid running in to problems is to develop a detailed knowledge and understadnig of the platform.
With that i mind, I'd recommend the following resources:
有关一般信息，请查看 MSDN 文档一个>.
我想特别提请您注意:设计资源，尤其是UI 指南 - 这样您就可以创建看起来好像它实际上是平台一部分的内容.
和 基本概念 - 所以你不要浪费时间尝试做不可能的事情.
For general information check out the MSDN documentation.
I'd like to particularly draw your attention to:
the design resources, particularly the UI guidelines - so you can create something which looks like it is actually part of the platform.
and the fundamental concepts - so you don't waste time trying to do something which isn't possible.
其他有用的资源是:
- 代码示例
- 在线培训(即将更新)
- Charles Petzold 的书
Other useful resources are:
- Code samples
- Online training (there are updates to this coming soon)
- the book by Charles Petzold