System.InvalidOperationException: An attempt was made to load a type with the fully qualified name of 'x'

Hey,

I generated classes from xml schema with https://github.com/mganss/XmlSchemaClassGenerator

The XML has attribute on the root element like xmlns:tns="http://jpk.mf.gov.pl/wzor/2017/11/13/1113/" but somehow ExtendedXmlSerializer can’t swallow it 😦. Normal XmlSerializer can but it’s kinda old and would love to switch to ExtendedXmlSerializer.

This is the schema I generated class from: https://www.gov.pl/documents/2034621/2182793/Schemat_JPK_VAT(3)_v1-1.xsd

Unhandled exception. System.InvalidOperationException: An attempt was made to load a type with the fully qualified name of 'http://jpk.mf.gov.pl/wzor/2017/11/13/1113/:JPK', but no type could be located with that name.
   at ExtendedXmlSerializer.ContentModel.Extensions.GetClassification(IClassification this, IFormatReader parameter, TypeInfo defaultValue)
   at ExtendedXmlSerializer.ExtensionModel.Xml.Read.Get(XmlReader parameter)
   at ExtendedXmlSerializer.ExtensionModel.Xml.Serializer.Deserialize(XmlReader reader)
   at ExtendedXmlSerializer.ExtensionModel.Xml.ExtendedXmlSerializer.Deserialize(XmlReader reader)
   at ExtendedXmlSerializer.ExtensionMethodsForSerialization.Deserialize[T](IExtendedXmlSerializer this, XmlReaderSettings settings, Stream stream)
   at ExtendedXmlSerializer.ExtensionMethodsForSerialization.Deserialize[T](IExtendedXmlSerializer this, Stream stream)
   at ConsoleApp3.Program.Main(String[] args) in C:\Users\Konrad\RiderProjects\ConsoleApp3\ConsoleApp3\Program.cs:line 18

Is there anyway to make it behave more like the original XmlSerializer?

var serializer = new ConfigurationContainer().UseAutoFormatting()
                .Create();

It tries to load “http://jpk.mf.gov.pl/wzor/2017/11/13/1113/:JPK” as a type but it’s not a type, it’s not even fully qualified type name so it should never try to load it.

This is how root node looks like:

<tns:JPK xsi:schemaLocation="http://jpk.mf.gov.pl/wzor/2017/11/13/1113/ https://www.gov.pl/documents/2034621/2182793/Schemat_JPK_VAT%283%29_v1-1.xsd" xmlns:tns="http://jpk.mf.gov.pl/wzor/2017/11/13/1113/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:etd="http://crd.gov.pl/xml/schematy/dziedzinowe/mf/2016/01/25/eD/DefinicjeTypy/" xmlns:kck="http://crd.gov.pl/xml/schematy/dziedzinowe/mf/2013/05/23/eD/KodyCECHKRAJOW/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msxsl="urn:schemas-microsoft-com:xslt" xmlns:usr="urn:the-xml-files:xslt">

https://github.com/ExtendedXmlSerializer/home/blob/16dd56a3066896787b85a90298434315741b8108/src/ExtendedXmlSerializer/ContentModel/Extensions.cs#L23

thx in advance

[bugproof]

Should be fine to solve that serialization problem. Thanks. XML in .NET is a tough topic, probably because everyone moved on to other formats. In that particular use case it seems like using original XmlSerializer is unavoidable 😄 The only thing that works with “legacy” xml.

[Mike-E-angelo]

Alright @bugproof after poking around at this I found another issue #200 that was similar and has a solution that involves adjustments to the extensions that are passed into the ConfigurationContainer constructor. Check it out:

https://github.com/ExtendedXmlSerializer/home/blob/97f458c56de54f7993ba521484eda9d220be8730/test/ExtendedXmlSerializer.Tests.ReportedIssues/Issue374Tests.cs#L18-L47

Since we are dancing around the limitations of ExtendedXmlSerializer’s legacy serialization support (trust me, it’s a sore topic 😆) my preference would be to try to stay away from touching the internals as much as possible and leverage the extension model if we can. Please let me know how that sits with you and/or any additional issues you might run into with getting this to work as desired.