-langversion:linq

If I set my project to the 2.0 profile does Monodevelop
invoke the
"-langversion:linq" behavior?  I don't see any
explicit way to enable
linq mode in the UI.

I have an extension method, which I think should work in
Mono, but when
I attempt to built the library in Monodevelop I get an
error.

Unhandled Exception: System.ArgumentNullException: Argument
cannot be
null.
Parameter name: customBuilder
  at System.Reflection.Emit.TypeBuilder.SetCustomAttribute
(System.Reflection.Emit.CustomAttributeBuilder
customBuilder) [0x00000] 
  at Mono.CSharp.Class.Emit () [0x00000] 
  at Mono.CSharp.TypeContainer.EmitType () [0x00000] 
  at Mono.CSharp.RootContext.EmitCode () [0x00000] 
  at Mono.CSharp.Driver.MainDriver (System.String[] args)
[0x00000] 
  at Mono.CSharp.Driver.Main (System.String[] args)
[0x00000] 


Build complete -- 2 errors, 0 warnings


mono-core-1.2.5.1-10.1
monodevelop-0.17-0.novell

-- 
Adam Tauno Williams, Network & Systems Administrator
Consultant - http://www.whitemi
ceconsulting.com
Developer - http://www.opengroupware
.org

_______________________________________________
Monodevelop-list mailing list
Monodevelop-listlists.ximian.com
http://lists.ximian.com/mailman/listinfo/monodevelop-li
st

MD does have a langversion dropdown in SVN, but it does not
include
linq because this compiler option will soon be renamed to
"default".
Until then you can use the "additional compiler
args" setting, also in
MD SVN.


On 12/9/07, Adam Tauno Williams <adamtaunowilliamsgmail.com> wrote:
> If I set my project to the 2.0 profile does Monodevelop
invoke the
> "-langversion:linq" behavior?  I don't see
any explicit way to enable
> linq mode in the UI.
>
> I have an extension method, which I think should work
in Mono, but when
> I attempt to built the library in Monodevelop I get an
error.
>
> Unhandled Exception: System.ArgumentNullException:
Argument cannot be
> null.
> Parameter name: customBuilder
>   at
System.Reflection.Emit.TypeBuilder.SetCustomAttribute
> (System.Reflection.Emit.CustomAttributeBuilder
customBuilder) [0x00000]
>   at Mono.CSharp.Class.Emit () [0x00000]
>   at Mono.CSharp.TypeContainer.EmitType () [0x00000]
>   at Mono.CSharp.RootContext.EmitCode () [0x00000]
>   at Mono.CSharp.Driver.MainDriver (System.String[]
args) [0x00000]
>   at Mono.CSharp.Driver.Main (System.String[] args)
[0x00000]
>
>
> Build complete -- 2 errors, 0 warnings
>
>
> mono-core-1.2.5.1-10.1
> monodevelop-0.17-0.novell
>
> --
> Adam Tauno Williams, Network & Systems
Administrator
> Consultant - http://www.whitemi
ceconsulting.com
> Developer - http://www.opengroupware
.org
>
> _______________________________________________
> Monodevelop-list mailing list
> Monodevelop-listlists.ximian.com
> http://lists.ximian.com/mailman/listinfo/monodevelop-li
st
>

-- 
Sent from Gmail for mobile | mobile.google.com

Michael Hutchinson
http://mjhutchinson.com
_______________________________________________
Monodevelop-list mailing list
Monodevelop-listlists.ximian.com
http://lists.ximian.com/mailman/listinfo/monodevelop-li
st

Hello,

    Am creating some data dynamically for a menu, and it is
not clear
how I can add this information to my window.

    The UIManager that Stetic creates is a local variable to
the build
routine so I can not access that.   Another option is to use
the
menubar that is attached to the Window, and the manually
walk the menu
hierarchy, but that sounds incredibly suboptimal since we
have the UImanager in place.

    Alternatively, I would be happy if I could insert a
placeholder in
the menu structure inside Stetic and reference that from the
source.

Any pointers?
_______________________________________________
Monodevelop-list mailing list
Monodevelop-listlists.ximian.com
http://lists.ximian.com/mailman/listinfo/monodevelop-li
st

