tag:blogger.com,1999:blog-20196010.post114025883026364693..comments2023-04-02T10:19:37.644+02:00Comments on Frederik Gheysels' DevLog: A 'problem' with custom configSections in .NET 2.0Frederik Gheyselshttp://www.blogger.com/profile/15416462808733991725noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-20196010.post-1143885397835730272006-04-01T11:56:00.000+02:002006-04-01T11:56:00.000+02:00If you still have those 'information messages' say...If you still have those 'information messages' saying, 'Cannot find schema information for ...', you can make them dissappear:<BR/>You'll have create your own XSD that describes your custom configuration section, and save it to the <BR/>\Program Files\Microsoft Visual Studio 8\Schemas\<BR/>directory.<BR/>Then, in the DotNetConfig.xsd file (which is located in that directory as well), you'll have to include the schema-file (xsd) you've just created, by adding this line:<BR/><xs:include schemaLocation="mySchemaFile.xsd" />Frederik Gheyselshttps://www.blogger.com/profile/15416462808733991725noreply@blogger.comtag:blogger.com,1999:blog-20196010.post-1143884337029167762006-04-01T11:38:00.000+02:002006-04-01T11:38:00.000+02:00I am playing a bit with the new Configuration clas...I am playing a bit with the new Configuration classes in .NET 2.0, and again, I ran into this stupid 'could not find schema information ... ' warning.<BR/>This is very annoying, and since I treat my warnings as errors, it is even more annoying.<BR/>So, I crawled a bit on the Internet, and I've found this post by Peter Ritchie, which was very helpfull in my situation:<BR/><A HREF="http://www.peterritchie.com/Hamlet/Articles/75.aspx" REL="nofollow">Silly config file warnings</A><BR/><BR/>Peter Ritchie has created an updated version of the DotNetConfig.xsd file. I've replaced the one that was installed by VS.NET by this updated version, and now it works like a charm.Frederik Gheyselshttps://www.blogger.com/profile/15416462808733991725noreply@blogger.com