Is it possible to run sharp develop on Linux using mono?
I have already tried it on wine but the only supported version is 2.n
This version does not support .Net 4.*
No, it is not. MonoDevelop is a fork from SharpDevelop precisely because at the time SharpDevelop could not run on Mono, and that has not signifcantly changed since then. In a way, this situation shows the flaw in Xamarin’s strategy of following MS .Net, which is a moving target. But MonoDevelop is useful for whatever is portable in .Net, which excludes MS VB.Net & WPF.
Related
I have just finished my vb.net application and I wanted to compile it with Mac and Linux as well.
I have looked around and found mono project... I tried to use mono to open my application but the GUI is not as it should be. so my question is: there is way to maintain my Gui even on other platform? If not there is an IDE for Mac/Linux that support vb.net? I use Xcode for programming in c but the GUI Builder is so hard to use... There are other simple IDE/Gui Builders?
Of course it will be great if I can build directly from visual studio or with some simple way as well.
Thanks for all future replies.
Mono's VB.NET was not very mature. So you might hit both compiler and runtime issues.
If possible, evaluate and wait for .NET Core.
I'm looking around and I "think" I'm reading conflicting statements about MonoDevelop's ability to support a VB.NET project. Some places say it's not possible yet, and other places say that you can with MonoDevelop V2.10... unfortunately I can't seem to find this elusive v2.10.
Do any of you know if this is currently possible (even if I have to install a beta)?
If you are using MD on Windows, then VB.NET 4 is supported when you compile against .NET 4. VB.NET 4 compiler in .NET 4 installation folder will be used.
If you are working on other OS, then Mono 2.10 is needed, as only since this release Mono's VB.NET compiler starts to support 4.0 profile.
http://www.mono-project.com/Release_Notes_Mono_2.10#VB_Compiler
Is there any way to develop for MonoTouch using VB.NET, rather than C#?
Currently Visual Basic is not supported in MonoTouch, but we plan on adding this to the mix in the future, as well as expanding our language support.
The reason for our lack of support is that in addition to shipping the VB compiler, we have to ship templates and we have to port the VB runtime which currently has many dependencies on desktop features of .NET and Mono.
Currently, C# is the only supported language in Monotouch. Also, Monotouch apps are not your average managed .net assemblies. Monotouch C# code is compiled to native code (similar to Vala)
I don't expect to see VB.Net in Monotouch in the near future - as of now, Miguel and his gang is busy with Monodroid & the Mono framework proper. According to their roadmap, they do have plans to support VB.net in the future. No time-frame has been mentioned.
I might need to write some GUI application that runs on .Net (and Windows), while what I can work with is Mono (on Ubuntu and/or Gentoo). I am very familiar with Python; in addition, I understand that the Mono Windows.Forms assemblies seem to be satisfactorily usable (I've run successfully .Net applications using Windows.Forms).
What are the steps I would have to take to have an environment where I can develop stand-alone IronPython on a GNU/Linux maching? Also, I would very much appreciate some .Net-Mono compatibility pointers (e.g. things I should know or avoid).
I'm not looking for an IDE; I'm quite at ease using vim for my editing purposes, and I don't mind building GUIs programmatically.
Note: what I'm actually asking, is help with the following:
I obviously have to install IronPython; so I make sure my Mono packages are installed, then I run the IronPython installer (using Mono, obviously) just like I would on Windows? Will this make the IronPython assemblies available to Mono? If not, how can I do that? Ubuntu 9.10 has a package for IronPython, but it's not the latest version; at the same time, for compatibility purposes, I can't upgrade the Ubuntu installation. I can't find an ebuild for Gentoo.
Do I have to install any more assemblies?
After I successfully install IronPython, how do I create a .Net/Mono executable from my IronPython sources? Is there a “proper” way?
Is there a way to “embed” the IronPython (and any other required) assemblies in the final .exe?
Check Windows Forms section on IronPython Cookbook for hints about creating Windows Forms applications.
As to the environment, I would write the app in Mono and check it works on Windows. I would set up two virtual machines and any source control system to transfer sources between them.
The key part is to write and run tests so you can verify it works on both platforms. So you cannot use just GNU/Linux machine to be sure. But I think you can install Windows 7 for 30-days trial period.
I used to write WinForms tests so here is link to my blog and several other articles:
GUIAT blog
Acceptance Testing .NET Applications using IronPython
Functional Testing of GUI Applications
IronPython says it requires Reflection.Emit and lightweight code generation. FAQ iOS tends to frown on that kind of thing. So if you want to do iOS, you may be out of luck.
Does anybody using latest enterprise library 4.1 in mono? I used mono migration analyzer to analyze my web application and realized all enterprise library dll is failed in mono.
I need to know is that true that enterprise library 4.1 is not compatible in mono 2.4?
I have an update on this.
Enterprise Library 4.0 now Open Source
I initially played a little with getting EntLib 4.0 to run on Mono:
http://jpobst.blogspot.com/2008/10/smart-client-software-factory-on-mono.html
I don't know if anyone has tried EntLib 4.1. Unfortunately, I know nothing about EntLib other than trying to get that sample to work. It seemed extremely complex.
Probably the best way to find out would be to try running you application on Mono and see if it works.
Ent Lib 4.1 is not mono compatible yet. I will have to switch my plan to not to use it.
As far as I know, Unity is not yet Mono friendly.
Remember that you can always use Moma to check those DLLs.
I think both parties (MS and Novell) need to work closely to address those remaining issues.