Incorrect assembly name in nuget package Castle.Core-log4net

[beginor]

When deploy to linux, I got the flowing error:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Castle.MicroKernel.SubSystems.Conversion.ConverterException: Could not convert string 'Castle.Services.Logging.Log4netIntegration.Log4netFactory,Castle.Services.Logging.Log4netIntegration,Version=4.0.0.0, Culture=neutral,PublicKeyToken=407dd0808d44fbdc' to a type. Assembly was not found. Make sure it was deployed and the name was not mistyped.
  at Castle.MicroKernel.SubSystems.Conversion.TypeNameConverter.GetType (System.String name) [0x000e7] in <da07e4a3dbff400986e1fa0da51c098b>:0 
  at Castle.MicroKernel.SubSystems.Conversion.TypeNameConverter.PerformConversion (System.String value, System.Type targetType) [0x0000b] in <da07e4a3dbff400986e1fa0da51c098b>:0 
  at Castle.MicroKernel.SubSystems.Conversion.DefaultConversionManager.PerformConversion (System.String value, System.Type targetType) [0x0001e] in <da07e4a3dbff400986e1fa0da51c098b>:0 
  at (wrapper remoting-invoke-with-check) Castle.MicroKernel.SubSystems.Conversion.DefaultConversionManager:PerformConversion (string,System.Type)
  at Castle.MicroKernel.SubSystems.Conversion.DefaultConversionManager.PerformConversion[TTarget] (System.String value) [0x00000] in <da07e4a3dbff400986e1fa0da51c098b>:0 
  at Castle.Facilities.Logging.LoggingFacility.GetLoggingFactoryType (Castle.Facilities.Logging.LoggerImplementation loggerApi) [0x00070] in <0c3db78b6aba4b999cd2ecc63cfb3b9e>:0 
  at Castle.Facilities.Logging.LoggingFacility.CreateProperLoggerFactory (Castle.Facilities.Logging.LoggerImplementation loggerApi) [0x00000] in <0c3db78b6aba4b999cd2ecc63cfb3b9e>:0 
  at Castle.Facilities.Logging.LoggingFacility.ReadConfigurationAndCreateLoggerFactory () [0x00007] in <0c3db78b6aba4b999cd2ecc63cfb3b9e>:0 
  at Castle.Facilities.Logging.LoggingFacility.Init () [0x0000e] in <0c3db78b6aba4b999cd2ecc63cfb3b9e>:0 

When I check the bin directory, The assembly I found is Castle.Services.Logging.log4netIntegration.dll, after I rename it to Castle.Services.Logging.Log4netIntegration.dll, it works!

This should be a spell mistake, but will break Castle.Core-log4net runing on case sensitive file system, please correct it!

[jonorossi]

It appears this was broken in 4.0.0. Previously in 3.3.3 the binary was named Castle.Services.Logging.Log4netIntegration.dll.

This has happened with the change to the new .NET tooling because the project file didn't match the assembly name:

• Castle.Services.Logging.log4netIntegration.csproj
• Castle.Services.Logging.Log4netIntegration

@beginor could you provide a pull request fixing the assembly name?

Just a side note: there are deprecation changes to the logging facility in Windsor 4.1.0 that affect this code path.

[beginor]

OK， maybe I can try it later

[jonorossi]

Thanks for the fix, I've merged it.