System.Data.SqlClient 4.6.1 vs System.Data.SqlClient 4.7.0

[EsaHeikkiPoutanen]

In my Azure Function (V2) with System.Data.SqlClient 4.6.1 everything works fine, but with System.Data.SqlClient 4.7.0 I get 'System.Data.SqlClient is not supported on this platform.' when
my function is trying to connect to Azure SQL db.

everything else stays the same.

what the hell is going on ???

Yours,
Esa Poutanen MOST Digital Oy
esa.poutanen@mostdigital.fi
+358-40-5538866

[EsaHeikkiPoutanen]

resolved using older version

[cheenamalhotra]

Hi @EsaHeikkiPoutanen

Thanks for reporting the issue, I was able to reproduce it and will reopen for further investigation.
For now you may proceed with older version that is working fine.

[Rychu-Pawel]

The issue made it to 4.8.0 preview. Could you please ensure us it is a bug, not a permanent change? :)

[EsaHeikkiPoutanen]

Well, I had to start using older version (4.6.1) of this to get things working, so I suppose it’s a bug, or are You trying to make people not using this ? Cheers, Esa Esa Poutanen Software Robotics Developer MOST Digital Oy esa.poutanen@mostdigital.fi<mailto:esa.poutanen@mostdigital.fi> [cid:image001.png@01D58432.4ECCE620] www.mostdigital.fi<http://www.mostdigital.fi/> From: Rychu <notifications@github.com> Sent: keskiviikko 16. lokakuuta 2019 14.55 To: dotnet/SqlClient <SqlClient@noreply.github.com> Cc: Esa Poutanen <esa.poutanen@mostdigital.fi>; Mention <mention@noreply.github.com> Subject: Re: [dotnet/SqlClient] System.Data.SqlClient 4.6.1 vs System.Data.SqlClient 4.7.0 (#227) The issue made it to 4.8.0 preview. Could you please ensure us it is a bug, not a permanent change? :) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#227?email_source=notifications&email_token=AKXL5G53IJPBEJHYMEKZJ63QO36IPA5CNFSM4I3FM2H2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBMGKWI#issuecomment-542664025>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKXL5GY3YWSLD5FUHVDZDSDQO36IPANCNFSM4I3FM2HQ>.

[yukiwongky]

@EsaHeikkiPoutanen I still have not been able to find the root cause for this, but seems like Azure Function isn't able to move the correct dll into the bin folder at build time. Meanwhile there is a workaround post here, and that is to add these lines in your csproj file.

<Target Name="PostBuild" AfterTargets="PostBuildEvent">
  <Exec Command="copy $(OutDir)$(ProjectName).deps.json $(OutDir)bin\function.deps.json" />
</Target>
<Target Name="PostPublish" BeforeTargets="Publish">
  <Exec Command="copy $(PublishDir)$(ProjectName).deps.json $(PublishDir)bin\function.deps.json" />
</Target>

[cheenamalhotra]

Hi @EsaHeikkiPoutanen

The issue was identified with Azure Functions SDK "Microsoft.Net.SDK.Functions" version 1.0.29. Newer versions of SDK (currently in Beta and Preview) have fixed the problem and now work properly with dependent libraries.

You can take a look at an example repository for Microsoft.Data.SqlClient and Azure Functions (all runtime versions), details posted here. The same should work for System.Data.SqlClient 4.7.0, please feel free to re-open if you face any problem.