Hi, I've been messing with building a rather low-level datastructure
to avoid the Large Object Heap.
One thing this required of me was to write a very small library
directly in IL. The function I implemented is this:
.method public static hidebysig
default int32 SizeOf () cil mana
Have you tried using the newer dynamic stuff to do your COM interop calls?
http://www.codeproject.com/Tips/143694/Get-rid-of-COM-Interop-DLL-by-using-the-new-C-4-dy
http://msdn.microsoft.com/en-us/magazine/ff714583.aspx
On Wed, Nov 14, 2012 at 4:27 AM, Peter Dillinger wrote:
> (This message wa
On Tue, Nov 13, 2012 at 9:42 AM, Jonathan Chambers wrote:
> You'll probably want to try dmcs (rather than mcs) in order to get C# 4.0
> dynamic binding.
I believe your comment only applies to 2.10.x and earlier. (I moved
to 2.11.x after being annoyed by the distinction.) From
http://www.mono-p
> This framework is constantly appearing as an issue when using WINE+mono.
>
> What would it take, to get the current implementation of the Presentation
> Framework from the Olive git repository to be part of the main stream mono
> repository? Mono currently has classes that aren't implemented comp
You'll probably want to try dmcs (rather than mcs) in order to get C# 4.0
dynamic binding. I think that is at least one of the errors.
http://www.mono-project.com/CSharp_Compiler
- Jonathan
On Tue, Nov 13, 2012 at 12:41 PM, Marek Safar wrote:
> Hi Peter,
>
> In investigating the ability to dr
Hi Peter,
In investigating the ability to drop in mcs as a replacement for csc
> (currently trying out mono 2.11.4), I've run into issues in compiling
> things from some Microsoft C# 4.0 code samples that involve COM
> interop. Here's a simplified example:
>
COM has never been high on our priori
(This message was not accepted from my work email and or from the
forum interface. Trying personal email...)
In investigating the ability to drop in mcs as a replacement for csc
(currently trying out mono 2.11.4), I've run into issues in compiling
things from some Microsoft C# 4.0 code samples th
Hi,
We wouldn't bring WPF into mono tree unless it becomes usable and solid
to some extent. There may be incomplete libraries but that does not
justify bringing extraneous components into mcs build.
Actually I don't think there is considerable difference between mono and
olive to create patche
