Question

Here is the scenario. I have built a data wrapper class for executing stored procedures. I would like to use this class in other projects. As we all know it is usually imperative that data layer code should execute as quickly as possible to avoid bottle-necking.

So my question is, If I were to build my data class in its own assembly which is easier to distribute to other solutions, does this create any sort of load time penalty for the class itself? The other alternative is to copy and paste the class files into each project.

Answer 1

You should note that while there is a non-zero (though likely trivial) cost associated with loading your assembly, in almost all cases it occurs only once per AppDomain, so bottle-necking is not a concern.