新的Windows应用程序 - 什么语言?应用程序、语言、Windows

2023-09-03 15:57:23 作者:埋头苦干

我们目前在pre开发的Windows桌面应用程序的阶段。但在Windows 8的Silverlight,WPF,木星听到所有的最新讨论的时候,我不知道该相信什么了。难道是错的开始与WPF一个新的项目吗?我应该切换到Silverlight的?或者我应该等待Windows 8的更多细节出来?

We are currently in pre phase of developing a desktop application for windows. But when hearing all the latest discussions on Windows 8, Silverlight, WPF, Jupiter I don't know what to believe anymore. Is it wrong starting a new project with WPF now? Should I switch to Silverlight? Or should I wait until more details of Windows 8 comes out?

推荐答案

有趣的话题,主要的一点是,如果你做的基础(的WinForms或WPF)或基于Web(ASP.NET MVC或Silverlight)。它的窗口

Interesting topic, main point is if you do it windows based (Winforms or WPF) or web based (ASP.NET MVC or Silverlight).

对于一个新的业务应用程序,我们才刚刚开始,现在,企业要基于Windows,因为他们希望有更多的功能,IT管理人员希望基于有一个集中的服务器,而不是试图在没有部署问题,更容易支持,以找出客户端计算机网络有...

For a new business application we are just starting now, business wants windows based because they want more features, IT wants web based to have no deployment issues and easier support on a centralized server instead of trying to figure out what the client machines has...

其实,我相信WPF准备LOB(即使仍然有比较少的WinForms第三方控件)。

In fact I believe WPF is ready for LOB (even if there are still less third party controls comparing to winforms).

我不会SL投资,因为仍需要一个插件,以及MVC / AJAX和HTML5,你可以做同样的,更无需任何插件,并在所有浏览器和平台运行具有相同的用户界面(我关注的非常有我Web应用程序的运行也是在iPad和Android平板电脑没有变化)

I would not invest on SL because still requires a plugin and with MVC / Ajax and HTML5 you can do the same and more with no plugins required and having same UI running on all browsers and platforms ( I focus very much of have my web app running also in iPad and Android tablets with no changes )...

重点是建筑,你如何分发跨服务器和层次,以便有良好分布式工作负载和可靠性好......那么,如果你有一个基于用户界面的Windows或基于网络的,只要这些用户界面消耗相同的服务器组件公开为WCF端点,例如......是细节的更多的是种......

Main point is the architecture, how you distribute it across servers and tiers so to have well distributed workloads and good reliability... then if you have a UI windows based or web based, as long these UIs consume the same server components exposed as WCF end points for example... is more a "kind" of detail...