If anyone has been monkeying around (like I have) trying to use Entities in config files to avoid having to change system dependant info based on machine (i.e. Keep the info in a file on the system that gets imported by a DTD External Entity), I've found out why this doesn't work. Here's what the Microsoft dude said:
�While web.config is an XML file, what you�re proposing isn�t really possible. There are a couple of reasons you don�t want to do this to, the main one being that in v1.X we actually restart the entire application when the web.config file changes. We also aren�t using an XML parser to read the .config file. Due to the size/complexity of the file (not to mention the memory impact) we actually only read the file in chunks � so when you access a portion of web.config we scan the file for a reference to that location and then use an XML parser only on the section you are currently accessing (we then cache that in memory in a object/class format). In V2 �Whidbey� we�ll have programmatic APIs for accessing the file, but we still won�t support DTD.� I'm not sure if this applies to the App.config files also, but I would assume so. __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree ------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
