Hi All,
I will be starting a project soon that will entail creating a large MVC .NET Web Application. The app will be in MVC 5, .NET 4.5, and be written using VS 2013. Most of the development is UI as the backend system and interfaces are already in place.
The application will be used by our external clients and suppliers. The application will compose of several modules including finance, capturing and managing orders, managing their own users, correspondence between the company and them, etc. Ultimately it will get quite large. I would like to get opinions on how I should structure the application both in VS2013 and when deploying.
I also want to adhere to the following upon deployment:
I don't know if I should create one massive web application project and add everything into that, and deploy as a single web application to IIS. For the above deployment list, a single web application will meet all the requirements very easily, but I am concerned that such a big app will be a heavy resource hog on the web server.
OR
If it is possible to create a VS2013 solution with all the various modules (finance, client, supplier, user, etc) as separate web applications and deploy each one separately to IIS, but as a complete solution. If I can, how do I ensure I meet my deployment requirements list without making development a pain, or making deployment a pain. I know how to deploy them sepately within IIS so that they will meet the URL requirement. But the 2 issues I don't have a full understanding on is how to centralise the JS and CSS during development and to ensure it is centralised upon deployment as well. Also, how could I handle single login page where user logs in once but can access the various modules (web applications) without having to login again.
Any advice based on previous experience will be greatly appreciated.
I will be starting a project soon that will entail creating a large MVC .NET Web Application. The app will be in MVC 5, .NET 4.5, and be written using VS 2013. Most of the development is UI as the backend system and interfaces are already in place.
The application will be used by our external clients and suppliers. The application will compose of several modules including finance, capturing and managing orders, managing their own users, correspondence between the company and them, etc. Ultimately it will get quite large. I would like to get opinions on how I should structure the application both in VS2013 and when deploying.
I also want to adhere to the following upon deployment:
- Single login page where user logs in once and will be able to access modules they have access to.
- A nice structured URL depending on module, ie: myapp.co.za/finance myapp.co.za/user myapp.co.za/supplier
- I do not want to duplicate CSS or JS files. The must only exist on the web server once.
I don't know if I should create one massive web application project and add everything into that, and deploy as a single web application to IIS. For the above deployment list, a single web application will meet all the requirements very easily, but I am concerned that such a big app will be a heavy resource hog on the web server.
OR
If it is possible to create a VS2013 solution with all the various modules (finance, client, supplier, user, etc) as separate web applications and deploy each one separately to IIS, but as a complete solution. If I can, how do I ensure I meet my deployment requirements list without making development a pain, or making deployment a pain. I know how to deploy them sepately within IIS so that they will meet the URL requirement. But the 2 issues I don't have a full understanding on is how to centralise the JS and CSS during development and to ensure it is centralised upon deployment as well. Also, how could I handle single login page where user logs in once but can access the various modules (web applications) without having to login again.
Any advice based on previous experience will be greatly appreciated.