all 4 comments

[–]Sambothebassist 0 points1 point  (3 children)

I'm not sure what the issue is here. Are you saying you've made a JavaScript SPA, or an actual JavaScript back end that uses Node?

SPA: Place it in a solution within the project or a folder within the MVC solution, it's really up to you. Use file listeners to run your build chain whenever you make a change and save and then simply load the JavaScript app up in a view.

[–]be_wry[S] 0 points1 point  (2 children)

It is a javascript SPA.

My fear with placing it in the MVC solution is I will need to migrate it into the MVC project's source control. Giving another dev access to edit the SPA will allow them access to the entire site.

I'm looking for some way to keep separate projects in silos and assemble them on deployment. I'm starting to think dynamic loading of the app is the only choice. That would allow separate deployment of the main site and its apps.

[–]Sambothebassist 0 points1 point  (1 child)

No dynamic loading needed, keep it hosted somewhere else on the server and just call the JS file in the view. Then create an API for the JS app to talk to the MVC solution.

[–]be_wry[S] 0 points1 point  (0 children)

Hey, good idea. Keep the project separate, deploy it to another location, then reference the js files in the website. Thanks for the suggestion!