NoMachine NX is a very good remote desktop application, with several free and open source implementations of the NX protocol. It – either in the form of the official NoMachine NX client or the FreeNX client – has long been my first choice when I need a remote GUI.

Now it looks like the upcoming 4.0 will kill that for new versions, meaning the FLOSS versions of NX will likely remain with version 3 of things. Which in turn makes me fear NX is soon to be dead for FLOSS.

It’s a bit uncommon to see previously open source projects taken closed source, so it will be interesting to see how this plays out.

Attachmate Acquisition: What does it mean for SUSE, openSUSE & open source?

—A Q&A with Jeff Hawn, chairman and CEO of Attachmate by Jos Poortvliet, openSUSE Community Manager at Novell

I had a chance to speak with Jeff Hawn, chairman and CEO of Attachmate Corporation about his views and intentions around SUSE and openSUSE. Jeff has commented that SUSE is an important brand and business that he wants to strengthen. What are his thoughts about the community and what does he see for SUSE and openSUSE? Here below are the questions I put forward and Jeff’s current thoughts. —Jos

Open Source

What is Attachmate’s history with open source projects?

Attachmate does not have a corporate track record in the open source business. However, we recognize the importance of open source technology, particularly Linux, and the growing value it brings to enterprises globally. We also recognize and value the openSUSE project, the contribution that the community makes to the SUSE business and most importantly, the many ways in which the community benefits SUSE customers.

At the end of the day, we are a technology company that is customer-driven, made up of engineers and technology enthusiasts. We have a lot of individuals that are long-time users of open source and participants in the open source movement. We recognize and understand what the community has developed, particularly over the last decade, and we are excited to be part of its future.

What is Attachmate’s view of open source software?

Attachmate recognizes that enterprises all over the world are utilizing more open source technology in their infrastructures, data centers and desktops every year. We believe this is a trend that will continue and that’s why we are excited about the Open Platform Solutions business and in particular, the SUSE Linux community.

It is easy for people to assume that because we are not currently in the open source business, we don’t value or understand it. This is far from the case. We are in the business of meeting customer needs and they see great value in utilizing open source technology solutions. Because of its open nature, open source is being adopted by enterprises in all industries around the world. Our intent is to keep it that way and continue to foster what has made it so successful for the Open Platforms Solutions business.

SUSE

Ok, then what is the plan for SUSE?

We cannot speak to specifics until after close, but what we can communicate now is our intention to establish a SUSE business unit on par with the existing Attachmate and NetIQ business units. We believe that establishing SUSE as its own business unit will give greater focus and flexibility to grow within a competitive market. We view SUSE as a well regarded and proven technology in the open source and enterprise Linux community and we want to further build upon that. We intend for SUSE to continue to provide the same high quality open source technology solutions, such as SUSE Linux Enterprise Server, needed to meet users’ demands for scalability, interoperability and cost effectiveness.

What will the SUSE business unit be – what do you mean by “business unit”?

A business unit brings together all the resources, IP, people and infrastructure needed to operate – to build product, deliver solutions and support customers. So, what is known today as Open Platform Solutions will now be centralized within the SUSE business unit. In most respects SUSE will continue to operate as it did as OPS, but will benefit from being a dedicated and more visible brand with a focused business unit behind it.

Does Attachmate intend to immediately sell the SUSE business?

I want to be clear here: all of our efforts will be focused on doing the things necessary to make SUSE the highest performing business with the strongest openSUSE community that we can. This is a healthy, growing dynamic business. We want to continue to nurture this business and grow it. This is why we want to elevate the SUSE brand and operate that part of the business as a distinct unit where it will receive greater visibility and focus.

How do you plan to compete in the Linux market?

We’re excited about SUSE because of the great competitive advantages it already has. With thousands of certified ISV applications, the best interoperability and unsurpassed scalability, it provides the best value and the lowest cost of ownership on the market. Attachmate intends to continue that commitment to high quality and cost-effective solutions.

What are your intentions for open source initiatives sponsored by Novell today?

No decisions have been made regarding any specific projects or sponsorships. Much more integration work needs to happen before discussions of changing the status of individual projects can occur. But we can say that the new SUSE business unit will stay committed to participating in the projects and initiatives that are most important to the SUSE business and its customers.

Will Attachmate continue to support Linux kernel development by employees as Novell has done?

Yes, we will. Key contributions to the Linux kernel are a benefit to everyone in the community. This sort of contribution is a key element of what makes the synergy between business and open source so successful and we intend to continue support it.

openSUSE

Will Attachmate increase or decrease the investments in development and marketing for openSUSE?

There is a lot of integration work to do before those decisions are made and some of that work cannot be done until after the transaction has closed. Our intent is to continue to sponsor and participate in the openSUSE project.

Will this impact the initiative to create an independent foundation for openSUSE?

No decisions on this initiative have been made. This is a complex topic that has been actively debated in the community for some time. We look forward to continuing that discussion with the community after the close of the transaction.

Will Attachmate continue to support the openSUSE conference?

No decisions have been made about the ongoing sponsorship of openSUSE conference. It is simply too early to reach conclusions on specific areas such as this – more integration work and collaboration with the SUSE team is needed. Our overall intent is to maintain the continuity of success we see within the SUSE business and that includes continuing to work closely with the openSUSE community.

Will the acquisition have any other effects on the openSUSE project or community?

We look forward to learning more about the project and working together with the community to figure out what’s working well, what could be done differently or improved. This will be a highly collaborative relationship.

Does Attachmate intend to shut down the openSUSE community project?

No, we don’t. Attachmate intends to continue the sponsorship and collaboration with the openSUSE project. We view the openSUSE project and its extended community as an important part of the overall SUSE business and we value its contributions to the technology that forms the heart of the SUSE offerings (see related statement on the Attachmate website here).

Intellectual Property

What IP assets are being purchased by CPTN Holdings LLC?

Attachmate cannot provide details on the IP assets being purchased, but we can clarify that CPTN is NOT purchasing products. They are purchasing 882 patents and patent applications as described in the initial 8-K filed by Novell.

The purchase does not include the Novell UNIX copyrights (see related statement on the Novell website here). It does not include the product source code or product implementations.

Attachmate would not buy a company and not preserve what is working nor hamper our ability to operate this business. So, SUSE will retain all the technology, rights and IP needed to continue and grow.

Does the purchase by CPTN Holdings impact the openSUSE project or the SUSE enterprise business?

After the merger is complete, the SUSE business unit will retain all the IP and technology rights needed to operate, continue its sponsorship of the openSUSE project and supporting SUSE customers.

What happens to the Novell UNIX copyrights after the sale of IP assets to CPTN Holdings?

No change. The purchase of IP assets by CPTN Holdings does not include the UNIX copyrights and the copyrights will continue to be owned by Novell (see related statement on the Novell website here).

Take it for what it’s worth, I guess. I’d say it doesn’t look good for the Open Source projects, especially those with no direct profitable application, but I take a cynical view of such press releases.

Consider the retardation of the question “Does Attachmate intend to shut down the OpenSUSE community project” – it’s not like Attachmate could do such a thing, even if the wanted to. What they could do (and what I suspect they eventually will do) is adopt the same sort of “relationship” with external communities that Oracle does: basically, do exactly what we want, how we want it, and we still won’t support you in any way whatsoever of import.

I’m dying to find a copy of the “Exhibit A” that lists the 882 patents – it is referred to in several SEC filings, but the exhibit itself is not available as far as I can tell.

My favorite bit: the “intention to establish a SUSE business unit on par with the existing Attachmate and NetIQ business units”. And since we all know how the existing Attachmate and NetIQ business units have lit the Linux world on fire with innovation and contribution, this can only be a fantastic development.

Oh Twitter User, It’s So Cute When You Try

So, as I parsed my enormous referrer logs, populated only with visits by Distinguished Guests of the Highest Caliber, I noticed some incoming Twitter traffic. Imagine my shock when I found someone defending Mono on Twitter! Then imagine my utter disbelief when I found that same someone – brace yourself – had their facts wrong! Why I nearly succumbed to the Vapors that Very Moment!

A shock I know, but steel yourself, Gentle Reader, as we journey forth again…(and to seven hells with Twitter for not having an easy-to-use threaded conversation view. I’ve often said this is because no one is interested in having a real conversation or discussion there. Twitter: Proof that a terrible UI is no bar to massive success.)

plaimbock: #ubuntu 11.04 switches to #banshee http://is.gd/i7avD but what about the #MCP/patent issues? pixie dust made them vanish? http://is.gd/i7aUx

trampstr: @plaimbock Their are no patient issues, Banshee is covered a legally binding “community promise” not to sue

trampstr: @plaimbock maybe you missed it but the work to cut back the size of the banshee install for 11.04 removed all non EMCA components. Its safe.

trampstr: @plaimbock http://bit.ly/e81pnr <- commit that removed all non emca components.

Of course, those who are paying attention in class already know the problem, but I’ll point it out here for anyone just joining us:

• Banshee is not covered, in any sense.
• All of the non-ECMA components were not removed.
• That commit doesn’t remove all the non-ECMA components.

3 tweets, every one of which is totally, 100% wrong presented as casually as you like without disclaimer, explainer or retainer.

Let me also note there is also an important distinction to be made between “Banshee is covered” and “Mono is covered”. If applications were directly being covered, then we wouldn’t care if Mono or Logo or Any Other Language were being used. But the Community Promise is applied to the C#/CLI implementation, which means it is Mono that the application developer is relying on to be safe within the confines of the Microsoft Community Promise.

In effect, the Mono project and its promoters are making a promise to application developers and users: “Use Mono to develop your applications, it’s useful and safe. Microsoft has made a promise.” The implication is that developers and users need not be concerned with verifying they are remaining withing the boundaries of Microsoft’s promise. But, this sort of Mono Apologist violates that trust by not only implementing things they know are not covered by the promise, but also by obfuscating which bits are “safe” and “unsafe” and then lying about it.

