We have the following setup
BUT we now require a new Web Project which would be almost identical to WebProject1 except for the fact that it would alter properties and input variables to functions/voids inside the Business Logic class to provide a different set of data for another completely different user. Think of Facebook as WebProject1 and Myspace as WebProject2. Same concept, same business layer almost but different products altogether.
Business Logic (Class Library)
Data Layer (Class Library containing EF,Web Services wrappers etc)
WebProject2 (similar to WebProject1 but different authentication, different UI, different pages etc)
Without completely destroying the Business Logic (as the class would now have to allow for 2 paths per set of input variables) how can we structure this to aviod doubling up on any code?
The delima is:
Should we maintain two Business Logic class libraries? Should we add preffixe
View Complete Post