Mielz' Thingamajig

public Example(XElement node)
{
    string str = (string)node.Attribute("Name"); //Convert it to a string
    int number = (int)node.Attribute("Number");  //Convert it to an int
}

As you can see here, the Attribute property of type XAttribute can be casted to an String aswel to an Int (and several more types like DateTime, TimeSpan, Guid etc). Which is unusual since these types are not in the inheritence chain of XAttribute. This behaviour is conceived by using the "explicit" operator. By implementing this operator, which is easy,  you are responsible for converting the current type to your target type by doing so:

class XAttribute {
  //More really exciting code

  public static explicit operator string(XAttribute a)
  {
      if (a == null)
      {
            return null;
      }
      return a.value;
  }
}

Now this isn't exactly rocket science or anything but good to know when you encouter this behaviour in your new Xlinq applications. I've somewhat mixed feelings on this operator since there is no visual intellisense support for it available, thus there is no way of telling wheter you can simply cast an type using that operator or need to implement your own custom casting. Except for that minor point it certainly eases writing Xlink queries. Also, there is an "implicit" operator which does a  similiar thing except you don't have to write the cast explicitly, thus typing:

string str = node.Attribute("Name")

will suffice. (Note that the XAttribute doesnt implement the "implicit" operator so this won't compile)

More information on explicit and implicit on msdn: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/csref/html/vclrfexplicit.asp