Home/ Questions/Q 6345447
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-24T20:49:29+00:00

I would like to ask you what experience you have with developing and deploying

  • 0

I would like to ask you what experience you have with developing and deploying one application that in general has some standard features, but the application can also have customer specific features.
For example:

  1. Customer 1 have the standard features but also want a search function.
  2. Customer 2 have the standard features only.
  3. Customer 3 have the standard features and also want an employee calendar.

How would you solve this?

Would you have one project where you deploy all the application from and then have some kind of config file to determind which features are avaliable in the specific application?

Would you have one project for each customer? This is how I’m doing it now, but the problem here is that if there are bugs that need to be fixed in the standard features I have to fix them in every project.

Any other suggestions are very welcome.

The application is developed in Delphi and C#.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    No definitely do not have one project per customer, you could have one solution per customer where you agregate all projects given setup need.

    Just to give you in an alternative to plugin architecture, which is right way to go, but also usualy fairly complex.

    Option1.

    1. Put common functionality in main project (Core)

    2. Additional stuff like calendar put in separated DLL projects ( one per functionality)

    3. Create VS SOLUTIONS, where you agregate all projects for specific setup + Core. So customer1 will have Customer1Silution with Core and all additional projects he need, customer2 its solution with Core and its additional stuff.

    Option2.

    Have one big setup for every one and based on its configuration/license enable/ disable access to user to a additional functionality.

    Depends on your resources like time, experience, people you work with, clients , you can chose an option more appropriate to you.

    1 plugin based: may be the best one but it, complex and it will take a time you become familiar with it, if you never did before something similiar.

    Option 1 easy and fast, but if the clients quantity and configyration become defer you will jump into scale problems.

    Option 2 is an average between those two, but keep an eye on your setup dimension.

    Considering tha fact that you refer projects and nit DLLs in your solutions, if you fix a problem in Core in one solution it will affect also all other solutions.

    • 0