are types being made private?

.NET obfuscator and automated error reporting

Moderators: Luke Jefferson, Alex.Davies, melvyn.harbour

are types being made private?

Postby ronzul » Wed Jul 07, 2010 11:25 am

Hi... newbie Ronny here

My CF2 app is not feeling very well after using SA.

I am using System.Xml.Serialization and it is throwing an InvalidOperationException saying that "Only public types can be processed".

Any clues?

Thanks
Ronny
ronzul
 
Posts: 2
Joined: Wed Jul 07, 2010 11:21 am

Postby Paul.Martin » Wed Jul 07, 2010 7:58 pm

A few questions:

Which protections are you applying to your assembly?

Is the type that is failing to be Serialized in the main assembly or in a separate dll? If it is in a separate dll are you merging it into the main assembly as this could cause issues for serialization.

Does the type that is failing to be Serialized have an attribute within the System.Xml.Serialization namespace, as SmartAssembly will pick this up and be very careful with the type.
Paul.Martin
 
Posts: 83
Joined: Wed Feb 03, 2010 11:20 am
Location: Cambridgeshire

Postby ronzul » Thu Jul 08, 2010 2:12 am

Many thanks

The classes being serialised were in external DLLs that were being merged. Simply adding an [XmlType] attribute to them did the trick.

Cheers
Ronny
ronzul
 
Posts: 2
Joined: Wed Jul 07, 2010 11:21 am


Return to SmartAssembly 5

Who is online

Users browsing this forum: No registered users and 0 guests