Databases
StackOverflow2013
Postsdbo
POMSBuild Error: The attribute "Remove" in element <ProjectReference> is unrecognized
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMSBuild Error: The attribute "Remove" in element <ProjectReference> is unrecognized
    primarykey
    data
    text
    <p>I'm attempting to setup a .csproj file to have a conditional item group which will remove all of the elements in the &lt;ProjectReference&gt; item group.</p> <p>For example:</p> <pre><code>&lt;ItemGroup&gt; &lt;ProjectReference Include="..\..\..\..\Projects\Registrar\Ucsb.Sa.Registrar.Common\Ucsb.Sa.Registrar.Common\Ucsb.Sa.Registrar.Common.csproj"&gt; &lt;Project&gt;{1EDDDE57-0181-41B4-B2AE-FB76450F85C8}&lt;/Project&gt; &lt;Name&gt;Ucsb.Sa.Registrar.Common&lt;/Name&gt; &lt;/ProjectReference&gt; &lt;/ItemGroup&gt; &lt;ItemGroup Condition="$(OnBuildServer) == 'true'"&gt; &lt;ProjectReference Remove="*" /&gt; &lt;/ItemGroup&gt; &lt;ItemGroup Condition="$(OnBuildServer) == 'true'"&gt; &lt;Reference Include="Ucsb.Sa.Registrar.Common"&gt; &lt;SpecificVersion&gt;False&lt;/SpecificVersion&gt; &lt;HintPath&gt;$(RegCommonDll)&lt;/HintPath&gt; &lt;/Reference&gt; &lt;/ItemGroup&gt; </code></pre> <p>But, when I load the project into VS 2008, I get the error message 'The attribute "Remove" in element &lt;ProjectReference&gt; is unrecognized". The odd thing is that the Remove attribute is in the schema (C:\Program Files\Microsoft Visual Studio 9.0\Xml\Schemas\1033\MSBuild\Microsoft.Build.Core.xsd). There is MSDN documentation on it (<a href="http://msdn.microsoft.com/en-us/library/bb651786.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/bb651786.aspx</a>). And, there is a comment about it at the bottom of the MSDN article titled &quot;MSBuild Items&quot;.</p> <p>The .csproj file seems to be pointing to .NET 3.5; but I am unable to verify if that version of msbuild is being used to load the project (does anyone know how to do that?)</p> <p>First line of .csproj file:</p> <pre><code>&lt;Project ToolsVersion="3.5" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003"&gt; </code></pre> <p>PS. I got the idea to use the conditionals from <a href="https://stackoverflow.com/questions/857379/build-with-msbuild-and-dynamically-set-project-references">Build with msbuild and dynamically set project references</a></p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USsmaglio81
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMSBuild Error: The attribute "Remove" in element <ProjectReference> is unrecognized
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI also tried changing the registry keys to default to 3.5. These keys don't configure Visual Studio, but instead configure the default values when creating a new project (http://msdn.microsoft.com/en-us/library/bb397428.aspx, \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\3.5\, \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\2.0\). That, of course, didn't do the trick. I also went through the PATH Environment Variable and replaced all references to the 2.0 directory with 3.5. Again, this didn't produce a solution.
      singulars
      1. POMSBuild Error: The attribute "Remove" in element <ProjectReference> is unrecognized
      1. USsmaglio81
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload