A Community Edition for the legendary Comic Book Manager ComicRack. ComicRack is back from the dead.
The Clone throws an exception about `XmlElement` not being marked as serializable. The culprit is when the `ComicBook` contains unparsed data (from it's xml file) that was caught in the `UnparsedElements` property. That data was never a problem when exporting a book or updating. Reference to the change in [this discussion](https://github.com/maforget/ComicRackCE/discussions/40#discussioncomment-8535853). https://github.com/maforget/ComicRackCE/blob/d939b585f470770f2719f5a8ec01040e3c1acd40/ComicRack.Engine/ComicBook.cs#L2261-L2269 The `BinaryFormatter` used in the CloneUtility throws the exception when using `Serialize`. The Serialization works correctly when using other like `XmlSerializer` or `DataContractSerializer`. https://github.com/maforget/ComicRackCE/blob/d939b585f470770f2719f5a8ec01040e3c1acd40/cYo.Common/CloneUtility.cs#L15-L21 But even updating the `CloneUtility` to use another serializer or using `ComicBook.Clone()` to pass the first exception there is still a problem when using `PasteComicData()`. `Clipboard.GetData` returns null if the copied data contains any value in `UnparsedElements` property. Even if IDataObject.GetDataPresent confirms before hand that the data is present. https://github.com/maforget/ComicRackCE/blob/d939b585f470770f2719f5a8ec01040e3c1acd40/ComicRack/Views/ComicBrowserControl.cs#L2739-L2748 I haven't debugged the `Clipboard.GetData` but some kind of internal serializer that also uses `BinaryFormatter`? Would using a newer framework change the outcome since `BinaryFormatter` isn't supported anymore? So possible solution may be to just use the text version copied of the ComicBook instead. This solution would also permit pasting data from across sessions and from just a simple text editor.
This issue appears to be discussing a feature request or bug report related to the repository. Based on the content, it seems to be still under discussion. The issue was opened by maforget and has received 0 comments.