When a .NET DLL library depends on an ADO.NET  data provider, we can either reference the ADO.NET  provider in our DLL project or we can use reflection in C# to dynamically load the data provider and not reference the provider assembly. The project in which the DLL is being used may prefer using an Oracle provider, a MySQL provider or a SQL Server provider, and therefore, there is a need to dynamically use the preferred provider. The code below implements such a requirement. Alternate sample...

Here we show an example of how to use a dynamically generated query to insert rows from a source table into a target table. We are using table variables, but the approach would be the same if you were using permanent stored tables. Note that we are using a parameterised INSERT query to prevent SQL Injection. The data from the source table is ordered by ProductId when inserting rows into the target table. A dynamically generated INSERT query is executed for each row in the source table, which...

When you publish a library called YourLibrary.dll to the NuGet platform, then you don't need to worry about what version of your library should be used in a .NET app. In other words, the NuGet platform will automatically include the correct version of the DLL for the .NET app. For example, after publishing your library to the NuGet platform, we will end up with the following structure. Based on the available .NET versions of YourLibrary.dll and the .NET app's .NET version, the best possible...