That’s a whole different thing than being honest and saying something like “Mono may be risky, but we think it’s useful and not too risky.” Nothing wrong with this premise, because I believe rational people can evaluate the level of acceptable risk differently. (Team Apologista has a problem here in how they argue it, but the premise is a decent enough starting point.)

So, the original questioner has been misled. Perhaps not maliciously – but misled nonetheless. Of course, there’s more:

plaimbock: @trampstr: what about this report that #banshee, tomboy, f-spot and #mono use non-ECMA namespaces? http://is.gd/iEe7Z

trampstr: @plaimbock thats old info, also it lists System.Xml as non EMCA but it is in ECMA335.

Um, no – it is not “old info”. Unless you consider the last 2 days “old”. The source code repository is ~2 days old, and the ECMA standard is the released-this-month 5th Edition. Any more up-to-date and it would be realtime. Furthermore, while parts of System.Xml are now in the standard, the commonly used methods by the Mono apps do not appear to be - as I explitictly mentioned in the “Cautionary note” in my post. The System.Xml thing is legit.

How do you combat this? One tries to be careful in researching and fact-checking – no-one is forthcoming with easy, available or comprehensive references in this area, after all – and yet any random jackass on Twitter will authoritatively deny something even when looking right at it! Is this person a liar? Incompetent? Lazy? Just repeating shit he read on some Mono Cabal Talking Points Memo? All or none of the above?

And of course, the final delight, an amazingly un-self-aware twit tweet :

trampstr: @plaimbock there are very strong opinions on both sides. and lots of miss information going around (from both sides).

FUUUUUUUUUU! YOU! YOU! You are the one spreading misinformation! Gah!

Aaaanywaaay

The good news is: now that it is clearly documented that:

• All of the most popular Mono applications in Linux use non-ECMA .NET namespaces extensively
• Mono is not split into ECMA/non-ECMA packages in Debian/Ubuntu, and probably not in any other distro either

I am supremely confident that we will never again hear another argument from a Mono Apologist suggesting otherwise. I also fully expect those very vocal Mono Apologists who manage to appear in every thread to defend Mono and may have stated or implied different, to go back and correct themselves so they don’t continue to mislead others. After all, I know factual accuracy is of the highest concern.

I am also expecting Swedish Triplets and a Lamborghini Spyder Performante for Xmas.

Which do think is more likely?

The Claim

One of the common claims of the Mono proponent is that distribution packagers are splitting Mono into ECMA and non-ECMA packages. Debian and/or Ubuntu are commonly held up as examples in this area.

This always seemed a questionable claim to me: for one thing, it’s not easy to determine exactly what bits go where, and to be frank who has the time to screw with that? Also, there are a host of technical considerations – what if they conflict somehow? Furthermore, how will users know which packages are “safe” or “unsafe”? And, as we have seen, all the Mono apps need “unsafe” stuff anyway – so why bother splitting things up?

Also, without being crass about things – I don’t think that most Mono proponents’ top priority is the safe/unsafe distinction. Generally, it seems to me, if you are supporting Mono, you are in for a penny in for a pound and not too concerned over nuance unless forced to discuss it by raging freetard zealots such as myself. We all have our special roles to play.

Enough setup — I thought I might check out a package and see if we can accept or reject the claim that some distribution packagers are splitting Mono into ECMA and non-ECMA pacakages.

The Exam

Now we do have some Debian packages like libmono-system-data2.0-cil and libmono-winforms2.0-cil, so a casual glance might suggest that there is some ECMA/non-ECMA division going on.

On that note, I took mscorlib.dll from the Debian package libmono-corlib2.0-cil (2.6.7-3). This is the “Core Library of Mono for CLI 2.0″, and as far as I can determine absolutely required for any Mono whatsoever on your system.

[jason@apollo 2.0]$ egrep -I -a -o 'S.y.s.t.e.m.............................' mscorlib.dll | sort | uniq
SystemSystem.Data1S
System Operators/BUI
System, Version=2.0.
System.Attribute.}e
System.Byte.!Value t
System.Char
           utf32QTh
System.Core, Version
System.Data, Version
System.Data.OleDb.Ol
System.Data.SqlClien
System.DateTimefile
System.DecimalCInval
System.Decimal.Parse
System.Design, Versi
System.Diagnostics.E
System.Diagnostics.P
System.DirectoryServ
System.DoubleUDouble
System.Drawing!Syste
System.Drawing, Vers
System.Drawing.Desig
System.Drawing.Print
System.Guid.CompareT
System.Int16ArraySu
System.Int16;Value i
System.Int32s%Value
System.Int64qInput s
System.Messaging, Ve
System.Messaging.Mes
System.Net.DnsPermis
System.Net.SocketPer
System.Net.WebPermis
System.NonSerialized
System.Reflection.As
System.Resources.Res
System.Resources.Run
System.Runtime.Compi
System.Runtime.Inter
System.RuntimeType)S
System.SByte.7Value
System.Security, Ver
System.Security.Cryp
System.Security.Perm
System.Security.Poli
System.Security.Supp
System.SerializableA
System.ServiceProces
System.Single.9Value
System.Text.CP5CodeP
System.Text.ENCCEnco
System.Type are not
System.UInt16.5Value
System.UInt32.Negat
System.UInt64.7Value
System.Web, Version=
System.Windows.Forms

What’s this!? System.Data? System.Drawing? System.Windows.Forms!?!

The Verification

So, it appears that there are non-ECMA bits even in the “most basic” Mono library. At this point, I was pretty sure we could reject the claim.

However, even in my freetarded factfinding frenzy I wanted to be sure, so I did something absolutely insane: I asked Jo Shields about it. (In case you don’t know, Mr. Shields packages Mono for Debian and Ubuntu.)

Mr. Shields was kind enough to respond, and here’s the summarized deal:

1. ECMA/non-ECMA is not a consideration in packaging Mono.
2. No distribution ships Mono with ECMA-only components.
3. It is not possible to do so without “deep surgery”.
4. Splitting along ECMA/non-ECMA lines is not a priority.

So, we can reject the claim that distribution packagers are splitting Mono into ECMA/non-ECMA components.

The Thank You

My sincere thanks to Jo for taking the time and effort to reply.

The Unredacted Email

At Mr. Shield’s suggestion, here is the unredacted email (which contains my original email), so everyone can get context and judge for themselves. I suggest reading it if you are interested in more about the packaging details behind Mono.

On Mon, 2010-12-13 at 14:43 +0900, Jason Melton wrote:
> Jo,
>
> Your favorite zealot here. I'd like to ask some questions on a Mono
> Packaging issue before I write a post about it. I want to do this so I
> have "asked someone in the know" as well as offer you an opportunity
> to respond if you desire in the post itself.
>
> If you want me to F off and not bother you again, I'll respect that, of course.

For actually asking me the question, I'm happy to answer fully. It's
more than Roy's ever done.

> Anyway, on to the questions:
>
> 1. Is the Debian Mono packaging split into ECMA / non-ECMA components?

It's split into a hundred odd packages, but no, ECMA/non-ECMA isn't a
consideration - the only consideration is minimizing dependency chains
whilst retaining usefulness (and reducing circular dependencies), and
grouping related items. As an example, a minimal install (mono-runtime
plus its dependencies) pulls in four library packages, containing the
following assemblies:

libmono-corlib2.0-cil:
mscorlib.dll

libmono-posix2.0-cil:
Mono.Posix.dll

libmono-security2.0-cil:
Mono.Security.dll

libmono-system2.0-cil:
System.Configuration.dll
CustomMarshalers.dll
System.Management.dll
System.Transactions.dll
System.Drawing.dll
System.Xml.Linq.dll
System.Xml.dll
System.Core.dll
System.Security.dll
System.dll
System.ServiceProcess.dll
System.Configuration.Install.dll

So these assemblies are the unavoidable minimums installed on a current
system (Ubuntu Maverick). But they cover most situations outside
compilation, where we pull in the kitchen sink in order to provide
simpler Build-Depends lines. And if you aren't aware, note that assembly
names do not necessarily match the namespaces provided therein. Whilst
it would be possible to chop things out of libmono-system2.0-cil to make
a pure-er (although likely not completely pure) minimal system, I think
the benefits to our users would be minimal, and the cost in terms of
awkwardness on upgrades high.

> 2. If there is a split is it an official policy?

See above

> 3. If there is a split is it comprehensive/complete or in
> progress/trying-our-best-but-not-100%-just-yet-for-whatever-reason?

See above-er

> 4. How could a non-packager determine which bits should go where and
> verify that the packaging is correct?

As I said, the concern is really just over minimizing chains of
dependencies, so what makes us sit up and make changes is cases where
pulling in an extra library leads to pulling in several more - that's a
scenario we want to avoid. As an example, when attempting to attack
Banshee with a scalpel (the changes noted in the current Natty package),
we found two instances where depending on a single library would pull in
buckets more random stuff. Using System.Data pulled in the
libmono-system-data2.0-cil package - but one of the rarely-used
assemblies in that package pulled in libmono-wcf3.0-cil and all ITS
dependencies, bloating things up. Our solution was to split the "bad"
assembly into a new package (will be in Mono 2.6.7-4), Banshee
upstream's solution was to drop System.Data entirely (already in the git
snapshot in Natty).

The other example is the Youtube extension using the google-gdata
packages (which contain about 14 assemblies for managing various Google
web services), one of which uses System.Web. Banshee upstream provided
us with a minimal patch to remove that dependency, by copying a little
of Mono's source code (GData upstream already did this to provide
missing namespaces on the Microsoft.NET Compact Framework, so we just
added one or two missing methods and removed the ifdef).
libmono-system-web2.0-cil suffers from a similar, but sadly unavoidable,
chain of dependencies which we sought to cut off. Due to obtuse Windows
line-ending issues, showing you the patch wouldn't be meaningful or
interesting.

So now Banshee's dependency list isn't much different from Tomboy or
gBrainy. See http://people.ubuntu.com/~hyperair/banshee-dep.png for the
visual version of the above.

