Forums - CSHTML5

Hi Team,

I got compile error Error generating serialization assemblies. Please look in the Output pane for details. This is usually due to two serializable types having the same name. If the error persists, please contact support@cshtml5.com or ignore this error by adding the following line to your CSPROJ file: <CSharpXamlForHtml5SkipSerializationAssemblies>True</CSharpXamlForHtml5SkipSerializationAssemblies> when consuming WCF service on client side. I couldn't find cause of this issue. service layer is compiling properly.

Could you please let me know the exact cause of this issue.

Thanks,

Hi Team,

Any update on this?

Thanks.

Hi Team,

PFA sample project which is giving SkipSerializationAssemblies error. In solution, I have used two projects i.e. ConsoleApp and WCF service



In WCF service, I have used custom class 'TestObject' which is passed as input in one service and returned in other service operation. After consumption in console app, it is giving error but it is also suggesting to add Tag <CSharpXamlForHtml5SkipSerializationAssemblies>True</CSharpXamlForHtml5SkipSerializationAssemblies> in .csproj. I added this tag and console app is compiled successfully but it is throwing error in catch when run in browser. Below are two exception message caught in catch of CallService1() and CallService2()
1. Error - "Error: Type initialization failed for type 'System.Xml.Serialization.XmlSerializer'\n at RegisterName_getter (-----

2. Error - "TypeError: Unable to get property 'TypeRef' of undefined or null reference\n at Anonymous function (-----

Could you please suggest.

Thanks.

Thank you sd1388.

We are going to investigate and keep you updated asap.

Regards,
JS-Support

Thanks, team, for the acknowledgement!

Hi Team,

Any update on this.

Thanks.

Hi Team,

Error -

C#/XAML for HTML5: SerializationAssembliesGenerator failed : System.Exception: The following serializable classes have the same name: "<Service1.Class1>" and "<Service2.Class1>". The current version of C#/XAML for HTML5 does not allow serializing two classes that have the same name. This is due to the fact that the XmlSerializer does not support namespaces at the moment. To work around this limitation, please rename one of the two classes, or remove its [Serializable] or [DataContract] attribute.
at b.a(String A_0, String A_1, ILogger A_2, String& A_3, String& A_4, Boolean& A_5)
at DotNetForHtml5.Compiler.SerializationAssembliesGenerator.Execute()......

I understand that creating duplicate class will resolve this issue but there are other more class properties are being used in Class1 and Class2 and these are also have same name. I have question that when shall we expect final resolution of this issue in coming weeks.

Thanks,
Swapnil