Suppose I have a big project, called Northwind. It's a website in front of a database. Now management want me to create a public API for this.
I create a new ASP.NET Core project called
But now the customers want a nuget package to invoke the API with. (They don't want to invoke REST calls directly). I would naturally call this client package
So there's a problem. Is there a convention for naming:
- The project that implements an API
- A library providing a wrapper that calls the API.
I can't call them both