Ok, the funny thing is that until I added mono.security into the referenced
libraries, it showed me on link stage:
error CS0122: 'Mono.Security.Cryptography.CryptoConvert' is inaccessible
due to its protection level
error CS0117: 'Mono.Security.Cryptography.CryptoConvert' does not contain a
defini
> > Moreover, Mono.Security assembly is shipped stripped, in particular it
> misses StrongName class - so even manual validation is not possible.
> Odd; my Mono.Security.dll contains it.
>
Hm, it seems I've checked the assembly from release folder - and it was
stripped in there.
In object browser
On Jun 27, 2012, at 5:53 PM, Igor Russkih wrote:
> Moreover, Mono.Security assembly is shipped stripped, in particular it misses
> StrongName class - so even manual validation is not possible.
Odd; my Mono.Security.dll contains it.
> What is the background behind these decisions?
I don't know w
Hello,
I've found that strong named assemblies are not validated upon load.
Moreover, Mono.Security assembly is shipped stripped, in particular it
misses StrongName class - so even manual validation is not possible.
What is the background behind these decisions?
The origin for the question is s
