This is an old revision of the document!
Configuration, project setup
Configuration
Each customer has own environment - e.g. sql server connections - and configuration.
Before work, it's necessary to setup environment configuration for these particular customer.
Go to directory for particular customer and run script for environment e.g. project Configuration/Agrofert/Activate_AGROFERT_TEST.cmd, it setups the connections strings, web configs, app config and other things.
Don't commit these changes in Configuration dir!
Database
There is database first approach.
First prepare data changes - update scripts for sql structures, stored procedures, views …
Generate changes into models
Table names are according particular module, and customers e.g. DDDiaryReportItem - item for DailyReport