You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (JIRA)" <ji...@apache.org> on 2018/01/19 13:02:00 UTC
[jira] [Commented] (IGNITE-7473) .NET: "Could not load file or
assembly ConfigurationManager" error on Linux
[ https://issues.apache.org/jira/browse/IGNITE-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16332222#comment-16332222 ]
Pavel Tupitsyn commented on IGNITE-7473:
----------------------------------------
Looks like there is no way to fix this issue in code. Core CLR attempts to load that assembly right at the start.
See https://github.com/dotnet/standard/issues/506.
> .NET: "Could not load file or assembly ConfigurationManager" error on Linux
> ---------------------------------------------------------------------------
>
> Key: IGNITE-7473
> URL: https://issues.apache.org/jira/browse/IGNITE-7473
> Project: Ignite
> Issue Type: Bug
> Components: platforms
> Affects Versions: 2.4
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Major
> Labels: .NET, xplat
> Fix For: 2.4
>
>
> Steps to reproduce:
> {code}
> dotnet new console
> dotnet add package Apache.Ignite
> nano Program.cs # Add Ignition.Start() line and a namespace import
> dotnet run
> {code}
> Error:
> {code}
> Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'System.Configuration.ConfigurationManager, Version=0.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'. The system cannot find the file specified.
> {code}
> Works on Windows, does not work on Linux.
> {{<PackageReference Include="System.Configuration.ConfigurationManager" Version="4.4.0" />}} is required to fix the issue.
> However, {{ConfigurationManager}} is not necessary for code configuration, we should be able to start without it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)