fcl

Why is the Process class part of the Diagnostics namespace? This is a part of design of the BCL that kept me wondering for some time now. I find it kind of counter-intuitive, I fail to see the connection between Process and for instance the Debug and Trace classes. The process class doesn't just represent a single process. It has a ton of information about the running processes on the computer. This info can be used to find problems or just get general information about your system state. you can see the diagnostics namespace description here: http://msdn.microsoft.com/en-us/library/system

I want to generate an XML Schema based upon a class, just as you can do with the Xsd.exe tool . E.g. xsd.exe /type: typename /outputdir:c:\ assmeblyname . Is there a way to do this by using classes in the .NET Framework instead of using the standalone tool? I'm sure I've seen information about task references or similar - i.e. something programmatic - that can be used in place of some of these standalone utilities, or that some standalone utilities get their features through the FCL or a Microsoft API. Found this which looks like it should do the trick... public static string GetSchema<T>() {

I want to generate a class from an XML XSD Schema, just as you can do with the Xsd.exe tool . E.g. XSD.exe /namespace:Generated.Xsd_1 /classes /outputdir:..\Classes Is there a way to do this by using classes in the .NET Framework instead of using the standalone tool? Shamelessly borrowed from here : using System; using System.IO; using System.Collections.Generic; using System.Reflection; using System.Text; using System.Xml; using System.Xml.Serialization; using System.Xml.Schema; using System.CodeDom; using System.CodeDom.Compiler; using Microsoft.CSharp; using NUnit.Framework; namespace