Re: [Mono-list] installing latest mono
I've got the later versions from that repo. Just to be safe, did you run apt-get update before installing? What is the mono version if you remove that repo? 2015-07-29 14:43 GMT+02:00 zganjei zzgan...@gmail.com: Hi, I installed mono on my ubuntu using the instructions here http://www.mono-project.com/docs/getting-started/install/linux/#debian-ubuntu-and-derivatives I expected to get the latest version of mono, i.e. 4.0.2 SR 2 (4.0.2.5), but the result of mono --version is Mono JIT compiler version 3.0.7 (tarball Wed Jun 26 15:53:19 CEST 2013) Copyright (C) 2002-2012 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com Am I missing something? Best -- View this message in context: http://mono.1490590.n4.nabble.com/installing-latest-mono-tp4666393.html Sent from the Mono - General mailing list archive at Nabble.com. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-winforms-list] Porting Visual Studio Created WinForms Applications C#
Hi, Is there a way I can contribute to this project? I do like working with Winforms, and now that you told me it's a community based project, I admire the effort alot ! Until now, every functionality seems to work flawlessly. It's mainly a matter of knowing which librareis you can/can't use and which controls and their properties to use and how to manipulate the controls so they work on multiple OSses. Kind regards, Marcel Burger On Wed, Jul 29, 2015 at 9:50 AM, st...@free.fr wrote: Hi, I'm hoping that future mono updates wil solve these graphical issues automagically, so the software works and looks as stunning as it does on a windows system :-) For your information, the WinForms project is only maintained by the community, so such a project would have to come from us. Xamarin won't do it. If not, I guess, HTML5 instead of WinForm will be a nice GUI replacement :-) There's also XWT (but still no designer): https://github.com/mono/xwt - Mail original - De: Marcel Burger m.burger.w...@gmail.com À: Stifu st...@free.fr Cc: mono-winforms-list@lists.ximian.com Envoyé: Mercredi 29 Juillet 2015 09:37:27 Objet: Re: [Mono-winforms-list] Porting Visual Studio Created WinForms Applications C# Hello Peter, Currently I'm also building a multi platform desktop application. I develop with VS, import it in a virtual Linux Mint via Git and build it with Monodevelop. I use Monodevelop and Google to fix the list of build failures Monodevelop comes up with. Besides that I try to use as little Dependencies as I can and only use Libraries which are crossplatform. So, 1 codebase - several deployments. Personally I don't mind the Designer files VS creates, since these files only initiate and set the properties of the controls you create when you use the visual designer is VS. The .resx files (also) contain the images you use in your application (b.t.w. I've noticed that it's better to avoid using Icon files but instead use png files and convert them to ico via code). Monodevelop doesn't have a WinForm designer so you will be creating (some sort of) Designer files yourself anyway to initiatie and set the controls you need. I have noticed that some Control properties set in VS don't act like they should in Monodevelop, many of which have been submitted as bugs. In many cases initiating those Controls and setting the properties yourself (via code instead of using the Visual Designer) solve the problems (but not all of them, some properties simply don't work so I choose to ommit them instead of creating hacks around them ...). So you can also stick to develop a winform app without a Visual Designer ;) Keep in mind that you will have some issues regarding: - visual refreshing on Unix systems (controls simply won't refresh themselve like they do on Windows, so sometimes you don't see the controls at all, which looks pretty awful. I see it in more applications on Unix systems ...) - The controls used via Monodevelop are based on winXP which make them look a buit outdated - Some controls used via Monodevelop have different base (not mutable) properties then WIndows, which leads to different spacing requirements ... (e.g. ComboBox). Since I only have the requirement that the software should work on Unix and that the graphical issues are not that important, I stick with my current development strategy. I think it's very cool that I only have to write the code once and deploy it on different OSses, but the graphical experience is a bit dissapointing. I'm hoping that future mono updates wil solve these graphical issues automagically, so the software works and looks as stunning as it does on a windows system :-) I don't mind helping out in that area ;) If not, I guess, HTML5 instead of WinForm will be a nice GUI replacement :-) cheers, Marcel Burger On Tue, Jul 28, 2015 at 5:23 PM, Stifu st...@free.fr wrote: Hi, MonoDevelop and Xamarin Studio don't have a WinForms designer, so you'd better stick with Visual Studio. I admit I'm not really up to date on this, but there must be VS plugins to run your app with Mono from the IDE. I've found the MonoDebugger project ( http://www.monodebugger.net/ ), but it seems it's still not available. Maybe Xamarin for Visual Studio does what you want ( http://xamarin.com/visual-studio ), but I'm not sure, since it's actually specialized in mobile development. Note you could also just build your app with VS then manually test it on Mono on all the targeted platforms. It's not ideal, but it's what I do (except I use SharpDevelop). jonesypeter wrote Hello, I wonder if I could ask a very simplistic question. I have searched for an answer before posting. I have created a very simple WinForms applications and created the .exe and checked that this runs with Mono as well and it all went fine. If I want to build this application directly with Mono how do I
Re: [Mono-winforms-list] Porting Visual Studio Created WinForms Applications C#
To clear things up, it's been in the hands of the community since 2010, but it was actually started by the Mono team. Sure, you can contribute in any way you like. Fix your own pet bugs, fix bugs from bugzilla, or add new stuff. Then submit patches / pull requests. Sources: https://github.com/mono/mono/tree/master/mcs/class/System.Windows.Forms Let me know if I can help. - Mail original - De: Marcel Burger m.burger.w...@gmail.com À: Stifu st...@free.fr Cc: mono-winforms-list@lists.ximian.com Envoyé: Mercredi 29 Juillet 2015 10:22:36 Objet: Re: [Mono-winforms-list] Porting Visual Studio Created WinForms Applications C# Hi, Is there a way I can contribute to this project? I do like working with Winforms, and now that you told me it's a community based project, I admire the effort alot ! Until now, every functionality seems to work flawlessly. It's mainly a matter of knowing which librareis you can/can't use and which controls and their properties to use and how to manipulate the controls so they work on multiple OSses. Kind regards, Marcel Burger On Wed, Jul 29, 2015 at 9:50 AM, st...@free.fr wrote: Hi, I'm hoping that future mono updates wil solve these graphical issues automagically, so the software works and looks as stunning as it does on a windows system :-) For your information, the WinForms project is only maintained by the community, so such a project would have to come from us. Xamarin won't do it. If not, I guess, HTML5 instead of WinForm will be a nice GUI replacement :-) There's also XWT (but still no designer): https://github.com/mono/xwt - Mail original - De: Marcel Burger m.burger.w...@gmail.com À: Stifu st...@free.fr Cc: mono-winforms-list@lists.ximian.com Envoyé: Mercredi 29 Juillet 2015 09:37:27 Objet: Re: [Mono-winforms-list] Porting Visual Studio Created WinForms Applications C# Hello Peter, Currently I'm also building a multi platform desktop application. I develop with VS, import it in a virtual Linux Mint via Git and build it with Monodevelop. I use Monodevelop and Google to fix the list of build failures Monodevelop comes up with. Besides that I try to use as little Dependencies as I can and only use Libraries which are crossplatform. So, 1 codebase - several deployments. Personally I don't mind the Designer files VS creates, since these files only initiate and set the properties of the controls you create when you use the visual designer is VS. The .resx files (also) contain the images you use in your application (b.t.w. I've noticed that it's better to avoid using Icon files but instead use png files and convert them to ico via code). Monodevelop doesn't have a WinForm designer so you will be creating (some sort of) Designer files yourself anyway to initiatie and set the controls you need. I have noticed that some Control properties set in VS don't act like they should in Monodevelop, many of which have been submitted as bugs. In many cases initiating those Controls and setting the properties yourself (via code instead of using the Visual Designer) solve the problems (but not all of them, some properties simply don't work so I choose to ommit them instead of creating hacks around them ...). So you can also stick to develop a winform app without a Visual Designer ;) Keep in mind that you will have some issues regarding: - visual refreshing on Unix systems (controls simply won't refresh themselve like they do on Windows, so sometimes you don't see the controls at all, which looks pretty awful. I see it in more applications on Unix systems ...) - The controls used via Monodevelop are based on winXP which make them look a buit outdated - Some controls used via Monodevelop have different base (not mutable) properties then WIndows, which leads to different spacing requirements ... (e.g. ComboBox). Since I only have the requirement that the software should work on Unix and that the graphical issues are not that important, I stick with my current development strategy. I think it's very cool that I only have to write the code once and deploy it on different OSses, but the graphical experience is a bit dissapointing. I'm hoping that future mono updates wil solve these graphical issues automagically, so the software works and looks as stunning as it does on a windows system :-) I don't mind helping out in that area ;) If not, I guess, HTML5 instead of WinForm will be a nice GUI replacement :-) cheers, Marcel Burger On Tue, Jul 28, 2015 at 5:23 PM, Stifu st...@free.fr wrote: Hi, MonoDevelop and Xamarin Studio don't have a WinForms designer, so you'd better stick with Visual Studio. I admit I'm not really up to date on this, but there must be VS plugins to run your app with Mono from the IDE. I've found the MonoDebugger project ( http://www.monodebugger.net/ ), but it seems it's still not available. Maybe Xamarin for Visual
Re: [Mono-dev] condition `class' not met
fwiw. You will likely need to ensure that your build of 'mono-native' and 'mono' recipes are both in sync. That solved the issue! Thanks! Daniel Alex J Lennon ajlen...@dynamicdevices.co.uk schrieb am Di., 28. Juli 2015 um 19:08 Uhr: On 28/07/2015 17:59, Zoltan Varga wrote: Hi, It is a transient failure when using a mismatching mono runtime and mscorlib.dll. Make sure you are using the latest version of both. Zoltan fwiw. You will likely need to ensure that your build of 'mono-native' and 'mono' recipes are both in sync. Alex ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-winforms-list] Porting Visual Studio Created WinForms Applications C#
Hi, I'm hoping that future mono updates wil solve these graphical issues automagically, so the software works and looks as stunning as it does on a windows system :-) For your information, the WinForms project is only maintained by the community, so such a project would have to come from us. Xamarin won't do it. If not, I guess, HTML5 instead of WinForm will be a nice GUI replacement :-) There's also XWT (but still no designer): https://github.com/mono/xwt - Mail original - De: Marcel Burger m.burger.w...@gmail.com À: Stifu st...@free.fr Cc: mono-winforms-list@lists.ximian.com Envoyé: Mercredi 29 Juillet 2015 09:37:27 Objet: Re: [Mono-winforms-list] Porting Visual Studio Created WinForms Applications C# Hello Peter, Currently I'm also building a multi platform desktop application. I develop with VS, import it in a virtual Linux Mint via Git and build it with Monodevelop. I use Monodevelop and Google to fix the list of build failures Monodevelop comes up with. Besides that I try to use as little Dependencies as I can and only use Libraries which are crossplatform. So, 1 codebase - several deployments. Personally I don't mind the Designer files VS creates, since these files only initiate and set the properties of the controls you create when you use the visual designer is VS. The .resx files (also) contain the images you use in your application (b.t.w. I've noticed that it's better to avoid using Icon files but instead use png files and convert them to ico via code). Monodevelop doesn't have a WinForm designer so you will be creating (some sort of) Designer files yourself anyway to initiatie and set the controls you need. I have noticed that some Control properties set in VS don't act like they should in Monodevelop, many of which have been submitted as bugs. In many cases initiating those Controls and setting the properties yourself (via code instead of using the Visual Designer) solve the problems (but not all of them, some properties simply don't work so I choose to ommit them instead of creating hacks around them ...). So you can also stick to develop a winform app without a Visual Designer ;) Keep in mind that you will have some issues regarding: - visual refreshing on Unix systems (controls simply won't refresh themselve like they do on Windows, so sometimes you don't see the controls at all, which looks pretty awful. I see it in more applications on Unix systems ...) - The controls used via Monodevelop are based on winXP which make them look a buit outdated - Some controls used via Monodevelop have different base (not mutable) properties then WIndows, which leads to different spacing requirements ... (e.g. ComboBox). Since I only have the requirement that the software should work on Unix and that the graphical issues are not that important, I stick with my current development strategy. I think it's very cool that I only have to write the code once and deploy it on different OSses, but the graphical experience is a bit dissapointing. I'm hoping that future mono updates wil solve these graphical issues automagically, so the software works and looks as stunning as it does on a windows system :-) I don't mind helping out in that area ;) If not, I guess, HTML5 instead of WinForm will be a nice GUI replacement :-) cheers, Marcel Burger On Tue, Jul 28, 2015 at 5:23 PM, Stifu st...@free.fr wrote: Hi, MonoDevelop and Xamarin Studio don't have a WinForms designer, so you'd better stick with Visual Studio. I admit I'm not really up to date on this, but there must be VS plugins to run your app with Mono from the IDE. I've found the MonoDebugger project ( http://www.monodebugger.net/ ), but it seems it's still not available. Maybe Xamarin for Visual Studio does what you want ( http://xamarin.com/visual-studio ), but I'm not sure, since it's actually specialized in mobile development. Note you could also just build your app with VS then manually test it on Mono on all the targeted platforms. It's not ideal, but it's what I do (except I use SharpDevelop). jonesypeter wrote Hello, I wonder if I could ask a very simplistic question. I have searched for an answer before posting. I have created a very simple WinForms applications and created the .exe and checked that this runs with Mono as well and it all went fine. If I want to build this application directly with Mono how do I do this, because Visual Studio creates a large list of files including Form1.Designer.cs, Form1.resz. and Program.cs Thanks Peter Jones -- View this message in context: http://mono.1490590.n4.nabble.com/Porting-Visual-Studio-Created-WinForms-Applications-C-tp4666376p4666385.html Sent from the Mono - WinForms mailing list archive at Nabble.com. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com
Re: [Mono-dev] condition `class' not met
On 29/07/2015 08:43, Daniel Kuhne wrote: fwiw. You will likely need to ensure that your build of 'mono-native' and 'mono' recipes are both in sync. That solved the issue! Great! Thanks for letting me know. You prompted me to look at the git support last night as I've been concentrating on other things, like tracking the Mono releases and refactoring. There were some problems with the git support, which hopefully I've addressed in recent commits. Would appreciate any feedback you have on whether those fixes work for you. (If you do have comments it might be best to come back via the the Yocto list so we don't upset the good people here ;) Cheers, Alex ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
