Comments
Sort by recent activity
Ok, thank you for the clarification. Glad you managed to reproduce it internally. / comments
Ok, thank you for the clarification. Glad you managed to reproduce it internally.
Hi Russell, Here is the entire project along with .saproj. Just build Release and it will call SA 7 in post build event. Also worth mentioning, since I'm doing this on a test machine, I'm using Personal (Trial) version of SA. Best regards / comments
Hi Russell,Here is the entire project along with .saproj.Just build Release and it will call SA 7 in post build event.Also worth mentioning, since I'm doing this on a test machine, I'm using Person...
Hello, sorry for bringing this topic from the dead, but I'm experiencing the similar issue with the latest SmartAssembly 7.0.3.2212. The simplest way I managed to reproduce this: Create new C# class lib targeting .NET 3.5. Add reference to System.Windows.Forms. Add a dummy Windows Form. The obfuscated assembly has it's references changed from 2.0 to 4.0 runtime for no apparent reason. See this (reflected using dotPeek): [image] For reference, here is the same project in VS2017: [image] The problem resolves when I remove the ref to System.Windows.Forms but that is not really a solution. Is there any workaround for this issue? / comments
Hello, sorry for bringing this topic from the dead, but I'm experiencing the similar issue with the latest SmartAssembly 7.0.3.2212.The simplest way I managed to reproduce this:Create new C# class ...