Guys, bit of a long winded one, but Im wondering a few things about developing modular .NET products. Any advice or input welcome on these points.
1) What is the best way to configure whether a module in a particular application is enabled - is an xml config file a good strategy or should this be in the database? Consider that the application will be rolled out to different customers and each will have different features switched on or off. Different versions of the software may have different capabilities enablable / disablable.
2) What is the best way to handle a new version of a product rollout, considering that it is possible that the database architecture may change, and that it may be difficult to detect when a new field in a table (which is needed for a new version of the software) is missing. Would running SQL update statements from inside the product (on first run) take care of this, or is there a tool for SQL Server synci ...
Go to the complete details ...