2011/8/23 Atsushi Eno
> I wonder where the corresponding sections in ECMA CLI specification or
> .NET documentation that mentions those functions shown in the code are.
>
> Atsushi Eno
>
> On 2011/08/22 19:21, Brandon Perry wrote:
> > Hi,
> >
> > The following link contains code that runs just fi
What Atsushi means is that this piece of code is exploiting a private
implementation detail of the .net framework, so no wonder it doesn't
«work» on Mono.
On Tue, Aug 23, 2011 at 10:28 AM, Stefanos A. wrote:
> 2011/8/23 Atsushi Eno
>>
>> I wonder where the corresponding sections in ECMA CLI spec
Exactly. Though if there is .NET documentation, JIT hackers can read
them and it might be still able to consider possible implementation.
I doubt that could happen though. Calling conventions differ in each
platform, compiler toolschains etc. Maybe not completely impossible, but
too fruitless.
Thanks for the info, I didn't realise it wasn't standard code.
On Tue, Aug 23, 2011 at 7:39 PM, Atsushi Eno
wrote:
> Exactly. Though if there is .NET documentation, JIT hackers can read
> them and it might be still able to consider possible implementation.
> I doubt that could happen though. Call
I would like to know the standard build environment for building the Mono
binaries for Windows. I have been currently using Cygwin using the "make
get-monolite-latest" after the autogen.sh command, but the build is very
unstable and often fails. The Cygwin environment seems to be rather
fragile.
Hi all,
I am trying to use chktrust to verify validity of the digital/counter
signature of a file. Specifically, I used AcroRD32.exe, which's been signed
by Adobe Systems, Incorporated and counter signed by verisign time stamping
service.
To add this to mono trust store, I exported the actual
