We're in a situation where we'd like to store sensitive information in Azure SQL. We're rolling out our own. In fact I even posted on
dba.stackexchange.com asking for a good design pattern to implement application level crypto against Azure SQL.
Then I ran into your library but noticed you support only code-first. Considering the rest of EF (after class generation) is the same beneath whether it be code-first, model-first or database first approaches- is there a way to use your library with EF database-first?
It would be awesome if you could have small "HOWTO" or a little article in the docs section on setting / using your library in such a scenario
PS: We used to be code-first but had to switch to database first as the project grew.