Does the .NET CLR have a circular dependency?

Question

Possible duplicate:
How did Microsoft create assemblies with round links?

I was going to build a small PowerShell cmdlet that would give me a dependency tree for .NET compilations when I discovered something strange:

CLR.NET 2.0 seems to have a circular dependency: System depends on System.Configuration and System.Configuration depends on System . This makes it rather difficult to give a complete dependency tree.

Am I really here? Are there any deceptions that I don't know about? Why (and, of course, HOW could it have been introduced) was this apparent violation of simple and almost universally accepted recipes for dependence?