Implement completion for package references in csproj files

[jchannon]

Environment data

dotnet --info output:

.NET Command Line Tools (1.0.0-rc4-004706)

Product Information:
 Version:            1.0.0-rc4-004706
 Commit SHA-1 hash:  e38bc4950c

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  10.11
 OS Platform: Darwin
 RID:         osx.10.11-x64
 Base Path:   /usr/local/share/dotnet/sdk/1.0.0-rc4-004706

VS Code version: 1.8.1 ee428b0eead68bf0fb99ab5fdc4439be227b6281
C# Extension version: 1.6.2

Steps to reproduce

Edit a netcore csproj

Expected behavior

Intellisense when trying to get nuget package names and versions. This is currently possible in project.json. Editing this file manually without intellisense is a bit painful.

Actual behavior

No behaviour its just editing a text file

[DustinCampbell]

This will likely happen at some point, but not for awhile (unless somebody wants to contribute! 😄)

[cmurczek-it]

Hi,
I'd be willing to give this a shot. I think this was/is a killer feature and I'm already starting to miss it! ;)

Are you planning on merging PR #224? In that case I should make the implementation for csproj somehow fit into what was there for project.json. Otherwise I'd use the project.json implementation as a template for csproj wherever it makes sense.

I'd start by raising the PR asap so you can easily follow up on progress. Since you tagged this issue as Backlog, should I target master or future with my PR?

Let me know your plans regarding #224 so I can compile the task list for my PR.

Cheers,
Christoph

[DustinCampbell]

You're welcome to take a stab at it! It'll be quite some time before I'm able to get to this.

[strake7]

Indeed editing without the intellisense is a bit of a pain so I've been using the dotnet cli to manipulate nuget packages. Though I would use this should it be completed. Good luck!

[tintoy]

BTW, there's a new extension for Visual Studio 2017 that provides PackageReference intellisense:

https://github.com/dotnet/ProjFileTools

Might help if anybody is curious about the mechanics of how to accomplish this.

[DustinCampbell]

@mlorbetske and I were talking about how we might pull this into OmniSharp and C# for VS Code just yesterday.

[stuartleeks]

Go go @mlorbetske :-)