Originally posted by NickFitz
View Post
And this isn't a documentation issue - it's a Microsoft product not following it's own specifications (I've been told it will be fixed on Feb 3rd but I'm not holding my breath).
Comment