H*******g
发帖数: 6997 | 1 建立了一个空的SOLUTION，然后建立了2个MVC 3的PROJECTS.
Project A: Front-End (default start up project)
Project B: Back-End
访问的时候，要能直接访问到Project B的东西。
那我这个Route Mapping怎么弄啊？GOOGLE了下，说是要用AREA，请问大侠有教程什么
的不？ |
S***k
发帖数: 370 | 2 where are the controllers? not in project A? |
H*******g
发帖数: 6997 | 3 2个PROJECT分别有自己的C和V
【在 S***k 的大作中提到】
: where are the controllers? not in project A?
|
S***k
发帖数: 370 | 4 Why put controller and view in a back-end project?
If project A calls some back-end functions in project B, a project C, which
holds those shared functions, could be created, and both A and B use C as
reference.
Otherwise, this could be a cross domain scenario. I don't know if area could
meet your needs.
【在 H*******g 的大作中提到】
: 2个PROJECT分别有自己的C和V
|
s***o
发帖数: 2191 | 5 what's in your "back-end" project? normally a back-end project is a class
library type, not a Web project type.
【在 H*******g 的大作中提到】
: 建立了一个空的SOLUTION，然后建立了2个MVC 3的PROJECTS.
: Project A: Front-End (default start up project)
: Project B: Back-End
: 访问的时候，要能直接访问到Project B的东西。
: 那我这个Route Mapping怎么弄啊？GOOGLE了下，说是要用AREA，请问大侠有教程什么
: 的不？
|
H*******g
发帖数: 6997 | 6 嗯。是我表达不准确。其实就是一个WEB APP的前台以及ADMIN
【在 s***o 的大作中提到】
: what's in your "back-end" project? normally a back-end project is a class
: library type, not a Web project type.
|
s***o
发帖数: 2191 | 7 I think it will make things simpler to put them in a single MVC project, and
you can use areas to separate them (if necessary).
Here is a tutorial about area on MSDN
http://msdn.microsoft.com/en-us/library/ee671793(v=vs.98).aspx
【在 H*******g 的大作中提到】
: 嗯。是我表达不准确。其实就是一个WEB APP的前台以及ADMIN
|
s***o
发帖数: 2191 | 8 I happened to see this article talking about how to put areas into different
projects. Try this hack if you are interested:
http://bob.archer.net/content/aspnet-mvc3-areas-separate-projec |
h***g
发帖数: 5 | |
