dotnet
IntelliSense for package reference versions while editing csproj
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"
+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.
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.
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.
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
Still not working even after installing the ProjFileTools extension in Visual studio 2017 Pro.
@avinash2wards What's not working? IntelliSense for packages? Or IntelliSense for MSBuild constructs?
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.
Any update on the IntelliSense working for package references & versions as mentioned by @geirsagberg?
Hey, I've noticed this issue has been dragging on for a while now, and it's still not fixed. Any updates on that? I see other people are hitting the same issue too, which shows there's a real need for a solution. There are tools like ProjFileTools and MonoDevelop.MSBuildEditor that could help, but they're either experimental or have been discontinued. Plus, MonoDevelop.MSBuildEditor was even promoted on the Visual Studio blog as offering a 'new MSBuild editing experience.' Wouldn't it make sense to integrate these into Visual Studio instead of starting from scratch?
cc @John0King @mhutch
