Is it better to avoid inlnine SQL with dapper? -

I've considered using dapper , but I still want to use inline SQL Do not like the idea of. Does anyone have any thoughts on stored procedures , so in this situation that there is a problem with the query, it will not require recompilation , but only one stored procedure Is there any option in a database such as keeping all SQL queries in its class library?

Dapper supports both options, and there is no opinion on this topic.

Your question tells you that deploying your codebase is difficult if it is a client-side code, then it may mean that for server-side code, the app is re-deployed instead of replacing an archived procedure. It is usually easy to do - ideally click through something like 1 TeamKitty. Of course, your stored procedures should also have also process / deployment control.

Keeping SQL in the class library will not buy you too much: you still need to be deployed Get the change Of course, this UI (Etc.) code will present your data in different assemblies -Major code may be able to understand, but this is a local architecture decision.