MoMA: Changes in 1.2.6 Version

I generally don't make any announcement when I release a new MoMA for the new Mono release. This is because you just click the "Check for newer version" link, which magically downloads the new definition files and life is chock full of rainbows and ponies. However, for the 1.2.6 release, we made 2 important changes to the definition files that warrant a mention.

- Removal of Design Namespaces -
One of our awesome mono-vangelists pointed out that people scan their app (and third party controls) and see all kinds of warnings about things missing in the Design classes. However, these classes are not used to run apps, just for designers such as Visual Studio. So we are potentially scaring off users for no reason. Therefore, beginning with 1.2.6, we no longer include the Design namespaces in MoMA reports. (If you really want the Design stuffs, you can download the definition file that includes them on the MoMA home page.)

- Addition of .Net 3.0/3.5 Classes -
Beginning with 1.2.6, we include the definitions needed to scan your .Net 3.0 and 3.5 apps. At this point, we report everything as missing. Even though we have implemented some of these classes in our Olive project, we do not currently ship this with the released Mono, and MoMA tracks the Mono releases.

So what good is adding the 3.0/3.5 stuffs if we are going to report it all as missing? We will soon be getting to the point where we need to figure out what new stuff to implement next. By scanning your app with MoMA and submitting the missing report, we can see which parts are the most important to our users so we can prioritize. (And yes, we _really_ use this data. MoMA reports have pretty much dictated our prioritization since it was released a year ago.)

- How Do I Get These New Features? -
So how do you get the new stuff? Just click on the "Check for newer version" link in MoMA, sit back, relax, and enjoy the rainbows and ponies. Or if you don't already have MoMA, you can grab it here.

UPDATE: I forgot that the new definitions contained a method signature that MoMA was unable to handle, so you actually DO have to download a new copy from the MoMA home page. Sorry. :/

Comments

Anonymous said…
I downloaded the 1.2.6.1 and extracted it to d:\tools directory on my windows xp professional which has Dot Net 2.0 and 3.0. But, when I run mamo.exe and select a .net assembly it gives me the "No definition files could be found. Please try to download the latest definition file" message.

I also tried using "Check for newer version" it checks and says it is downloading.. but, where??
I still get the "No definitions ....." error (mentioned above). Am I missing something? I just want to run some analysis on the .Net code.

thanks,
unixos@yahoo.com
March 6, 2008 at 1:41 PM
Post a Comment

Popular posts from this blog

Introducing Pinta

Image
Over the holiday break, I stumbled upon this article from OSNews stating that there was a need for something like Paint.NET for Gtk. Having some experience with porting Paint.NET to Mono Winforms before, I knew that that was a massive task. But it still got me curious about Cairo and creating a layered canvas, since I had never played with Cairo or Gtk. After playing around for a few hours, I actually had a working paintbrush and canvas. Intrigued by my success, I played around with it for a few more days. By the end of the week I had a nifty little paint program with a few features. Now, a month later, it's time to open my little project up to the world: Pinta . Pinta is a clone of Paint.NET. It already has a small, but hopefully useful, set of features like multiple layers and infinite levels of Undo/Redo. I hope to implement the same feature set as Paint.NET. Currently there are several tools missing, as well as adjustments like brightness/contrast and levels and Pain
Read more

Mono in Visual Studio 2010

Image
One cool new feature in Visual Studio 2010 is enhanced Multi Targeting . Presumably, its all about allowing developers to target both the 2.0 and 4.0 runtimes from VS2010, but what it really means is you can easily target Mono from within Visual Studio 2010. Like this: To enable this, you need to unzip this file to: C:\Program Files\Reference Assemblies\Microsoft\Framework\.NETFramework\v3.5\Profile Once you do that, you can take your .NET project: Go to project properties and switch it to the Mono 2.4 Profile: Now it will compile using Mono's assemblies, and will flag methods that Mono does not contain, like thus: This also works for Intellisense: And Object Browser: We are very excited about this feature, which should make it easy for people to ensure they are staying compatible with the Mono subset of the .NET framework without leaving Visual Studio. Once VS2010 is released, we will hopefully release the profile packs as we release each Mono version!
Read more

I don't get KDE

Image
Last night while browsing the internets, I saw some screenshots of KDE 4.3 running on openSUSE 11.2. I've never tried KDE, so I installed the openSUSE 11.2 M8 build to briefly play with it. What got me interested was this element of the KDE desktop: I look at that and see hope. It is elegant and refined. It is glassy and tasteful. It says: "I can easily compete with Windows 7 and OSX." Simply put, it is beautiful. Yes, there are some problems with it. The buttons do not highlight in any way on hover. There are no tooltips, so I don't even know what the top two buttons do. From what I can tell, they do absolutely nothing. But it really lives up to KDE's reputation of eye candy. And then you open a window: It is.. gray. There is no glass. There are no gradients. There is no depth. There is no elegance. There is just gray. It says: "I am kicking Windows 95's ass! Barely!" I just don't get it. How can half of your desktop (let's
Read more