Project-system: IntelliSense for package reference versions while editing csproj

[srivatsn]

Today csproj has schema based IntelliSense but we should provide intellisense for package names and versions while editing the project file.

This likely requires a "MSBuild language service"

[RichiCoder1]

+1 Specifically for a MSBuild Language Service. Would love to see a powerful MSBuild lang service that could also be shared with Code/VS for Mac/other LSP implementer. Sure the guys on the code team would agree.

[michaeldaw]

One of my favorite features of the project.json system was having intellisense when manually adding Nuget packages, for both names and versions. I've found the csproj system frustrating because it lacks this.

[srivatsn]

There's now an extension for package intellisense built out of https://github.com/dotnet/ProjFileTools Keeping this issue to track putting that in the box.

[Daniel15]

Direct link to the VS Gallery page for the intellisense extension listed above: https://marketplace.visualstudio.com/items?itemName=ms-madsk.ProjectFileTools

I really wish this was built in to Visual Studio, like how it was built in for project.json

[avinash2wards]

Still not working even after installing the ProjFileTools extension in Visual studio 2017 Pro.

[davkean]

@avinash2wards What's not working? IntelliSense for packages? Or IntelliSense for MSBuild constructs?

[geirsagberg]

IntelliSense for the XML part seems to work, but not the IntelliSense for packages:

I am using VS2017 15.3 Preview 3, with Project File Tools 1.0.2.