Comments
Sort by recent activity
Hi Richard,
Unfortunatelly support contract had expired. Does it mean that nobody would be interested to investigate the issue? / comments
Hi Richard,
Unfortunatelly support contract had expired. Does it mean that nobody would be interested to investigate the issue?
With help of a very helpful lady from the support we have been able to find the cause of the problem. SA is very sensitive to the version of reference assemblies that are used during obfuscation and when you run your application.
Basically what was happening is that during obfuscation version 9.0.XXX of a reference assembly was used. But the installation of the application contained version 9.0.YYY of reference assemblies. Apparently that's what was causing crashes. / comments
With help of a very helpful lady from the support we have been able to find the cause of the problem. SA is very sensitive to the version of reference assemblies that are used during obfuscation an...
jessica.ramos wrote:
Thanks for your post and sorry to hear you're running into some trouble with SmartAssembly!
Just to confirm--if the app has obfuscation turned off but you still build it through SmartAssembly (with no options enabled), does that build run on other machines without crashing?
It happens with all the obfuscations turned off. The only option shown "green" in SmartAssembly is Generate Debug Info. All other options are turned off "yellow".
jessica.ramos wrote:
I'm also curious.. is .NET 4.5 installed on any of the other machines you've tested on?
Yes, .Net 4.5 is installed. Our application is targeting .Net 4.0.
This is becoming a showstopper for us, please advise what we should do next. / comments
jessica.ramos wrote:
Thanks for your post and sorry to hear you're running into some trouble with SmartAssembly!
Just to confirm--if the app has obfuscation turned off but you still build it thr...