[IGNITE-12176] .NET: Apache.Ignite.exe fails when config has custom logger or plugins

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8
• Component/s: platforms
• Labels: .NET
• Assignee: Pavel Tupitsyn
• Reporter: Pavel Tupitsyn
• Created: 17/Sep/19 12:07
• Updated: 17/Sep/19 18:28
• Resolved: 17/Sep/19 18:28

Description

Steps to reproduce:

• Implement Apache.Ignite.Core.Log.ILogger interface, compiled into assembly
• Create a config file with that logger:

  <configuration>
      <configSections>
          <section name="igniteConfiguration" type="Apache.Ignite.Core.IgniteConfigurationSection, Apache.Ignite.Core" />
      </configSections>
  
      <igniteConfiguration xmlns="http://ignite.apache.org/schema/dotnet/IgniteConfigurationSection">
          <logger type='CustomNs.CustomLogger, CustomAsm' />
      </igniteConfiguration>
  </configuration>
  

• Run Apache.Ignite.exe with that config file while CustomAsm is in a separate dir:

  Apache.Ignite.exe -ConfigFileName=myconfig.xml -assembly=c:\w\CustomAsm.dll
  

Issue Links

• is related to: IGNITE-12166 .NET: ExecutableTest fails with PathTooLong error
• links to: #6872
• links to: GitHub Pull Request #6872