[Mono-list] mono and comercial apps.

Leandro André Zis lezis@st.com.br
Wed, 24 Mar 2004 17:52:13 -0300


This is a multi-part message in MIME format.
--------------020707070108030309090709
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

J# requires one aditional framework compatible with java

Ben Maurer wrote:

>Hello,
>
>I am going to adress the pratical issues you bring up. I am not sure
>about legal issues (such as licensing Windows to use the J# assemblies).
>
>On Wed, 2004-03-24 at 13:58, Wendell Nichols wrote:
>  
>
>>J#,
>>    
>>
>Assuming the J# assemblies comply to the CLI specs (which I assume, but
>have not verified, they do) they should run on Mono. However, there
>might be pathing issues, as I am not sure the J# designers were keeping
>in mind Linux. They might use "\" as the path seperator char. If this
>were the case, you might have to round trip the j# assemblies in an
>ilassembler and fix bugs. Of course, you would have to check if this
>were compliant with the EULA.
>
>One other option might be to use the ikvm (http://www.ikvm.net/) to
>simulate the java classlibs. The issue would be getting things to
>compile.
> 
>  
>
>>and comercial third party controls.
>>    
>>
>There are a few possible issues here:
>     1. Most component venders obfuscate their code. Some code
>        obfuscators emit code that does not comply to the CLI
>        specification, and is thus invalid. Some of these invalid
>        sequences are incorrectly accepted by Microsoft's jit, while our
>        jit compliantly rejects them.
>     2. I have seen many third party components that store licencing
>        information in the registry obviously this is a problem
>     3. As above, a third party component might not be built with linux
>        in mind and might hardcode the path seperator char, etc.
>
>All three issues are things that you could obviously bring up with the
>vendor.
>
>  
>
>>Is there now or will there ever be a way to run an app like this on linux mono? 
>>    
>>
>Short of the above issues, or any issues in your own code, this
>application should run on Mono. If it does not, bug reports would help
>us to help you get the application running.
>
>Good luck,
>-- Ben
>
>_______________________________________________
>Mono-list maillist  -  Mono-list@lists.ximian.com
>http://lists.ximian.com/mailman/listinfo/mono-list
>
>  
>

--------------020707070108030309090709
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body>
J# requires one aditional framework compatible with java<br>
<br>
Ben Maurer wrote:
<blockquote cite="mid1080157137.353.17.camel@Ben" type="cite">
  <pre wrap="">Hello,

I am going to adress the pratical issues you bring up. I am not sure
about legal issues (such as licensing Windows to use the J# assemblies).

On Wed, 2004-03-24 at 13:58, Wendell Nichols wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">J#,
    </pre>
  </blockquote>
  <pre wrap=""><!---->Assuming the J# assemblies comply to the CLI specs (which I assume, but
have not verified, they do) they should run on Mono. However, there
might be pathing issues, as I am not sure the J# designers were keeping
in mind Linux. They might use "\" as the path seperator char. If this
were the case, you might have to round trip the j# assemblies in an
ilassembler and fix bugs. Of course, you would have to check if this
were compliant with the EULA.

One other option might be to use the ikvm (<a class="moz-txt-link-freetext" href="http://www.ikvm.net/">http://www.ikvm.net/</a>) to
simulate the java classlibs. The issue would be getting things to
compile.
 
  </pre>
  <blockquote type="cite">
    <pre wrap="">and comercial third party controls.
    </pre>
  </blockquote>
  <pre wrap=""><!---->There are a few possible issues here:
     1. Most component venders obfuscate their code. Some code
        obfuscators emit code that does not comply to the CLI
        specification, and is thus invalid. Some of these invalid
        sequences are incorrectly accepted by Microsoft's jit, while our
        jit compliantly rejects them.
     2. I have seen many third party components that store licencing
        information in the registry obviously this is a problem
     3. As above, a third party component might not be built with linux
        in mind and might hardcode the path seperator char, etc.

All three issues are things that you could obviously bring up with the
vendor.

  </pre>
  <blockquote type="cite">
    <pre wrap="">Is there now or will there ever be a way to run an app like this on linux mono? 
    </pre>
  </blockquote>
  <pre wrap=""><!---->Short of the above issues, or any issues in your own code, this
application should run on Mono. If it does not, bug reports would help
us to help you get the application running.

Good luck,
-- Ben

_______________________________________________
Mono-list maillist  -  <a class="moz-txt-link-abbreviated" href="mailto:Mono-list@lists.ximian.com">Mono-list@lists.ximian.com</a>
<a class="moz-txt-link-freetext" href="http://lists.ximian.com/mailman/listinfo/mono-list">http://lists.ximian.com/mailman/listinfo/mono-list</a>

  </pre>
</blockquote>
</body>
</html>

--------------020707070108030309090709--