Comments
4 comments
-
*bump*? -
Hi Mike.
Apologies for the delay in replying.
You wrote "embed" once but I assume you were referring to merging. Please clarify.
Merging can break namespaces , which means it will cause problems should you use reflection to call a method or type by name.
You can trace any use of reflection using the error reporting as described in the troubleshooting guide. Or you can try embedding the dependency instead. -
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? -
Merging and possible failure modes (see troubleshooting section) are described here:
http://www.red-gate.com/supportcenter/C ... rtAssembly
You should be able to process the entire project as described here
http://www.red-gate.com/supportcenter/C ... 362558.htm
Add comment
Please sign in to leave a comment.
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 application .dll the OOB app displays the white screen of death.
No errors are returned from the build process.
If error reporting is enabled, no errors are reported.
No options are turned on except for merging the required Silverlight .dll.
Thanks!
[ALSO]
I have read the document on troubleshooting common problems...