PublishSingleFile causes Target symbol-name is unknown: 'RichTextBox'

[nlog]

PublishSingleFile causes Target symbol-name is unknown: 'RichTextBox'

[snakefoot]

Have you tried to explicit include the Assembly in your NLog.config:

<nlog> 
  <extensions> 
    <add assembly="NLog.Windows.Forms"/> 
  </extensions> 

[304NotModified]

Hi,

Could you please try this?

https://github.com/nlog/nlog/wiki/Register-your-custom-component#register-nlog-extensions-from-assembly-at-runtime

[lionengine123]

I added this one code line

NLog.LogManager.Setup().SetupExtensions(s =>s.RegisterAssembly("MyAssembly"));

at the very beginning of the program.cs main method and exchanged 'MyAssembly' with my Assembly name.
However this did not work. It still does not log into the corresponding richtext box when the program is published as single file.

[snakefoot]

Maybe try this:

NLog.LogManager.Setup().SetupExtensions(s => s.RegisterAssembly(typeof(NLog.Windows.Forms.RichTextBoxTarget).Assembly));

[lionengine123]

yes, this works.

However we have 20 Projects and try to keep it as 'tidy' as possible. In case it would be possible to fix the issue within the future version of nlog windows forms library, it would be great.

System.Configuration.ConfigurationManager had a similiar problem and fixed it with version 6.0.0 btw.

[lionengine123]

No, my nlog.config does not include any extension entries. Holen Sie sich Outlook für Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Rolf Kristensen ***@***.***> Sent: Saturday, March 26, 2022 11:27:44 PM To: NLog/NLog.Windows.Forms ***@***.***> Cc: lionengine123 ***@***.***>; Author ***@***.***> Subject: Re: [NLog/NLog.Windows.Forms] PublishSingleFile causes Target symbol-name is unknown: 'RichTextBox' (Issue #99) Does your NLog.config include: <nlog> <extensions> <add assembly="NLog.Windows.Forms"/> </extensions> — Reply to this email directly, view it on GitHub<#99 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AXEDVSVKL2A47TUBWIW2C6LVB6FOBANCNFSM5RQSXD7Q>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[snakefoot]

No, my nlog.config does not include any extension entries.

You can replace the explict RegisterAssembly in source-code with <extensions>-section in NLog.config.

Notice NLog 5.0 will no longer scan and load NLog-extension-assemblies automatically. Instead NLog-extension-assemblies must always be explicitly specified. But NLog 5.0 also introduces support for specifying assembly-name in target-type:

<target xsi:type="RichTextBox, NLog.Windows.Forms" name="myRichTextBox" ... />

[lionengine123]

Have you tried to explicit include the Assembly in your NLog.config:

<nlog> 
  <extensions> 
    <add assembly="NLog.Windows.Forms"/> 
  </extensions> 

Thank you this also works. (So no code changes aka 'RegisterAssembly' necessary.)

[lionengine123]

You can replace the explict RegisterAssembly in source-code with <extensions>-section in NLog.config.

Notice NLog 5.0 will no longer scan and load NLog-extension-assemblies automatically. Instead NLog-extension-assemblies must always be explicitly specified. But NLog 5.0 also introduces support for specifying assembly-name in target-type:

<target xsi:type="RichTextBox, NLog.Windows.Forms" name="myRichTextBox" ... />

Adding
<target xsi:type="RichTextBox, NLog.Windows.Forms" name="myRichTextBox" ... />

was not sufficient (/ is not needed) when publishing as single file.
There also needs to be this declaration:

<extensions> <add assembly="NLog.Windows.Forms"/> </extensions>

(Tested with 5.0.0-rc2)

[snakefoot]

NLog InternalLogger looks like this on my machine, and it just works with NLog 5.0-RC2:

Info Message Template Auto Format enabled
Debug ScanAssembly('NLog, Version=5.0.0.0, Culture=neutral, PublicKeyToken=5120e14c03d0593c')
Info Loading assembly: NLog.Windows.Forms
Debug ScanAssembly('NLog.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=5120e14c03d0593c')

If I just use xsi:type="RichTextBox" then it fails like you experience.

[lionengine123]

This thread is all about publishing as single file.
Did you publish your application as Single file?

[snakefoot]

This is my csproj-file:

  <PropertyGroup>
    <OutputType>WinExe</OutputType>
    <TargetFramework>net6.0-windows</TargetFramework>
    <RuntimeIdentifier>win-x64</RuntimeIdentifier>
    <UseWindowsForms>true</UseWindowsForms>
    <PublishSingleFile>true</PublishSingleFile>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="NLog" Version="5.0.0-rc2" />
  </ItemGroup>

And this is the command that I was running to perform the publish:

dotnet publish -c Release

This is the publish-folder:

This is the NLog.config:

<?xml version="1.0" encoding="utf-8" ?>
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation="http://www.nlog-project.org/schemas/NLog.xsd NLog.xsd">

  <targets>
    <target xsi:type="RichTextBox, NLog.Windows.Forms"
            name="target1"
            layout="${message}"

            autoScroll="true"
            maxLines="30"
     
            useDefaultRowColoringRules="true" />

[lionengine123]

Thanks,
I was just asking because the program behaviour differs in comparison to our application.
we also build with
dotnet publish -c:Release

However we have: (Net5.0)

<TargetFramework>net5.0-windows</TargetFramework>
and also usually
<IncludeNativeLibrariesForSelfExtract>true</IncludeNativeLibrariesForSelfExtract>

Perhaps that's where the different behaviour comes from.
As
<target xsi:type="RichTextBox, NLog.Windows.Forms" ... />
doesn't work for us.

Your answer:

Have you tried to explicit include the Assembly in your NLog.config:

<nlog> 
  <extensions> 
    <add assembly="NLog.Windows.Forms"/> 
  </extensions> 

is already our solution and solves the problem on our side.

[lionengine123]

In your Testsetting I realized you are not using a controlName. Do you log into a separate Logging Window?
We are logging into an existing richtextbox, which is a big difference ...

`

<target name="locatortextbox" xsi:type="RichTextBox" controlName="locatorTextBox" formName="LogForm" maxLines="100" autoScroll="true"
    useDefaultRowColoringRules="true" layout="${longdate} ${uppercase:${level}} ${message}" allowAccessoryFormCreation="False"/>

...
`

(Net5 <-> Net6 didnt make any difference)
<IncludeNativeLibrariesForSelfExtract>true</IncludeNativeLibrariesForSelfExtract> also didnt make any difference.

[snakefoot]

Think your questions are beyond my skill-set when it comes to the NLog.Windows.Forms-package.

I was mostly interested in whether xsi:type="RichTextBox, NLog.Windows.Forms" worked with NLog 5.0 and PublishSingleFile=true (And it did for me).

And yes when using NLog 4.7 with PublishSingleFile=true, then it will only work with:

<nlog> 
  <extensions> 
    <add assembly="NLog.Windows.Forms"/> 
  </extensions>

[snakefoot]

Closing issue as answered due to inactivity