Hello, First off, I'd just like to say that I am very new to ASP.NET Core so please forgive my naivety, but I am currently attempting to deploy my application to IIS only to receive a platform not supported exception for SQL Client, but am not getting the error at all when running IIS Express on the same machine. The machine that I am running it off of was Windows Server 2016 installed, and the machine that has the SQL Server (2012) is running on Windows Server R2. I'd be more than happy to provide any further information. Thank you

Firstly, did you install the .NET 5 runtime onto the IIS machine and ensure that you restarted IIS so it took effect as discussed here ? When you created your IIS app pool for your application did you set the .NET CLR Version to No managed Code ? This is needed for .NET 5. Did you configure the app pool to be x86 or x64? Check in the app pool's advanced settings in IIS for Enable 32-bit Applications . What is the target framework of your application (from the project file)? As part of your deployment SqlClient requires the native SNI binaries as well. There are issues with deployments around this component so the general recommendation is to add an explicit NuGet dependency in your project ( Manage Nuget Packages for Project ) on Microsoft.Data.SqlClient.SNI .

As it’s a new project you should upgrade to .net 6, which has support for 3 more years, while .net 5 has less than 6 months left.

ASP.NET Core 5 sqlclient not supported

Accepted answer

Michael Taylor 48,826 Reputation points

2021-12-13T15:59:12.63+00:00

Firstly, did you install the .NET 5 runtime onto the IIS machine and ensure that you restarted IIS so it took effect as discussed here?

When you created your IIS app pool for your application did you set the .NET CLR Version to No managed Code? This is needed for .NET 5.
Did you configure the app pool to be x86 or x64? Check in the app pool's advanced settings in IIS for Enable 32-bit Applications.

What is the target framework of your application (from the project file)?

As part of your deployment SqlClient requires the native SNI binaries as well. There are issues with deployments around this component so the general recommendation is to add an explicit NuGet dependency in your project (Manage Nuget Packages for Project) on Microsoft.Data.SqlClient.SNI.
Please sign in to rate this answer.
Brad Gardner 21 Reputation points

2021-12-13T16:25:02.907+00:00

I have installed the runtime for .NET 5, as well as restarted IIS to no avail.

I did not have the CLR version set to No managed Code, but have since updated it.

The app pool has Enable 32-bit Applications set to false (otherwise cause a 503 to be returned).

The target framework is net5.0

I added the dependency through nuget (version 4.0.0), but did receive a warning stating that the package may not be fully compatible.

Thank you

Michael Taylor 48,826 Reputation points

2021-12-13T16:36:51.097+00:00

The native runtime folder structure is needed for SNI. Have you confirmed that the x64 Windows folder (runtime/win-x64) is present since you're running IIS x64?

Brad Gardner 21 Reputation points

2021-12-13T16:40:38.84+00:00

Correct, the folder is present containing a native folder which contains the dll and pdb for Microsoft.Data.SqlClient.SNI as well as sni.dll.

Thank you

Michael Taylor 48,826 Reputation points

2021-12-13T17:11:43.833+00:00

Can you post the exact error message from IIS along with a callstack if available?

What version of SqlClient are you using? Are you using EF Core or a similar data access library.

Brad Gardner 21 Reputation points

2021-12-13T17:14:10.587+00:00

SqlClient version 4.5.1 and EntityFrameworkCore version 5.0.12

Michael Taylor 48,826 Reputation points

2021-12-13T17:38:24.07+00:00

It sounds like it is hitting the dummy DLL instead of the platform specific one. This will trigger those errors.

In the file system look at the version of Microsoft.Data.SqlClient.dll that is in your bin directory when deployed on IIS. Compare this version # to what you have in your bin directory after your build that is properly running under IIS.

To clarify: all your checking needs to be done against the directory where IIS is looking for your binaries, including the native binaries.

How are you deploying your app to IIS?

Brad Gardner 21 Reputation points

2021-12-13T18:07:59.607+00:00

The version numbers are the same, and I am deploying it by publishing from Visual Studio 2019 Community using the folder option, stopping and restarting the IIS site in between each publish.

Thank you

Michael Taylor 48,826 Reputation points

2021-12-13T19:06:20.387+00:00

So you're publishing to a folder instead of IIS directly then. When you set up your publishing profile did you set the target runtime for win-x64 or did you leave it as portable?

Brad Gardner 21 Reputation points

2021-12-13T20:03:36.467+00:00

I have it set to self-contained deployment with a target runtime of win-x64

Michael Taylor 48,826 Reputation points

2021-12-13T21:15:45.063+00:00

I see you marked an answer as accepted. Does that mean you were able to resolve your issue?

Brad Gardner 21 Reputation points

2021-12-13T21:17:31.6+00:00

Yes I did, and I apparently forgot to hit submit on the comment. The fix required that I move it back to framework-dependent and set the target runtime back to portable. Thank you for your help.

Michael Taylor 48,826 Reputation points

2021-12-13T21:32:45.007+00:00

Glad to hear you resolved it.
Sign in to comment

ASP.NET Core 5 sqlclient not supported

1 additional answer