Hi,

I'm wondering if someone can shed some light on why the web.admin project is structured the way its is? In the solution it is a seperate project at the same level as Nop.web but in reality it lives under nop.web in the directory structure.

The deploy.bat file moves files from nop.admin into nop.web at the appropriate place. You cant run the admin project independant so what advantage does this give you?

The problem it causes is that we are deploying to azure and cant hook an azure deployment project directly to the nop.web project because of the smoke and mirrors required by the build script to restructure the solution at deploy time.

What would be the disdvantage of either of the following:
1. The web.admin code living directly the corresponding location in the nop.web project
2. Moving the nop.admin project physically outside the nop.web project and copying the files in using post build scripts which would almost make the whole admin site a plugin.

Welcome your thoughts.

bump

Any thoughts people?