Am Dienstag, 11. Dezember 2007 05:57 schrieb Miguel de
Icaza:
> Hello,
>
>     Am creating some data dynamically for a menu, and
it is not clear
> how I can add this information to my window.
>
>     The UIManager that Stetic creates is a local
variable to the build
> routine so I can not access that.   Another option is
to use the
> menubar that is attached to the Window, and the
manually walk the menu
> hierarchy, but that sounds incredibly suboptimal since
we have the
> UImanager in place.
>
Hi,

in fact, fiddling around with the menubar (first having made
it accessible 
from the source code by using "Bind to field") is
what I've done in my app, 
which reads out a whole menu hierarchy out of a PostgreSQL
DBMS and then adds 
it to the menubar.

Regards
Jacek Rużyczka
_______________________________________________
Monodevelop-list mailing list
Monodevelop-listlists.ximian.com
http://lists.ximian.com/mailman/listinfo/monodevelop-li
st

El dl 10 de 12 del 2007 a les 23:57 -0500, en/na Miguel de
Icaza va
escriure:
> Hello,
> 
>     Am creating some data dynamically for a menu, and
it is not clear
> how I can add this information to my window.
> 
>     The UIManager that Stetic creates is a local
variable to the build
> routine so I can not access that.   Another option is
to use the
> menubar that is attached to the Window, and the
manually walk the menu
> hierarchy, but that sounds incredibly suboptimal since
we have the UImanager in place.
> 
>     Alternatively, I would be happy if I could insert a
placeholder in
> the menu structure inside Stetic and reference that
from the source.

You can add a set of actions to the menu and dynamically
hide/show/update them at run-time. If that is not enough,
the only
option right now is to walk the menu hierarchy. However, it
might make
sense to make the UIManager accessible. I add it to my
TODO.

Lluis.


_______________________________________________
Monodevelop-list mailing list
Monodevelop-listlists.ximian.com
http://lists.ximian.com/mailman/listinfo/monodevelop-li
st

Hello Lluis,

    Thanks for your response:

> You can add a set of actions to the menu and
dynamically
> hide/show/update them at run-time. If that is not
enough, the only
> option right now is to walk the menu hierarchy.
However, it might make
> sense to make the UIManager accessible. I add it to my
TODO.

     The situation I have is that I need to populate
dynamically the
menus, and doing the population manually is going to be
error-prone, and
since the data is dynamic it would hard-code a lot of things
into the
UI.

     I would be fine with either the uimanager accessible,
or having
some way of referencing a placeholder in the menus.

Thanks for the feedback!
Miguel.
_______________________________________________
Monodevelop-list mailing list
Monodevelop-listlists.ximian.com
http://lists.ximian.com/mailman/listinfo/monodevelop-li
st

On Wed, 2007-12-12 at 12:15 +0100, Lluis Sanchez wrote:

> You can add a set of actions to the menu and
dynamically
> hide/show/update them at run-time. If that is not
enough, the only
> option right now is to walk the menu hierarchy.
However, it might make
> sense to make the UIManager accessible. I add it to my
TODO.

What are the chances of this being snuck in before 1.0?



David


_______________________________________________
Monodevelop-list mailing list
Monodevelop-listlists.ximian.com
http://lists.ximian.com/mailman/listinfo/monodevelop-li
st

El dg 02 de 03 del 2008 a les 13:03 +0000, en/na David A
Knight va
escriure:
> On Wed, 2007-12-12 at 12:15 +0100, Lluis Sanchez
wrote:
> 
> > You can add a set of actions to the menu and
dynamically
> > hide/show/update them at run-time. If that is not
enough, the only
> > option right now is to walk the menu hierarchy.
However, it might make
> > sense to make the UIManager accessible. I add it
to my TODO.
> 
> What are the chances of this being snuck in before
1.0?

No chances. 1.0 was frozen weeks ago.

> 
> 
> 
> David
> 
> _______________________________________________
> Monodevelop-list mailing list
> Monodevelop-listlists.ximian.com
> http://lists.ximian.com/mailman/listinfo/monodevelop-li
st

_______________________________________________
Monodevelop-list mailing list
Monodevelop-listlists.ximian.com
http://lists.ximian.com/mailman/listinfo/monodevelop-li
st