blocks|key|3254422|text|您可能会感兴趣的一个工具是ILMerge|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3254423|3254424|http://research.microsoft.com/en-us/people/mbarnett/ilmerge.aspx|unordered-list-item|offset|length|3254425|3254426|这是一个允许您将多个.Net程序集合并到单个DLL中的工具。它可用于将多个项目的输出合并到单个DLL中进行部署。|3254427|我从来没有在MVC中尝试过它，而且我对Asp.Net架构也不够熟悉，不知道它是否适合您的情况。但这可能值得一试。|3254428|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|1S|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|U|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|V|8|@]|9|@$F|W|G|X|1|Y]]|A|$]]|$1|H|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|10|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|11|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|D]]]]

One tool you may be interested in looking at is called ILMerge
<ul>
<li><a href="http://research.microsoft.com/en-us/people/mbarnett/ilmerge.aspx" rel="nofollow noreferrer">http://research.microsoft.com/en-us/people/mbarnett/ilmerge.aspx</a></li>
</ul>
This is a tool that will allow you to merge several .Net assemblies into a single DLL. It could be used to combine the output of your several projects into a single DLL for deployment.
I haven't ever tried it with Asp.Net MVC and I'm not familiar enough with the MVC architecture to say whether or not it will work for your situation. But it's likely worth a try.

blocks|key|413553|text|如果您的应用程序不需要区域，而您的目标只是允许团队独立，为什么不直接使用更好的源代码控制系统呢？除非您有真正独立的模块，否则听起来通过subversion中的分支进行管理是合适的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|413554|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If your app doesn't require areas, and your goal is just to allow team independence, why not just use a better source code control system? Unless you have truly independent modules, sounds like managing via branches in subversion is appropriate.

blocks|key|3467519|text|只需创建多个MVC项目，并在最后通过简单的复制和粘贴合并输出即可解决问题:)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3467520|下面是我们遵循的结构：|3467521|3467522|MyApp.Web.Shell+(仅包含web+app)|unordered-list-item|3467523|MyApp.Web.Home|3467524|MyApp.Web.UserManagement|3467525|MyApp.Web.DeviceManagement|3467526|MyApp.Web.ContentManagement|3467527|.....etc...|3467528|所需的主题、css、js和图像|3467529|最后，我们使用构建脚本来合并所有项目的输出，并生成整个web应用程序运行所需的文件。|3467530|如果您在实现类似的解决方案方面需要任何帮助，请通过link+text与我联系|offset|length|3467531|entityMap|0|LINK|mutability|MUTABLE|url|http://techdreams.org/^0|0|0|0|0|0|0|0|0|0|0|0|P|9|0|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|18|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|19|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|1A|8|@]|9|@]|A|$]]|$1|H|3|I|5|G|7|1B|8|@]|9|@]|A|$]]|$1|J|3|K|5|G|7|1C|8|@]|9|@]|A|$]]|$1|L|3|M|5|G|7|1D|8|@]|9|@]|A|$]]|$1|N|3|O|5|G|7|1E|8|@]|9|@]|A|$]]|$1|P|3|Q|5|G|7|1F|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1G|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1H|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1I|8|@]|9|@$X|1J|Y|1K|1|1L]]|A|$]]|$1|Z|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]]|10|$11|$5|12|13|14|A|$15|16]]]]

The problem is sorted out by just creating multiple MVC projects and merging the output at the end by simple copy &amp; paste :)

here is the structure we followed:

<ul>
<li>MyApp.Web.Shell (just contains themes, css, js &amp; images required for the web app)</li>
<li>MyApp.Web.Home</li>
<li>MyApp.Web.UserManagement</li>
<li>MyApp.Web.DeviceManagement</li>
<li>MyApp.Web.ContentManagement</li>
<li>.....etc...</li>
</ul>

At the end we are using build scripts to merge output of all the projects and generate the files required for the total web app to run. 

If you need any help in implementing similar solution, get in touch with me at <a href="http://techdreams.org" rel="nofollow noreferrer" title="my blog">link text</a>

