jb
unread,Aug 3, 2011, 7:11:48 PM8/3/11Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Sign in to report message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to JavaScriptMVC
Hi,
I am trying to replace a .NET MVC3 set of views with JMVC, and am
having some trouble understanding how to integrate these two projects
Is the common practice that these projects are maintained as
autonomous projects? That is, even deployment consists of (at least in
IIS world) deploying two different apps? For instance the JMVC app
might be deployed to a root app, and the backend to a subdirectory?
Or are the projects generally integrated, where the JMVC code is
copied (or stored) in the MVC app itself. If this latter case, how is
routing handled? Is there a standard layout? If they are hosted
together, how are 'conflicts' handled (for instance JMVC route of /
recipes needs to access the MVC route of /recipes?
Also, given the latter approach, how is dev vs production managed? Has
anyone tied it into a .NET MVC project before?
Thanks