c# - keep the call center / admin functionality seperate from the purchase tunnel but not duplicate the code -


i've got asp.net mvc 4 application basic purchase tunnel application

the project structure looks

myproject.domainmodel  myproject.repository  myproject.service  myproject.ui.purchasetunnel 

i need add call centre functionality, allow call centre users log in , place orders people on phone , admin tasks.

for security reasons don't want deploy call centre functionality on our public facing web servers, want purchase tunnel.

how keep call centre functionality separate purchase tunnel not duplicate purchase tunnel code project?

i've played around areas "callcenter" area deployed application, making stake holders nervous.

any ideas?

i've never had flawless experience areas. work in principal create new section of site separate configuration, it's pain serve css/js/img assets.

you have few options. largely depends on how code you'll share public facing , call-center sides

  • use same site different roles. if call-center site same thing, can use same application have different security roles grand them access specific functionality (you'd if going areas well.) risks run forgetting limit admin functionality right role, or average user finding way become admin (high functionality sharing)
  • build controllers in separate assembly , public , admin facing websites contain controllers inherit base controllers. this post has more information putting controllers in separate assembly. (medium functionality sharing)
  • push logic can myproject.service , call services 2 web front ends (low functionality sharing)

Comments

Popular posts from this blog

php - regexp cyrillic filename not matches -

c# - OpenXML hanging while writing elements -

sql - Select Query has unexpected multiple records (MS Access) -