Let's say you have an intranet development team where it is in your best interest for each developer to be happy with their work - one person leaving will negatively impact the others. Some developers wish to embrace the Web (i.e. ASP.NET MVC). Others wish to work in a stateful environment where Web is merely the medium for delivery (i.e. SilverLight).
假设您有一个内部网开发团队，每个开发人员都对他们的工作感到满意——一个人离开会对其他人产生负面影响。一些开发人员希望拥抱Web(即ASP)。净MVC)。其他人希望在有状态的环境中工作，在这种环境中，Web仅仅是交付的媒介(例如SilverLight)。
I don't want to argue the merits of either (I have my opinion). Rather I want suggestions for legitimate arrangements such that we can have our cake and eat it too. Is it possible for some members of the team to work with SilverLight while others work with ASP.NET MVC without ending up in pandemonium?
我不想争论两者的优点(我有我的意见)。我想要的是合理安排的建议，这样我们就可以吃蛋糕了。是否有可能团队中的一些成员使用SilverLight而其他人使用ASP。NET MVC不会陷入混乱?
I'm thinking that MAYBE we could have ASP.NET MVC for the majority of our applications and then have the SilverLight people develop components that can be used in the UI? But according to this question that didn't turn out so well.
我在想也许我们可以有ASP。NET MVC为我们的大多数应用然后让SilverLight的人开发可以在UI中使用的组件?但是根据这个问题，结果并不是很好。
I'm just looking for a scenario that would allow the team to effectively use SilverLight and/or ASP.NET MVC in their work (not necessarily in the same app) without imploding.
我只是在寻找一个能让团队有效地使用SilverLight和/或ASP的场景。NET MVC在他们的工作中(不一定是在同一个应用中)没有内爆。
Any links to articles with information pertaining to how well a given scenario works would also be appreciated.
与文章的任何链接，以及与给定场景的工作情况有关的信息，也将受到赞赏。
3 个解决方案
#1
1
Unfortunately you can't make all of the people happy all of the time.
不幸的是，你不能让所有的人都一直快乐。
...which is what it sounds to me like you're trying to do. You have to pick the best technology that suits your application and roll with it. Trying to mix and match technologies just to keep people that want to use one or the other is going to fail.
…这就是我听起来你想做的。您必须选择最适合您的应用程序的技术，并使用它。试图混合和匹配技术只是为了让那些想要使用其中一种的人失败。
If your application has legitimate uses for both ASP.NET MVC and Silverlight, then by all means give the Silverlight development to the people that want to do it and let the ASP.NET MVC people handle the rest. Just don't introduce Silverlight to give the developers who want it something to make them happy.
如果您的应用程序对这两个ASP都有合法的用途。NET MVC和Silverlight，然后把Silverlight的开发交给那些想做的人，让ASP来做。NET MVC人处理其余的。只是不要引入Silverlight给那些想让他们开心的开发者。
#2
1
We have a mixture of Silverlight and regular ASP.Net on my team. It's a pretty big application but about 50% of it is Silverlight apps. People who want to work on Silverlight do that and the rest of us do web development. There is one big .sln that has all the projects and a bunch of smaller ones that have projects related to specific functional areas in the app. We have a build process that compiles everything and puts it all together.
我们有Silverlight和regular ASP的混合物。网络在我的团队。这是一个相当大的应用程序，但大约50%是Silverlight应用程序。想要在Silverlight上工作的人会这样做，而我们其他人会做web开发。有一个很大的。sln包含了所有的项目，还有一些较小的项目，这些项目与应用中特定的功能领域相关。
Which parts of the application are SL and which parts of the app are HTML depends on a combination of business requirements and end user capabilities -- NOT whether the dev just want's to do SL or HTML.
应用程序的哪些部分是SL，哪些部分是HTML取决于业务需求和最终用户功能的组合——而不是开发人员只想做SL还是HTML。
If you want both do co-exist in your environment, you will need a process and it should revolve around business requirements and not just what fun toy a dev wants to use.
如果您希望两者在您的环境*存，那么您将需要一个流程，它应该围绕业务需求而不是开发人员想要使用的有趣玩具。
#3
0
I think you should re-examine your assumptions. In particular:
我认为你应该重新审视你的假设。特别是:
- One need not develop with MVC to embrace the Web; Web forms + Ajax works great in many scenarios.
- 不需要使用MVC来开发Web;Web表单+ Ajax在很多情况下都很有用。
- Silverlight apps don't need to be stateful. In fact, Silverlight apps don't even require a UI.
- Silverlight应用不需要有状态。事实上，Silverlight应用甚至不需要UI。
IMO, the best approach is to start with a detailed architectural design for your site, and to look carefully at where each technology might be best applied. With an architecture in-hand, you can begin design and agile development, and let developers choose which areas they would prefer to be involved with, subject to overall project management constraints. But the key is to have the architecture drive the technology choices, not the other way around.
在我看来，最好的方法是从站点的详细架构设计开始，并仔细研究每种技术可能在哪里得到最好的应用。有了一个现成的体系结构，您就可以开始设计和敏捷开发，并让开发人员根据项目管理的总体约束，选择他们希望参与的领域。但关键是让架构驱动技术选择，而不是反过来。
#1
1
Unfortunately you can't make all of the people happy all of the time.
不幸的是，你不能让所有的人都一直快乐。
...which is what it sounds to me like you're trying to do. You have to pick the best technology that suits your application and roll with it. Trying to mix and match technologies just to keep people that want to use one or the other is going to fail.
…这就是我听起来你想做的。您必须选择最适合您的应用程序的技术，并使用它。试图混合和匹配技术只是为了让那些想要使用其中一种的人失败。
If your application has legitimate uses for both ASP.NET MVC and Silverlight, then by all means give the Silverlight development to the people that want to do it and let the ASP.NET MVC people handle the rest. Just don't introduce Silverlight to give the developers who want it something to make them happy.
如果您的应用程序对这两个ASP都有合法的用途。NET MVC和Silverlight，然后把Silverlight的开发交给那些想做的人，让ASP来做。NET MVC人处理其余的。只是不要引入Silverlight给那些想让他们开心的开发者。
#2
1
We have a mixture of Silverlight and regular ASP.Net on my team. It's a pretty big application but about 50% of it is Silverlight apps. People who want to work on Silverlight do that and the rest of us do web development. There is one big .sln that has all the projects and a bunch of smaller ones that have projects related to specific functional areas in the app. We have a build process that compiles everything and puts it all together.
我们有Silverlight和regular ASP的混合物。网络在我的团队。这是一个相当大的应用程序，但大约50%是Silverlight应用程序。想要在Silverlight上工作的人会这样做，而我们其他人会做web开发。有一个很大的。sln包含了所有的项目，还有一些较小的项目，这些项目与应用中特定的功能领域相关。
Which parts of the application are SL and which parts of the app are HTML depends on a combination of business requirements and end user capabilities -- NOT whether the dev just want's to do SL or HTML.
应用程序的哪些部分是SL，哪些部分是HTML取决于业务需求和最终用户功能的组合——而不是开发人员只想做SL还是HTML。
If you want both do co-exist in your environment, you will need a process and it should revolve around business requirements and not just what fun toy a dev wants to use.
如果您希望两者在您的环境*存，那么您将需要一个流程，它应该围绕业务需求而不是开发人员想要使用的有趣玩具。
#3
0
I think you should re-examine your assumptions. In particular:
我认为你应该重新审视你的假设。特别是:
- One need not develop with MVC to embrace the Web; Web forms + Ajax works great in many scenarios.
- 不需要使用MVC来开发Web;Web表单+ Ajax在很多情况下都很有用。
- Silverlight apps don't need to be stateful. In fact, Silverlight apps don't even require a UI.
- Silverlight应用不需要有状态。事实上，Silverlight应用甚至不需要UI。
IMO, the best approach is to start with a detailed architectural design for your site, and to look carefully at where each technology might be best applied. With an architecture in-hand, you can begin design and agile development, and let developers choose which areas they would prefer to be involved with, subject to overall project management constraints. But the key is to have the architecture drive the technology choices, not the other way around.
在我看来，最好的方法是从站点的详细架构设计开始，并仔细研究每种技术可能在哪里得到最好的应用。有了一个现成的体系结构，您就可以开始设计和敏捷开发，并让开发人员根据项目管理的总体约束，选择他们希望参与的领域。但关键是让架构驱动技术选择，而不是反过来。