Writing API in C# for My Application -
I will write an application, but I have not allowed people to use their application programming interfaces first. I mean, how should I kindly design people to let people use my methods like the API from outside the world.
Please someone shows me a path. I am new to this.
- Express as little as you can. Whatever you publish, it will come back to you x100 in the next version. Keeping consistency is very difficult.
- Create instability for whatever you publish You will definitely change your interior, but your existing users should stay consistent.
- Mark everything internally Even the main method of your application will be to use each one method that can be used.
- Check your public API in the same way that you would for the interface. Integration test and so on Note that your API will be used in an unexpected way.
- Maximize the conference on the configuration This is necessary even if your API is the only way, you will still need to support it.
- Resolve as many FxCop and StyleCop errors as possible.
- Check your API is consistent with the naming guidelines of your platform.
- Give as many examples as you can, and remember that most of your API usage will be Ctrl + C and Ctrl + V from these examples.
- Try providing documentation that you do not have GhostDoc-style auto-generated documents, everyone hates it.
- Include information about how to find you.
- Do not bother with ambiguity. This will help you and your users.
ADDED
- There should be less dependency in the API as you can. For example, dependence on IOC containers should be prohibited. If your code internally uses it just ask them in your assemblies.
Comments
Post a Comment