- ago
what kind of dll I need to copy to WL folder to use SQL Server ?
0
600
Solved
6 Replies

Reply

Bookmark

Sort
- ago
#1
Unexpected question for someone who says he's built his own data provider. A general rule of thumb is: it depends on assembly references you linked when building it.

No copying required if you just leveraged one of the built-in .NET classes for SQL connectivity. Assemblies registered in the GAC only need their checkboxes enabled in Tools > Assembly References.
0
- ago
#2
The problem is that I copied Microsoft.Data.SqlClient.dll into WL folder but this assembly is not loaded by WL
0
- ago
#3
If it is the correct version and it has all permisdions it should load.

Tip: Copy all assemblies you need for your compilation to the WL binary folder.
Then in Visual Studio add references to these Assemblies.
Make sure you add all dependencies.
0
Glitch8
 ( 10.62% )
- ago
#4
If you or your client needs more in-depth development support you/they can also use our Concierge Support service. Also don't forget to keep your subscription up to date, it's set to cancel in a few days!
1
- ago
#5
QUOTE:
The problem is that I copied Microsoft.Data.SqlClient.dll into WL folder but this assembly is not loaded by WL

As "it doesn't work" always gets me triggered, for the sake of completeness I'd ask: How did you determine that the "assembly is not loaded by WL"?
0
Best Answer
- ago
#6
It's work fine, sorry it was a small error
0

Reply

Bookmark

Sort