SQL Server Connectivity
API = syntax + behavior
Yet, there is a formal mechanism to describe syntax, and no formal mechanism to describe behavior.
Be careful of the level of detail you share the behavior... if you end up sharing code, then you tightly couple the caller with the code being called.
How would you formally describe behavior so that you maintain (and encourage) loose coupling but additionally allow a computer system (like visual studio) to help the programmer use the API correctly?
Canonical functions were introduced in the Beta 2 release of Entity Framework. Their purpose is to expose
