Here is the complete test case code: using System; using System. I'll try to help with the latter in the coming months. It'd be cool if someone just dropped a blog post as a "ping" every few weeks like "We're still here! " kind of like an Out of Office Response, but for blogs.I’m currently working on an XML File Explorer application, which I intend on highlighting XML files which do not conform to an XSD schema, as part of this I have created a class for containing the details of performing XSD validation against an XML document, which I thought I would share with you (although the XML File Explorer will be open source).The code is pretty simple but I’m a fan of hiding away any complexities so that I don’t have to think about them when I’m working on a project.I don’t want this, I want it to remain as a XSD schema file.
I found a lot of examples doing it without LINQ, but how would you do it with LINQ?Even though we hear about technologies like LINQ to SQL and LINQ to Entities or ASP. For example, LINQ to XSD was mentioned in June of 2007, looked rockin' sweet, and then went silent.NET MVC and WCF and get confused about if they are complementary, there (usually) a plan behind the whole stack, even if that plan isn't very well-communicated. However, small teams like this continue to move the ball forward, but we (the outside world) don't hear from them.I'm trying to avoid specifying the structure of the entire XML file because the library shouldn't care what the entire XML looks like as long as the specific elements it needs are structured correctly.To that end, I have 3 separate is another good idea that should have occurred too me (I spent too much time trying to find out how to convert it, and i missed the obvious solution).