Scott Hanselman

Mono 1.0 was just released

July 01, 2004 Comment on this post [2] Posted in ASP.NET | DasBlog | Bugs
Sponsored By

Congrats to all! Anyone out there running their dasBlog on Mono?

Mono is a comprehensive open source development platform based on the .NET framework that allows IT and ISV developers to build Linux and cross-platform applications with unprecedented productivity.

Mono's .NET implementation is based on the ECMA standards for C# and the Common Language InfrastructureMono includes a compiler for the C# language, an ECMA-compatible runtime engine (the Common Language Runtime, or CLR),and class libraries. The libraries include Microsoft .NET compatibility libraries (including ADO.NET and ASP.NET), Mono's own and third party class libraries. Mono's runtime can be embedded into applications for simplified packaging and shipping. In addition, the Mono project offers an IDE, debugger, and documentation browser.

If you have questions about the project, read the project launch statement or visit our list of Frequently Asked QuestionsFor details on the project's future direction, read the roadmap, and download Mono 1.0.

About Scott

Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.

facebook twitter subscribe
About   Newsletter
Hosting By
Hosted in an Azure App Service
July 01, 2004 22:51
Scott, the stock dasblog uses the Win32 registry, so isn't portable to *NIX. Jackson Harper has done a port of an old revision (I think it's 1.2.x) available at that works quite nicely on mono.
July 05, 2004 2:43
we are having tons of fun with Mono last few days. *very impressive*. btw if any .NET developers here think they have to have Linux to try Mono, its not true - Mono includes Windows build. If you want to compile for Mono from VS.NET: get NAnt, get NAntContrib, add one 'slingshot' task, follow it with XSLT task which which converts all references path from .NET to mono (e.g. "...Microsoft.NET\Framework\v1.1.4322\" -> "...Mono-1.0\lib\mono\1.0" ) and you done! With this setup you can keep working as usual on VS.NET and having automatic mono build when you need it.

It was sureal expirience building our core communication suite (Remoting, System.Data, XML, Collections.Specialized, tons of other stuff - virtually eveyrhting you ever need on server side) and lunched our server on Mono for first time. to everybody surprise it started flawlessly communicating with existing .NET clients. One of my devs IMed me "Do you realize we are not running a single line of Microsoft code at the moment?". Amazing!

Comments are closed.

Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.