Activity overview
Latest activity by mikeanderson12
SmartAssembly breaks the app.manifest functionality...
I have custom settings that change UAC, etc. for my .exe and it doesn't appear that SA respects the existing manifest when rebuilding my .exe.
I created an app.manifest that solves this problem (ht...
Thanks for the reply.
Yes, I meant 'merge'.
I can obfuscate .dll 'A' separately from .dll 'B' and recreate the .xap using the two obfuscated .dlls and my SL application works correctly. It would seem that I should be able to process both .dll's together.
No reflection is used to call methods in either .dll.
If merging can break namespaces, then there are known conditions which could be communicated to the user, yes?
Aside from reflection, which makes sense, which other conditions will break merging? / comments
Thanks for the reply.
Yes, I meant 'merge'.
I can obfuscate .dll 'A' separately from .dll 'B' and recreate the .xap using the two obfuscated .dlls and my SL application works correctly. It would s...
*bump*? / comments
*bump*?
SA failing to merge Silverlight 4 .dlls.
I am running an OOB app.
With all settings set to 'Off', the SL app works fine after processing.
When I elect to embed a required Silverlight .dll (our app's common/shared code) into the applicatio...