[
https://issues.apache.org/jira/browse/IGNITE-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16347088#comment-16347088
]
Pavel Tupitsyn edited comment on IGNITE-7473 at 1/31/18 4:26 PM:
-----------------------------------------------------------------
Reopening. Turns out it worked in nightly builds right after IGNITE-2662 was
merged, and was broken after IGNITE-6615 merge.
Looks like this is caused by generic {{GetConfigurationSection<T>}} method, may
be removing generic constraint will fix the problem?
was (Author: ptupitsyn):
Reopening. Turns out it worked in nightly builds right after IGNITE-2662 was
merged, and was broken after IGNITE-6615 merge.
> .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.5
>
>
> 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)
