Suppose I have a very large site like amazon.com. I’d like to use asp.net mvc for the whole site but having one large project with hundreds of contributors is not practical. I’d like to split the work into projects like books, tools, toys, groceries, etc. for each department. Then when they build and deliver a new release I can just drop the “books.dll” into the site and it all magically works. I see this thing called “areas” but it looks like they’re still part of the same project. I need something that could potentially be stored not just in a separate project but a separate TFS instance as well. The departments would only ever come together on my test/production servers and hopefully just by dropping in DLLs. Anyone know of a way to do this?
views:
181answers:
3
+4
A:
Asp MVC 2 has support for Project Areas catering for this development scenario
More detail at Phil Haack blog
gg
2009-11-24 17:26:49
http://msdn.microsoft.com/en-us/library/ee307987%28VS.100%29.aspx is the actual answer. Phil has good info so I'll give you the check.
No Refunds No Returns
2009-11-25 21:42:14
Couple of notes: 1) Make sure you install the MVC 2 Preview 2, not just the MVC 2 Beta. B) The directions at this link often say "area" when they mean project.
No Refunds No Returns
2009-12-07 20:07:14
Looks like formal support for multiple projects will not be offered with this release. "maybe" in a future release.
No Refunds No Returns
2009-12-08 16:54:45
+1
A:
Shoulda looked harder before posting:
http://msdn.microsoft.com/en-us/library/ee307987%28VS.100%29.aspx "Walkthrough: Creating an ASP.NET MVC Areas Application Using Multiple Projects"
(self-slap!)
No Refunds No Returns
2009-11-24 17:46:25