Learn how to get the Mono beta up and running for deploying .NET apps to Linux and other platforms.
Using Mono for .NET Linux Development
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
That’s great, but what runs on this? Will an app that was written without Linux compatibility in mind run on Linux? If so, which ones?
Or is this like one of those wine things where only notepad.net runs out of the box?
That’s great, but what runs on this?
Uh? Did you click on the link to read more?
“Or is this like one of those wine things where only notepad.net runs out of the box?”
wine runs much more than that. it ran office 97 out of the box last time i checked. so maybe you should learn more about wine first before you get into mono and please read the article before commenting
i’ve got Wine to run office 2000 out of the box, it didnt particularly like OfficeXP so i opted for 2000 to see if it was supported and for me it works fine on my SuSE 9.0 Box
“why promote a MS technology. ”
regardless of the origin, many of the specs are also an ecma standard and likely to have a major impact. making things interoperate well is important.
if people find this interesting they are bound to do it. i dont think its a good idea to do this but there are obvious advantages
.net wont move very fast and mono already has a alternative linux oriented stack. so there is no problem with being late
well it can be looked at this way. One of the things I hear the most from people who don’t want to try linux is because there are no applications that run on it. If an application is made with .NET then mono can be used for the application to be ported.
Quote:
“don’t said me it’s to increase application under linux, the majority of today development is done with c++ or java.
this language run under more system than .net. ”
Actually, the language C++ might be the same on other systems, but not the api’s.
On windows you can use Win32 and MFC for example.
Programs written with those api function won’t compile on linux or mac, unless there’s a port of win32 (like wine tries to do), or other used api’s.
And .net can be used for that purpose, IF the .net standards on every system remain the same.
Since MS changed some things from 1.0 to 1.1, making some applictions written with .net 1.1 not work with .net 1.0, I hope for people who do want to use mono for system independent development, that the .net standards don’t change a lot anymore.
I think another aspect to this is that when Longhorn is released, .Net will be where it’s at on the Windows platform. “So?” you may ask, “Who cares about Windows?” Well, look at it this way .. in the era of Longhorn, most Windows developers will be using .Net to program with. If they ever wanted to switch to Linux, why not give them something to work with that they already know? I think a jump from .Net to Mono would be easier than .Net to C++ and QT/GTK or Java.
The easiest way to install the Mono beta is to download the zip file that contains all of the RPM files that you need. Once you have unzipped the RPM files, you may try to install each of the individual packages by double-clicking each package to launch the installer, but there may be dependencies or other applications that need to be installed first. The easiest way to install all of the RPM files at once is from the command line.
>
>
Who the heck uses ZIP under Linux for archiving *anything* ?
Tell me again that MONO and the rest of the .NET crap is going to widely adopted by the non-windows world, when the people pushing this crap can’t figure out how or be bothered to use the *standard* Linux archiving tools…
Some people may think this is nitpicking, but to me this says a lot about the mindset of the people pushing MONO and the other .NET garbage.
It’s not meant to benefit Linux and non-Windows systems
users at all.
“I hear the most from people who don’t want to try linux is because there are no applications that run on it. ”
think like a texan … big winner
it’s true that a couple of hundred a thousand of software is not enough
I think another aspect to this is that when Longhorn is released, .Net will be where it’s at on the Windows platform. “So?” you may ask, “Who cares about Windows?” Well, look at it this way .. in the era of Longhorn, most Windows developers will be using .Net to program with. If they ever wanted to switch to Linux, why not give them something to work with that they already know? I think a jump from .Net to Mono would be easier than .Net to C++ and QT/GTK or Java.
>
>
And give *ONE* reason why non-Windows users should care what
Windows developers do?
It’s not as they ever gave a damn about anyone.
It’s not as they ever gave a damn about anyone.
Now that’s a bit short sighted.