just wanted to clarify the options for client presentation :
只是想澄清客户介绍的选项:
1) winforms - for windows client - older technology 2) wpf - for windows client - newer technology, uses xaml
1)winforms - 用于Windows客户端 - 旧技术2)wpf - 用于Windows客户端 - 更新的技术,使用xaml
3) jquery - for web client - uses javascript 4) asp.net ajax - for web client - older technology 5) silverlight - for web client - newer technology, uses xaml
3)jquery - 用于web客户端 - 使用javascript 4)asp.net ajax - 用于web客户端 - 旧技术5)silverlight - 用于web客户端 - 更新的技术,使用xaml
for the web client, what are the pros and cons of option 3, 4, 5. is it better to learn jquery or asp.net ajax ? is silverlight mature enough to be used ?
对于Web客户端,选项3,4,5的优点和缺点是什么。学习jquery或asp.net ajax会更好吗?银光成熟到足以使用?
4 个解决方案
#1
In terms of desktop applications, you cannot go past WPF, the problem is there doesn't seem to be a huge knowledge or push for commercial projects using WPF.
在桌面应用程序方面,你不能超越WPF,问题是似乎没有大量的知识或推动使用WPF的商业项目。
I have been using it to write my companies in house applications and it is miles ahead of winforms, it brings all the UI templating and reuse that asp.net can have to desktop apps, plus a whole lot more.
我一直用它来编写我公司的内部应用程序,它比winforms领先一步,它带来了asp.net可以用于桌面应用程序的所有UI模板和重用,以及更多。
Spend some time to play with it, especially look at the binding side the using Linq and a project like CLinq or BindableLinq to propagate changes to the base lists to the UI without handling any events.
花一些时间来玩它,特别是看看绑定方面使用Linq和像CLinq或BindableLinq这样的项目将更改传播到基本列表到UI而不处理任何事件。
#2
jQuery and ASP.NET Ajax complement each other so I guess it's not an either or for them, at least not according to Microsoft.
jQuery和ASP.NET Ajax相互补充,所以我猜它不是一个或两个,至少不是微软的。
The problem with Silverlight is not maturity but rather the low rate of installations. In an intranet scenario this might not be a problem. Also Silverlight suffers from the same problems as Flash. It's harder to get linkability, searchability and such.
Silverlight的问题不是成熟,而是安装率低。在Intranet方案中,这可能不是问题。 Silverlight也遇到了与Flash相同的问题。获得可链接性,可搜索性等更难。
#3
I'd like to add MVC, it's part of asp.net depending on who you ask but it's so different that it's worth being on it's own.
我想添加MVC,它是asp.net的一部分,取决于你问的是谁,但它是如此不同,以至于值得它自己。
I recently rebuild an old asp.net webapplication in asp.net mvc for a customer and he was very impressed with how much more intuitive and fast the application had become. I did not do any functional changes. Just the presentation part was changed. I'd say it's worth mentioning here.
我最近在asp.net mvc中为客户重建了一个旧的asp.net web应用程序,他对应用程序变得更加直观和快速的印象非常深刻。我没有做任何功能改变。只是演示文稿部分被更改了。我想在这里值得一提。
#4
These 2 blog entries from ASP.Net answers my question
来自ASP.Net的这两篇博客文章回答了我的问题
http://weblogs.asp.net/paullitwin/archive/2009/03/30/the-four-pillars-of-asp-net.aspx
http://weblogs.asp.net/shijuvarghese/archive/2008/07/09/asp-net-mvc-vs-asp-net-web-form.aspx
#1
In terms of desktop applications, you cannot go past WPF, the problem is there doesn't seem to be a huge knowledge or push for commercial projects using WPF.
在桌面应用程序方面,你不能超越WPF,问题是似乎没有大量的知识或推动使用WPF的商业项目。
I have been using it to write my companies in house applications and it is miles ahead of winforms, it brings all the UI templating and reuse that asp.net can have to desktop apps, plus a whole lot more.
我一直用它来编写我公司的内部应用程序,它比winforms领先一步,它带来了asp.net可以用于桌面应用程序的所有UI模板和重用,以及更多。
Spend some time to play with it, especially look at the binding side the using Linq and a project like CLinq or BindableLinq to propagate changes to the base lists to the UI without handling any events.
花一些时间来玩它,特别是看看绑定方面使用Linq和像CLinq或BindableLinq这样的项目将更改传播到基本列表到UI而不处理任何事件。
#2
jQuery and ASP.NET Ajax complement each other so I guess it's not an either or for them, at least not according to Microsoft.
jQuery和ASP.NET Ajax相互补充,所以我猜它不是一个或两个,至少不是微软的。
The problem with Silverlight is not maturity but rather the low rate of installations. In an intranet scenario this might not be a problem. Also Silverlight suffers from the same problems as Flash. It's harder to get linkability, searchability and such.
Silverlight的问题不是成熟,而是安装率低。在Intranet方案中,这可能不是问题。 Silverlight也遇到了与Flash相同的问题。获得可链接性,可搜索性等更难。
#3
I'd like to add MVC, it's part of asp.net depending on who you ask but it's so different that it's worth being on it's own.
我想添加MVC,它是asp.net的一部分,取决于你问的是谁,但它是如此不同,以至于值得它自己。
I recently rebuild an old asp.net webapplication in asp.net mvc for a customer and he was very impressed with how much more intuitive and fast the application had become. I did not do any functional changes. Just the presentation part was changed. I'd say it's worth mentioning here.
我最近在asp.net mvc中为客户重建了一个旧的asp.net web应用程序,他对应用程序变得更加直观和快速的印象非常深刻。我没有做任何功能改变。只是演示文稿部分被更改了。我想在这里值得一提。
#4
These 2 blog entries from ASP.Net answers my question
来自ASP.Net的这两篇博客文章回答了我的问题
http://weblogs.asp.net/paullitwin/archive/2009/03/30/the-four-pillars-of-asp-net.aspx
http://weblogs.asp.net/shijuvarghese/archive/2008/07/09/asp-net-mvc-vs-asp-net-web-form.aspx