Comments
Sort by recent activity
So only when the option to do ANY level of "Control Flow Obfuscation" does the build of this cmdlet dll fail every time. If set to none but other settings left enabled, the build succeeds.
Here's the end of the log. Does this tell you anything as to what's causing this failure? Should SA be able to properly do control flow obfuscation on a net3.5 csharp cmdlet dll?
2014-02-09 14:35:39,892 INFO SmartAssembly.ProcessingAssembly: Obfuscating assembly code...
2014-02-09 14:35:40,001 ERROR SmartAssembly.ProcessingProject: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
at System.ThrowHelper.ThrowArgumentOutOfRangeException()
at System.Collections.Generic.List`1.get_Item(Int32 index)
at System.Collections.ObjectModel.Collection`1.get_Item(Int32 index)
at ?.?.(IList`1 , Int32 )
at ?.?.( , IList`1 )
at ?.?.( )
at ..()
at ?.?.( )
at ?.?.( )
at ?..() / comments
So only when the option to do ANY level of "Control Flow Obfuscation" does the build of this cmdlet dll fail every time. If set to none but other settings left enabled, the build succeeds.
Here's ...
Hi Jessica, that worked! That is really weird that it failed with the reduce memory allocation enabled but thank you! Is that going to be fixed in the next release? / comments
Hi Jessica, that worked! That is really weird that it failed with the reduce memory allocation enabled but thank you! Is that going to be fixed in the next release?