切换到 silverlight 进行企业应用程序？
经过 9 个月使用 MVC + JQuery 开发企业应用程序后，我们的管理层和股东有兴趣转换并切换到 silverlight！他们认为它比Ajax更强大，使开发速度比我们当前的解决方案更快，它是Windows和Web并且不那么令人头疼。
不幸的是，我们的股东对 Web 和 Web 应用程序的无状态状态一无所知，他们总是与窗口应用程序进行比较。
但我们团队中没有人了解 silverlight。我不确定这是一个好的决定。我认为我们会尽快发展。我们开发了一个很棒的框架和代码生成器以实现快速开发。
谢谢，抱歉英语不好。
After 9 month developing an enterprise application using MVC + JQuery our Management and stockholders interesting to convert and switch to silverlight! they think it's more powerful than Ajax, make development speed faster than our current solution, It's Windows and Web and less headache.
Unfortunately, our stockholders dos not know anything about web and stateless state of web application and they always compare with window applications.
But nobody in our team know anything about silverlight. I am not sure that is a good decision. I think we develop as fast as possible. we develop a great framework and code generator for fast develop.
Thanks and sorry for bad English.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
放弃现有的东西并在开发过程中进行重建几乎总是一个坏主意。
对于个人项目，我正是这样做的。它最初是在 asp.net MVC 测试版期间构建的。我让应用程序达到了可用的阶段（实际上我仍然每天使用它），但它还远没有为外界做好准备。这就是问题所在；这需要做大量的工作才能让其他人使用它...
当 Silverlight 3 发布时，我实际上抓住了应用程序的后端 - 将 RIA 服务插入其中，并在那天启动并运行了几个屏幕无需任何先前的 SL 知识。我本来可以继续沿着这条路走下去，但当我开始意识到 silverlight 的力量时，我突然灵光一现。我的应用程序的目标帖子发生了变化，我开始了 SL 特定的重写。
从那时起，我已经开始重写大约五次了。我想我仍在学习如何最好地在 SL 中构建应用程序，在我职业生涯的最后 12 年左右的时间里一直致力于无状态 Web 应用程序，这涉及到一个巨大的思维转变。
我是一个比 Silverlight 开发人员更好的 Web 开发人员，但如果它是一个真正的项目（而不是一个宠物项目） - 它现在已经被运送出去了。
我确信 SL 是大多数 Web 应用程序的理想平台（只要它是一个插件就不会有任何问题）。
话虽如此，运输仍然是最重要的。 SL 很棒，但学习曲线很陡。如果你们快要完成这个应用程序了，我会坚持你们继续使用 mvc，也许找人建立一个 SL 分支。
Dumping what you have and going for a rebuild mid development is almost always a bad idea.
For a personal project, I did exactly this. It was originally built during the betas of asp.net MVC. I got the app to a stage where it was usable (actually I still use it daily), but it was nowhere near ready for the outside world. And this was the problem; it was going to take an enormous amount of work so that other people could use it...
When Silverlight 3 was announced, I literally grabbed the backend of the app - stuck RIA services in between and had a few screens up and running that day without any prior SL knowledge. I probably could have kept going down this path but something clicked when I started to realise the power of silverlight. The goal posts for my app moved, and I began a SL specific rewrite.
Since then, I've started re-writing about 5 times over. I guess I'm still just learning how to best build an app in SL, having spent the last 12 years or so of my career working on stateless web apps, there was a big mental shift involved.
I'm a much better web developer then I am a silverlight developer, but if it was for a real project (rather then a pet side project) - it would have been shipped and out the door by now.
I'm convinced that SL is the ideal platform for most web applications (as long as it being a plugin isn't going to be any issue).
With that said, shipping is still the most important thing. SL is great, but the learning curve is steep. If you guys are anywhere near completing the app, I'd insist you forge on with mvc and maybe get someone to build a SL branch.
重新构建应用程序平台总是成本高昂，尽管如果您的 MVC 正确，理论上用其他内容替换应用程序的“VIEW”部分应该更容易。
至于 Silverlight 是否为您提供的不仅仅是 HTML / JavaScript，取决于您使用它的目的。如果您正在做的事情与媒体相关或高度图形化，Silverlight 可能是一个不错的选择。如果您的应用程序与大多数商业应用程序一样（即某些输入字段由对数据库的某些读/写支持），那么 Silverlight 并没有真正为此类操作提供任何切实的时间节省。
如果 Web 应用程序是公共的，并且您关心搜索引擎索引，那么语义 HTML 会提供最佳选择。
Re-platform an application is always costly, although if you've got your MVC right it should theoretically be easier to replace the "VIEW" part of the application with something else.
As to whether Silverlight offers you more than HTML / JavaScript is down to what you're using it for. If what you are doing is media-related or highly graphical, Silverlight might be a good choice. If your application is like most business apps (i.e. some input fields backed by some read / write to database) Silverlight doesn't really offer any tangible time saving for this kind of operation.
If the web application is public and you care about search engine indexing, semantic HTML offers the best possible option.