Comments
Sort by recent activity
Thanks for the reply. I think I know why the modules are failing to open in SmartAssembly - the assembly entry point is not specified.
I added App.xaml to all of the modules, and set it as the entry point in the project properties. This allowed the assembly to be loaded in SA.
When prompted for dependencies, I added a new search folder to the shell output folder, which works well and should translate across servers using relative paths.
The remaining step was to exclude views loaded by reflection - haven't found any other problems so far although my testing is not exhaustive.
So I have a working solution for now. Thanks for your help! / comments
Thanks for the reply. I think I know why the modules are failing to open in SmartAssembly - the assembly entry point is not specified.
I added App.xaml to all of the modules, and set it as the entr...
Also, I can't obfuscate any of the module XAPs either, I get the message "'XXX' is not a valid .NET assembly" whenever I try to open the source XAP.
These modules are PRISM modules, meaning they just compile the project DLL into the XAP, and references are all set to Copy Local=False, which is the standard pattern.
This is a bit of a show-stopper, if I can't even open module XAPs. Is anyone aware of this issue? / comments
Also, I can't obfuscate any of the module XAPs either, I get the message "'XXX' is not a valid .NET assembly" whenever I try to open the source XAP.
These modules are PRISM modules, meaning they ju...
I've already tried excluding the service contracts and implementations - that resolved the first error, but then I got an error that data contracts could not be serialized.
Excluding or re-writing all data contracts wasn't feasible.
However, I have managed to get a solution that is acceptable for our server-side application - the service host itself does not really need obfuscation as it is really just a thin wrapper for WCF hosting and doesn't contain any business logic.
I obfuscated the application DLLs separately in their own projects, and this seems to work fine - dependency merging / embedding doesn't work but we don't really need it. / comments
I've already tried excluding the service contracts and implementations - that resolved the first error, but then I got an error that data contracts could not be serialized.
Excluding or re-writing ...