WCF Call breaking when some of the dlls are obfuscated...
You get an error with the following words in it:
"WCF obfuscated dll Error line position Element _BackingField from namespace not expected"
A moron once told me that there is no need to put DataContract and DataMember attributes for the entity objects anymore. I did not listen, he went ahead and stopped putting it in.
Turns out, if any of the moron's entity classes are modified to add more fields later, the WCF call to the server which takes the entity breaks with this weird error.
Looks like the obfuscator handles classes with these attributes while it creates problems when the class does not have the attribute.
This is why whenever we ran code with obfuscation it failed, while the code without obfuscation from the exact same source code works fine.
REF: http://stackoverflow.com/questions/5921635/is-datacontract-attributes-required-for-wcf
"WCF obfuscated dll Error line position Element _BackingField from namespace not expected"
A moron once told me that there is no need to put DataContract and DataMember attributes for the entity objects anymore. I did not listen, he went ahead and stopped putting it in.
Turns out, if any of the moron's entity classes are modified to add more fields later, the WCF call to the server which takes the entity breaks with this weird error.
Looks like the obfuscator handles classes with these attributes while it creates problems when the class does not have the attribute.
This is why whenever we ran code with obfuscation it failed, while the code without obfuscation from the exact same source code works fine.
REF: http://stackoverflow.com/questions/5921635/is-datacontract-attributes-required-for-wcf
Comments
Post a Comment