> 5. When I examine mscorlib.dll I see references to non-ECMA components
> such as System.Data and System.Drawing. [1] Does this mean that
> mscorlib.dll (from the Debian package
> libmono-corlib2.0-cil_2.6.7-3_all.deb) contains non-ECMA components?

Congratulations for being the first Mono critic (AFAIK) to notice this.
I was going to blog on this topic at some point, once finishing my
current secret Project Marmoset.

You're correct. ECMA 335 defines HOLY SHIT. They updated it to .NET 4.0!
That's news to me that is! You'd have thought Miguel would have blogged
about it. Damn, now I need to restart Project Marmoset.

Sorry. Anyway, the currently MCP'd version of ECMA 335 (4th edition,
2006) defines 331 different classes, with 617 properties and 2097
methods, split across System.dll, mscorlib.dll, System.Xml.dll, and
System.Threading.Parallel.dll. Not every namespace in those assemblies
is defined in the ECMA spec - the spec covers individual methods and
properties on individual objects, each one needing vetting one by one by
the standards committee.

So the current (okay, not current, I'm on 2.6.7 here) Mono
implementations of the named libraries contain:

mscorlib.dll: 1085 classes, 13438 methods, 3213 properties.
System.dll: 822 classes, 8644 methods, 3109 properties.
System.Xml.dll: 240 classes, 5384 methods, 2158 proprties.

I should stress that I'm relying on grep for numbers here, so I don't
know how much autogenerated noise is included in the monodis output.
Probably plenty, but even with that it's clear that the implemented
methods & properties exceed the ECMA methods and properties. And no, I
don't know where System.Threading.Parallel.dll is either. And yes, I
know that the Community Promise needs everything in the spec to be
implemented. Go figure.

FYI, ECMA 335 5th edition increases the number of ratified classes from
331 to 374, properties from 617 to 651, and methods from 2097 to 2319.

> Obviously, I think that the package contains non-ECMA bits and want to
> point this out as a counter argument to those who say that Mono is
> split into "safe"/"unsafe" bits by distro packagers and often use
> Debian/Ubuntu as an example.

As far as I can tell, most people consider some technologies
more dubious than others - System.Windows.Forms or System.Data is
hairy, whereas a non-spec method on the String class doesn't make
everybody leap in fear. Whether that's naive is the topic for a
different flame war, I suspect.

So it's true that we have distinct packages for the "scary" bits like
System.Data versus "less scary" stuff like mscorlib.dll, but it is
absolutely true to say that no distribution ships a Mono framework with
ECMA-only components, and it's not possible to do so without deep
surgery on the class library, requiring a lot of man hours. Which is
time Miguel would rather get his guys to invest in MonoDroid or
MonoTouch. Completely hypothetically, I think using the monolinker tool
from MonoTouch (which creates custom minimized versions of the class
libraries on a per-app basis) to turn a "full" Mono into an ECMA-only
Mono would be a faster route to the stated goal, but I have no idea
what would run, and no idea whether monolinker would be prepared to
chop off that much stuff. Would sure be interesting though, wouldn't it?

> I'm trying to get your input so I can be sure of my facts and to
> present "the other side". It's the first time I've tried such a thing,
> so your response is much appreciated. If it helps I can send you a
> copy before I post it so you know I don't quote you out of context or
> anything shady like that.

Whilst I think we disagree pretty strongly about comparative risk, your
dedication towards accuracy in this matter is appreciated. I don't
think anything I've written here is incorrect, so I don't want you to
feel you need to provide me with your intended blog post in advance. If
I'm wrong, I'm sure corrections will appear in comments. And wrong or
right, people like gnufreex will call me Satan, so there's not much
advantage to advance copy.

I think the question of context would be best served by providing
readers access to all emails unredacted, so they (pro or anti Mono) can
form their own opinions on context.

> [1] Basically: egrep -I -a -o 'S.y.s.t.e.m....[lots of dots]...' mscorlib.dll

Try using "monodis", which decompiles .NET code to MSIL (or whatever
they're calling it today). A cursory examination suggests there are
mentions, but not dependencies. Stuff like InternalsVisibleTo, at a
guess, which gives those assemblies access to non-public content inside
mscorlib. I can't read MSIL, so I'm largely guessing. If there were a
true dependency, the packaging would pick up on it.

I usually listen to The Adam Carolla Show - which is great by the way,  check it out – and it recently picked up Bing as a sponsor. This means the host usually does a short “live read”  where they read ad copy about the product (or in Adam’s case he may go off on a crazy rant tangent in the middle of the ad).

The funny thing I noticed: “Microsoft” is never mentioned. It’s all copy about a “decision engine” or a “next-generation search engine” or similar, but it’s been about a week or so and you’d never know by listening that Bing was from Microsoft.

It just makes me wonder if Microsoft realizes its brand is so bad that it is intentionally downplaying the name.

You’ll often hear Team Apologista (when cornered) say something like: “Maybe not all of Mono is covered by the ECMA standard, but all the bits used in Linux programs are.” (Here’s just one example from the recent Reddit thread, but like all Team Apologista arguments, you’ll see a similar talking point repeatedly.)

Now of course, we know that is simply not true – System.Data was used in Banshee at least until very recently, but let’s dive deeper.

Does the claim that “All of the pieces of Mono that are used in Linux apps are covered by the MCP.” hold up under examination?

Non-ECMA Namespaces

According to Wikipedia, here is a list of BCL namespaces that are not part of the ECMA standard:

System.CodeDom
System.ComponentModel
System.Configuration
System.Data
System.Deployment
System.DirectoryServices
System.Drawing
System.EnterpriseServices
System.Linq
System.Linq.Expressions
System.Management
System.Media
System.Messaging
System.Resources
System.ServiceProcess
System.Timers
System.Transactions
System.Web
System.Windows.Forms
System.Xml

Note that this is only Base Class Libraries not a part of the ECMA standard – there may be other .NET namespaces Mono implements that are also not covered by ECMA. However since I don’t think Team Apologista will be forthcoming with a comprehensive list, nor do I think it will be necessary to do so in order to prove the point here, I see no need to search them out at this time. That being said, if someone feels motivated to do so, I would be very interested in seeing the results!

Cautionary Note: The Wikipedia list appears to be up to date, but if you like you can verify against this .zipped XML file on the Microsoft ECMA C# and  Common Language Infrastructure Standards page. However, when checking it myself I think there may be some System.XML stuff that is part of the standard. I did check for more specific entries that the Mono apps use, such as System.XML.Serialization, System.XML.XPath, System.XML.Schema and so forth, and did not see them in the standard. So, I’m leaving that bit in for now.

UPDATE 2010.12.15: Since System.Xml is now (as of this month) in the standard, it’s probably better to leave all the System.Xml* stuff out altogether. I have left the file listings intact, and posted numbers “minus System.Xml” in the summary at the end. Thanks to OneAndOnlySnob over on Reddit for pointing this out.

The programs

So, armed with this list, let’s examine a few of the “crazy delicious awesome rocks” Mono applications and see what we find. In every case I am searching against a copy of the source code repository cloned the day of this writing. Don’t want to fall into the it’s-not-really-released-yet-but-we-fixed-it trickery trap twice!

Banshee

Let’s hit this one first, since it was the starter:

[jason@apollo banshee-git]$ find . -name '*.cs'|xargs egrep -i "using system.codedom|using system.componentmodel|using sytem.configuration|using system.data|using system.deployment|using system.directoryservices|using system.drawing|using system.enterpriseservices|using system.linq|using system.management|using system.media|using system.messaging|using system.resources|using system.serviceprocess|using system.timers|using system.transactions|using system.web|using system.windows.forms|using system.xml"
./banshee/src/Dap/Banshee.Dap/Banshee.Dap/DapLibrarySync.cs:using System.Linq;
./banshee/src/Dap/Banshee.Dap/Banshee.Dap/DapSource.cs:using System.Linq;
./banshee/src/Dap/Banshee.Dap/Banshee.Dap/DapSync.cs:using System.Linq;
./banshee/src/Dap/Banshee.Dap/Banshee.Dap/DapService.cs:using System.Linq;
./banshee/src/Dap/Banshee.Dap/Banshee.Dap.Gui/LibrarySyncOptions.cs:using System.Linq;
./banshee/src/Dap/Banshee.Dap/Banshee.Dap.Gui/DapContent.cs:using System.Linq;
./banshee/src/Dap/Banshee.Dap.MassStorage/Banshee.Dap.MassStorage/MassStorageDevice.cs:using System.Linq;
./banshee/src/Extensions/Banshee.Audiobook/Banshee.Audiobook/Actions.cs:using System.Linq;
./banshee/src/Extensions/Banshee.Audiobook/Banshee.Audiobook/BookView.cs:using System.Linq;
./banshee/src/Extensions/Banshee.Audiobook/Banshee.Audiobook/AudiobookLibrarySource.cs:using System.Linq;
./banshee/src/Extensions/Banshee.Lastfm/Banshee.Lastfm/LastfmSource.cs:using System.Linq;
./banshee/src/Extensions/Banshee.Lastfm/Banshee.Lastfm/LastfmPreferences.cs:using System.Linq;
./banshee/src/Extensions/Banshee.Lastfm/Banshee.Lastfm.Audioscrobbler/Queue.cs:using System.Web;
./banshee/src/Extensions/Banshee.Lastfm/Banshee.Lastfm.Audioscrobbler/Queue.cs:using System.Xml;
./banshee/src/Extensions/Banshee.Lastfm/Banshee.Lastfm.Recommendations/RecommendationPane.cs:using System.Linq;
./banshee/src/Extensions/Banshee.YouTube/Banshee.YouTube.Data/DataFetch.cs:using System.Web;
./banshee/src/Extensions/Banshee.Daap/Banshee.Daap/DaapProxyWebServer.cs:using System.Web;
./banshee/src/Extensions/Banshee.Daap/Daap/ContentFetcher.cs:using System.Web;
./banshee/src/Extensions/Banshee.Daap/Daap/Client.cs:using System.Web;
./banshee/src/Extensions/Banshee.MiroGuide/Banshee.MiroGuide/MiroGuideSource.cs:using System.Linq;
./banshee/src/Extensions/Banshee.AmazonMp3/Banshee.AmazonMp3/AmzXspfPlaylist.cs:using System.Xml;
./banshee/src/Extensions/Banshee.AmazonMp3/Banshee.AmazonMp3/ConsoleTool.cs:using System.Linq;
./banshee/src/Extensions/Banshee.AmazonMp3/Banshee.AmazonMp3/AmazonDownloadManager.cs:using System.Linq;
./banshee/src/Extensions/Banshee.InternetArchive/InternetArchive/Details.cs:using System.Linq;
./banshee/src/Extensions/Banshee.InternetArchive/InternetArchive/Search.cs:using System.Linq;
./banshee/src/Extensions/Banshee.InternetArchive/InternetArchive/DetailsFile.cs:using System.Linq;
./banshee/src/Extensions/Banshee.InternetArchive/InternetArchive/JsonExtensions.cs:using System.Linq;
./banshee/src/Extensions/Banshee.InternetArchive/InternetArchive/SearchResults.cs:using System.Linq;
./banshee/src/Extensions/Banshee.InternetArchive/InternetArchive/SearchResult.cs:using System.Linq;
./banshee/src/Extensions/Banshee.InternetArchive/InternetArchive/DetailsReview.cs:using System.Linq;
./banshee/src/Extensions/Banshee.InternetArchive/Banshee.InternetArchive/Actions.cs:using System.Linq;
./banshee/src/Extensions/Banshee.InternetArchive/Banshee.InternetArchive/SearchView.cs:using System.Linq;
./banshee/src/Extensions/Banshee.InternetArchive/Banshee.InternetArchive/DetailsView.cs:using System.Linq;
./banshee/src/Extensions/Banshee.InternetArchive/Banshee.InternetArchive/HomeView.cs:using System.Linq;
./banshee/src/Extensions/Banshee.InternetArchive/Banshee.InternetArchive/HeaderFilters.cs:using System.Linq;
./banshee/src/Extensions/Banshee.InternetArchive/Banshee.InternetArchive/HomeSource.cs:using System.Linq;
./banshee/src/Extensions/Banshee.InternetArchive/Banshee.InternetArchive/SearchSource.cs:using System.Linq;
./banshee/src/Extensions/Banshee.InternetArchive/Banshee.InternetArchive/Item.cs:using System.Linq;
./banshee/src/Extensions/Banshee.InternetArchive/Banshee.InternetArchive/SearchDescription.cs:using System.Linq;
./banshee/src/Extensions/Banshee.InternetArchive/Banshee.InternetArchive/DetailsSource.cs:using System.Linq;
./banshee/src/Extensions/Banshee.PlayerMigration/Banshee.PlayerMigration/ItunesPlayerImportSource.cs:using System.Xml;
./banshee/src/Extensions/Banshee.PlayerMigration/Banshee.PlayerMigration/RhythmboxPlayerImportSource.cs:using System.Xml;
./banshee/src/Extensions/Banshee.Fixup/Banshee.Fixup/Problem.cs:using System.Linq;
./banshee/src/Extensions/Banshee.Fixup/Banshee.Fixup/FixActions.cs:using System.Linq;
./banshee/src/Extensions/Banshee.Fixup/Banshee.Fixup/AlbumDuplicateSolver.cs:using System.Linq;
./banshee/src/Extensions/Banshee.Fixup/Banshee.Fixup/ArtistDuplicateSolver.cs:using System.Linq;
./banshee/src/Extensions/Banshee.Fixup/Banshee.Fixup/GenreDuplicateSolver.cs:using System.Linq;
./banshee/src/Extensions/Banshee.Fixup/Banshee.Fixup/ColumnCellSolutionOptions.cs:using System.Linq;
./banshee/src/Extensions/Banshee.Fixup/Banshee.Fixup/Solver.cs:using System.Linq;
./banshee/src/Extensions/Banshee.Fixup/Banshee.Fixup/Tests.cs:using System.Linq;
./banshee/src/Extensions/Banshee.LibraryWatcher/Banshee.LibraryWatcher/SourceWatcher.cs:using System.Linq;
./banshee/src/Extensions/Banshee.PlayQueue/Banshee.PlayQueue/PlayQueueSource.cs:using System.Linq;
./banshee/src/Extensions/Banshee.PlayQueue/Banshee.PlayQueue/HeaderWidget.cs:using System.Linq;
./banshee/src/Extensions/Banshee.Emusic/Banshee.Emusic/EmusicService.cs:using System.Xml;
./banshee/src/Extensions/Banshee.Emusic/Banshee.Emusic/EmusicImport.cs:using System.Xml;
/banshee/src/Extensions/Banshee.Emusic/Banshee.Emusic/DownloadManager/DownloadManagerInterface.cs:using System.ComponentModel;
./banshee/src/Extensions/Banshee.LastfmStreaming/Banshee.LastfmStreaming/LastfmTrackInfo.cs:using System.Web;
./banshee/src/Extensions/Banshee.Podcasting/Banshee.Podcasting.Gui/DownloadManager/DownloadManagerInterface.cs:using System.ComponentModel;
./banshee/src/Extensions/Banshee.Podcasting/Banshee.Podcasting.Data/PodcastSource.cs:using System.Linq;
./banshee/src/Extensions/Banshee.Podcasting/Banshee.Podcasting/PodcastImageFetchJob.cs:using System.Xml;
./banshee/src/Extensions/Banshee.Podcasting/Banshee.Podcasting/PodcastService.cs:using System.Linq;
./banshee/src/Clients/Nereid/Nereid/PlayerInterface.cs:using System.Linq;
./banshee/src/Core/Banshee.Services/Banshee.Playlists.Formats/PlaylistParser.cs:using System.Web;
./banshee/src/Core/Banshee.Services/Banshee.Playlists.Formats/AsxPlaylistFormat.cs:using System.Xml;
./banshee/src/Core/Banshee.Services/Banshee.MediaProfiles/MediaProfileManager.cs:using System.Xml;
./banshee/src/Core/Banshee.Services/Banshee.MediaProfiles/Pipeline.cs:using System.Xml;
./banshee/src/Core/Banshee.Services/Banshee.MediaProfiles/ProfileConfiguration.cs:using System.Xml;
./banshee/src/Core/Banshee.Services/Banshee.MediaProfiles/PipelineVariable.cs:using System.Xml;
./banshee/src/Core/Banshee.Services/Banshee.MediaProfiles/Profile.cs:using System.Xml;
./banshee/src/Core/Banshee.Services/Banshee.ServiceStack/ServiceManager.cs:using System.Linq;
./banshee/src/Core/Banshee.Services/Banshee.Sources/Tests.cs:using System.Linq;
./banshee/src/Core/Banshee.Services/Banshee.Metadata.MusicBrainz/MusicBrainzQueryJob.cs:using System.Xml;
./banshee/src/Core/Banshee.Services/Banshee.Metadata.MusicBrainz/MusicBrainzQueryJob.cs:using System.Web;
./banshee/src/Core/Banshee.Services/Banshee.Metadata.LastFM/LastFMQueryJob.cs:using System.Xml;
./banshee/src/Core/Banshee.Services/Banshee.Metadata.LastFM/LastFMQueryJob.cs:using System.Web;
./banshee/src/Core/Banshee.Services/Banshee.Networking/DotNetNetworking.cs:using System.Linq;
./banshee/src/Core/Banshee.Services/Banshee.Web/BaseHttpServer.cs:using System.Web;
./banshee/src/Core/Banshee.Services/Banshee.Query/BansheeQuery.cs:using System.Linq;
./banshee/src/Core/Banshee.Services/Banshee.Collection.Indexer/CollectionIndexer.cs:using System.Xml;
./banshee/src/Core/Banshee.Services/Banshee.Collection.Database/Shuffler.cs:using System.Linq;
./banshee/src/Core/Banshee.Services/Banshee.Collection.Database/RandomBy.cs:using System.Linq;
./banshee/src/Core/Banshee.Services/Banshee.Collection.Database/Bookmark.cs:using System.Linq;
./banshee/src/Core/Banshee.Services/Banshee.Collection.Database/DatabaseTrackListModel.cs:using System.Linq;
./banshee/src/Core/Banshee.Services/Banshee.Collection.Database/RandomBySlot.cs:using System.Linq;
./banshee/src/Core/Banshee.Services/Banshee.Equalizer/EqualizerManager.cs:using System.Xml;
./banshee/src/Core/Banshee.Services/Banshee.Metadata/BaseMetadataProvider.cs:using System.Linq;
./banshee/src/Core/Banshee.Services/Banshee.Metadata/SaveTrackMetadataJob.cs:using System.Linq;
./banshee/src/Core/Banshee.Services/Banshee.Database/BansheeDbConnection.cs:using System.Linq;
./banshee/src/Core/Banshee.Services/Banshee.Database/SortKeyUpdater.cs:using System.Linq;
./banshee/src/Core/Banshee.Services/Banshee.Metrics/BansheeMetrics.cs:using System.Linq;
./banshee/src/Core/Banshee.Services/Banshee.Metadata.Rhapsody/RhapsodyQueryJob.cs:using System.Xml;
./banshee/src/Core/Banshee.ThickClient/Banshee.Gui/SourceActions.cs:using System.Linq;
./banshee/src/Core/Banshee.ThickClient/Banshee.Addins.Gui/AddinView.cs:using System.Linq;
./banshee/src/Core/Banshee.ThickClient/Banshee.ContextPane/ContextPane.cs:using System.Linq;
./banshee/src/Core/Banshee.ThickClient/Banshee.Collection.Gui/TrackListView.cs:using System.Linq;
./banshee/src/Core/Banshee.ThickClient/Banshee.Collection.Gui/XmlColumnController.cs:using System.Xml;
./banshee/src/Core/Banshee.ThickClient/Banshee.Collection.Gui/ColumnCellCreativeCommons.cs:using System.Linq;
./banshee/src/Core/Banshee.ThickClient/Banshee.Sources.Gui/SourceView.cs:using System.Linq;
./banshee/src/Core/Banshee.ThickClient/Banshee.Sources.Gui/SourceSwitcherEntry.cs:using System.Linq;
./banshee/src/Core/Banshee.Core/Banshee.IO/Provider.cs:using System.Linq;
./banshee/src/Core/Banshee.Core/Banshee.IO/Tests.cs:using System.Linq;
./banshee/src/Core/Banshee.Core/Banshee.Configuration/XmlConfigurationClient.cs:using System.Timers;
./banshee/src/Core/Banshee.Core/Banshee.Configuration/XmlConfigurationClient.cs:using System.Xml;
./banshee/src/Core/Banshee.Core/Banshee.Configuration/XmlConfigurationClient.cs:using System.Xml.Serialization;
./banshee/src/Core/Banshee.Core/Banshee.Base/ProductInformation.cs:using System.Xml;
./banshee/src/Core/Banshee.Core/Banshee.Base/Localization.cs:using System.Xml;
./banshee/src/Core/Banshee.Core/Banshee.Base/Localization.cs:using System.Xml.XPath;
./banshee/src/Backends/Banshee.GStreamerSharp/Banshee.GStreamerSharp/PlayerEngine.cs:using System.Linq;
/banshee/src/Backends/Banshee.Gio/Banshee.IO.Gio/Directory.cs:using System.Linq;
./banshee/src/Backends/Banshee.Gio/Banshee.IO.Gio/Tests.cs:using System.Linq;
./banshee/src/Backends/Banshee.Gio/Banshee.Hardware.Gio/BlockDevice.cs:using System.Linq;
./banshee/src/Backends/Banshee.Gio/Banshee.Hardware.Gio/Device.cs:using System.Linq;
./banshee/src/Backends/Banshee.Gio/Banshee.Hardware.Gio/DeviceMediaCapabilities.cs:using System.Linq;
./banshee/src/Backends/Banshee.Gio/Banshee.Hardware.Gio/LowLevel/Manager.cs:using System.Linq;
./banshee/src/Backends/Banshee.Gio/Banshee.Hardware.Gio/LowLevel/RawDevice.cs:using System.Linq;
./banshee/src/Libraries/MusicBrainz/MusicBrainz/Disc.cs:using System.Xml;
./banshee/src/Libraries/MusicBrainz/MusicBrainz/MusicBrainzItem.cs:using System.Xml;
./banshee/src/Libraries/MusicBrainz/MusicBrainz/MusicBrainzEntity.cs:using System.Xml;
./banshee/src/Libraries/MusicBrainz/MusicBrainz/Artist.cs:using System.Xml;
./banshee/src/Libraries/MusicBrainz/MusicBrainz/Event.cs:using System.Xml;
./banshee/src/Libraries/MusicBrainz/MusicBrainz/MusicBrainzObject.cs:using System.Xml;
./banshee/src/Libraries/MusicBrainz/MusicBrainz/Release.cs:using System.Xml;
./banshee/src/Libraries/MusicBrainz/MusicBrainz/Track.cs:using System.Xml;
./banshee/src/Libraries/MusicBrainz/MusicBrainz/Label.cs:using System.Xml;
./banshee/src/Libraries/Migo/Migo.Net/AsyncWebClient.cs:using System.ComponentModel;
./banshee/src/Libraries/Migo/Migo.Net/TransferStatusManager.cs:using System.Timers;
./banshee/src/Libraries/Migo/Migo.Net/EventArgs/DownloadProgressChangedEventArgs.cs:using System.ComponentModel;
./banshee/src/Libraries/Migo/Migo.Net/EventArgs/DownloadDataCompletedEventArgs.cs:using System.ComponentModel;
./banshee/src/Libraries/Migo/Migo.Net/EventArgs/DownloadStringCompletedEventArgs.cs:using System.ComponentModel;
./banshee/src/Libraries/Migo/Migo.DownloadCore/DownloadManager.cs:using System.Web;
./banshee/src/Libraries/Migo/Migo.DownloadCore/DownloadManager.cs:using System.ComponentModel;
./banshee/src/Libraries/Migo/Migo.DownloadCore/HttpFileDownloadGroup.cs:using System.Timers;  // migrate to System.Threading.Timer
./banshee/src/Libraries/Migo/Migo.DownloadCore/HttpFileDownloadGroup.cs:using System.ComponentModel;
./banshee/src/Libraries/Migo/Migo.DownloadCore/HttpFileDownloadTask.cs:using System.ComponentModel;
./banshee/src/Libraries/Migo/Migo.DownloadCore/DownloadGroupStatusManager.cs:using System.Timers;
./banshee/src/Libraries/Migo/Migo.Syndication/FeedUpdateTask.cs:using System.ComponentModel;
./banshee/src/Libraries/Migo/Migo.Syndication/Tests/XmlTests.cs:using System.Linq;
./banshee/src/Libraries/Migo/Migo.Syndication/RssParser.cs:using System.Xml;
./banshee/src/Libraries/Migo/Migo.Syndication/OpmlParser.cs:using System.Xml;
./banshee/src/Libraries/Migo/Migo.TaskCore/GroupProgressManager.cs:using System.ComponentModel;
./banshee/src/Libraries/Migo/Migo.TaskCore/TaskGroup.cs:using System.ComponentModel;
./banshee/src/Libraries/Migo/Migo.TaskCore/EventArgs/TaskCompletedEventArgs.cs:using System.ComponentModel;
./banshee/src/Libraries/Migo/Migo.TaskCore/Task.cs:using System.ComponentModel;
./banshee/src/Libraries/Mono.Media/Media.Playlists.Xspf/Tests/XspfTests.cs:using System.Xml;
./banshee/src/Libraries/Mono.Media/Media.Playlists.Xspf/Tests/XspfTests.cs:using System.Xml.Schema;
./banshee/src/Libraries/Mono.Media/Media.Playlists.Xspf/XmlUtil.cs:using System.Xml;
./banshee/src/Libraries/Mono.Media/Media.Playlists.Xspf/XspfBaseObject.cs:using System.Xml;
./banshee/src/Libraries/Mono.Media/Media.Playlists.Xspf/Track.cs:using System.Xml;
./banshee/src/Libraries/Mono.Media/Media.Playlists.Xspf/Playlist.cs:using System.Xml;
./banshee/src/Libraries/Lastfm/Lastfm.Data/DataEntryCollection.cs:using System.Xml;
./banshee/src/Libraries/Lastfm/Lastfm.Data/DataCore.cs:using System.Web;
./banshee/src/Libraries/Lastfm/Lastfm.Data/DataCore.cs:using System.Xml;
./banshee/src/Libraries/Lastfm/Lastfm.Data/LastfmData.cs:using System.Web;
./banshee/src/Libraries/Lastfm/Lastfm.Data/LastfmData.cs:using System.Xml;
./banshee/src/Libraries/Lastfm/Lastfm.Data/DataEntry.cs:using System.Xml;
./banshee/src/Libraries/Lastfm/Lastfm/LastfmRequest.cs:using System.Web;
./banshee/src/Libraries/Lastfm/Lastfm/RadioConnection.cs:using System.Xml;
./banshee/src/Libraries/Lastfm/Lastfm/RadioConnection.cs:using System.Web;
./banshee/src/Libraries/Lastfm/Lastfm/AudioscrobblerConnection.cs:using System.Timers;
./banshee/src/Libraries/Lastfm/Lastfm/AudioscrobblerConnection.cs:using System.Web;
./banshee/build/AddinXmlStringExtractor.cs:using System.Xml.XPath;
./banshee/build/DllMapVerifier.cs:using System.Xml;
./banshee/tests/Analyzer/Analyzer.cs:using System.Linq;
./banshee/tests/Analyzer/Analyzer.cs:using System.Xml.Linq;
./banshee/extras/metrics/Metric.cs:using System.Linq;

Banshee: 165 references.

Banshee has a little bonus, by the way:

[jason@apollo ~]$ find . -name '*.cs'|xargs egrep -i "using microsoft."
./banshee-git/banshee/src/Libraries/MusicBrainz/MusicBrainz/DiscWin32NT.cs:using Microsoft.Win32.SafeHandles;

Tomboy

[jason@apollo tomboy-git]$ find . -name '*.cs'|xargs egrep -i "using system.codedom|using system.componentmodel|using sytem.configuration|using system.data|using system.deployment|using system.directoryservices|using system.drawing|using system.enterpriseservices|using system.linq|using system.management|using system.media|using system.messaging|using system.resources|using system.serviceprocess|using system.timers|using system.transactions|using system.web|using system.windows.forms|using system.xml"
./tomboy/Tomboy/XmlPreferencesClient.cs:using System.Xml;
./tomboy/Tomboy/Note.cs:using System.Xml;
./tomboy/Tomboy/Tomboy.cs:using System.Xml;
./tomboy/Tomboy/ManagedWinapi.EventDispatchingNativeWindow.cs:using System.Windows.Forms;
./tomboy/Tomboy/NoteTag.cs:using System.Xml;
./tomboy/Tomboy/Addins/Sketching/Stroke.cs:using System.Xml;
./tomboy/Tomboy/Addins/Sketching/Paper.cs:using System.Xml;
./tomboy/Tomboy/Addins/Sketching/Handwriting.cs:using System.Xml;
./tomboy/Tomboy/Addins/StickyNoteImport/StickyNoteImportNoteAddin.cs:using System.Xml;
./tomboy/Tomboy/Addins/ExportToHtml/ExportToHtmlNoteAddin.cs:using System.Xml;
./tomboy/Tomboy/Addins/ExportToHtml/ExportToHtmlNoteAddin.cs:using System.Xml.XPath;
./tomboy/Tomboy/Addins/ExportToHtml/ExportToHtmlNoteAddin.cs:using System.Xml.Xsl;
./tomboy/Tomboy/Addins/WebSyncService/MonoHttp/HttpListenerException.cs:using System.ComponentModel;
./tomboy/Tomboy/Addins/WebSyncService/Api/OAuth.cs:using System.Web;
./tomboy/Tomboy/Addins/WebSyncService/Api/AnonymousConnection.cs:using System.Web;
./tomboy/Tomboy/Addins/WebSyncService/WebSyncPreferencesWidget.cs:using System.Web;
./tomboy/Tomboy/Addins/WebSyncService/OAuth/Mono.Rocks/IEnumerable.cs:using System.Linq;
./tomboy/Tomboy/Addins/WebSyncService/OAuth/Base.cs:using System.Linq;
./tomboy/Tomboy/Addins/WebSyncService/OAuth/Base.cs:using System.Web;
./tomboy/Tomboy/Addins/Evolution/EvolutionNoteAddin.cs:using System.Xml;
./tomboy/Tomboy/Addins/Evolution/EvolutionNoteAddin.cs:using System.Web;
./tomboy/Tomboy/Addins/Tasks/TaskArchiver.cs:using System.Xml;
./tomboy/Tomboy/Addins/Bugzilla/BugzillaNoteAddin.cs:using System.Xml;
./tomboy/Tomboy/WindowsKeybinder.cs:using System.Windows.Forms;
./tomboy/Tomboy/Utils.cs:using System.Xml;
./tomboy/Tomboy/NoteBuffer.cs:using System.Xml;
./tomboy/Tomboy/NoteBuffer.cs:using System.Xml.XPath;
./tomboy/Tomboy/NoteBuffer.cs:using System.Xml.Xsl;
./tomboy/Tomboy/Synchronization/TomboySyncClient.cs:using System.Xml;
./tomboy/Tomboy/Synchronization/SyncManager.cs:using System.Xml;
./tomboy/Tomboy/Synchronization/FileSystemSyncServer.cs:using System.Xml;
./tomboy/Tomboy/GnomeApplication.cs:using System.Xml;
./tomboy/Tomboy/System.Web/HttpUtility.cs://using System.Web.Util;
./tomboy/Tomboy/ManagedWinapi.Hotkey.cs:using System.ComponentModel;
./tomboy/Tomboy/ManagedWinapi.Hotkey.cs:using System.Windows.Forms;
./tomboy/Tomboy/ActionManager.cs:using System.Xml;

Tomboy: 36 references.

F-Spot

[jason@apollo fspot-git]$ find . -name '*.cs'|xargs egrep -i "using system.codedom|using system.componentmodel|using sytem.configuration|using system.data|using system.deployment|using system.directoryservices|using system.drawing|using system.enterpriseservices|using system.linq|using system.management|using system.media|using system.messaging|using system.resources|using system.serviceprocess|using system.timers|using system.transactions|using system.web|using system.windows.forms|using system.xml"
./f-spot/lib/unique-sharp/generator/StructBase.cs:      using System.Xml;
./f-spot/lib/unique-sharp/generator/ChildProperty.cs:   using System.Xml;
./f-spot/lib/unique-sharp/generator/PropertyBase.cs:    using System.Xml;
./f-spot/lib/unique-sharp/generator/Signature.cs:       using System.Xml;
./f-spot/lib/unique-sharp/generator/MethodBase.cs:      using System.Xml;
./f-spot/lib/unique-sharp/generator/ClassGen.cs:        using System.Xml;
./f-spot/lib/unique-sharp/generator/CallbackGen.cs:     using System.Xml;
./f-spot/lib/unique-sharp/generator/BoxedGen.cs:        using System.Xml;
./f-spot/lib/unique-sharp/generator/VirtualMethod.cs:   using System.Xml;
./f-spot/lib/unique-sharp/generator/Ctor.cs:    using System.Xml;
./f-spot/lib/unique-sharp/generator/VMSignature.cs:     using System.Xml;
./f-spot/lib/unique-sharp/generator/Property.cs:        using System.Xml;
./f-spot/lib/unique-sharp/generator/GenBase.cs: using System.Xml;
./f-spot/lib/unique-sharp/generator/Parser.cs:  using System.Xml;
./f-spot/lib/unique-sharp/generator/ObjectBase.cs:      using System.Xml;
./f-spot/lib/unique-sharp/generator/GenerationInfo.cs:  using System.Xml;
./f-spot/lib/unique-sharp/generator/Parameters.cs:      using System.Xml;
./f-spot/lib/unique-sharp/generator/InterfaceGen.cs:    using System.Xml;
./f-spot/lib/unique-sharp/generator/Method.cs:  using System.Xml;
./f-spot/lib/unique-sharp/generator/EnumGen.cs: using System.Xml;
./f-spot/lib/unique-sharp/generator/ClassBase.cs:       using System.Xml;
./f-spot/lib/unique-sharp/generator/StructGen.cs:       using System.Xml;
./f-spot/lib/unique-sharp/generator/HandleBase.cs:      using System.Xml;
./f-spot/lib/unique-sharp/generator/OpaqueGen.cs:       using System.Xml;
./f-spot/lib/unique-sharp/generator/StructField.cs:     using System.Xml;
./f-spot/lib/unique-sharp/generator/CodeGenerator.cs:   using System.Xml;
./f-spot/lib/unique-sharp/generator/ObjectGen.cs:       using System.Xml;
./f-spot/lib/unique-sharp/generator/ObjectField.cs:     using System.Xml;
./f-spot/lib/unique-sharp/generator/FieldBase.cs:       using System.Xml;
./f-spot/lib/unique-sharp/generator/ReturnValue.cs:     using System.Xml;
./f-spot/lib/unique-sharp/generator/Signal.cs:  using System.Xml;
./f-spot/lib/dpap-sharp/lib/ContentFetcher.cs:using System.Web;
./f-spot/lib/dpap-sharp/lib/Server.cs:using System.Web;
./f-spot/lib/dpap-sharp/lib/Client.cs:using System.Web;
./f-spot/lib/gio-sharp/generator/StructBase.cs: using System.Xml;
./f-spot/lib/gio-sharp/generator/ChildProperty.cs:      using System.Xml;
./f-spot/lib/gio-sharp/generator/PropertyBase.cs:       using System.Xml;
./f-spot/lib/gio-sharp/generator/Signature.cs:  using System.Xml;
./f-spot/lib/gio-sharp/generator/MethodBase.cs: using System.Xml;
./f-spot/lib/gio-sharp/generator/ClassGen.cs:   using System.Xml;
./f-spot/lib/gio-sharp/generator/CallbackGen.cs:        using System.Xml;
./f-spot/lib/gio-sharp/generator/BoxedGen.cs:   using System.Xml;
./f-spot/lib/gio-sharp/generator/VirtualMethod.cs:      using System.Xml;
./f-spot/lib/gio-sharp/generator/Ctor.cs:       using System.Xml;
./f-spot/lib/gio-sharp/generator/VMSignature.cs:        using System.Xml;
./f-spot/lib/gio-sharp/generator/Property.cs:   using System.Xml;
./f-spot/lib/gio-sharp/generator/GenBase.cs:    using System.Xml;
./f-spot/lib/gio-sharp/generator/Parser.cs:     using System.Xml;
./f-spot/lib/gio-sharp/generator/ObjectBase.cs: using System.Xml;
./f-spot/lib/gio-sharp/generator/GenerationInfo.cs:     using System.Xml;
./f-spot/lib/gio-sharp/generator/Parameters.cs: using System.Xml;
./f-spot/lib/gio-sharp/generator/InterfaceGen.cs:       using System.Xml;
./f-spot/lib/gio-sharp/generator/Method.cs:     using System.Xml;
./f-spot/lib/gio-sharp/generator/EnumGen.cs:    using System.Xml;
./f-spot/lib/gio-sharp/generator/ClassBase.cs:  using System.Xml;
./f-spot/lib/gio-sharp/generator/StructGen.cs:  using System.Xml;
./f-spot/lib/gio-sharp/generator/HandleBase.cs: using System.Xml;
./f-spot/lib/gio-sharp/generator/OpaqueGen.cs:  using System.Xml;
./f-spot/lib/gio-sharp/generator/StructField.cs:        using System.Xml;
./f-spot/lib/gio-sharp/generator/CodeGenerator.cs:      using System.Xml;
./f-spot/lib/gio-sharp/generator/ObjectGen.cs:  using System.Xml;
./f-spot/lib/gio-sharp/generator/ObjectField.cs:        using System.Xml;
./f-spot/lib/gio-sharp/generator/FieldBase.cs:  using System.Xml;
./f-spot/lib/gio-sharp/generator/ReturnValue.cs:        using System.Xml;
./f-spot/lib/gio-sharp/generator/Signal.cs:     using System.Xml;
./f-spot/lib/Mono.Google/Mono.Google/MultipartRequest.cs:using System.Xml;
./f-spot/lib/Mono.Google/Mono.Google/Authentication.cs:using System.Web;
./f-spot/lib/Mono.Google/Mono.Google.Picasa/XmlUtil.cs:using System.Xml;
./f-spot/lib/Mono.Google/Mono.Google.Picasa/PicasaAlbum.cs:using System.Xml;
./f-spot/lib/Mono.Google/Mono.Google.Picasa/PicasaWeb.cs:using System.Xml;
./f-spot/lib/Mono.Google/Mono.Google.Picasa/PicasaPicture.cs:using System.Xml;
./f-spot/lib/Mono.Tabblo/Mono.Tabblo/Connection.cs:using System.Web;
./f-spot/lib/SmugMugNet/SmugMugNet/Album.cs:using System.Xml;
./f-spot/lib/SmugMugNet/SmugMugNet/SmugMugUploadException.cs:using System.Xml;
./f-spot/lib/SmugMugNet/SmugMugNet/Category.cs:using System.Xml;
./f-spot/lib/SmugMugNet/SmugMugNet/Credentials.cs:using System.Xml;
./f-spot/lib/SmugMugNet/SmugMugNet/SmugMugApi.cs:using System.Xml;
./f-spot/lib/SmugMugNet/SmugMugNet/SmugMugException.cs:using System.Xml;
./f-spot/lib/SmugMugNet/SmugMugNet/SmugMugProxy.cs:using System.Xml;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.Gallery/FSpot.Exporters.Gallery/GalleryAccount.cs:using System.Web;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.Gallery/FSpot.Exporters.Gallery/GalleryRemote.cs:using System.Web;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.Gallery/FSpot.Exporters.Gallery/FormClient.cs:using System.Web;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.Gallery/FSpot.Exporters.Gallery/AccountDialog.cs:using System.Web;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.Gallery/FSpot.Exporters.Gallery/GalleryExport.cs:using System.Web;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.Gallery/FSpot.Exporters.Gallery/GalleryAddAlbum.cs:using System.Web;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.Gallery/FSpot.Exporters.Gallery/GalleryAccountManager.cs:using System.Web;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.SmugMug/FSpot.Exporters.SmugMug/SmugMugAccount.cs:using System.Web;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.SmugMug/FSpot.Exporters.SmugMug/SmugMugAccountManager.cs:using System.Web;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.SmugMug/FSpot.Exporters.SmugMug/SmugMugExport.cs:using System.Web;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.SmugMug/FSpot.Exporters.SmugMug/SmugMugAccountDialog.cs:using System.Web;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.SmugMug/FSpot.Exporters.SmugMug/SmugMugAddAlbum.cs:using System.Web;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.Facebook/Mono.Facebook/Notification.cs:using System.Xml.Serialization;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.Facebook/Mono.Facebook/Album.cs:using System.Xml.Serialization;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.Facebook/Mono.Facebook/SessionWrapper.cs:using System.Xml.Serialization;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.Facebook/Mono.Facebook/Responses.cs:using System.Xml.Serialization;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.Facebook/Mono.Facebook/Tag.cs:using System.Xml.Serialization;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.Facebook/Mono.Facebook/Photo.cs:using System.Xml.Serialization;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.Facebook/Mono.Facebook/PeopleList.cs:using System.Xml.Serialization;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.Facebook/Mono.Facebook/Event.cs:using System.Xml.Serialization;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.Facebook/Mono.Facebook/User.cs:using System.Xml.Serialization;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.Facebook/Mono.Facebook/Friend.cs:using System.Xml.Serialization;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.Facebook/Mono.Facebook/Util.cs:using System.Xml;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.Facebook/Mono.Facebook/Util.cs:using System.Xml.Serialization;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.Facebook/Mono.Facebook/Group.cs:using System.Xml.Serialization;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.Facebook/Mono.Facebook/Error.cs:using System.Xml.Serialization;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.Facebook/Mono.Facebook/FriendInfo.cs:using System.Xml.Serialization;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.Facebook/Mono.Facebook/Location.cs:using System.Xml.Serialization;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.Facebook/Mono.Facebook/SessionInfo.cs:using System.Xml.Serialization;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.Facebook/Mono.Facebook/FacebookSession.cs:using System.Xml;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.Facebook/Mono.Facebook/FacebookSession.cs:using System.Linq;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.Facebook/FSpot.Exporters.Facebook/FacebookExport.cs:using System.Web;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.PicasaWeb/FSpot.Exporters.PicasaWeb/GoogleAccountDialog.cs:using System.Web;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.PicasaWeb/FSpot.Exporters.PicasaWeb/GoogleAccountManager.cs:using System.Web;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.PicasaWeb/FSpot.Exporters.PicasaWeb/GoogleAccount.cs:using System.Web;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.PicasaWeb/FSpot.Exporters.PicasaWeb/GoogleAddAlbum.cs:using System.Web;
./f-spot/src/Extensions/Exporters/FSpot.Exporters.PicasaWeb/FSpot.Exporters.PicasaWeb/PicasaWebExport.cs:using System.Web;
./f-spot/src/Clients/MainApp/FSpot.UI.Dialog/PreferenceDialog.cs:using System.Linq;
./f-spot/src/Clients/MainApp/FSpot.UI.Dialog/SelectionRatioDialog.cs:using System.Xml.Serialization;
./f-spot/src/Clients/MainApp/FSpot.Editors/CropEditor.cs:using System.Xml.Serialization;
./f-spot/src/Clients/MainApp/FSpot/PhotoView.cs:using System.Xml.Serialization;
./f-spot/src/Clients/MainApp/FSpot/App.cs:using System.Linq;
./f-spot/src/Clients/MainApp/FSpot/SelectionDataExtensions.cs:using System.Linq;
./f-spot/src/Clients/MainApp/FSpot/FolderQueryWidget.cs:using System.Linq;
./f-spot/src/Clients/MainApp/FSpot/Photo.cs:using System.Linq;
./f-spot/src/Clients/MainApp/FSpot/MainWindow.cs:using System.Linq;
./f-spot/src/Clients/MainApp/FSpot/UriCollection.cs:using System.Xml;
./f-spot/src/Core/FSpot.Bling/FSpot.Bling/Animation.cs:using System.ComponentModel;
./f-spot/src/Core/FSpot.Core/FSpot.Core/FilePhoto.cs:using System.Xml;
./f-spot/src/Core/FSpot.Gui/FSpot.Widgets/SelectionCollection.cs:using System.Linq;
./f-spot/build/AddinXmlStringExtractor.cs:using System.Xml.XPath;
./f-spot/build/DllMapVerifier.cs:using System.Xml;

F-Spot: 131 references.

Do

[jason@apollo do-bzr]$ find . -name '*.cs'|xargs egrep -i "using system.codedom|using system.componentmodel|using sytem.configuration|using system.data|using system.deployment|using system.directoryservices|using system.drawing|using system.enterpriseservices|using system.linq|using system.management|using system.media|using system.messaging|using system.resources|using system.serviceprocess|using system.timers|using system.transactions|using system.web|using system.windows.forms|using system.xml"
./do/Do.Platform.Linux/src/Do.Universe/GNOMESpecialLocationsItemSource.cs:using System.Linq;
./do/Do.Platform.Linux/src/Do.Universe/CategoryItem.cs:using System.Linq;
./do/Do.Platform.Linux/src/Do.Universe/ApplicationItemSource.cs:using System.Linq;
./do/Do.Platform.Linux/src/Do.Universe/GNOMEBookmarkItem.cs:using System.Linq;
./do/Do.Platform.Linux/src/Do.Universe/GNOMETrashItem.cs:using System.Linq;
./do/Do.Platform.Linux/src/Do.Universe/ApplicationItem.cs:using System.Linq;
./do/Do.Platform.Linux/src/Do.Platform/Do.Platform.Linux/KeyBindingService.cs:using System.Linq;
./do/Do.Platform.Linux/src/Do.Platform/Do.Platform.Linux/GnomeKeyringSecurePreferencesService.cs:using System.ComponentModel;
./do/Do.Platform.Linux/src/Do.Platform/Do.Platform.Linux/EnvironmentService.cs:using System.Linq;
./do/Do.Platform.Linux/src/Do.Platform/Do.Platform.Linux/UniverseFactoryService.cs:using System.Linq;
./do/Do.Universe/src/Do.Universe/ItemSource.cs:using System.Linq;
./do/Do.Universe/src/Do.Universe/Element.cs:using System.Linq;
./do/Do.Universe/src/Do.Universe/Do.Universe.Safe/SafeItemSource.cs:using System.Linq;
./do/Do.Universe/src/Do.Universe/Do.Universe.Safe/SafeAct.cs:using System.Linq;
./do/Do.Universe/src/Do.Universe/ProxyItem.cs:using System.Linq;
./do/Do.Universe/src/Do.Universe/Act.cs:using System.Linq;
./do/Do.Interface.Linux.AnimationBase/src/Do.Interface/Do.Interface.AnimationBase/BezelGlassResults.cs:using System.Linq;
./do/Do.Interface.Linux.AnimationBase/src/Do.Interface/Do.Interface.AnimationBase/AnimationBaseConfigurationWidget.cs:using System.Linq;
./do/Do.Interface.Linux.AnimationBase/src/Do.Interface/Do.Interface.AnimationBase/Bezel.cs:using System.Linq;
./do/Do/src/Mono.Addins/AddinExtensions.cs:using System.Linq;
./do/Do/src/PathExtensions.cs:using System.Linq;
./do/Do/src/Do.Core/SecondSearchController.cs:using System.Linq;
./do/Do/src/Do.Core/ItemExtensions.cs:using System.Linq;
./do/Do/src/Do.Core/SimpleSearchController.cs:using System.Linq;
./do/Do/src/Do.Core/PluginManager.cs:using System.Xml;
./do/Do/src/Do.Core/PluginManager.cs:using System.Linq;
./do/Do/src/Do.Core/Shortcut.cs:using System.Linq;
./do/Do/src/Do.Core/Paths.cs:using System.Linq;
./do/Do/src/Do.Core/UniverseManager.cs:using System.Linq;
./do/Do/src/Do.Core/Controller.cs:using System.Linq;
./do/Do/src/Do.Core/FirstSearchController.cs:using System.Linq;
./do/Do/src/Do.Core/HistogramRelevanceProvider.cs:using System.Linq;
./do/Do/src/Do.Core/ThirdSearchController.cs:using System.Linq;
./do/Do/src/Do.Universe/ItemSourceItemSource.cs:using System.Linq;
./do/Do/src/CorePreferences.cs:using System.Linq;
./do/Do/src/Do.UI/PluginConfigurationWindow.cs:using System.Linq;
./do/Do/src/Do.UI/ColorConfigurationWidget.cs:using System.Linq;
./do/Do/src/Do.UI/KeybindingTreeView.cs:using System.Linq;
./do/Do/src/Do.UI/PreferencesWindow.cs:using System.Linq;
./do/Do/src/Do.UI/ManagePluginsPreferencesWidget.cs:using System.Linq;
./do/Do/src/Do.Platform/PluginManagerService.cs:using System.Linq;
./do/Do/src/Do.Platform/CoreService.cs:using System.Linq;
./do/Do.Platform/src/Do.Universe/Do.Universe.Common/OpenWithAction.cs:using System.Linq;
./do/Do.Platform/src/Do.Universe/Do.Universe.Common/CopyToClipboardAction.cs:using System.Linq;
./do/Do.Platform/src/Do.Universe/Do.Universe.Common/EmailAction.cs:using System.Linq;
./do/Do.Platform/src/Do.Platform/Services.cs:using System.Linq;
./do/Do.Platform/src/Do.Platform/IEnvironmentService.cs:using System.Linq;
./do/Do.Platform/src/Do.Platform/Do.Platform.Default/KeyBindingService.cs:using System.Linq;
./do/Do.Platform/src/Do.Platform/KeyBinding.cs:using System.Linq;
./do/Do.Platform/src/Do.Platform/Do.Platform.Common/AbstractKeyBindingService.cs:using System.Linq;
./do/Do.Platform/src/Do.Platform/SecurePreferencesWrapper.cs:using System.ComponentModel;
./do/Do.Platform/src/Do.Platform/LogBase.cs:using System.Linq;
./do/Do.Interface.Linux/src/Do.Interface/Do.Interface.Widgets/ResultsWindow.cs:using System.Linq;
./do/Do.Interface.Linux/src/Do.Interface/PixbufSurfaceCache.cs:using System.Linq;
./do/Do.Interface.Linux/src/Do.Interface/InterfaceManager.cs:using System.Linq;
./do/Do.Interface.Linux/src/Do.Interface/ClassicInterface/ClassicWindow.cs:using System.Linq;

Do: 56 references.

Gbrainy

[jason@apollo gbrainy-git]$ find . -name '*.cs'|xargs egrep -i "using system.codedom|using system.componentmodel|using sytem.configuration|using system.data|using system.deployment|using system.directoryservices|using system.drawing|using system.enterpriseservices|using system.linq|using system.management|using system.media|using system.messaging|using system.resources|using system.serviceprocess|using system.timers|using system.transactions|using system.web|using system.windows.forms|using system.xml"
./gbrainy/sample_extensions/Memory/MemorySample.cs:using System.Timers;
./gbrainy/src/Clients/WebForms/Default.aspx.cs:using System.Web;
./gbrainy/src/Clients/WebForms/Default.aspx.cs:using System.Web.UI;
./gbrainy/src/Clients/WebForms/WebSession.cs:using System.Web.SessionState;
./gbrainy/src/Clients/WebForms/Status.aspx.cs:using System.Web;
./gbrainy/src/Clients/WebForms/Status.aspx.cs:using System.Web.UI;
./gbrainy/src/Clients/WebForms/Status.aspx.cs:using System.Web.UI.WebControls;
./gbrainy/src/Clients/WebForms/Global.asax.cs:using System.ComponentModel;
./gbrainy/src/Clients/WebForms/Global.asax.cs:using System.Web;
./gbrainy/src/Clients/WebForms/Global.asax.cs:using System.Web.SessionState;
./gbrainy/src/Clients/WebForms/MasterPage.master.cs:using System.Web;
./gbrainy/src/Clients/WebForms/MasterPage.master.cs:using System.Web.UI;
./gbrainy/src/Clients/WebForms/MasterPage.master.cs:using System.Web.UI.WebControls;
./gbrainy/src/Clients/WebForms/Finish.aspx.cs:using System.Web;
./gbrainy/src/Clients/WebForms/Finish.aspx.cs:using System.Web.UI;
./gbrainy/src/Clients/WebForms/Game.aspx.cs:using System.Web;
./gbrainy/src/Clients/WebForms/Game.aspx.cs:using System.Web.UI;
./gbrainy/src/Core/Main/Verbal/AnalogiesFactory.cs:using System.Xml;
./gbrainy/src/Core/Main/IDrawRequest.cs:using System.ComponentModel;
./gbrainy/src/Core/Main/PlayerHistory.cs:using System.Xml.Serialization;
./gbrainy/src/Core/Main/Game.cs:using System.ComponentModel;
./gbrainy/src/Core/Main/Memory.cs:using System.Timers;
./gbrainy/src/Core/Main/GameSessionHistory.cs:using System.Xml.Serialization;
./gbrainy/src/Core/Main/GameSession.cs:using System.Timers;
./gbrainy/src/Core/Main/GameSession.cs:using System.ComponentModel;
./gbrainy/src/Core/Main/Xml/GameXmlFactory.cs:using System.Xml;
./gbrainy/src/Core/Main/Preferences.cs:using System.Xml;
./gbrainy/src/Core/Main/Preferences.cs:using System.Xml.Serialization;
./gbrainy/src/Core/Toolkit/Widget.cs:using System.ComponentModel;
./gbrainy/src/Core/Views/CountDownView.cs:using System.Timers;
./gbrainy/src/Core/Views/CountDownView.cs:using System.ComponentModel;

Gbrainy: 31 references.

Summary

UPDATED 2010.12.15 – The struck-through text is the original figure with System.Xml as part of the search. The un-struckthrough text is without.

• Banshee: 165 118 refs (and 1 Microsoft refs for giggles)
• Tomboy: 36 13 refs
• F-Spot: 131 32 refs
• Do: 56 55 refs
• Gbrainy: 31 25 refs

So, that’s the 5 most popular (give-or-take) Mono applications for Linux. Not a single one of which doesn’t have a significant amount of references to non-ECMA namespaces. As the Microsoft Community Promise covering any implementation is limited to the “extent it conforms to one of the Covered Specifications”, we can reject the claim that “All of the pieces of Mono that are used in Linux apps are covered by the MCP.”

I will leave it to bolder souls than I to speculate on whether it is even possible to write a non-trivial Mono program that does not require non-ECMA namespaces and, if so, that limitation is intentional on Microsoft’s part.

UPDATE 2010.12.16 – Miguel de Icaza responds on his blog, with some additional comments from myself there.

Now, I usually don’t comment on other sites about Mono/Moonlight because 99.99% of the arguments that come up are simply repeats. In my opinion (a polite way of me saying “It is a fact that”), I have dismantled any Team Apologista argument so throughly that only the most deluded rail against my fierce logic.

That being said, as I read the commentary at Reddit, one long bit jumped out at me, by my old friend zekopeko. Those of us that keep abreast of Team Apologista will recognize the name, as Mr. Peko is a very active defender of all things Mono. It’s amusing because his main tactic is simply parroting other people’s arguments, but I guarantee you if you read a dozen things about Mono at Ubuntu Forums, OMG Ubuntu, Reddit, or any other similar site, 10 of them will be graced with Mr. Peko’s presence.

Because it amused me, I commented on  - but allow me expand a bit here, for I know the Gentle Readers of This Humble Blog will appreciate the details:

I’ll take your word for it.

In my original argument I said:

Tomboy and F-Spot use unsafe bits of .NET

This is true for Banshee as well, a fact also acknowledged by Mr. de Icaza.

Mr. Peko’s response on Reddit:

He also mentions Banshee as using non-safe bits by quoting a 1.5 year old post.Banshee doesn’t use the “evil” System.Data anymore. That guy is a Debian Developer and Mono packager for Debian/Ubuntu.

Now there are 2 problems with this response:

1. I didn’t say that “System.Data” was the only unsafe bit being used.
2. Banshee still uses System.Data

You see, I have this crazy tendency to fact check things before I use them in an argument. I might not always get everything right, but I do always make an honest effort. So, I downloaded the Bansee source code and I searched it for “using system.data”, the C# language incantation necessary to use System.Data:

[jason@apollo banshee-1-1.8.0]$ find . | xargs grep -i “using system.data”
./src/Hyena/Hyena.Data.Sqlite/Hyena.Data.Sqlite/Tests/SqliteModelProviderTests.cs:using System.Data;
./src/Hyena/Hyena.Data.Sqlite/Hyena.Data.Sqlite/HyenaSqliteArrayDataReader.cs:using System.Data;
[.. 70 more files snipped ..]

All told, there are 72 C# source files in Banshee that use System.Data.

Now, I realize Mr. Peko is simply parroting something he read on Twitter and probably has never looked at the Banshee source code, nor could understand it if he did, but this is a dramatic (and admittedly amusing) example of the quality and rigor of Team Apologista’s arguments.

Take it a little further

Remember before how I said I didn’t say that “System.Data” was the only unsafe bit being used? Well, if you check for all the Non Standardized Namespaces in Banshee, you come up with an even longer list:

[jason@apollo banshee-1-1.8.0]$ find . | xargs egrep -i “using system.codedom|using system.componentmodel|using sytem.configuration|using system.data|using system.deployment|using system.directoryservices|using system.drawing|using system.enterpriseservices|using system.linq|using system.management|using system.media|using system.messaging|using system.resources|using system.serviceprocess|using system.timers|using system.transactions|using system.web|using system.windows.forms|using system.xml”

./src/Dap/Banshee.Dap/Banshee.Dap/DapLibrarySync.cs:using System.Linq;
[.. 280 more files snipped ..]

That’s right 281 files use non-standardized .NET namespaces not covered by ECMA or the Microsoft Community Promise. Out of 1240 C# source files. 22%, just short of a quarter, of all the C# source files in Banshee require non-standardized .NET namespaces.

When Team Apologista tries to talk down the importance of the non-ECMA namespaces, or when they try to suggest that while the Mono project proper might not split into safe and un-safe portions, but packagers for most major distributions do, keep Banshee in mind as an example.

A final note

The rest of Mr. Peko’s response and his many other responses in that Reddit thread are filled with a veritable cornucopia of factual and logical errors, I won’t bother with tediously dissecting them here (mainly because I think they are transparent to any honest reader), but I did want to mention it lest someone think this gross factual inaccuracy be the only failing.

A final final note

I guess I need to specifically point out that I am using the latest public release of code at the time of writing (1.8.0) as available from the Banshee “download” page. Apparently, the git version of Banshee has removed System.Data dependencies.

If Banshee is able to remove all non-standardized namespaces, then that does remove one point of criticism against it. We will see how it looks whenever a new public release is made.