What is the best, or better RECOMMENDED, way of containing any schema or
stylesheet that is needed by an application, in a situation where you
are not sure any other type of access will be allowed. such as file://
or http://.
So far I've put all the XML within a resource file but I see that you
can just add an XML file to a .Net project and set it as an "embedded
resource". Perhaps this is better? Surely this must be a common
question so where exactly is the best place to put all my XML documents,
if I want them accessible within the assembly.
dickster - 20 Apr 2006 11:41 GMT
I suppose a factor in your decision depends on deployment.
I had been down this road where I tried embedding XSD files in an
assembly.
However I came stuck as my schemas included and imported other schemas.
That was .NET 1.1 - I believe there is now an XmlSchemaSet in 2.0 which
would support this
If you do not embed the XML file this gives you the flexibilty of
updating a referenced XML file without having to recompile the
assembly. e.g. web.config
Dickster