[Mono-dev] ObservableCollection.Reentrant not marked Serializable. Why?

The class ObservableCollection.Reentrant is not marked as Serializable which causes ObservableCollection to fail binary serialization. Is there any reason it cannot be made serializable? -- View this message in context: http://mono.1490590.n4.nabble.com/ObservableCollection-Reentrant-not-marked

Re: [Mono-dev] LLVM auto vectorization

No work has been done to enable auto vectorization on mono with LLVM. On Wed, Jan 30, 2013 at 10:39 PM, wrote: > Is any of the LLVM auto vectorization code in the version of LLVM cleared > for mono? (http://llvm.org/docs/Vectorizers.html) > > ___ > Mo

Re: [Mono-dev] System.Date.Now.ToString() on ARM processor

Please file a bug report with a minimal test case. On Wed, Jan 30, 2013 at 11:00 PM, hernan casta wrote: > Dear list, > > I'm running mono on an ARM processor (Raspberry pi plataform). Somebody > had the same error on datetime format in this platform? > > System.DateTime.Now.ToString(); gives as

Re: [Mono-dev] A bug in System.Xml blocking Entity Framework usage, #6653.

Thanks for the heads up. Yes there was. The problem with that bug report is that it does not bother to try to minimize the schema. It is actually so annoying task. Now I've trimmed down to 35 lines out from 1000. There are many extraneous schema components and type definitions that are irrel

[Mono-dev] System.Date.Now.ToString() on ARM processor

Dear list, I'm running mono on an ARM processor (Raspberry pi plataform). Somebody had the same error on datetime format in this platform? System.DateTime.Now.ToString(); gives as result "00/734898/0001 21:52:34" Similar problem with the following instruction DateTime.Now.ToString("ddd, dd MMM

[Mono-dev] LLVM auto vectorization

Is any of the LLVM auto vectorization code in the version of LLVM cleared for mono? (http://llvm.org/docs/Vectorizers.html) ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Empty IEnumerable Implementation Crashes C# Compiler

Just tested in 3.0.3 and compiled so it's only a 2.x problem I guess -- View this message in context: http://mono.1490590.n4.nabble.com/Empty-IEnumerable-Implementation-Crashes-C-Compiler-tp4658346p4658355.html Sent from the Mono - Dev mailing list archive at Nabble.com. ___

Re: [Mono-dev] Empty IEnumerable Implementation Crashes C# Compiler

I actually know about that and based my solution on http://msmvps.com/blogs/jon_skeet/archive/2010/12/24/reimplementing-linq-to-objects-part-5-empty.aspx -- View this message in context: http://mono.1490590.n4.nabble.com/Empty-IEnumerable-Implementation-Crashes-C-Compiler-tp4658346p4658353.html

Re: [Mono-dev] Empty IEnumerable Implementation Crashes C# Compiler

There's also simply: Enumerable.Empty () shmuelie wrote > Didn't know that I could just do that. Fixed it by implementing a > Enumerator manually but may switch to that. At this point its more of a > compiler bug then a problem for me -- View this message in context: http://mono.1490590.n4.

[Mono-dev] Microsoft.Build: The parameter 'FrameworkVersion45Path' was not found for the 'GetFrameworkPath' task

Hi, I'm trying to execute the ResolveAssemblyReferences task using the Microsoft.Build namespace. This (F#) project builds nicely from the command line using xbuild, so the logic is capable. The project file can be found here: https://github.com/fsharp/fsharpbinding/blob/master/FSharp.AutoComplete

Re: [Mono-dev] Empty IEnumerable Implementation Crashes C# Compiler

On 30/01/13 17:30, shmuelie wrote: Didn't know that I could just do that. Fixed it by implementing a Enumerator manually but may switch to that. At this point its more of a compiler bug then a problem for me Then test with the last version (mono 3.0.3) and if that still doesn't work, please fi

Re: [Mono-dev] Empty IEnumerable Implementation Crashes C# Compiler

Didn't know that I could just do that. Fixed it by implementing a Enumerator manually but may switch to that. At this point its more of a compiler bug then a problem for me -- View this message in context: http://mono.1490590.n4.nabble.com/Empty-IEnumerable-Implementation-Crashes-C-Compiler-tp4

Re: [Mono-dev] Empty IEnumerable Implementation Crashes C# Compiler

As a workaround, you can use the simpler: IEnumerator IEnumerable.GetEnumerator () { yield break; } Petr Onderka On Wed, Jan 30, 2013 at 5:50 PM, shmuelie wrote: > I needed to create a quick and dirty IEnumerable that that had no elements. > To do so I used the following code: > > IEnum

[Mono-dev] Empty IEnumerable Implementation Crashes C# Compiler

I needed to create a quick and dirty IEnumerable that that had no elements. To do so I used the following code: IEnumerator IEnumerable.GetEnumerator () { while(false) { yield return string.Empty; } } It compiled and work in .NET 4.0 but when I tried to use

[Mono-dev] A bug in System.Xml blocking Entity Framework usage, #6653.

Hello, There is a 5 months old bug #6653 and discussions on StackOverflow about troubles with Entity Framework when it loads metadata from xml model: How to setup Entity Framework / SQL Server with Mono

[Mono-dev] mono performance analysis and optimization

Hello, could anyone point me to discussions and resources which deal with mono performance analysis and optimization? For starters I'm looking for a benchmark suite that would allow me to test mono runtime performance. I only found this http://d3s.mff.cuni.cz/projects/performance_evaluation/mono/o

Re: [Mono-dev] PowerShell 3.0 on Mono

Hi, On Tue, Jan 29, 2013 at 10:51 PM, Bruno Lauzé wrote: > Hi, > > I want to share with you the complete PowerShell 3.0 recompiled for Mono. > > > Code base: https://github.com/brunolauze/pash While I know you are posting this with good intentions, please note that posting decompiled Microsoft s

Re: [Mono-dev] PowerShell 3.0 on Mono

Impressive achievement... But what about licensing? And about compatibility with Nuget? Rafael "Monoman" Teixeira --- "The most exciting phrase to hear in science, the one that heralds new discoveries, is not 'Eureka!' (I found it!) but 'That's funny ...'" Isaac

[Mono-dev] ARM/NativeClient port

Hi, We're working on implementation of Mono JIT/ARM for Native Client, and want to discuss certain details about design of our solution. Native Client's sandboxing mechanism, being a SFI solution, has rather strict limitations on how verifiable machine code may look like. To be precise: 1.