dotnet / dotnet/SqlClient

VSTO for Outlook and the known issue of the 3 **Microsoft.Data.SqlClient.SNI.xxx.dll**

Open
#2,480 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
989
Forks
340
Avg merge
4d 19h
Merged PRs (30d)
72

Description

**Hello team**,

### Describe the bug
This concerns the publish of a VSTO for Outlook and the known issue of the 3 **Microsoft.Data.SqlClient.SNI.xxx.dll** files that are not included in the deployment folder as **Microsoft.Data.SqlClient.SNI.xxx.dll.deploy** files.

Our environment is Visual Studio **2017** in dotnet **4.6.2**, so we've just changed the use of the **system.data.sqlclient** component to **microsoft.data.sqlclient** Nuget. This is a substantial application that we'll have to maintain in .NET Framework 4.x and, for various reasons, still under VS 2017 (but we plan to transport it to VS 2022 asap).

### To reproduce
1. Create a VSTO project under VS 2017
2. Reference Nuget Microsoft.Data.SqlClient
3. Standard publish
4. Observe the publish folder :

![image](https://github.com/dotnet/SqlClient/assets/78490503/1ed713a8-0ef5-4f94-b365-41d15d485603)

### Expected behavior
Of course the files are copied to the deployment folder :-)

### Further technical details
Microsoft.Data.SqlClient version: 5.2.0
Visual Studio 2017
.NET target: Framework 4.6.2
Operating system: Windows 10

**Additional context**

I've read every single issue on your site and in other sites, and unless I'm wrong, I haven't found a suitable solution. For now, our workaround in the csproj file is as follows (found here https://developercommunity.visualstudio.com/t/VSTO-Project-does-not-deploy-MicrosoftD/10512579?sort=newest by Alexander Milenz ) :

![image](https://github.com/dotnet/SqlClient/assets/78490503/063483fe-985e-4265-97d6-11dea5dda419)

Has the most elegant possible solution been found since then? and that I may have missed.
Thank you very much for your help.

Kind regards,
Herve

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.