Create an application that has different types of licenses like basic, gold, silver...

Question

1.00/5 (1 vote)

See more:

, +

Hello All,

Hope you can help me out here. I need to develop an application in .Net for a business that will be offering various features(email, chat, searches, reports) and services(legal, consultation, queries) based on profile/license of the user. Few of the services and features are available for all, rest comes at a price.

What kind of architecture I need to follow so that I can implement this feature/services based licensing model for current and future feature/services too.

N.B. - I don't need programming help for any features/services. I need the idea/concept/framework suggestion and a sample to go with it for the architecture.

What I have tried:

I have been juggling ideas, and thought SaaS may be the answer, but since I have never tried SaaS, i am not sure whether it is the right way or the only way.

Posted 21-May-17 21:08pm

girlprogrammer

Updated 21-May-17 21:19pm

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Kornfeld Eliyahu Peter · Answer 1 · 2017-05-21T21:19:00

It is very hard to advise something exact (as you were not exact too)... But I would think of a plugin-based model (your own or maybe MEF)
You should use a interface based plugin, where all modules will implement an extra interface for validation... The main module will hold some keys (or one combined) for any feature and passing it to all loaded modules. If the module passes the validation (one of the keys fits to its feature set) the main module will merge it, if not it will silently be dropped...