Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Given a single .net codebase for a piece of software (let’s use C# for argument’s sake), and I want to break this software down into different editions based on functionality (like a basic edition and an advanced edition), what is the best way to go about this?
Would I have to factor this into my software architecture?
Editions are more on the marketing side then on technical side. try to keep it simple as possible. You need to disable some features rather then provide different set of functionalities.