type eligible for equivalence, but is not marked as public

.NET obfuscator and automated error reporting

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

type eligible for equivalence, but is not marked as public

Postby vk » Mon Sep 06, 2010 8:16 pm

I am using trial version of SmartAssembly, and having issue with understanding what can i do to avoid next error

Form1.ExecuteNextStep-Could not load type 'XX.XX' from assembly 'MyAssembly, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'. The type is marked as eligible for type equivalence, but it is not marked as public.
[2010-09-06 14:23:23.484] Form1.ExecuteNextStep- at X.
vk
 
Posts: 1
Joined: Mon Sep 06, 2010 7:59 pm

Postby Brian Donahue » Wed Sep 08, 2010 10:53 am

Hi Volody,

It's pretty clear that you are trying to bind to a member in another assembly using reflection, so if you are using merging you may have to switch to embedding. Trying to bind to types that have been renamed by SmartAssembly may also fail.
Brian Donahue
 
Posts: 6669
Joined: Mon Aug 23, 2004 10:48 am

Postby Brian Donahue » Fri Sep 10, 2010 1:31 pm

It could also be that the assembly being merged has the PrimaryInteropAsssembly attribute set. SA doesn't support that merging scenario yet as far as I'm aware.
Brian Donahue
 
Posts: 6669
Joined: Mon Aug 23, 2004 10:48 am


Return to SmartAssembly 5

Who is online

Users browsing this forum: No registered users and 0 guests