I started getting warning messages like ' Could not find schema information for the element 'supportedRuntime'' after adding an app.config file to my project. It seems that Microsoft have not completely specified the 'startup' element in the relevant .xsd file. To fix this:

Navigate to the file 'C:\Program Files\Microsoft Visual Studio 10.0\Xml\Schemas\DotNetConfig.xsd'.

If the startup element looks like this:
<:xs:element name="startup" vs:help="configuration/startup">

Change it to:
<xs:element name="startup" vs:help="configuration/startup">
< xs:complexType>
< xs:choice minOccurs="1" maxOccurs="1">
< xs:element name="requiredRuntime" vs:help="configuration/startup/requiredRuntime">
< xs:complexType>
< xs:attribute name="version" type="xs:string" use="optional" />
< xs:attribute name="safemode" type="xs:boolean" use="optional" />
< /xs:complexType>
< /xs:element>
< xs:element name="supportedRuntime" minOccurs="1" maxOccurs="unbounded" vs:help="configuration/startup/supportedRuntime">
< xs:complexType>
< xs:attribute name="version" type="xs:string" use="optional" />
< xs:attribute name="sku" type="xs:string" use="optional" />
< /xs:complexType>
< /xs:element>
< /xs:choice>
< xs:attribute name="useLegacyV2RuntimeActivationPolicy" type="xs:boolean" use="optional" />
< !-- see http://msdn.microsoft.com/en-us/library/bbx34a2h.aspx -->
< /xs:complexType>
< /xs:element>

That should get rid of the annoying warnings.

Comments

Post a Comment

Popular posts from this blog

Path environmental variable on mac

To view your paths in terminal type: $ echo $PATH To add a path for the duration of this terminal session type: $ export PATH=$PATH:/my/new/path Note: the $PATH: is important as it adds the new path to your existing one. Without $PATH: the existing path is overwritten with the new one. The disadvantage with this approach is that you modification to the path is lost when the terminal session ends. To add to the path for all users permanently you need to edit the paths file in /etc.  In terminal navigate to /etc. Type $ sudo pico paths Add your path. Type ^x (note: ^ = ctrl key). You'll be prompted to save. Type Y . To view your paths using echo $PATH you'll need to reopen the terminal to see your changes.
Read more

Setting up node-sass on a mac

I followed the installation instructions for node-sass but it would not run from the terminal. The message was something like 'command not found'. Eventually I worked out that I needed to add  /Users/my_user_name/node_modules/node-sass/bin to the path. To do that see my post on setting the path on macs .
Read more