Miguel de Icaza | 1 Jul 01:31 2011

Mono Support and Consulting.

Hey guys,


    I just posted this on my blog:

        We are getting flooded with paid support requests for
        Mono.   Developers looking for us to fix bugs in Mono, to do
        some custom work, to port applications, libraries and adjust
        Mono for some specific needs.

        But we are trying to be a product company as opposed to a
        support company.

        We still want to help the Mono user community, and with all
        of the Mono talent out there, at least we can use this
        opportunity to get both groups in touch: the users that want
        custom engineering done, with the talented list of hackers.

        If you are a consultant available to do custom engineering
        and support for customers, we would love to put you in touch
        with people that need the custom engineering done.    Email us
        at contact <at> xamarin.com, in the subject line, specify that you
        are available for custom engineering, and in the body of the
        message list both your Mono skills (C# or C coding) and your
        availability to engage on those gigs.

        We will then get you in touch with users that needs the
        work done.

_______________________________________________
Mono-devel-list mailing list
Mono-devel-list <at> lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
ah hatem | 1 Jul 12:01 2011
Picon

Mono's future

Hi,

What is the current status of mono after the layoff of the entire mono team? How will that affect mono on the short and long terms? How much of the mono source was contributed by the community and how much by the Novel team?

Thanks a lot....
_______________________________________________
Mono-devel-list mailing list
Mono-devel-list <at> lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Robert Jordan | 1 Jul 13:47 2011
Picon
Picon

Re: Mono's future

On 01.07.2011 12:01, ah hatem wrote:
> What is the current status of mono after the layoff of the entire mono team?
> How will that affect mono on the short and long terms? How much of the mono

The former Novell employees are now focused on product development
for mobile platforms and their tooling. Parts of Mono/.NET
framework unrelated to these platforms may become more or less
abandoned, but they already were, so this is nothing new!

The really juicy parts like C# compiler, runtime, core class
library, GTK#, MonoDevelop are still actively developed and maintained.

> source was contributed by the community and how much by the Novel team?

Check https://github.com/mono/mono

Robert
agerrius | 1 Jul 22:57 2011
Picon

xbuild & x86 target

Hello,

I am trying to build a .NET solution with xbuild and mono on Linux. Actually
the building itself goes fine, but I have a problem when later running the
application on 64 bit Windows. Users reported error messages, which I found
are related to the application not being build with the x86 target but with
the anycpu target.

In the solution I have x86 target set and I also tried to provide it as
input to xbuild from the command prompt. But I do still get those crashes on
64 bit Windows machines.

I am missing something? Is there another way to make sure the application is
build with x86 target?

Thanks,

Arno

--
View this message in context: http://mono.1490590.n4.nabble.com/xbuild-x86-target-tp3639281p3639281.html
Sent from the Mono - Dev mailing list archive at Nabble.com.
John Fallows | 2 Jul 04:35 2011

Support for Portable Class Libraries (PCL)

Microsoft has recently introduced support for Portable Class Libraries, allowing the same DLL to be reused for both .Net 4 and Silverlight 4 without recompiling the source.  There are restrictions on which APIs are available, and some minor API changes from their non-portable equivalents to gain consistency across the platforms.



What additional development effort would be required for the Mono project to deliver equivalent Portable Class Library system library implementations, to be used as library references when compiling .Net 4 / Silverlight 4 portable code with gmcs?

Kind Regards,
John Fallows
--
>|< Kaazing Corporation >|<
John Fallows | CTO | +1.650.960.8148
444 Castro St, Suite 1100 | Mountain View, CA 94041, USA

_______________________________________________
Mono-devel-list mailing list
Mono-devel-list <at> lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Marek Safar | 2 Jul 10:32 2011
Picon

Re: Support for Portable Class Libraries (PCL)

Hello,
Microsoft has recently introduced support for Portable Class Libraries, allowing the same DLL to be reused for both .Net 4 and Silverlight 4 without recompiling the source.  There are restrictions on which APIs are available, and some minor API changes from their non-portable equivalents to gain consistency across the platforms.


What additional development effort would be required for the Mono project to deliver equivalent Portable Class Library system library implementations, to be used as library references when compiling .Net 4 / Silverlight 4 portable code with gmcs?
We don't have Portable .NET profile. The first step would be to create this build profile and probably use linker or hack the compiler to strip all IL code as it's not needed. On top of that runtime support for retargetable assemblies is needed. There is already a bug report about this feature in bugzilla.

I think that's all what is needed.

Marek
_______________________________________________
Mono-devel-list mailing list
Mono-devel-list <at> lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
gelin yan | 2 Jul 15:30 2011
Picon

Re: Mono's future

I am more concerned on when mono 3.0 will be released. As we know, about performance, mono still has a long way to go. The gc and socket performance improved significantly but not enough..

regards

gelin yan

On Fri, Jul 1, 2011 at 7:47 PM, Robert Jordan <robertj <at> gmx.net> wrote:
On 01.07.2011 12:01, ah hatem wrote:
> What is the current status of mono after the layoff of the entire mono team?
> How will that affect mono on the short and long terms? How much of the mono

The former Novell employees are now focused on product development
for mobile platforms and their tooling. Parts of Mono/.NET
framework unrelated to these platforms may become more or less
abandoned, but they already were, so this is nothing new!

The really juicy parts like C# compiler, runtime, core class
library, GTK#, MonoDevelop are still actively developed and maintained.

> source was contributed by the community and how much by the Novel team?

Check https://github.com/mono/mono

Robert

_______________________________________________
Mono-devel-list mailing list
Mono-devel-list <at> lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

_______________________________________________
Mono-devel-list mailing list
Mono-devel-list <at> lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
John Fallows | 2 Jul 21:48 2011

Re: Support for Portable Class Libraries (PCL)

Thanks Marek.

Would you mind sending a link to the relevant issue on bugzilla so I can track it?

tc,
-john.

On Sat, Jul 2, 2011 at 1:32 AM, Marek Safar <marek.safar <at> gmail.com> wrote:
Hello,

Microsoft has recently introduced support for Portable Class Libraries, allowing the same DLL to be reused for both .Net 4 and Silverlight 4 without recompiling the source.  There are restrictions on which APIs are available, and some minor API changes from their non-portable equivalents to gain consistency across the platforms.


What additional development effort would be required for the Mono project to deliver equivalent Portable Class Library system library implementations, to be used as library references when compiling .Net 4 / Silverlight 4 portable code with gmcs?
We don't have Portable .NET profile. The first step would be to create this build profile and probably use linker or hack the compiler to strip all IL code as it's not needed. On top of that runtime support for retargetable assemblies is needed. There is already a bug report about this feature in bugzilla.

I think that's all what is needed.

Marek

_______________________________________________
Mono-devel-list mailing list
Mono-devel-list <at> lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list




--
>|< Kaazing Corporation >|<
John Fallows | CTO | +1.650.960.8148
444 Castro St, Suite 1100 | Mountain View, CA 94041, USA

_______________________________________________
Mono-devel-list mailing list
Mono-devel-list <at> lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Marek Safar | 3 Jul 13:43 2011
Picon

Re: Support for Portable Class Libraries (PCL)

Hi,

Would you mind sending a link to the relevant issue on bugzilla so I can track it?
https://bugzilla.novell.com/show_bug.cgi?id=608069

Marek

On Sat, Jul 2, 2011 at 1:32 AM, Marek Safar <marek.safar <at> gmail.com> wrote:
Hello,

Microsoft has recently introduced support for Portable Class Libraries, allowing the same DLL to be reused for both .Net 4 and Silverlight 4 without recompiling the source.  There are restrictions on which APIs are available, and some minor API changes from their non-portable equivalents to gain consistency across the platforms.


What additional development effort would be required for the Mono project to deliver equivalent Portable Class Library system library implementations, to be used as library references when compiling .Net 4 / Silverlight 4 portable code with gmcs?
We don't have Portable .NET profile. The first step would be to create this build profile and probably use linker or hack the compiler to strip all IL code as it's not needed. On top of that runtime support for retargetable assemblies is needed. There is already a bug report about this feature in bugzilla.

I think that's all what is needed.

Marek

_______________________________________________
Mono-devel-list mailing list
Mono-devel-list <at> lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list




--
>|< Kaazing Corporation >|<
John Fallows | CTO | +1.650.960.8148
444 Castro St, Suite 1100 | Mountain View, CA 94041, USA


_______________________________________________
Mono-devel-list mailing list
Mono-devel-list <at> lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Rolf Bjarne Kvinge | 4 Jul 12:16 2011
Picon

Re: Continuous Integration for Mono

Hi,

 

From: mono-devel-list-bounces <at> lists.ximian.com [mailto:mono-devel-list-bounces <at> lists.ximian.com] On Behalf Of Miguel de Icaza
Sent: lunes, 27 de junio de 2011 2:24
To: grompf <at> gmail.com
Cc: mono-devel-list
Subject: Re: [Mono-dev] Continuous Integration for Mono

 

For the sake of throwing it out there, Mono used to run on Wrench,
written by Rolf, and I hosted the wrench server for moonlight free of
charge for the last few years.  I'm happy to do that indefinitely
going forward on the same server if the community wants to go that
way.

 

I would love to keep reusing the existing setup.

 

I guess what needs to be done is to add servers and configurations to it?

 

How are those servers added, and how do we need to coordinate with you to get those updated?

 

Miguel

 

 

I’ll setup a server on Geoff’s machine, then it’s just a matter of adding builders, which is easy. I can also teach Alex about it so that he can take over from Andrew.

 

The problem has always been getting enough hardware in all the variations mono supports. So if anybody has any machines or VMs that can run full-time please send me a mail. Have in mind that it’ll be pretty much required to give us root access to the machine (it’s a lot easier and faster to have one person with access to all the bots than having that person contacting all the individual admins whenever something has to be changed / installed on the builder).

 

Rolf

_______________________________________________
Mono-devel-list mailing list
Mono-devel-list <at> lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Gmane