[Mono-dev] Getting Started

Miguel Mudge michael.mudge at welchallyn.com
Fri May 18 15:07:17 UTC 2012


No problem, I love the enthusiasm.  I couldn't tell you how to get involved
in the Mono project - someone else will point you in the right direction.

There is no way to know what Microsoft will do and if they really feel that
their toes are being stepped on, but Mono has a lot going for it.
 Microsoft has developed and published the CLR under the Microsoft
Community Promise.  I think this basically means that Mono's core CLR
implementation is safe.  Microsoft has even provided Mono some guidance and
clarification on the details of the standard.  The legal safety of the
libraries outside of the core framework are not quite as clear - Microsoft
has not stated any "opinion" on Mono's capabilities, but they've had plenty
of time to act.  If Microsoft pulls the rug out from under Mono, I think
people may choose against Visual Studio in favor of Java due to portability
issues, and Microsoft doesn't want that.  If Oracle loses their case
against Google, it may suggest that all of Microsoft's public-facing
interfaces can legally be reimplemented.  If Oracle wins, Google might take
a serious look at the Mono framework as an alternative.  (this is so very
exciting!)  There's more information here:
http://en.wikipedia.org/wiki/Mono_(software)#Mono_and_Microsoft.27s_patents

Yes, Mono's assemblies are all written in C#.  They compile using Mono's C#
compiler, but I have been able to compile them under Visual Studio too
(that takes a bit of organizing).  At the "bottom" of those framework
libraries are internal and P/Invoke calls that bridge the core
functionality with native functions.

Before you get too far ahead of yourself, get MonoDevelop and play around a
bit - see what might benefit from your contributions.

Thanks,
Michael "Kipp" Mudge | Welch Allyn | Lead Software Engineer
315-554-4057 | michael.mudge at welchallyn.com



On Fri, May 18, 2012 at 10:08 AM, <adhirramjiawan0 at gmail.com> wrote:

> **
> Hi there!
>
> Yes yes! I've being using a lot of the .Net platform in the past and
> although the factors of licensing costs affect me negatively, I do find the
> .net platform to a be high quality framework. With that being said, I
> really do like open source and having the mono framework is the perfect
> bridge for me :) I would love to have mono sitting on enterprise servers
> one day as novell is doing. I would love to know where do I start
> developing the mono framework itself to introduce more components and
> features to suit the enterprise. I do know of the enterprise library from
> microsoft. I have a few concerns of the future of mono being under threat
> from microsoft one day. Also, how does one know or find out how to build
> these components into mono without stamping on microsoft's feet?
>
> I'm assuming all mono's assemblies are written in C# and compiled as .net
> dlls?
>
> Please help as and when you can, I would really love to use mono instead
> of other open source languages such as scala, java or ruby.
>
> Many thanks for your informative reply!
>
> Adhir Ramjiawan
> Sent via my BlackBerry from Vodacom - let your email find you!
> ------------------------------
> *From: * Miguel Mudge <michael.mudge at welchallyn.com>
> *Date: *Fri, 18 May 2012 09:52:25 -0400
> *To: *Adhir Ramjiawan<adhirramjiawan0 at gmail.com>
> *Cc: *Mono Dev List<mono-devel-list at lists.ximian.com>
> *Subject: *Re: [Mono-dev] Getting Started
>
> Hey Adhir, thanks for emailing!
>
> The Mono development experience is very similar to Java.  If you
> are familiar with Visual Studio or Eclipse, you should feel quite at home.
>  Mono is a cross-platform implementation of the Common Langauge Runtime,
> and includes most of the features provided by Microsoft's implementation
> (called the Microsoft .NET Framework).  The entire purpose of these
> implementations is simply to run C# code (and some other less common
> languages), which provide way to write code that is inherently fast and
> cross-platform - on the surface, it is very much like Java.
>
> "Using" Mono boils down to writing C#, so you will need to know it.
>  MonoDevelop is the tool of choice for developing Mono applications - there
> are lots of C# tutorials out there.  Most of these tutorials are aimed at
> Visual Studio - you could use that too (but only on Windows) - and
> MonoDevelop is very similar, so you should have no problem following the
> tutorials.  You can get MonoDevelop here: http://www.monodevelop.com
>
> Mono has some slight differences and extra features that you might find
> interesting.  There is a wealth of information on
> http://www.mono-project.com, and Googling for information on Mono
> features works out quite well.
>
> You may also want to start a discussion on mono-list - lots of people who
> work with Mono are subscribed to that list.  (On this list we generally
> discuss how we can develop Mono itself)
>
> Good luck, and feel free to ask any further questions.
>
> Michael "Kipp" Mudge | Welch Allyn | Lead Software Engineer
> 315-554-4057 | michael.mudge at welchallyn.com
>
>
> On Fri, May 18, 2012 at 7:29 AM, Adhir Ramjiawan <
> adhirramjiawan0 at gmail.com> wrote:
>
>> Hi All
>>
>> How could I get started with mono development? I see a great future
>> for it and maybe even one day compete against J2EE.
>>
>>
>> Many Thanks
>> Adhir
>> _______________________________________________
>> Mono-devel-list mailing list
>> Mono-devel-list at lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20120518/c8f00ff4/attachment-0001.html>


More information about the Mono-devel-list mailing list