CODEWITHSUNDEEP
asp.net-mvcasp.net-mvc-3
fes
fes

Reputation: 2515

ASP.NET MVC 3 Structure - Go to view in another project

I've got the following project setup

Project A (main)

  1. Business
  2. Data
  3. View (asp.net mvc 3 project)

Project N

  1. Business
  2. Data
  3. View (asp.net mvc 3 project)

How can I call from Project A the View in Project N and from N back to A. Essentially what I'm trying to do is package each Project N to have its own individual MVC as it comes from different sources and plug it in to the main project and then just have it navigate to the correct view.

Can this be done? Or is there a better way to do this?

Upvotes: 5

Views: 2091

Answers (2)

MikeSW
MikeSW

Reputation: 16348

I do sugest another approach if possible. if I understood correctly, those projects are somehow ike plugins but they are not standalone applications.Also they now about each others so they are coupled. It's, let's say tricky, but I would use only 1 asp.net mvc project (the web ui). All the UI bits which belong to other projects I'd make them helpers (pretty much widgets). This means, that each project contains only the helpers which will be used to construct a view.

I think it's a bit of an architectural problem if you only want to keep the views in each project just for the sake of hosting them in a different assembly. Going the widgets' way it might seem mkore work, but I think you gain the most control and the separation level you want. The only thing is you don't have full Views defined, but why you would want to have full Views (partials, layouts) in separate places if they will be used in one place only?!

Now, if each project is indeed a plugin, independent of other plugins, then going with compiled views is the best way. But if Project B knows about the view of Project N, then I think the above solution is more suitable. That or the whole app is too over engineered. Separation is good when it doesn't create a whole new jungle to navigate it.

Upvotes: 0

Darin Dimitrov
Darin Dimitrov

Reputation: 1038780

You could write a custom virtual path provider. Here's a nice blog post which shows an example of such a virtual path provider allowing you to embed Razor views into assemblies as resources and reusing them in multiple applications.

Unfortunately without a custom virtual path provider, you cannot cross reference views between multiple ASP.NET MVC applications. This simply is not allowed by the default provider which looks for views only inside the current application.

Upvotes: 3

Related Questions