Comments
Sort by recent activity
We also need this Update.
Seems like actual support for this product has de facto ended? / comments
We also need this Update.
Seems like actual support for this product has de facto ended?
Yes, the two constructors are labelled with "rtspecialname".
Nothing else in the class, though. / comments
Yes, the two constructors are labelled with "rtspecialname".
Nothing else in the class, though.
I generated the log.
The relevant properties aren't listed in the log file.
The only entries for a relevant class (as an example) I could find in the log are the following:
2014-04-30 15:19:05,045 TRACE SmartAssembly.ObfuscationAnalyzer: Method [NAMESPACE]NAMESPACE.Accommodation::instance System.Void .ctor(valuetype [mscorlib]System.Guid) excluded from obfuscation: RtSpecialName
2014-04-30 15:19:05,045 TRACE SmartAssembly.ObfuscationAnalyzer: Method [NAMESPACE]NAMESPACE.Accommodation::instance System.Void .ctor() excluded from obfuscation: RtSpecialName
The properties of "Accommodation" stay public and don't get obfuscated. / comments
I generated the log.
The relevant properties aren't listed in the log file.
The only entries for a relevant class (as an example) I could find in the log are the following:
2014-04-30 15:19:05,045 ...
No, they aren't labelled that way. / comments
No, they aren't labelled that way.
Brian, could you please be more specific what you mean by "incompatible resources"? I have the problem as well and I really don't want to uninstall .NET Framework 4.5, nor should I have to imo.
I'm targeting .NET 4.0. / comments
Brian, could you please be more specific what you mean by "incompatible resources"? I have the problem as well and I really don't want to uninstall .NET Framework 4.5, nor should I have to imo.
I'm...