I am using the Okta.Sdk nuget package (v4.0) in an ASP.Net Framework (4.6.1) application to create/update users.
All works well in the local Visual Studio environment, but when deployed to an IIS server we receive the following exception:
[FileLoadException: Could not load file or assembly ‘System.Runtime.InteropServices.RuntimeInformation, Version=0.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ or one of its dependencies. The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)]
Okta.Sdk.Internal.HomePath.TryGetHomePath(String& homePath) +0
Okta.Sdk.Internal.HomePath.Resolve(String pathSegments) +95
Okta.Sdk.OktaClient.GetConfigurationOrDefault(OktaClientConfiguration apiClientConfiguration) +134
Okta.Sdk.OktaClient…ctor(OktaClientConfiguration apiClientConfiguration, ILogger logger, ISerializer serializer) +31
Have tried:
- Explicitly adding the System.Runtime.InteropServices.RuntimeInformation nuget package
- Adding a dependent assembly binding to the project for 0* to current version
It appears to be looking for a yaml file in the user’s home directory, despite our passing in configuration to the constructor.
Thanks in advance for any assistance,
Paul Jackson