• Anyone using Mono?

    From Sam Alexander@VERT to All on Thu Nov 11 09:05:26 2010
    I'm seriously thinking of jumping into Mono development on Linux since we use Visual Studio and C# for all our projects at work. This would hopefully let me get more experience on C# plus what I write will be portable between operating systems.

    Anyone else out there working with Mono or the Mono Develope IDE? I have some ideas of projects I'd like to tackle, but now I just need to find the time :)

    Sam


    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ telnet://vert.synchro.net
  • From Corey@VERT/TSGC to Sam Alexander on Thu Nov 11 09:23:08 2010
    Re: Anyone using Mono?
    By: Sam Alexander to All on Thu Nov 11 2010 09:05 am

    I'm seriously thinking of jumping into Mono development on Linux since we us Visual Studio and C# for all our projects at work. This would hopefully let get more experience on C# plus what I write will be portable between operati systems.

    Anyone else out there working with Mono or the Mono Develope IDE? I have so ideas of projects I'd like to tackle, but now I just need to find the time :

    Sam



    no, but I had it once...

    "Practise safe Lunch, Use a Condiment"


    ---
    ■ Synchronet ■ Three Stooges Gentlemens Club - Las Vegas, Nv - tsgc.dyndns.org
  • From Tracker1@VERT/TRN to Sam Alexander on Fri Jan 14 00:20:08 2011
    Sam Alexander wrote:
    I'm seriously thinking of jumping into Mono development on Linux since we use Visual Studio and C# for all our projects at work. This would hopefully let me
    get more experience on C# plus what I write will be portable between operating
    systems.

    Anyone else out there working with Mono or the Mono Develope IDE? I have some
    ideas of projects I'd like to tackle, but now I just need to find the time :)

    I used it for a kiosk solution a few years ago... mono + gtk-moz-embed, worked out really well for what I was doing. Using a Firebird backend database. Haven't done as much lately, but they've done a fair job of keeping up with many of the changes moving forward (ASP.Net MVC 3 is probably already close to being included on the dev side).

    It made sense for the kiosks, but depends on what you're doing.. I've found for many things on the linux side, it's been easier for me to work with.

    --
    Michael J. Ryan - http://tracker1.info/

    ... FRA #009: Opportunity plus instinct equals profit.

    ---
    ■ Synchronet ■ Roughneck BBS - telnet://roughneckbbs.com - www.roughneckbbs.com
  • From Nightfox to Tracker1 on Wed Jan 19 22:38:54 2011
    Re: Re: Anyone using Mono?
    By: Tracker1 to Sam Alexander on Fri Jan 14 2011 00:20:08

    I used it for a kiosk solution a few years ago... mono + gtk-moz-embed, work out really well for what I was doing. Using a Firebird backend database. Haven't done as much lately, but they've done a fair job of keeping up with many of the changes moving forward (ASP.Net MVC 3 is probably already close being included on the dev side).

    A while ago, I read that Microsoft might start taking action (legal or technical) to prevent 3rd parties from developing their own .NET runtimes. I like Mono, so I hope that doesn't happen.. Have you read about that?

    I think it's a bit unfortunate that 3rd parties, by nature, can't keep up with the official product. It has always seemed like Mono was a step or two behind Microsoft.. When the new versions of the .NET framework come out, the Mono developers need to wait until the technical details are released before they can start developing the equivalent Mono release.

    The idea behind the .NET framework seems similar to Java: To provide a runtime that can be implemented on different platforms; developers can then target the .NET rumtime, and their app will be able to run wherever the .NET runtime is implemented. However, Microsoft only develops their .NET runtime for the various editions of Windows. I can see why Microsoft would feel that it's in their best interest to only develop the .NET runtime for Windows, and as such, I am a little confused about why they created .NET in the first place. Initially, I wondered if Microsoft was going to develop versions of the .NET runtime for Linux and Mac OS X, but that hasn't happened.. so it has been left up to 3rd parties, such as Mono, to do so.

    Around the time when Microsoft first released .NET, I remember reading that Microsoft wanted to start shifting toward a web-based paradigm, where they would start creating versions of their software that could only be used online, via software-as-a-service. It seemed that .NET was part of that plan, and that they (and other software companies) would start developing software with .NET that people would access and use via the internet. Microsoft hasn't done that quite yet (only recently have I started to hear that Microsoft wants to develop a net-only version of MS Office), but I could see how Microsoft might want to do this with .NET, and force customers to use Windows because Microsoft only develops their .NET runtime for Windows.

    Nightfox
  • From Tracker1@VERT/TRN to Nightfox on Tue Feb 15 23:48:28 2011
    Nightfox wrote:
    A while ago, I read that Microsoft might start taking action (legal or technical) to prevent 3rd parties from developing their own .NET runtimes. I like Mono, so I hope that doesn't happen.. Have you read about that?

    FUD... MS has even provided technical and financial support for Moonlight specifically, and released a lot of stuff under a compatible licence (ASP.Net MVC, etc)

    I think it's a bit unfortunate that 3rd parties, by nature, can't keep up with
    the official product. It has always seemed like Mono was a step or two behind
    Microsoft.. When the new versions of the .NET framework come out, the Mono developers need to wait until the technical details are released before they can start developing the equivalent Mono release.

    True, Mono keeps up pretty well on the language features though (C#), and has a lot o libraries that aren't in the box from MS though... I actually prefer VS to Monodevelop, but Mono is a decent option, esp if you are targetting multiple platforms.

    The idea behind the .NET framework seems similar to Java: To provide a runtime
    that can be implemented on different platforms; developers can then target the
    .NET rumtime, and their app will be able to run wherever the .NET runtime is implemented. However, Microsoft only develops their .NET runtime for the various editions of Windows. I can see why Microsoft would feel that it's in their best interest to only develop the .NET runtime for Windows, and as such,
    I am a little confused about why they created .NET in the first place. Initially, I wondered if Microsoft was going to develop versions of the .NET runtime for Linux and Mac OS X, but that hasn't happened.. so it has been left
    up to 3rd parties, such as Mono, to do so.

    It's more about a managed runtime to minimize memory leaks, simplify new deveopment and provide decent ability to interface with system libraries. The platform agnostic nature was an eye toward supporting .Net under other platforms from the beginning... see Windows 8 on ARM for example.. .Net apps are easier to port to native, than other options out of the gate. Silverlight was x-platform from the start. MS released an incomplete learning implementation for OSX, but never finished as dotgnu and mono were both ahead... Though the business decision to stick with windows makes sense from that standpoint.

    Around the time when Microsoft first released .NET, I remember reading that Microsoft wanted to start shifting toward a web-based paradigm, where they would start creating versions of their software that could only be used online,
    via software-as-a-service. It seemed that .NET was part of that plan, and that

    That was when MS was using ".Net" as a term on too many prodects and platforms... Office XP was going to be "Office .Net" for example... it watered down the term. Now it pretty much refers to the languages (mainly C#), the tools Visual Studio, and Microsoft's version of the runtime environment (CLR/CLI)

    they (and other software companies) would start developing software with .NET that people would access and use via the internet. Microsoft hasn't done that
    quite yet (only recently have I started to hear that Microsoft wants to develop
    a net-only version of MS Office), but I could see how Microsoft might want to do this with .NET, and force customers to use Windows because Microsoft only develops their .NET runtime for Windows.

    http://www.officelive.com/en-us/

    Though I really like .Net and C#, I have been doing more research into JS based platforms.. NodeJS, MongoDB etc... starting my new job next week (Director of Development for Inxsol), and my pet project will be working out a
    development infrastructre with multiple VMs running NodeJS/expressjs, MongoDB, RabbitMQ and Postgres... should be interesting as a nvNext of a product in current dev could see that kind of infrastructure behind it... one language front to back. Though postgres is sql, it would be limited to transactional data, mongo would do the heavy lifting.

    --
    Michael J. Ryan - http://tracker1.info/

    ... FRA #261: A wealthy man can afford anything except a conscience.

    ---
    ■ Synchronet ■ Roughneck BBS - telnet://roughneckbbs.com - www.roughneckbbs.com
  • From Nightfox to Tracker1 on Thu Feb 17 07:21:12 2011
    Re: Re: Anyone using Mono?
    By: Tracker1 to Nightfox on Tue Feb 15 2011 23:48:28

    FUD... MS has even provided technical and financial support for Moonlight specifically, and released a lot of stuff under a compatible licence (ASP.Ne MVC, etc)

    Ah, that's cool..

    I actually prefer
    VS to Monodevelop, but Mono is a decent option, esp if you are targetting multiple platforms.

    I really like VS too, but if you're developing on Linux, MonoDevelop might be your only option between the two. I suppose you might be able to run VS on Linux using Wine, but I haven't tried that - I don't know how well VS would run in Wine.

    starting my new job next week
    (Director of Development for Inxsol)

    Congrats on your new job :)

    my pet project will be working out
    development infrastructre with multiple VMs running NodeJS/expressjs, MongoDB, RabbitMQ and Postgres... should be interesting as a nvNext of a

    I haven't heard about NodeJS, MongoDB, or RabbitMQ.. I guess it would be good for me to look into those.

    Nightfox