<html> <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 11 (filtered)"> <style>  </style> </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> If you have tried to compile Mercury with the –il option using .NET 2.0 you will eventually get to the following problem noted in the dev mailing list. <a href="http://www.cs.mu.oz.au/research/mercury/mailing-lists/mercury-developers/mercury-developers.200605/0005.html" title="http://www.cs.mu.oz.au/research/mercury/mailing-lists/mercury-developers/mercury-developers.200605/0005.html">Mercury on .NET 2 and Mono </a> With help from Jonathan Morgan, I have been able to get a stripped down version of dir__csharp_code.cs to compile. The step at which dir__csharp_code.cs is compiled is what causes the errors noted above. The errors were cause by the modules being referenced as assemblies. Once the IL code was changed in a sandbox version that recreated the errors, dir__csharp_code.cs compiled. Now that the signature of the problem is known, I will work toward fixing the code for the compiler, but as I only built Mercury for the first time a week ago, I have a lot of catching up. Attached is a diff between the sandboxed Mercury code and valid code that shows the specific changes. If you are working on getting Mercury to build with –il using .NET 2.0, I would be interested in working together. I am in New Jersey, USA, so for those of you in Australia, it will be interesting. Eric </div> </body> </html>