Mono Support and Consulting.
2011-06-30 23:31:26 GMT
Hey guys,
_______________________________________________ Mono-devel-list mailing list Mono-devel-list <at> lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Hey guys,
_______________________________________________ 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
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
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.
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.
_______________________________________________ Mono-devel-list mailing list Mono-devel-list <at> lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
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.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.
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?
_______________________________________________ Mono-devel-list mailing list Mono-devel-list <at> lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
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 01.07.2011 12:01, ah hatem wrote:The former Novell employees are now focused on product development
> 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
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.Check https://github.com/mono/mono
> source was contributed by the community and how much by the Novel team?
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
Hello,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.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?
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
_______________________________________________ Mono-devel-list mailing list Mono-devel-list <at> lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
https://bugzilla.novell.com/show_bug.cgi?id=608069Would you mind sending a link to the relevant issue on bugzilla so I can track it?
On Sat, Jul 2, 2011 at 1:32 AM, Marek Safar <marek.safar <at> gmail.com> wrote:Hello,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.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?
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.8148444 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
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
RSS Feed50 | |
|---|---|
140 | |
66 | |
110 | |
127 | |
91 | |
133 | |
96 | |
65 | |
126 | |
155 | |
376 | |
115 | |
81 | |
82 | |
107 | |
149 | |
72 | |
127 | |
67 | |
80 | |
135 | |
163 | |
99 | |
128 | |
200 | |
249 | |
191 | |
239 | |
192 | |
219 | |
236 | |
153 | |
220 | |
214 | |
216 | |
244 | |
318 | |
345 | |
212 | |
207 | |
196 | |
213 | |
210 | |
295 | |
158 | |
198 | |
205 | |
355 | |
366 | |
346 | |
489 | |
389 | |
329 | |
424 | |
314 | |
256 | |
317 | |
317 | |
293 | |
359 | |
401 | |
248 | |
320 | |
348 | |
540 | |
360 | |
389 | |
321 | |
420 | |
351 | |
221 | |
389 | |
349 | |
359 | |
355 | |
349 | |
377 | |
382 | |
505 | |
454 | |
638 | |
422 | |
455 | |
325 | |
473 | |
577 | |
485 | |
475 | |
362 | |
498 | |
481 | |
618 | |
821 | |
634 | |
770 | |
430 | |
457 | |
552 | |
564 | |
566 | |
466 | |
544 | |
452 | |
382 | |
451 | |
545 | |
670 | |
818 | |
448 | |
470 | |
462 | |
458 | |
256 | |
405 | |
495 | |
287 | |
237 | |
405 | |
297 | |
402 | |
332 | |
246 | |
1 |