The ServiceColor serialization does not work with the net5 publish feature.

[schattenmann80]

I have a small net5 project where I use the FCTB.
And when I start the programm localy in Visual Studio or over they exe there are not problems.

But if I use the publish feature from net5 und try to start the exe I get the following Error:

Exception Info: System.Runtime.Serialization.SerializationException: Invalid BinaryFormatter stream.
---> System.TypeInitializationException: The type initializer for 'System.Runtime.Serialization.Formatters.Binary.Converter' threw an exception.
---> System.IO.FileNotFoundException:
....

After some searching I did found that the problem is the ServiceColor serialization, in the desinger generated code.
But if I remove the following line, in the desinger generated code:
this.InputFCTextBox.ServiceColors = ((FastColoredTextBoxNS.ServiceColors)(resources.GetObject("InputFCTextBox.ServiceColors")));
It does work again.
But I can't save the ServiceColors.

My solution was to remove the [Serializable] attribute from the ServiceColors class.
Than the ServiceColor does not get serializated and stored in the resx file.
Instead the ServiceColors will be stored in the desinger generated code.

I do not unterstand why the ServiceColors must be serializated.
It does take up more space then the generated code.

[Hexman768]

Have you tested to check and confirm that everything in the FCTB works properly after publishing (in the executable)?

I would be worried that something would go wrong with the colors in the fonts.

As far as the issue, I do not have much time currently to work on these issues, and I am the only maintainer available for the time being. This issue is probably going to get prioritized behind others only because this project does not natively support .NET 5.

[schattenmann80]

I did not test everything. But as far as I can tell it is locking find. I did not find any problem until now.

What should I Test ?

[Hexman768]

What do you mean by "locking find"?

Also, I'm not sure what ServiceColors does off the top of my head, but if you have a change to stop serializing it and haven't seen any issues after publishing, I would say that the change is probably valid.

[lizhihua0625]

/// <summary> /// Colors of some service visual markers /// </summary> [Browsable(false)] [Description("Colors of some service visual markers.")] [TypeConverter(typeof(ExpandableObjectConverter))] [DesignerSerializationVisibility(DesignerSerializationVisibility.Hidden)] public ServiceColors serviceColors { get; set; }
这样修改后可以。。。

[schattenmann80]

Sorry that was a typo. I wanted to say: it is looking fine.

I will make a pull request and if you like it you can merge it.

Pull request: "Removed serialization from ServiceColors for compatibility to Net5 #279 "