Comments
Sort by recent activity
Thanks, fixed a few errors I was receiving under the previous build. I must say I'm finding this a very useful tool.
Any idea of pricing when it's finished EAP? / comments
Thanks, fixed a few errors I was receiving under the previous build. I must say I'm finding this a very useful tool.
Any idea of pricing when it's finished EAP?
Thanks Brian, any idea when there'll be a viable workaround or built-in solution? / comments
Thanks Brian, any idea when there'll be a viable workaround or built-in solution?
Yup, tried that, no success either. / comments
Yup, tried that, no success either.
Thanks. Tried the DWORD in both HKLM and HKCU with no luck even after a reboot. Will attempt the ILDSAM route next. / comments
Thanks. Tried the DWORD in both HKLM and HKCU with no luck even after a reboot. Will attempt the ILDSAM route next.
Version 6.6.2.35 / comments
Version 6.6.2.35
Brian Donahue wrote:
The output of a .NET Console project referencing System.CoreX and System.Interactive can be successfully processed by SmartAssembly 6.6.
But can they be embedded or merged? / comments
Brian Donahue wrote:
The output of a .NET Console project referencing System.CoreX and System.Interactive can be successfully processed by SmartAssembly 6.6.
But can they be embedded or merged?
I'm having the same problem hee, but with Reactive Extensions: System.CoreEx and System.Reactive. Instantiating and using classes from either DLL in my main project doesn't help, SA still doesn't see them as dependencies. Is this something to do with the fact they they're in the System namespace? / comments
I'm having the same problem hee, but with Reactive Extensions: System.CoreEx and System.Reactive. Instantiating and using classes from either DLL in my main project doesn't help, SA still doesn't s...
They're an MS Labs library all the cool guys are using: http://msdn.microsoft.com/en-us/data/gg577609
IObserver<T> and IObservable<T> are probably the most common uses, I specifically use IEvent<T> in this case. / comments
They're an MS Labs library all the cool guys are using: http://msdn.microsoft.com/en-us/data/gg577609
IObserver<T> and IObservable<T> are probably the most common uses, I specifically use IEvent<T>...
I am experiencing this same problem after upgrading an application to .NET 4.0. It runs fine before obfuscation, but in the obfuscated executable a TypeLoaderException is thrown with a SecurityException as the inner.
Decoded stack trace is:
at SmartAssembly.SmartExceptionsCore.StackFrameHelper.CreateExceptionN(Exception , Object[] )
at SmartAssembly.SmartExceptionsCore.StackFrameHelper.CreateException4(Exception , Object , Object , Object , Object )
at SmartAssembly.StringsEncoding.Strings..cctor()
Occurs with or without string encoding enabled.
Fake Edit:
Adding the following attribute to the Assembly resolved the issue:
<Assembly: System.Security.SecurityRules(System.Security.SecurityRuleSet.Level1)> / comments
I am experiencing this same problem after upgrading an application to .NET 4.0. It runs fine before obfuscation, but in the obfuscated executable a TypeLoaderException is thrown with a SecurityExce...
I'm encountering a similar problem.
We access some assemblies in our application only through reflection, and even though we have a project reference to the assembly in Visual Studio (and TFS builds this reference for us and deploys it to the drop folder), SA doesn't identify it as a dependency.
As a workaround, somewhere in the executing assembly we force a dependency by declaring a variable as a type in the target assembly.
But it would be great if SA would allow us to include these unused references as dependencies so we can embed and optionally obfuscate and prune them. / comments
I'm encountering a similar problem.
We access some assemblies in our application only through reflection, and even though we have a project reference to the assembly in Visual Studio (and TFS build...