RESOLVED: Error related to .NET Remoting

.NET obfuscator and automated error reporting

Moderators: Luke Jefferson, Alex.Davies, melvyn.harbour

RESOLVED: Error related to .NET Remoting

Postby bobishkindaguy » Fri Jan 14, 2011 8:37 pm

Hi, I have been trying for days to get my application to pass remoting messages by various combinations of excepting from pruning and obfuscation.

Here is the .NET Remoting-related error message:
The argument type 'BizLayer.nBZClientFunctions.MessageFromServerToClientHandler' cannot be converted into parameter type 'BizLayer.nBZClientFunctions.MessageFromServerToClientHandler'.

The remoting capabilities of my app involve many different classes, and subroutines within classes, but it would be helpful to know exactly what settings I need to set/not set in smartassembly to prevent this error.

For example, if I exclude the whole project, the error does not occur. But that leaves that whole project unprotected.
Thank you!

UPDATE:
I have relocated all remoting-related code into a separate project, and this problem has disappeared !!
I did not "merge" the remoting project, but I did "embed" it, and then I turned on the maximum features for everything else, and there do not seem to be any problems for the moment.
bobishkindaguy
 
Posts: 1
Joined: Fri Jan 14, 2011 8:32 pm

Postby Alex.Davies » Sun Jan 16, 2011 10:03 am

Yes, when something complains that two types that look the same aren't the same, it's merging that's broken it. That's a fundamental limitation of any merging technique.
Alex
Developer,
Red Gate .NET Tools
Alex.Davies
 
Posts: 335
Joined: Tue Dec 02, 2008 12:23 pm
Location: Cambridge, uk


Return to SmartAssembly 5

Who is online

Users browsing this forum: No registered users and 0 guests

cron