Quelques nouvelles de Mono: passage de la version 1.2.6 à la version 1.9.0 Preview, Gendarme, MoMA

- Source: http://lists.ximian.com/mailman/listinfo/mono-devel-list ("I can tell you that we jumped from 1.2.6 to 1.9 in preparation for our next release which will be Mono 2.0. See the road map for more details of what that entails ( http://mono-project.com/Roadmap#Mono_2.0 ").

- http://lists.ximian.com/mailman/listinfo/mono-devel-list ("de miguel@ximian.com : "Hey folks, Am assembling the release notes for Mono 1.9, please send me additions, edits, etc:http://www.go-mono.com/archive/1.9")

- http://mono-project.com/Gendarme("Gendarme is an extensible rule-based tool to find problems in .NET applications and libraries. Gendarme inspects programs and libraries that contain code in ECMA CIL format (Mono and .NET) and looks for common problems with the code, problems that compiler do not typically check or have not historically checked.The current Gendarme framework, Gendarme.Framework.dll, is a work in progress. It will probably change a lot before 1.0 is released. It’s main goal is to make it easier to write and test rules. The current Gendarme framework, Gendarme.Framework.dll, is a work in progress. It’s main goal is to make it easier to write and test rules. It requires a C# 3 compliant compiler to compile properly (it works with Mono from SVN and with VS.NET 2008). At this stage we’re not committed to a final API, so things may still change a lot before version 1.0 is released…You can follow the Gendarme’s development discussions on it’s Google Group . This is also where you’ll find the roadmap  to the future versions, (wish)list of todo, rules  proposal and developer documentation. Gendarme’s developers are also IRC (#gendarme on GIMPnet). Source code is available from SVN  (tarball . Since Mono 1.9.0 Gendarme is part of mono-tools and is probably available for your distro (if recent) or from openSUSE Build Service .")

- http://mono-project.com/Moma ("The Mono Migration Analyzer (MoMA) tool helps you identify issues you may have when porting your .Net application to Mono. It helps pinpoint platform specific calls (P/Invoke) and areas that are not yet supported by the Mono project.")

- http://tirania.org/blog/archive/2008/Feb-03.html ("Shawn at CogmationMono is being used as the scripting engine for their robotFoundry application… has written us to notify us that We discovered Mono while we were evaluating 3D engines. Mono was successfully being used to develop video games and it was extremely fast. We performed a small test and compared the speed between Python and C# mono and were shocked at how fast mono was compared to python. In addition to the speed increase and portability, we now had the ability to allow our users to write scripts in any .Net language...")

Le futur proche de DotNet: Mono, VisualStudio 2008, C#3, ..NET3.5, Ironpython2.0, LINQ

Des nouvelles en provenance de:

• http://www.asp-php.net/tutorial/asp.net/linq-1.php ("Cette article est, je l’espère, le première d’une série que j’ai décidé de nommer « LINQ et vous ». Force est de constater que dans la lignée de mes articles précédent relatifs au .NET Framework 2.0 et Visual Studio 2005, nous avons toujours dans cette nouvelle version une convergence de plus en plus forte des langages et outils de développements associés…")
• http://www.asp-php.net/tutorial/asp.net/linq-2.php?page=1 ("L’objectif est toujours de nous amener pas à pas vers la finalité de l’évolution du .NET Framework en version 3.5. Poursuivons ainsi notre découverte du .NET Framework 3.5 et de son écosystème !")

Les principaux enseignements de ces billets:

• Les versions de Framework et de la CLR ne sont pas pas associés. Entre 2005 et 2008 c’est toujours la machine virtuelle CLR V2.0=="Vous pouvez ainsi faire évoluer aisément vos applications actuelles vers les nouvelles librairies du .NET Framework 3.0 ou 3.5"
• les nouveautés des langages viennent non pas de la modification de la CLR mais des demandes des développeurs pour le développement de LINQ
• "Les évolutions du .NET Framework de la version 2.0 à 3.5 peuvent être en quelque sorte considérées comme des ajouts de nouvelles librairies basées elles-mêmes sur le .NET Framework 2.0 et de ce fait la CLR 2.0.
• Les projets Visual Studio 2005 sont récupérables sans migration dans Visual Studio 2008.
• Visual Studio 2008 vous permet de sélectionner la version du .NET Framework que vous souhaitez cibler pour chaque projet mais plus encore de modifier cette cible à tout moment !

Historique de .Net Framework

Source: http://www.asp-php.net/tutorial/asp.net/linq-2.php?page=1

"Voici pour rappel, quelques dates clés :

• 2002 : .NET Framework 1.0
• 2003 : .NET Framework 1.1
• Fin 2005 : .NET Framework 2.0
• Fin 2006 : .NET Framework 3.0
• Fin 2007 (début 2008) : .NET Framework 3.5"

Autres sites à consulter

