McC*_*int 7 c# deployment log4net single-file .net-5
尝试使用 log4net 作为单个文件部署用 .Net 5 编写的控制台应用程序。运行部署的应用程序抛出异常。
重现步骤
static void Main(string[] args)
{
log4net.Config.XmlConfigurator.Configure(new FileInfo("log.config"));
var logger = log4net.LogManager.GetLogger("TestLogger");
logger.Info("Hello World!");
}
Run Code Online (Sandbox Code Playgroud)
<?xml version="1.0" encoding="utf-8" ?>
<log4net>
<logger name="TestLogger">
<level value="ALL" />
<appender-ref ref="console" />
</logger>
<appender name="console" type="log4net.Appender.ConsoleAppender">
<layout type="log4net.Layout.PatternLayout">
<conversionPattern value="%level - %message%newline" />
</layout>
</appender>
</log4net>
Run Code Online (Sandbox Code Playgroud)
dotnet publish -o .\Publish --self-contained true -r win-x64
dotnet publish -o .\Publish --self-contained true -r win-x64 -p:PublishSingleFile=true
抛出异常:
log4net:ERROR Exception while reading ConfigurationSettings. Check your .config file is well formed XML.
System.Configuration.ConfigurationErrorsException: Configuration system failed to initialize
---> System.IO.FileNotFoundException: Cannot find file. (0x80070002)
at System.Reflection.RuntimeModule.GetFullyQualifiedName()
at System.Reflection.RuntimeModule.get_Name()
at System.Configuration.ClientConfigPaths..ctor(String exePath, Boolean includeUserConfig)
at System.Configuration.ClientConfigPaths.GetPaths(String exePath, Boolean includeUserConfig)
at System.Configuration.ClientConfigurationHost.get_ConfigPaths()
at System.Configuration.ClientConfigurationHost.GetStreamName(String configPath)
at System.Configuration.ClientConfigurationHost.get_IsAppConfigHttp()
at System.Configuration.Internal.DelegatingConfigHost.get_IsAppConfigHttp()
at System.Configuration.ClientConfigurationSystem..ctor()
at System.Configuration.ConfigurationManager.EnsureConfigurationSystem()
--- End of inner exception stack trace ---
at System.Configuration.ConfigurationManager.EnsureConfigurationSystem()
at System.Configuration.ConfigurationManager.PrepareConfigSystem()
at System.Configuration.ConfigurationManager.GetSection(String sectionName)
at System.Configuration.ConfigurationManager.get_AppSettings()
at log4net.Util.SystemInfo.GetAppSetting(String key)
log4net:ERROR Exception while reading ConfigurationSettings. Check your .config file is well formed XML.
System.Configuration.ConfigurationErrorsException: Configuration system failed to initialize
---> System.IO.FileNotFoundException: Cannot find file. (0x80070002)
at System.Reflection.RuntimeModule.GetFullyQualifiedName()
at System.Reflection.RuntimeModule.get_Name()
at System.Configuration.ClientConfigPaths..ctor(String exePath, Boolean includeUserConfig)
at System.Configuration.ClientConfigPaths.GetPaths(String exePath, Boolean includeUserConfig)
at System.Configuration.ClientConfigurationHost.get_ConfigPaths()
at System.Configuration.ClientConfigurationHost.GetStreamName(String configPath)
at System.Configuration.ClientConfigurationHost.get_IsAppConfigHttp()
at System.Configuration.Internal.DelegatingConfigHost.get_IsAppConfigHttp()
at System.Configuration.ClientConfigurationSystem..ctor()
at System.Configuration.ConfigurationManager.EnsureConfigurationSystem()
--- End of inner exception stack trace ---
at System.Configuration.ConfigurationManager.PrepareConfigSystem()
at System.Configuration.ConfigurationManager.GetSection(String sectionName)
at System.Configuration.ConfigurationManager.get_AppSettings()
at log4net.Util.SystemInfo.GetAppSetting(String key)
Run Code Online (Sandbox Code Playgroud)
我错过了什么?
所以我相信这个问题是由于 .NET 5 中的更改造成的。我还假设 log4net 需要更新才能使用新的单一文件格式。
这里讨论了 .NET 5 如何与 3.1 不同地处理单个文件。
https://github.com/dotnet/core/issues/5409#issuecomment-715522029
在 3.1 中,从技术上讲,单个可执行文件被解压缩并从 temp 运行(至少根据我的经验,如果这些文件未在项目文件中设置为包含在单个文件之外,这可能会导致本地引用文件出现问题)。在 .NET 5 中,他们试图转移到程序集在内存中执行时保留在同一目录中的情况。然而,显然,这会导致其他问题,正如您在 log4net 中发现的那样。
上面的这个链接让我找到了答案:
dotnet publish -r win-x64 /p:PublishSingleFile=true /p:IncludeAllContentForSelfExtract=true
Run Code Online (Sandbox Code Playgroud)
/p:IncludeAllContentForSelfExtract=true 强制 .NET 5 单个文件的行为与 3.1 完全相同,这对我有用。
在接下来的几个月里,我将继续尝试,希望 log4net .NET 5 兼容性能够开始使用新格式。但至少这面旗帜让我继续前进。
| 归档时间: |
|
| 查看次数: |
1681 次 |
| 最近记录: |