project-system: Schema-based auto-completion for .csproj not working

For some reasons, .csproj auto-completion doesn’t seem to work on my machine:

VS Edition: 2017 Enterprise. Installed workloads: x-plat .NET Core development.

Note: I suspect this issue may be caused by an incomplete setup, as I had to block the Microsoft.DiagnosticsHub.KB2882822.Win7 package to work around this issue: https://developercommunity.visualstudio.com/content/problem/3097/setup-operation-failed-vs2017-rc-community-invalid.html (that was not fixed in RTM, BTW).

Thing is everything works just fine, except the .csproj auto-completion. Is there any additional setup command I could run to register the missing .csproj schema?

/cc @davkean

About this issue

Original URL
State: closed
Created 7 years ago
Reactions: 1
Comments: 15 (8 by maintainers)

Most upvoted comments

Hi,

I have a very similar issue, however I am using the english locale. Somehow the intellisense for XML files (in my case axml for android Xamarin) stopped working after one of the last updates.

my catalog.xml.

<?xml version="1.0" encoding="utf-8"?>
<SchemaCatalog xmlns="http://schemas.microsoft.com/xsd/catalog">
  <Schema href="%InstallRoot%/Common7/IDE/Policy/Schemas/TDLSchema.xsd"              targetNamespace="http://www.microsoft.com/schema/EnterpriseTemplates/TDLSchema" />
  <Schema href="%InstallRoot%/Common7/IDE/Policy/Schemas/Policy.xsd"                 targetNamespace="http://schemas.microsoft.com/VSPolicy/PDLSchema"               />
  <Schema href="%InstallRoot%/xml/schemas/%LCID%/snippetformat.xsd"                  targetNamespace="http://schemas.microsoft.com/VisualStudio/2005/CodeSnippet"    />
  <Schema href="%InstallRoot%/xml/schemas/%LCID%/vstemplate.xsd"                     targetNamespace="http://schemas.microsoft.com/developer/vstemplate/2005"        />
  <Schema href="%InstallRoot%/xml/schemas/%LCID%/Microsoft.Build.xsd"                targetNamespace="http://schemas.microsoft.com/developer/msbuild/2003"           />
  <Schema href="%InstallRoot%/xml/schemas/%LCID%/vscontent.xsd"                      targetNamespace="http://schemas.microsoft.com/developer/vscontent/2005"         />
  <Schema href="%InstallRoot%/xml/schemas/%LCID%/customUI.xsd"                       targetNamespace="http://schemas.microsoft.com/office/2006/01/customui"          />
  <Schema href="%InstallRoot%/common7/packages/SDM/Schema/SystemDefinitionModel.xsd" targetNamespace="http://schemas.microsoft.com/SystemDefinitionModel/2005/1"     />

  <Association extension="config" schema="%InstallRoot%/xml/schemas/dotNetConfig20.xsd" condition="starts-with($TargetFrameworkMoniker, '.NETFramework,Version=v2.')" />
  <Association extension="config" schema="%InstallRoot%/xml/schemas/dotNetConfig30.xsd" condition="starts-with($TargetFrameworkMoniker, '.NETFramework,Version=v3.0')" />
  <Association extension="config" schema="%InstallRoot%/xml/schemas/dotNetConfig35.xsd" condition="starts-with($TargetFrameworkMoniker, '.NETFramework,Version=v3.5')" />
  <Association extension="config" schema="%InstallRoot%/xml/schemas/dotNetConfig40.xsd" condition="starts-with($TargetFrameworkMoniker, '.NETFramework,Version=v4.0')" />
  <Association extension="config" schema="%InstallRoot%/xml/schemas/dotNetConfig45.xsd" condition="$TargetFrameworkMoniker = '.NETFramework,Version=v4.5'" />
  <Association extension="config" schema="%InstallRoot%/xml/schemas/%LCID%/dotNetConfig.xsd" condition="starts-with($TargetFrameworkMoniker, '.NETFramework,Version=v4.5.') or starts-with($TargetFrameworkMoniker, '.NETFramework,Version=v4.6') or $TargetFrameworkMoniker = ''" />

  <Association extension="csproj" schema="%InstallRoot%/xml/schemas/%LCID%/Microsoft.Build.xsd" defaultNamespace="http://schemas.microsoft.com/developer/msbuild/2003" enableValidation="false"/>
  <Association extension="msbuildproj" schema="%InstallRoot%/xml/schemas/%LCID%/Microsoft.Build.xsd" defaultNamespace="http://schemas.microsoft.com/developer/msbuild/2003" enableValidation="false"/>
  <Association extension="proj" schema="%InstallRoot%/xml/schemas/%LCID%/Microsoft.Build.xsd" defaultNamespace="http://schemas.microsoft.com/developer/msbuild/2003" enableValidation="false"/>
  <Association extension="props" schema="%InstallRoot%/xml/schemas/%LCID%/Microsoft.Build.xsd" defaultNamespace="http://schemas.microsoft.com/developer/msbuild/2003" enableValidation="false"/>
  <Association extension="targets" schema="%InstallRoot%/xml/schemas/%LCID%/Microsoft.Build.xsd" defaultNamespace="http://schemas.microsoft.com/developer/msbuild/2003" enableValidation="false"/>
  <Association extension="vbproj" schema="%InstallRoot%/xml/schemas/%LCID%/Microsoft.Build.xsd" defaultNamespace="http://schemas.microsoft.com/developer/msbuild/2003" enableValidation="false"/>
  <Association extension="vcxproj" schema="%InstallRoot%/xml/schemas/%LCID%/Microsoft.Build.xsd" defaultNamespace="http://schemas.microsoft.com/developer/msbuild/2003" enableValidation="false"/>
</SchemaCatalog>

In Visual studio I tryed adding android schemes manually (even though they were already there)

Can you help me? Really killing productivity

Philipp

superphil0 on Apr 20, 2017

Thank you for helping us figure out the issue. There’s most like a setup bug here, I’ll forward that to the appropiate folks on our side.

RaulPerez1 on Mar 11, 2017