• Le framework .Net (http://en.wikipedia.org/wiki/Microsoft_.NET)
• La bibliothèque de base (http://en.wikipedia.org/wiki/Base_Class_Library, "The Base Class Library (BCL) is a standard library available to all languages using the .NET Framework. In order to make the programmer’s job easier, .NET includes the BCL in order to encapsulate a large number of common functions, such as file reading and writing, graphic rendering, database interaction, and XML document manipulation. It is much larger in scope than standard libraries for most other languages, including C++, and would be comparable in scope to the standard libraries of Java")
• C#3 (http://en.wikipedia.org/wiki/CSharp#C.23_3.0_new_language_features, "C# 3.0 is the next version of the language as proposed by Microsoft. It includes new features inspired by functional programming languages such as Haskell and ML, and is driven largely by the introduction of the Language Integrated Query (LINQ) pattern to the Common Language Runtime")
• Ironpython ("http://en.wikipedia.org/wiki/IronPython , Ironpython is an implementation of the Python programming language, targeting .NET and Mono, created by Jim Hugunin. Version 1.0 was released on September 5, 2006. The current 1.1 version targets CPython 2.4.4 for compatibility. However, there are some differences between the Python reference implementation and IronPython.[1]. Release 2.0, currently in alpha state, targets CPython 2.5. IronPython 2.0 is built on top of the Dynamic Language Runtime which contains a Dynamic Type System and Dynamic Language Hosting Environment abstracted out of IronPython 1. The DLR runs on top of the core CLR that ships with Microsoft Silverlight. This means that IronPython can be used for client-side browser scripting with Silverlight.")
• DLR (http://en.wikipedia.org/wiki/Dynamic_Language_Runtime , "The Dynamic Language Runtime (DLR) from Microsoft is a set of services that run on top of the CLR and provides language services like:
• Dynamic type system
• Dynamic method dispatch
• Dynamic code generation
• Hosting API. It can be used to implement dynamic languages like PythonRuby on the .NET Framework. The DLR services are used in IronRuby, a .NET implementation of the Ruby language, IronLisp, a .NET implementation of the Lisp language, IronPython 2.0, dynamic Visual Basic .NET (VBx) and Managed JScript (ECMAScript 3.0)"

• LINQ (http://en.wikipedia.org/wiki/Language_Integrated_Query , "Language Integrated Query (LINQ), pronounced "link", is a Microsoftsyntax reminiscent of SQL to .NET Framework programming languages, initially to the Visual Basic .NETC# languages. Many of the concepts that LINQ has introduced were originally trialled in Microsoft’s Cω research project. LINQ defines project that adds a native querying and standard query operators that allow code written in LINQ-enabled languages to filter, enumerate, and create projections of several types of collections using the same syntax. Such collections may include arrays, enumerable classes, XML, datasets from relational databases, and third party data sources. The LINQ project uses features of version 2.0 of the .NET Framework, new LINQ-related assemblies, and extensions to the C# and Visual Basic .NET languages. Microsoft has distributed a preview release of LINQ, consisting of those libraries and compilers for C# 3.0 and Visual Basic 9. LINQ is planned for release with the ‘Orcas‘ version of Visual Studio 2008. [6] The release date for Visual Studio 2008 has been announced by Microsoft as February 27, 2008.")

• Mono (http://en.wikipedia.org/wiki/Mono_%28software%29, "Mono is a project led by Novell (formerly by Ximian) to create an Ecma standard compliant .NET compatible set of tools, including among others a C#compiler and a Common Language Runtime. Mono can be run on Linux, BSD, UNIX, Mac OS X, Solaris and Windows operating systemsAug 29, 2007). This version provides the core API of the .NET Framework as well as partial support for C# 2.0 and Visual Basic.NET. Support for the 2.0 APIs is partial at this point (core, ADO.NET and ASP.NET) but other components like Windows.Forms are not yet complete. Complete support for the .NET Framework 2.0, including the .NET 2.0 version of Windows.Forms, is planned for Mono 2.2, by the end of 2007.Implementation of .NET Framework 3.0 is under development under an experimental Mono subproject called Olive, but the availability of a Mono framework supporting .NET 3.0 is still not planned yet. An open source implementation of Silverlight called Moonlight is now underway. Parts of it are in the core of Mono, parts are implemented as part of the Olive components. As stated by Miguel de Icaza, Moonlight will ship as part of Mono 1.2.6 release)

• Visual Studio 2008 : http://msdn2.microsoft.com/en-us/vstudio/aa700830.aspx
• .NET Framework 3.5 http://www.microsoft.com/downloads/details.aspx?familyid=d2f74873-c796-4e60-91c8-f0ef809b09ee&displaylang=en

Les fils de syndication

• Miguel de Icaza (http://tirania.org/blog/miguel.rss2)
• Mono project news (http://www.mono-project.com/news/index.rss2)
• The server side news (http://www.theserverside.net/rss/theserverside-rss2.xml)
• Seo Sanghyeon (http://fepy.blogspot.com/feeds/posts/default?alt=rs)
• The Code Project Latest Articles (http://www.codeproject.com/webservices/articlerss.aspx?cat=1)
• CodeBetter.Com (http://codebetter.com/blogs/mainfeed.aspx)
• unethical blogger (http://www.unethicalblogger.com/rss.xml)
• IronPython URL’s (http://ironpython-urls.blogspot.com/feeds/posts/default?alt=rss)
• InCisif.net (http://blog.incisif.net/atom.aspx)