Asp.net vs Silverlight建议 [英] Asp.net vs Silverlight suggestion

问题描述

亲爱的所有人，
我想开始在ERP系统上工作，我迫切需要您的建议，哪种工具可以更好地完成任务?我应该选择Asp.net还是Silverlight?
您还能给我一些为什么一个比另一个更好的原因吗?

在此先感谢！

Dear all,
I want to start working on an ERP system and I''m in dire need of your suggestions which tool is better up to the task? Should I choose Asp.net or Silverlight?
Can you also give me some reasons why one would be better than the other?

Thanks in advance!

推荐答案

有趣的问题...

好吧，我会说这取决于您的专业知识，经验和预算.任何一种工具/技术都需要大量时间才能掌握.话虽如此，通过基础教程可以用任何编程语言在几分钟或几秒钟内编写"Hello world"程序，但是当您开始开发实际应用程序时，问题和挑战就开始了.

如果您打算使用任何工具，则必须花时间来了解它的+和-.做可行性分析，一个简单的例子是，如果您想将Silverlight谷歌用于问题Silverlight"或"Silverlight功能"，您会看到很多人在评论或主张Silverlight.然后将您的业务需求放到位，并检查哪些属于现有技术问题领域，并查看是否有合适的解决方案.

如果我再举一个WPF客户端的示例，则需要使用瘦客户端将它安装在每一个新发行版的每台用户计算机上，那么您将不会获得全部收益，但您会获得更快的UI.同样，如果将服务保留在一个服务器中并与客户端连接，则可能会用SOAP进行连接，然后可能需要为每个请求放置身份验证代码，这也会使传出请求变得庞大.

ASP.NET-Web表单肯定很沉重，但是还有其他替代选择，例如使用Ajax或Visual Studio 2010附带的新MVC.MVC可以为您提供TDD，它更加简洁，并且其开源和源代码更重要.由Microsoft提供.

因此，我将投票给asp.net MVC.



谢谢，
赫曼特


采取平衡的方法.
-如果用户较少，则可以使用WPF，但如果总用户很大，则将有问题.
-客户端应用程序的好处是它们速度快并且在使用桌面资源方面没有什么限制，但是坏的事情是不同的桌面可能会基于那里的系统配置而引发不同类型的异常.
-询问企业最常做的工作，然后对要使用的技术进行一些研发.
-Web服务很好，但是它们使用XML且是字符串，这意味着如果客户端和服务器之间有大量二进制数据传输，而不是必须将二进制数据转换为base64(即字符串)，那将是昂贵的.但是如果这种操作很少，那么就没有问题.
-如果性能至关重要，则创建小型POC并测试网络流量.您可以使用Fiddler，它是免费的，并且有免费的附加组件.

谢谢，
Hemant

Interest question...

Well I''ll say it depends on your expertise, experience and budget. Any kind of tool/technology takes a good amount of time to become a master in that. having that said the "Hello world" program can be written in minutes or seconds in any programming language by going through basic tutorials but the problem and challanges start when you start developing a real world application.

If you are planning for any tool, you have to pay time to understand the + and - of it. Do a feasibility analysis, a simple example would be if you want to use Silverlight google for "problem silverlight" or "features of silverlight" you''ll see lot of people commenting or advocating about silverlight. Then put your business requirement in place and check which falls under existing technology problem area and see if a proper solution is available.

If i take another example of WPF client you need to install it on every users machine with every new release if you are targeting it with a thin client then you wont get full benefit, but you will get a faster UI. Again if you''re keeping services in one server and hitting it with client then probably you will hit them with SOAP and then you may need to put Authentication code for each request, that too, will make outgoing request bulky.

ASP.NET - the web forms are certainly heavy but there are alternatives like use ajax or the new MVC comes with Visual Studio 2010. The MVC can provide you TDD it is much more cleaner and on top of it its open source and the source code is provided from Microsoft.

So I''ll vote for asp.net MVC.



Thanks,
Hemant


Take a balanced approach.
- If user are less then you can go with WPF but if the total user are huge then it will be problematic.
- The good thing about client applications is they are fast and they have less restriction in terms of using desktop resources, but the bad thing is different desktop may raise different types of exception based on there system configuration.
- Ask the business what is the most common work they do and then do some R&D on the technology you want to use.
- The webservices are good but they use XML and that is string, that means if there are lots of binary data transfer between client and server than you have to convert binary data to base64 (i.e. string) and that will be costly. but if such operation is rare, then no issue.
- Create small POC''s and test the network traffic if performance is critical. you can use Fiddler, its free and there are free addons available.

Thanks,
Hemant

没有一个.我真的不想做涉及大型表单(例如网页)或什至使用Silverlight的事情.我的建议是使用Web服务(可能是WCF服务)连接到服务器的WPF客户端.


除了允许使用更好的用户界面外，将演示文稿移至客户端还有更多优势.您可以在客户端的RAM中缓冲数据，以最大程度地减少通过Web服务的请求量.另外，使用可用的带宽，Web服务本身更为经济，因为它仅下载数据，而不下载任何标记，图像或设计.

None of them. I would not really want to do something which involves large forms as web page or even with Silverlight. My advice would be a WPF client which connects to the server with a webservice (possibly a WCF service).


Moving the presentation to the client side has some more advantages, besides allowing to use a better user interface. You can buffer data in the client''s RAM to minimize the amount of requests over the webservice. Also, the webservice itself is more economic with the available bandwith, as it only downloads data and not any markup, images or design.

如果您需要带有精美UI的仪表板，Silverlight是更好的选择.
随着HMML5的出现，您可能还需要将其作为一个选项.

它的确也取决于您的专业知识.

If you need a dashboard with fancy UI, Silverlight is the better choice.
With HMML5 coming in, you might need to consider that as an option too.

It does depend on your expertise as well.

这篇关于Asp.net vs Silverlight建议的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！