Organazing ASP.Net Single Page Application with Nancy

Posted by OnesimusUnbound on Programmers See other posts from Programmers or by OnesimusUnbound
Published on 2012-12-10T05:39:43Z Indexed on 2012/12/10 11:23 UTC
Read the original article Hit count: 302

Filed under:
|

As a personal project, I'm creating a single page, asp.net web application using Nancy to provide RESTful services to the single page. Due to the complexity of the single page, particularly the JavaScripts used, I've think creating a dedicated project for the client side of web development and another for service side will organize and simplify the development.

solution
  |
  +-- web / client side (single html page, js, css)
  |    - contains asp.net project, and nancy library 
  |      to host the modules in application ptoject folder
  |
  +-- application / service (nancy modules, bootstrap for other layer)
  |
  .
  .
  . and other layers (three teir, domain driven, etc)
  .

Is this a good way of organizing a complex single page application? Am I over-engineering the web app, incurring too much complexity?

© Programmers or respective owner

Related posts about ASP.NET

Related posts about code-organization