1 <a href="#basics">Basics</a><br>
2 <a href="#ximian">The Ximian Role in the Mono project</a><br>
3 <a href="#gnome">Mono and GNOME</a><br>
4 <a href="#gui">Building GUI applications with Mono</a><br>
5 <a href="#msft">Mono and Microsoft</a><br>
6 <a href="#pnpproject">Mono and the Portable.NET Project</a><br>
7 <a href="#webservices">Web Services</a><br>
8 <a href="#asp">Mono and ASP.NET</a><br>
9 <a href="#ado">Mono and ADO.NET</a><br>
10 <a href="#devel">Development Tools and Issues</a><br>
11 <a href="#java">Mono and Java</a><br>
12 <a href="#extending">Extending Mono</a><br>
13 <a href="#portability">Portability</a><br>
14 <a href="#reuse">Reusing Existing Code</a><br>
15 <a href="#gcc">Mono and GCC</a><br>
16 <a href="#performance">Performance</a><br>
17 <a href="#licensing">Licensing</a><br>
18 <a href="#patents">Patents</a><br>
19 <a href="#etc">Miscellaneous Questions</a><br>
20 <a href="#problems">Mono Common Problems</a><br>
23 href="http://www.es.gnome.org/documentacion/articulos/mono-puf/mono-puf/">Spanish
24 translation</a> is also available
29 Q: What is Mono exactly?
31 A: The Mono Project is an open development initiative sponsored by
32 Ximian that is working to develop an open source, Unix
33 version of the Microsoft .NET development platform. Its objective
34 is to enable Unix developers to build and
35 deploy cross-platform .NET Applications. The project will
36 implement various technologies developed by Microsoft that have now
37 been submitted to the ECMA for standardization.
39 Q: What is the difference between Mono and the .NET Initiative?
41 A: The ".NET Initiative" is a somewhat nebulous company-wide effort by
42 Microsoft, one part of which is a cross-platform development
43 framework. Mono is an implementation of the development framework,
44 but not an implementation of anything else related to the .NET
45 Initiative, such as Passport, software-as-a-service, or
46 corporate re-branding.
48 Q: What technologies are included in Mono?
50 A: Mono contains a number of components useful for building new
54 * A Common Language Infrastructure (CLI) virtual
55 machine that contains a class loader, Just-in-time
56 compiler, and a garbage collecting runtime.
58 * A class library that can work with any language
59 which works on the CLR.
61 * A compiler for the C# language. In the future we
62 might work on other compilers that target the Common
67 Windows has compilers that target the virtual machine from <a
68 href="http://msdn.microsoft.com/net/thirdparty/default.asp#lang">a
69 number of languages:</a> Managed C++, Java Script, Eiffel,
70 Component Pascal, APL, Cobol, Perl, Python, Scheme,
71 Smalltalk, Standard ML, Haskell, Mercury and Oberon.
73 The CLR and the Common Type System (CTS) enables applications and
74 libraries to be written in a collection of different languages that
77 This means for example that if you define a class to do algebraic
78 manipulation in C#, that class can be reused from any other
79 language that supports the CLI. You could create a class in C#,
80 subclass it in C++ and instantiate it in an Eiffel program.
82 A single object system, threading system, class libraries, and
83 garbage collection system can be shared across all these languages.
85 Q: Where can I find the specification for these technologies?
87 A: You can find the work-in-progress documentation from the T3G ECMA
90 <a href="http://www.dotnetexperts.com">http://www.dotnetexperts.com</a>
92 Q: Will you implement the .NET Framework SDK class libraries?
94 A: Yes, we will be implementing the APIs of the .NET Framework SDK
97 Q: Will you offer an ECMA-compliant set of class libraries?
99 A: Eventually we will. Our current focus is on inter-operating
100 with the Microsoft SDK, but we will also offer an ECMA compliant
103 Q: What does the name "Mono" mean?
105 A: Mono is the word for `monkey' in Spanish. We like monkeys.
109 A: The JIT engine is usable on Intel x86 machines. An interpreter
110 can be used on other non-Intel x86 machines.
112 The class libraries are mature enough to run some real applications
113 (the compiler for instance, and every day more and more applications
114 are natively developed with Mono).
116 Q: When will you ship it?
118 A: Different parts of Mono will achieve usability at different stages,
119 once we are comfortable with the compiler, we will release "Mono Core",
120 which contains everything needed to develop applications with the base
121 class libraries. This should be available at some point during 2002.
123 Other higher level class libraries (ASP.NET, ADO.NET) will
124 be released when they become stable.
126 Q: What major components will you include in Mono?
128 A: Hopefully everything that Microsoft ships on their Framework
129 (ADO.NET, ASP.NET), and
130 we encourage third party developers to create reusable components that
131 work on both Mono and Windows.
133 Q: How can I contribute?
135 A: Check the <a href="contributing.html">contributing</a> section.
137 Q: Aren't you just copying someone else's work?
139 A: We are interested in providing the best tools for programmers to
140 develop applications for Free Operating Systems. We also want to help
141 provide the interoperability that will allow those systems to fit in
142 with other standards.
144 For more background, read the <a href="http://www.go-mono.com/rationale.html">Mono
145 Project white paper</a>.
148 Q: Miguel said once that Mono was being implemented in COBOL. Is that true?.
150 A: No. It was a joke.
153 <a name="ximian"></a>
155 ** The Ximian Role in the Mono Project
157 Q: Why is Ximian working on .NET?
159 A: Ximian is interested in providing the best tools for programmers to
160 develop applications for Free Operating Systems.
162 For more information, read the project <a
163 href="rationale.html">rationale</a> page.
165 Q: Will Ximian be able to take on a project of this size?
167 A: Of course not. Ximian a supporter of the Mono project, but the only way
168 to implement something of this size is for the entire free software
169 community to get involved. Visit the <a href="contributing.html">contributing</a>
170 page if you'd like to help out.
172 Q: What pieces will Ximian be working on?
174 A: We will devote most of our resources to work on the pieces which are
175 on the critical path to release a development and execution
176 environment. Once the project is at a stage where it is useful in
177 the real world, it will achieve a critical mass of developers to
180 Q: Will Ximian offer Mono commercially?
182 A: When Mono is ready to be shipped Ximian will offer a commercial
183 support and services for Mono.
185 Q: Does Ximian provide consulting services around Mono?
187 A: Yes, Ximian does provide consulting services around Mono to
188 make it suitable to your needs. Porting the runtime engine,
189 customizing it, working on specific classes or tuning the code
190 for your particular needs.
192 Q: Will you wait until Mono is finished?
194 A: Mono will ship on various stages as they mature. Some people
195 require only a subset of the technologies, those will ship first.
197 More advanced features will take more time to develop. A support
198 time line will be available in June 2002.
203 Q: How is Mono related to GNOME?
205 A: In a number of ways. This project was born out of the need of
206 providing improved tools for the GNOME community, and will use
207 existing components that have been developed for GNOME when they
208 are available. For example, we plan to use Gtk+ and Libart to
209 implement Winforms and the Drawing2D API and are considering
212 Q: Has the GNOME Foundation or the GNOME team adopted Mono?
214 A: Mono is too new to be adopted by those groups. We hope that the
215 tools that we will provide will be adopted by free software
216 programmers including the GNOME Foundation members and the GNOME
219 Q: Should GNOME programmers switch over to Mono now?
221 A: It is still far to early for discussions of "switching over." No
222 pieces of Mono will be ready within the next six months, and a
223 complete implementation is roughly one year away.
225 We encourage GNOME developers to continue using the existing tools,
226 libraries and components. Improvements made to GNOME will have an
227 impact on Mono, as they would be the "back-end" for various classes.
229 Q: Will Mono include compatibility with Bonobo components? What is the
230 relationship between Mono and Bonobo?
232 A: Yes, we will provide a set of classes for implementing and using
233 Bonobo components from within Mono. Mono should allow you to write
234 Bonobo components more easily, just like .NET on Windows allows you
235 to export .NET components to COM.
237 Q: Does Mono depend on GNOME?
239 A: No, Mono does not depend on GNOME. We use a few packages produced by
240 the GNOME team like the `glib' library.
242 Q: But will I be able to build GNOME applications?
244 A: Yes, we will enable people to write GNOME applications using Mono.
246 Q: Do you have C# bindings for GNOME?.
248 A: Yes, we currently bind libgnome, libgnomecanvas, and libgnomeui --
249 although I dare say I have no idea how functional the bindings are
250 outside of what I tested in the sample app. I imagine other libraries
251 under the GNOME framework will be added on an as-needed (and as-requested)
252 basis...although a truly good bonobo binding will have to wait on the CORBA
253 remoting support which has been started recently.
258 Q: Will Mono enable GUI applications to be authored?
260 A: Yes, you will be able to build GUI applications. Indeed, that is our
261 main focus. We will provide both the Windows.Forms API and the Gtk# API.
263 Q: What is the difference between Gtk# and System.Windows.Forms?
265 A: Gtk# is a set of bindings for the Gtk+ toolkit for C# (and other
266 CIL-enabled languages). System.Windows.Forms is an API defined
267 by Microsoft to build GUI applications.
269 Q: Will I be able to run my smart clients on systems powered by Mono?
271 A: As long as your applications are 100% .NET and do not make use
272 of P/Invoke to call Win32 functions, your smart client applications
273 will run on Mono platforms.
275 Q: Where can I learn more about Gtk#?
277 A: The following <a href="http://gtk-sharp.sourceforge.net>link</a> sends you to the page of the project.
279 Q: What can I do with Gtk#?.
281 A: Gtk# is becoming very usable and you can create applications and
282 applets like those you see in a GNOME desktop environment. It's
283 easy to install so it's worth a try.
285 Q: How can I compile my HelloWorld.cs which uses Gtk#?.
287 A: Try: mcs --unsafe -o HelloWorld.exe -r glib-sharp -r pango-sharp -r
288 atk-sharp -r gdk-sharp -r gtk-sharp -r gdk-imaging-sharp
291 Q: Is there any way how to connect DataAdapter to some GTK# controls?
293 A: There is a sample file called `DbClient' in gtk-sharp/samples that you
294 might to look at. It is a sample program in Gtk# that adds/updates/deletes
295 information on a Postgress database. When we have the new table/tree widgets,
296 I am sure someone would write an adapter for System.Data (in Gtk2 the
297 tree/list widgets are written using a view/model, so you only need to write
298 a model that maps to the database). You can have a look at
299 gtk-sharp/sample/DbClient, where there is a GTK# application that uses
300 System.Data. It does not use DataAdapter, but DataReader though.
302 Q: Do you have an estimate for when Windows.Forms will be released?
304 A: We do not know, volunteers are working on this, but there is no set
305 date yet. The current approach is using the Wine Library to implement
309 ** Mono and Microsoft
311 Q: Is Microsoft helping Ximian with this project?
313 A: No. Ximian CTO Miguel de Icaza had a friendly conversation with
314 Microsoft software architect David Stutz, but that's about the
315 extent of the contact. Microsoft is interested in other
316 implementations of .NET and are willing to help make the ECMA spec
317 more accurate for this purpose.
319 Ximian representatives have also spoken with Sam Ruby at the ECMA
320 TG3 committee to discuss the same issues.
322 Q: Is Microsoft or Corel paying Ximian to do this?
326 Q: Do you fear that Microsoft will change the spec and render Mono
329 A: No. Microsoft proved with the CLI and the C# language that it was
330 possible to create a powerful foundation for many languages to
331 inter-operate. We will always have that.
333 Even if changes happened in the platform which were undocumented,
334 the existing platform would a value on its own.
336 Q: Are you writing Mono from the ECMA specs?
338 A: Yes, we are writing them from the ECMA specs and the published
339 materials in print about .NET.
341 Q: If my applications use Mono, will I have to pay a service fee?
343 A: No. Mono is not related to Microsoft's initiative of
344 software-as-a-service.
346 Q: Is the Mono Project is related to the Microsoft Hailstorm effort? Is
347 Ximian endorsing Hailstorm?
349 A: No. The Mono Project is focused on providing a compatible set of
350 tools for the Microsoft .NET development platform. It does not
351 address, require, or otherwise endorse the MS Passport-based
352 Hailstorm single sign-on system that is part of Windows XP and
355 Q: Will Mono or .NET applications depend on Microsoft Passport?
357 A: No. MS Passport is unrelated to running .NET compatible applications
358 produced with the Mono tools. The only thing you will need is a
359 just-in-time compiler (JIT).
361 Q: What is a 100% .NET application?
363 A: A `100% .NET application' is one that only uses the APIs defined
364 under the System namespace and does not use PInvoke. These
365 applications would in theory run unmodified on Windows, Linux,
366 HP-UX, Solaris, MacOS X and others.
368 Q: If Microsoft will release a port of their .NET platform under the
369 `Shared Source' license, why should I bother with anything else?
371 A: The Shared Source implementation will be expensive and its uses
372 will be tightly restricted, especially for commercial use. We are
373 working towards an implementation that will grant a number of
374 important rights to recipients: use for any purpose,
375 redistribution, modification, and redistribution of modifications.
377 This is what we call <a
378 href="http://www.gnu.org/philosophy/free-sw.html">Free Software</a>
380 Q: Is Mono a free implementation of Passport?
382 A: No. Mono is just a runtime, a compiler and a set of class
385 Q: Will the System.Web.Security.PassportIdentity class mean
386 that my software will depend on Passport?
388 A: No. Applications may use that API to contact a Passport site, but
389 are not required to do so.
391 As long as your application does not use Passport, you will not
394 Q: Will Mono running on Linux make Passport available for Linux?
396 A: No. However, the Passport toolkit for Linux-based web servers is
397 available from Microsoft.
399 Q: Will Mono allow me to run Microsoft Office on Linux?
401 A: No, it will not. Microsoft Office is a Windows application. To
402 learn more about running Windows applications on Intel Unix systems
403 refer to <a href="http://www.winehq.com">the Wine Project</a>.
405 Q: Will I be able to compile a Microsoft VB.NET application and execute
406 the resultant MSIL file under MONO on Linux without converting to C#
409 A: Once we have a complete VisualBasic runtime, yes.
411 Q: Can mono run the WebMatrix?
413 A: No. That requires System.Windows.Forms support which is not
414 currently implemented.
416 Q: Does mono have something like Passport?
417 Will mono have a server side Passport/Similar framework for XSP as well as client classes?
419 A: Not yet, but the client side API for authentication is not the problem.
420 We will likely have a lot of other authentication APIs, like the Liberty
421 Alliance APIs. The problem is people on the web provider end that might use
422 this for authentication.
424 <a name="pnpproject"></a>
425 ** Mono and Portable.NET
427 Q: What are the differences between Mono and Portable.NET?
429 A: Most of Mono is being written using C#, with only
430 a few parts written in C (The JIT engine, the runtime, the
431 interfaces to the garbage collection system).
433 It is easier to describe what is unique about Mono:
435 <li> A self-hosting C# compiler written in C#, which is clean, easy
438 <li> A multi-platform runtime engine: both a JIT engine and an
439 interpreter exist. The JIT engine runs currently on x86
440 systems, while the interpreter works on SPARC, StrongARM and
443 <li> Supports Linux, Windows and Solaris at this point.
445 <li> The JIT engine is written using a portable instruction
446 selector which not only generates good code (we are told
447 that we are faster than Rotor, but it is hard to tell) but
448 is also the foundation to re-target the JIT engine to other
451 The system employed is described in various compiler
452 books and it is very similar to what is described in the
453 book that covers LCC, the ANSI C retargetable C compiler.
455 <li> The JIT engine supports in-lining, constant folding and propagation,
457 <li> Full support for remoting in the runtime, but the class
458 libraries are still behind.
460 <li> The C# compiler, the JIT engine and the class libraries are
461 mature enough that the whole system is self-hosting. This means that
462 we develop Mono completely with itself at this point.
464 <li> We are not yet done, and there is a lot of work left to be
467 <li> We have a great community of developers, without which Mono
468 would not be possible.
470 <li> We will provide an ahead of time compilation mode in the
474 <a name="webservices"></a>
477 Q: How is Mono related to Web Services?
479 A: Mono is only related to Web Services in that it will implement the
480 same set of classes that have been authored in the .NET Framework
481 to simplify and streamline the process of building Web Services.
483 But most importantly, Mono is an Open Source implementation of the
486 Q: Can I author Web Services with Mono?
488 A: You will be able to write Web Services on .NET that run on Mono and
491 Q: If Mono implements the SDK classes, will I be able to write and
492 execute .NET Web Services with it?
494 A: Yes. When the project is finished, you will be able to use the
495 same technologies that are available through the .NET Framework SDK
496 on Windows to write Web Services.
498 Q: What about Soup? Can I use Soup without Mono?
500 A: Soup is a library for GNOME applications to create SOAP servers and
501 SOAP clients, and can be used without Mono. You can browse the
502 source code for soup using <a
503 href="http://cvs.gnome.org/bonsai">GNOME's Bonsai</a>.
507 A: Yes. The CLI contains enough information about a class that
508 exposing it to other RPC systems (like CORBA) is really simple, and
509 does not even require support from an object.
511 We will be implementing CORBA inter-operation as an extension to the
512 Mono classes so that we can integrate with Bonobo, just like
513 Microsoft provides COM inter-operation classes and support
516 Q: Can I serialize my objects to other things other than XML?
518 A: Yes, although the serializing tools have not yet been planned, and
519 you would probably have to implement them yourself.
521 Q: Will Mono use ORBit?
523 A: No. Mono will be using a new implementation of CORBA that isn't still started.
526 ** Development Tools and Issues
528 Q: Will it be possible to use the CLI features without using byte codes
531 A: Yes. The CLI engine will be made available as a shared library.
532 The garbage collection engine, the threading abstraction, the
533 object system, the dynamic type code system and the JIT will be
534 available for C developers to integrate with their applications if
537 Q: Will you have new development tools?
539 A: With any luck, Free Software enthusiasts will contribute tools to
540 improve the developer environment. These tools could be developed
541 initially using the Microsoft implementation of the CLI and then
542 executed later with Mono.
544 Q: What kind of rules make the Common Intermediate Language useful for
547 A: The main rule is that the stack in the CLI is not a general purpose
548 stack. You are not allowed to use it for other purposes than
549 computing values and passing arguments to functions or return
552 At any given call or return instruction, the types on the stack
553 have to be the same independently of the flow of execution of your
556 Q: Is it true that the CIL is ideal for JITing and not efficient for
559 A: The CIL is better suited to be JITed than JVM byte codes, but you
560 can interpret them as trivially as you can interpret JVM byte
563 Q: Isn't it a little bit confusing to have the name of "XSP" (the same
564 as in the Apache Project) for the ASP.NET support in Mono?.
566 A: In Mono, xsp is just the name of the C# code generator for ASP.NET
567 pages. In the Apache Project, it is a term for the "eXtensible Server
568 Pages" technology so as they are very different things, they don't
571 Q: What about using something like Jabber instead of the System.Messaging
574 A: In short, MSMQ is not something like Jabber, but asynchronous messaging
575 through queues. Useful queues do more than serialize messages, they are
576 also platform bridges.
578 Q: Are you supporting XMLDocument and relatives?.
580 A: Currently, we aren't implementing them yet. It would require updates to
581 most of the XmlNode derivatives so it's not a trivial task. We are
582 currently focusing on getting XPath support working.
584 Q: Is there any plan to develop an aspx server for Mono?.
586 A: The web server turned out to be very simple compared to the rest of the
587 work. Gonzalo has got the page generator mostly done (a module called
588 xsp, who has nothing to do with the XSP term used in the Apache Project).
589 Patrik has done a lot of the work to get the ProcessRequest to work.
590 You can try to help in the final touches to the System.Web classes and
591 writing regression tests for the widgets we have.
593 Q: Is there any way I can develop the class libraries using Linux yet?
595 A: Yes. Some class libraries can be developed on Linux. Search for
596 Paolo's post (he lists which classes can be compiled fine now).
598 Q: Is there any way I can install a known working copy of mono in /usr,
599 and an experimental copy somewhere else, and have both copies use
600 their own libraries? (I'm still not very good at library paths in
603 A: Yes. Just use two installation prefixes.
605 Q: How should I write tests or a tests suite?
607 A: If you do a test suite for C#, you might want to keep it
608 independent of the Mono C# compiler, so that other compiler
609 implementations can later use it.
611 Q: Would it be too terrible to have another corlib signed as mscorlib?
613 A: We rename corlib to mscorlib also when saving the PE files, in fact,
614 the runtime can execute program created by mono just fine.
616 Q: Is there a relatively straightforward way to repeat the steps taken
617 by Paolo to get Mono completely self-hosted on Linux?
619 A: To build the compiler and class libraries in Linux, run:
620 <ul><li>make -f makefile.gnu. To install them, run: </li>
621 <li>make -f makefile.gnu install prefix=/opt/mono</li>
624 If you want to produce and distribute a monocharge tarball, run:
625 make -f makefile.gnu dist
626 Of course you have to run these in the top level mcs directory.
628 Q: Is it possible to build a C# file to some sort of intermediate format which
629 can linked into a final module, like the traditional .c -> .o -> .so path?
631 A: You could do: mcs /target:module file1.cs, mcs /target:module file2.cs,
632 mcs /target:exe file1.dll file2.dll /out:mybin.exe
634 Q: Is there any plans for implementing remoting in the near future?, When will
635 work in System.Runtime.Remoting.dll start?
637 A: The remoting infrastructure is in place. Some of the channels and
640 Q: I'm wondering if there are any plans to start using nant to build the
641 class lib + test lib. i think that every project need/should use an
642 automated build process and nant + a couple of tools enables this. is
643 the problem that the compiler can't run nant yet?
645 A: Maybe well be doing some sort of automated build process + testing when
651 Q: Is Mono supporting ASP.NET?
653 A: Yes. The development of the support for ASP.NET comes in various stages,
654 here is what Gonzalo has been working on: 1. The Parser. 2. Getting the
655 parser to generate output compatible with ASP.NET. 3. Running the sample
656 output with the real Microsoft runtime but using our generated page. 4.
657 Running the sample with our classes with the .NET runtime. 5. Running
658 our sample code with our classes with our runtime. This is the process
659 we are following. Currently Gonzalo has reached point 5.
661 Q: Do I need install cygwin to work on ASP.NET in mono or Linux is enough since
662 it is self host right now.
666 Q: Any plan to make ASP.NET in mono works with Apache in Linux?.
668 A: Yes, we have plans to do so, but we need to wait for Patrik's patches to
669 HttpRuntime. Once that is there, writing a mod_mono should be trivial
670 (look at mono/samples/embed for a sample embedded application).
675 Q: What is the status of ADO.NET support?. Could I start migrating
676 applications from MS.NET to Mono?.
678 A: You could start right now using the ADO.NET support in mono, of course,
679 if you want to help filling the missing gaps while you develop your app
680 :-) Well, what I mean is that we're not that far to having full ADO.NET
681 support in Mono, and we've got a lot of working things, so if we could
682 get more help, we'd finish it really soon :-)
684 Q: In developing the data architecture for the application are there and
685 objects I should stay away from in order to insure the smoothest possible
686 transition (minimum code rewrite) to Mono's ADO.NET implementation? (For
687 example, strongly typed datasets versus untyped datasets, etc...)
689 A: We are implementing all the classes in Microsoft .NET's System.Data, so
690 you can be sure that things will work the same in Mono as with the Microsoft
696 Q: Why don't you use Java? After all, there are many languages that
699 A: You can get very good tools for doing Java development on free
700 systems right now. <a href="http://www.redhat.com">Red Hat</a> has
701 contributed a <a href="http://gcc.gnu.org">GCC</a> <a
702 href="http://gcc.gnu.org/java">front-end for Java</a> that can take
703 Java sources or Java byte codes and generate native executables; <a
704 href="http://www.transvirtual.com">Transvirtual</a> has implemented
705 <a href="http://www.kaffe.org">Kaffe</a> a JIT engine for Java;
706 Intel also has a Java VM called <a
707 href="http://www.intel.com/research/mrl/orp">ORP</a>.
709 The JVM is not designed to be a general purpose virtual machine.
710 The Common Intermediate Language (CIL), on the other hand, is
711 designed to be a target for a
712 wide variety of programming languages, and has a set of rules
713 designed to be optimal for JITers.
715 Q: Could Java target the CLI?
717 A: Yes, Java could target the CLI. We have details on a <a
718 href="ideas.html#guavac">project</a> that someone could take on to
721 Microsoft has an implementation of the Java language called J# that
722 can target the CIL execution engine.
724 Q: Is it possible to write a JVM byte code to CIL converter?
726 A: Yes, it is possible. Here are a few starting point:
729 * A byte code representation is really a flattened forest of
730 trees. Look at the Mono JIT engine to see how we compute
731 the basic blocks (this is used to figure out the "trees").
733 The forest is just an array of trees.
735 Indeed, run the JIT engine with -d (mono -d prog.exe) and
736 you will see how these trees look like.
738 You will have to do something similar for Java.
740 * Each "forest of trees" has a meaning. This meaning can now
741 be translated into the equivalent "meaning" in CLR-land.
744 Q: Could mono become a hybrid CIL/java platform?
746 A: No. It is quite far from the philosophy of the project. The idea of Mono
747 is, to have only _one_ VM, on which all can run. And if there existing a
748 binary-converter from Java-.class to IL and if there existing something
749 like J-Sharp on Mono, you can write programs in Java, which than can run
750 on Mono. You do not need two bindings (like your example: GTK-Sharp _and_
751 Java-Gnome). You need only _one_ of it (GTK-Sharp). Thats the idea of Mono.
752 An other point is, that there are no people, who use Open Source-JVMs. They
753 all prefer Suns original. But for Unix there don't exist a .NET-Framework.
754 So it is possible, that in the future Mono is the standard .NET for Unixes.
756 Q: Do you plan to implement a Javascript compiler?
758 A: Yes. Eto Demerzal has started a Rhino port to C#.
759 After this is completed, we will begin developing
760 the JavaScript compiler.
762 <a name="extending"></a>
765 Q: Would you allow other classes other than those in the
768 A: Yes. The Microsoft class collection is very big, but it is by no
769 means complete. It would be nice to have a port of `Camel' (the
770 Mail API used by Evolution inspired by Java Mail) for Mono
773 You might also want to look into implementing CORBA for Mono. Not
774 only because it would be useful, but because it sounds like a fun
775 thing to do, given the fact that the CLI is such a type rich
778 For more information on extending Mono, see our <a
779 href="ideas.html">ideas</a> page.
781 Q: Do you plan to Embrace and Extend .NET?
783 A: Embracing a good technology is good. Extending technologies in
784 incompatible ways is bad for the users, so we do not plan on
785 extending the technologies.
787 If you have innovative ideas, and want to create new classes, we
788 encourage you to make those classes operate correctly well in both
791 Q: Is there any way I can develop the class libraries using Linux yet?
793 A: Yes. Some class libraries can be developed on Linux. Search for
794 Paolo's post (he lists which classes can be compiled fine now).
796 Q: Is there any way I can install a known working copy of mono in /usr,
797 and an experimental copy somewhere else, and have both copies use
798 their own libraries? (I'm still not very good at library paths in
801 A: Yes. Just use two installation prefixes.
804 <a name="portability"></a>
807 Q: Will Mono only work on Linux?
809 A: Currently, we are doing our work on Linux-based systems and
810 Windows. We do not expect many Linux-isms in the code, so it
811 should be easy to port Mono to other UNIX variants.
813 Q: What about Mono on non Linux-based systems?
815 A: Our main intention at Ximian is to be able to develop GNOME
816 applications with Mono, but if you are interested in providing a
817 port of the Winforms classes to other platforms (frame buffer or
818 MacOS X for example), we would gladly integrate them, as long
819 they are under an open source license.
821 Q: What operating systems/CPUs do you support
823 A: Mono currently runs on Linux, Windows, Solaris and FreeBSD.
824 There is a JIT engine available for x86 processors that can
825 generate code and optimizations tailored for a particular CPU.
827 Interpreters exist for the SPARC, PowerPC and StrongARM CPUs.
829 Q: Does Mono run on Windows?
831 A: Yes. You can get pre-compiled
832 binaries from <a href="http://www.go-mono.com/download.html">http://www.go-mono.com/download.html</a>
834 Q: Does Mono run on Linux?
836 A: Yes. You can get pre-compiled
837 binaries from <a href="http://www.go-mono.com/download.html">http://www.go-mono.com/download.html</a>
839 Q: Will I require Cygwin to run mono?
841 A: No. Cygwin is only required to build Mono.
843 Q: Will Mono depend on GNOME?
845 A: It will depend only if you are using a particular assembly (for
846 example, for doing GUI applications). If you are just interested
847 in Mono for implementing a `Hello World Enterprise P2P Web
848 Service', you will not need any GNOME components.
850 Q: Is anyone working on porting Mono to IA-64?
852 A: Nobody is working on such port.
854 Q: If I were about to start a Mono port to IA-64,would the same lburg code
855 generator work for IA-64 also? or anything else need to be used for code
856 generation(as the processor architecture is totally different from IA32)
858 A: The lburg approach can be use for any processor architecture. But you might
859 think in another better approach.
861 Q: Do you plan to port Rhino to C#?.
863 A: Eto Demerzal has started a Rhino port to C#.
865 Q: Has anyone succeeded in building a Mac version of the C# environment.
866 If so can you explain how?
868 A: You could try to check with the Darwin people, or the Fink people.
869 Mono/C# is self hosting on Linux/PPC which is the hard part, so it
870 should be relatively simple to get it to work on MacOS
873 ** Reusing Existing Code
875 Q: What projects will you reuse or build upon?
877 A: We want to get Mono in the hands of programmers soon. We are
878 interested in reusing existing open source software.
880 Q: What about Intel's research JIT framework, ORP?
882 A: At this time, we are investigating whether we can use elements of
883 ORP for Mono. ORP is a research JIT engine that has a clearly
884 defined API that splits the JIT from the GC system and the actual
885 byte code implementation.
887 We are using some pieces of ORP (Their code generation interface)
888 and we use it as a source of inspiration for optimizations. Paolo
889 and Dietmar consider ORP as being one of the best JIT engines out
890 there (and their research work and papers are very useful if you are
891 interested in JIT technology).
893 Q: What about using GNU Lightning?
895 A: We are not using GNU Lightning. Our JIT is using an instruction
896 selector based on tree-pattern matching, and a code generation
897 interface that is very tied to the current architecture.
899 Q: Will I be able to use Microsoft SQL Server 2000 or will I need to switch
900 to a specific Open Source Database. Will I need to recode?
902 A: There should not be any need to recode.
904 Q: What do I need to watch out for when programming in VB.NET so that I'm
905 sure to be able to run those apps on Linux?
907 A: Not making any PInvoke or DLL calls should and not using anything in
908 the Microsoft.* namespaces should suffice. Also do not use any
909 Methods/Classes marked as "This type/method supports the .NET Framework
910 infrastructure and is not intended to be used directly from your code."
911 even if you know what these classes/methods do.
913 Q: Will built-in reporting be supported for crystal reports? This is a
914 heavily used part of our system.
916 A: Probably not. Crystal Reports are propriety. Someone may try to emulate
917 the behavior, but no-one has yet volunteered.
919 Q: Who about writing to the registry? As I understand it, Linux does not have
920 a counterpart to the registry. Should I avoid relying on that feature?
922 A: Try to avoid it. Although there would be a emulation for registry in
923 Mono too. GNOME does have a registry like mechanism for configuration. But
924 Even if gnome has a configuration system similar to the registry, the keys
925 will not be equal, so you will probably end up having to do some runtime
926 detection, and depending on this load an assembly that has your
927 platform-specific hacks.
929 Q: System.Data.SqlClient with FreeTDS, will you port parts of these to C# and
932 A: if their license is compatible with mono's, yes, we'd think about porting
933 them. If not, we'll continue with the plan of using FreeTDS.
938 Q: Are you working on a GCC front-end to C#? A GCC back-end that will
939 generate CIL images? What about making a front-end to GCC that
940 takes CIL images and generates native code?
942 A: We are currently seeking volunteers for those projects.
943 Visit the <a href="contributing.html">contributing</a> section if
946 Q: But would this work around the GPL in the GCC compiler and allow
947 people to work on non-free front-ends?
949 A: People can already do this by targeting the JVM byte codes (there
950 are about 130 compilers for various languages that target the JVM).
952 Q: Why are you writing a JIT engine instead of a front-end to GCC?
954 A: We want the JIT engine and runtime engine because they will be able
955 to execute CIL executables generated on Windows, and so no recompilation
958 <a name="performance"></a>
961 Q: How fast will Mono be?
963 A: We can not predict the future, but a conservative estimate is that
964 it would be at least `as fast as other JIT engines'.
966 We would like to ship various JIT engines with Mono, just like
967 Microsoft has done with their .NET development platform. We could
968 provide a faster, JIT for fast load times but lower performance,
969 and an and an optimizing JIT that would be slower at generating
970 code but produce more optimal output.
972 The CIL has some advantages over the Java byte code: it is really
973 an intermediate representation and there are a number of
974 restrictions on how you can emit CIL code that simplify creating
977 For example, on the CIL, the stack is not really an abstraction
978 available for the code generator to use at will. Rather, it is a
979 way of creating a postfix representation of the parsed tree. At
980 any given call point or return point, the contents of the stack are
981 expected to contain the same object types independently of how the
982 instruction was reached.
984 <a name="licensing"></a>
987 Q: Will I be able to write proprietary applications that run with
990 A: Yes. The licensing scheme is planned to allow proprietary
991 developers to write applications with Mono.
993 Q: What license or licenses are you using for the Mono Project?
995 A: The C# Compiler is released under the terms of the <a
996 href="http://www.opensource.org/licenses/gpl-license.html">GNU GPL</a>. The runtime
997 libraries are under the <a
998 href="http://www.opensource.org/licenses/lgpl-license.html">GNU
999 Library GPL</a>. And the class libraries are released
1000 under the terms of the <a
1001 href="http://www.opensource.org/licenses/mit-license.html">MIT X11</a>
1004 The Mono runtime and the Mono C# Compiler are also available under
1005 a proprietary license for those who can not use the LGPL and the
1008 For licensing details, contact <a
1009 href="mailto:mono-licensing@ximian.com">mono-licensing@ximian.com</a>
1012 Q: I would like to contribute code to Mono under a particular
1013 license. What licenses will you accept?
1015 A: We will have to evaluate the licenses for compatibility first,
1016 but as a general rule, we will accept the code under the same
1017 terms of the "container" module.
1022 <a name="patents"></a>
1025 Q: Could patents be used to completely disable Mono (either submarine
1026 patents filed now, or changes made by Microsoft specifically to
1027 create patent problems)?
1029 A: No. First, its basic functional capabilities have pre-existed too
1030 long to be held up by patents. The basic components of Mono are
1031 technologically equivalent to Sun's Java technology, which has been
1034 Mono will also implement multi-language and
1035 multi-architecture support, but there are previous technologies
1036 such as UCSD p-code and ANDF that also support multiple languages
1037 using a common intermediate language. The libraries are similar
1038 to other language's libraries, so again, they're too similar to
1039 be patentable in large measure.
1041 However, if Microsoft does patent some technology, then our plan is
1042 to either (1) work around it, (2) chop out patented pieces, (3)
1043 find prior art that would render the patent useless.
1045 Not providing a patented capability would weaken the
1046 interoperability, but it would still provide the free software /
1047 open source software community with good development tools, which
1048 is the primary reason for developing Mono.
1051 ** Miscellaneous Questions
1053 Q: You say that the CLI allows multiple languages to execute on the
1054 same environment. Isn't this the purpose of CORBA?
1056 A: The key difference between CORBA (and COM) and the CLI is that the
1057 CLI allows "data-level interoperability" because every
1058 language/component uses the same data layout and memory management.
1060 This means you can operate directly upon the data types that someone
1061 else provides, without having to go via their interfaces. It also
1062 means you don't have to "marshal" (convert) parameters (data
1063 layouts are the same, so you can just pass components directly) and
1064 you don't have to worry about memory management, because all
1065 languages/components share the same garbage collector and address
1066 space. This means much less copying and no need for reference
1069 Q: Will you support COM?
1071 A: The runtime will support XPCOM on Unix systems and COM on Windows.
1072 Most of the code for dynamic trampolines exists already.
1074 Q: Will Ximian offer certifications on Mono or related technologies?.
1076 A: It's possible. But there is no plan about this. So the short answer is no.
1078 Q: Are there any Boehm's GC binaries?
1080 A: Yes. You can find RPMs <a href="http://java.thn.htu.se/~toor/">here</a>, though
1081 if your distribution provides the correct packages, you should use those.
1082 The suggested version of the Boehm GC is 6.1.
1084 Q: How can I report a bug?
1086 A: The best thing is to track down the bug and provide a simple test to
1087 reproduce the bug. You can then add the bug to the
1088 <a href="http://bugzilla.ximian.com/enter_bug.cgi">bugtracking system</a>.
1090 Please provide information about what version of mono you're using
1091 and any relevant details to be able to reproduce the bug. Note that
1092 bugs reported on the mailing-list may be easily forgotten, so it's
1093 better to file them in the <a href="http://bugzilla.ximian.com/enter_bug.cgi">bug tracking system</a>.
1095 Q: Does mcs support the same command line options as the MS C#
1098 A: The Mono C# compiler now supports the same command line
1099 arguments as the Microsoft C# compiler does.
1101 Q: How about getting searchable archives on lists.ximian.com?
1103 A: You can perform a search on the mono-related mailing lists
1104 <a href="http://www.go-mono.com/mailing-lists.html">here</a>.
1106 Q: When using mono from cvs or from a snapshot, I get an error messaage
1107 saying that Mono and the runtime are out of sync. How do I fix that?
1109 A: If you use mono from cvs, you need to be prepared for changes in the
1110 runtime internals. This means that you should keep a working setup
1111 before blindling updating (a working setup may just be the last released
1112 tarball or a recent binary snapshot).
1113 Usually, compiling corlib with mcs before recompiling the C runtime does
1114 the right thing (but occasionally you may need to do it the other
1119 <a name="problems"></a>
1120 ** Mono Common Problems
1122 If you are having problems compiling or running Mono software
1123 or if you think that you found a bug, etc. Please visit the
1124 <a href="http://geneura.ugr.es/~jaime/deploy/mono-common-problems.html">Mono Common Problems</a> document and try there.