创建现有 ASP.Net 3.5 应用程序的移动版本的建议
我有一个使用 ASP.Net F/W 3.5 开发的现有 Web 应用程序，并且需要创建该应用程序的移动版本。
我想就以下问题提出一些建议：
我应该从哪里开始？有一些链接吗？哪些网站可以让我更清楚地了解如何满足此要求？
是否有任何 ASP.Net/IIS 功能或 Visual Studio 选项可以简化此移动版本的创建？
因为有 RadControls 和整个应用中使用了AJAX，需要注意什么？
是否需要替换 UI 中的每个表单并与旧 UI 创建时间相同？
从性能/优化的角度我应该考虑什么？
I have an existing web application developed in ASP.Net F/W 3.5 and a mobile version of the same needs to be created.
I would like to have some suggestions on:
Where should I start? Are there some links & sites that would give me more clarity on how to approach this requirement?
Are there any ASP.Net/IIS features or Visual Studio options that might ease this mobile version creation?
As there are RadControls & AJAX used throughout the application, what should I be careful about?
Will it require every form in the UI to be replaced and take the same time as the old UI creation?
What should I be considering from the performance/optimization point of view?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
从技术角度来看，需要制作一个单独的移动版本是相当没有意义的。至少在发达国家，现代智能手机浏览器和移动网络足够好，可以处理人们可以处理的大多数事情。他们显然对臃肿的脚本和图像更敏感，但无论如何你应该优化这些东西。
单独处理移动设备的原因是用例——使用移动网站的人们与使用完整版本的人们追求的东西不同。移动设备的使用往往是匆忙的，并旨在解决一个非常具体的问题——浴室在哪里？这台笔记本电脑在亚马逊上多少钱？演出什么时候开始？而桌面用户往往更加放松。然后在多点触控风格的界面上层，你就会看到一个完全不同的野兽。以至于人们几乎想到为您的服务开发移动客户端，而不是移动网站本身。
From a technical standpoint, needing to do a separate mobile version is pretty moot. At least in the developed world, modern smartphone browsers and mobile networks are good enough that they can handle most things one can throw at them. They are obviously a bit more sensitive to bloated scripts and images, but you should be optimizing that stuff anyhow.
The reason to handle mobile separately is use case -- people using mobile sites are after different things than folks using the full-boned versions. Mobile usage tends to be hurried and pointed at solving a very specific problem -- where is the bathroom? How much is this laptop on amazon? When does the show start? Whereas desktop users tend to be a bit more relaxed. Then layer on top a multi-touch style interface and you are looking at a whole different beast. To the point one almost thinks of doing mobile clients for your services not mobile websites per se.
我读到一些移动设备支持最新版本的 telerik ajax 控件的改进（请参阅更多 此处）。最重要的是，他们在 2011 年第一季度发布时考虑了一些额外的增强功能 - 我认为它们将在您的 Web 应用程序的移动版本上表现得相当不错，但前提是它们不是本机移动组件:)
I read about some mobile devices support improvements in the recent version of the telerik ajax controls (see more here). On top of that they had some additional enhancements in mind for the Q1 2011 release - I suppose that they will perform pretty decently on a mobile version of your web app, provided that they are not native mobile components though :)
只是简化您的设计，您可以从http://www.forum.nokia.com/info/sw.nokia.com/id/5d9cd41a-7438-495a-9a46-7470e7ec8576/Nokia_Mobile_Web_Templates.html< /p>
如果您的目标是 iPhone、Android 或 WM7 等现代设备，应该没问题。但你应该小心 MS ajax 控件。它们加载相当大的脚本大小。
它将需要一个新的设计。
为了获得良好的体验，我尝试使网站尽可能简单并且手指/触摸友好。
尽量保持页面/图像/脚本尺寸较小
just simplify your design, you can download samples from http://www.forum.nokia.com/info/sw.nokia.com/id/5d9cd41a-7438-495a-9a46-7470e7ec8576/Nokia_Mobile_Web_Templates.html
Although asp.net has mobile web controls but they haven;t been updated quite a while. Besides there is no need for that.
If you target modern devices like iPhone or Android or WM7 it should be ok. But you should be carefull about MS ajax controls. They load quite large script sizes.
It will require a new design.
For a good experience I try to make site(s) as simple as possible and finger/touch friendly.
Try to keep page/image/script sizes small