Ron,
It's a quirk. I think its a bug, but it is by design to aid performance.
It's actually even uglier than you describe.
a) you have to (in at least some cases) close _all_ versions of Visual
Studio, not just the one you're working with
b) Visual Studio does not recognize the xsi:schemaLocaion in your document.
That is the schema that's used by default in a validating reader. Thus you
can easily have VS validate against a different schema than used at design
time.
You can search MSDN for "wish" and I think you'll find the best location to
report this as something to fix in Whidbey.
--
Kathleen Dollard
Microsoft MVP
Author "Code Generation in Microsoft .NET"
"Ron Rohrssen" <rl******@killspam.rockwellcollins.com> wrote in message
news:07****************************@phx.gbl...
I've been working on learning XML schemas and trying to
make use of the MS classes for validating data against a
schema.
So, I've been trying to work through some simple schemas
and instances. But, the parser inside of Visual Studio
seems to frequently validate against a cached version of
the schema.
Occassionally I have an XML file that won't validate
against the schema, which I'm sure is correct. I exit
VS.NET and open it [VS.NET] up again. Then the XML file
will validate without errors.
Am I doing something wrong? Or, is this just a quirk of
the parser inside VS.NET?