[Mono-devel-list] current cygwin/ms runtime issues

Sébastien Pouliot spouliot at videotron.ca
Mon May 3 13:54:15 EDT 2004

Hello all,

This isn't exhaustive and the issues may not be here for long but this may
save you some problems/questions.

* MCS build

The mcs build breaks after the default (1.1) profile - i.e. the net_2_0
profile doesn't compile correctly at the moment.

* Using Mono assemblies under Windows

Mono assemblies are now delay-signed, i.e. they now have a public key (and
token) inside them but aren't signed.
By default the MS runtime won't accept to execute such assemblies. You can
turn off signature verification by using the (MS) sn.exe tool.

This will skip verification for all assemblies with the Mono public key.
> sn -Vr *,0738eb9f132ed756

You can view the list of skip entries using sn -Vl
and remove entries using sn -Vu

* NUnit under Windows (MS runtime)

There are also some path issues on the cygwin build that makes it hard to
"make run-test" with the MS runtime.
The easiest trick I found was to GAC (using MS gacutil.exe) the NUnit.*.dll
assemblies (which are now fully signed by Mono using the NUnit key).

> gacutil /i NUnit.Framework.dll
> gacutil /i NUnit.Util.dll

Sebastien Pouliot

More information about the Mono-devel-list mailing list