blocks|key|413580|text|在我之前的工作中，我们处理这个问题的一种方法是构建一个主“控制器”应用程序。此应用程序已部署并面向公众。它的工作是读取传入的URL，并根据配置文件中的一系列映射规则，将该URL映射到运行在同一服务器上的其他MVC应用程序。这给了我们很多选择，比如如果我们想要进行粗略的负载平衡，可以在场中的不同服务器上运行备份应用程序。您需要跨多个应用程序管理诸如身份验证之类的事情(如果您正在使用身份验证)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|413581|这基本上使您能够根据需要在服务器上运行任意多个不同的MVC应用程序，所有这些应用程序都使用相同的前端控制器(本质上)|413582|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

One way we handled this in my previous job was to build a master 'controller' application. This app was deployed and was public facing. It's job was to read the incoming URL and, based on a bunch of mapping rules in config files, map that URL to other MVC applications running on the same server. This gave us lots of options such as being able to run the backing apps on different servers in the farm if we wanted to do crude load balancing. You need to manage things such as authentication across the multiple apps (if you're using authentication).

This basically gives you the ability to have as many different MVC apps as you need running on the servers all with the same front controller (essentially)

blocks|key|3467580|text|ASP.NET+MVC+V2有一个称为区域的功能，它允许您拥有主应用程序引用的单独项目。看看ScottGu的post吧。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3467581|entityMap|0|LINK|mutability|MUTABLE|url|http://weblogs.asp.net/scottgu/archive/2009/07/31/asp-net-mvc-v2-preview-1-released.aspx^0|1I|4|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

ASP.NET MVC V2 has a feature called Areas which allows you to have separate projects referenced by the main application. Check out ScottGu's <a href="http://weblogs.asp.net/scottgu/archive/2009/07/31/asp-net-mvc-v2-preview-1-released.aspx" rel="nofollow noreferrer">post</a>.

blocks|key|3254547|text|你可以使用好的源代码控制，让各自的团队检查他们需要做的事情。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3254548|这样，您在编译时只有一个dll+...|3254549|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

You could just use good Source Control and have the respective teams check out what they need to work on. 

This way you have only one dll at compile time...

blocks|key|410689|text|点击这个链接就可以解决你的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|410690|只需10分钟即可完成演练。|410691|Walkthrough:+Organizing+an+ASP.NET+MVC+Application+by+Logical+Areas|offset|length|410692|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/ee307987%2528VS.100%2529.aspx^0|0|0|0|1V|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

Follow this link it will solve you problem.

Takes just 10 mins to complete the walk-through.

<a href="http://msdn.microsoft.com/en-us/library/ee307987%28VS.100%29.aspx" rel="nofollow noreferrer">Walkthrough: Organizing an ASP.NET MVC Application by Logical Areas</a>

We want to split our large asp.net mvc web application into multiple Visual Studio projects so that each team can independently on their visual studio project.

Desired structure is:

<ol>
<li>ASP.NET MVC application that is responsible for the base UI</li>
<li>Module 1 - VS Project (Does this need to be a ASP.net MVC App or .dll?)</li>
<li>Module 2 - VS Project (Does this need to be a ASP.net MVC App or .dll?)</li>
<li>so on....</li>
</ol>

Each module should contain it's own controller &amp; views that are responsible for functioning of the module. T

How to split the ASP.NET Application in to multiple projects and then merge them as a single website during build process?

Multiple ASP.NET MVC projects that builds as single ASP.NET MVC Application

Visual Studio

身份验证

服务器

我们希望将我们的大型asp.net mvc web应用程序拆分成多个Visual Studio项目，以便每个团队都可以独立完成他们的visual studio项目。所需的结构为：负责基本UI的ASP.NET MVC应用程序模块1- VS项目(需要是ASP.net MVC应用程序还是.dll？)模块2- VS项目(需要是...

问作为单个ASP.NET ASP.NET应用程序构建的多个MVC项目
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问作为单个ASP.NET ASP.NET应用程序构建的多个MVC项目EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问作为单个ASP.NET ASP.NET应用程序构建的多个MVC项目
EN