Skip to content
This repository was archived by the owner on Mar 17, 2025. It is now read-only.
This repository was archived by the owner on Mar 17, 2025. It is now read-only.

IntelliSense for XML nodes in project files missing #47

Open

Description

@fredrikhr

Installed product versions

  • Visual Studio: Visual Studio Enterprise 2017, Version 15.7.5
  • This extension: 1.1.0 (installed through the Visual Studio Extensions and Updates menu)

Description

When editing a csproj file and type a opening angle bracket <, I get no IntelliSense for the possible XML nodes used by the project system, like ItemGroup or PropertyGroup. The IntelliSense that is provided only shows the default XML IntelliSense for XML comments as shown in the screenshot below.

image

Current behavior

As shown in the screenshot above the IntelliSense only shows the three default XML IntelliSense suggestions which are always shown when VS has no schema information for the XML file it is editing.

The only time I get IntelliSense support is when editing the Include and Version attribute values of a PackageReference node like shown in the screenshot below.

image

Also pressing the key kombination for forcing the IntelliSense popup (Ctrl+J in my settings) does not give me any more IntelliSense

Expected behavior

IntelliSense should provide suggestions for the possible nodes in the CSPROJ file.

NOTE: This used to work perfectly fine some time ago. Maybe this is an Visual Studio update regression?

Activity

  1. Styxxy commented on Aug 29, 2018

    @Styxxy

    I have the same from time to time. But currently I don't have this extension installed. I guess it is a Visual Studio regression.

    You might want to submit an issue over at https://github.com/dotnet/project-system .

  2. chm-tm commented on Aug 25, 2021

    @chm-tm

    For me, it works when specifying the XML namespace by adding

    xmlns="http://schemas.microsoft.com/developer/msbuild/2003"
    

    to the Project element. This helps Visual Studio to select the correct schema. I don't think that this is related to this extension since Visual Studio finds the schema without this extension enabled.

    Maybe the real issue is some addiction to minimize the project file authoring 😉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions