Project-system: Make the PackageReference support general purpose for all languages

[davkean]

We added support for <PackageReference /> this release, but other languages/project types are interested in consuming it including C++, MSIX deployment and NuGetizer.

The work required, that I can see is:

• [x] General purpose the PackageRestoreInitiator and make it work for all project types. Done - works via PackageReferences capability (16.1)
• [x] General purpose the ProjectAssetsFileWatcher and make it work for all project types. Done - works via PackageReferences capability (16.1)
• [x] Embed restore rules into .NET Project System
• [x] NuGet features should light up for projects that have the capability; "PackageReferences" (~https://github.com/NuGet/Home/issues/9957~, https://github.com/NuGet/NuGet.Client/pull/3644)
• [ ] [<ProjectAssetsFile> needs to be moved lower than the SDK](https://github.com/dotnet/sdk/issues/13255)
• [ ] Figure out how all these project types pick up the NuGet SDK tasks/targets that produce assets (references, copy to output items, etc) for consumption during build and assets that are used to populate the DependenciesTree.
• [ ] Move PackageRestore code to CPS -or- install .NET Project System in all the same places as CPS
  
  
  
  • Without this, Package Restore code would not light up if we weren't installed.
  
  

[kzu]

Is there an update on when the "Microsoft.PackageDependency.Sdk` will ship @natidea?

I'm on 15.6 Preview 3 but it's not there yet :(

[natidea]

Is there an update on when the "Microsoft.PackageDependency.Sdk` will ship

@kzu our most recent discussions on this have focused on refactoring these tasks because of performance concerns. The SDK team has already made changes to the command line build to avoid this code path because it was too expensive. For the dependencies tree, we are considering several options including perhaps bypassing MSBuild to improve the performance profile. /cc @nguerrera @livarcocc

I don't have any other updates yet, but will post something as our plans unfold.

[kfertitta]

Is there an update on this issue? We have a custom project system for which we really need to support PackageReference. We'd be happy to require the latest shipping VS version as the minimal version, but it's not clear if support is yet available.

Thanks in advance.

[kzu]

Ditto, would love to see this happen 👍

[DevKumar4Git]

We are providing guidance to package build tools as NuGet & use package reference to pull it down while using build/restore.
https://docs.microsoft.com/en-us/nuget/create-packages/creating-a-package#including-msbuild-props-and-targets-in-a-package

If CPS doesn't support this for custom project types, then its an adoption blocker & lot of overhead for developers who intend to quickly use this to build project systems. Would love to get this prioritized or hear about a workaround that can be easily removed once the support comes back.

[amis92]

Since it's a blocker for sfproj supporting SDK-style, shouldn't this be triaged a bit higher than 'Unknown/Backlog'?

[aL3891]

Any update on this one?

[bhardwajs]

Since it's a blocker for sfproj supporting SDK-style, shouldn't this be triaged a bit higher than 'Unknown/Backlog'?

Any updates on this one? Unblocking https://github.com/microsoft/service-fabric/issues/885 will be helpful.

[davkean]

Filed https://github.com/dotnet/project-system/issues/6594 to track the the dependency tree, and making this bug just about PackageReference support (restore, lighting up NuGet features, etc).

[kfertitta]

@davkean Great to see this. We've been blocked on it for quite some time on one of our project systems. I'd like to setup a test VM to check this out. Traversing the fan-out of issues from this one, I can see there's a lot of cross talk with NuGet.Client. Do I just need to build master branches of this repo and NuGet.Client, or other repos as well? And, what version of VS do I need to use?

Really eager to jump on this and validate things. Any advice/guidance is very much appreciated.

[davkean]

Kirk, understand your excitement. :)

However, this is still all very experimental and all the pieces don't land until Preview 4. We needed changes in CPS to make this work.

[kfertitta]

@davkean Thanks much for the quick reply. Really appreciate you taking this issue up. We managed to get the nomination to "work" in that our PRs would restore upon opening in VS, but without proper support in the Package Manager, it's just not shippable.

We'll hang tight until Preview 4. Any timing hints on that release that are able to be shared?

Thanks again.

[davkean]

I can't give a date, but look back at the times between previews of large releases (this release and 16.5 for example) and this should give you an indication of how this plays out.

With my capabilities change in Preview 3 (and that PR that got merged in on NuGet), the package manager will light up if you define PackageReferences, but I suspect we might not iteract well with you're own nomination.

[kfertitta]

I can't give a date, but look back at the times between previews of large releases (this release and 16.5 for example) and this should give you an indication of how this plays out.

With my capabilities change in Preview 3 (and that PR that got merged in on NuGet), the package manager will light up if you define PackageReferences, but I suspect we might not iteract well with you're own nomination.

Understood. Thanks again.

[stevenbrix]

I've run into problems when adding nuget references into the .wapproj, nuget will add the assemblies as references, which causes the .wapproj to fail. just want to mention it in case this scenario needs to be tested

[edwardskrod]

@stevenbrix

I've run into problems when adding nuget references into the .wapproj, nuget will add the assemblies as references, which causes the .wapproj to fail. just want to mention it in case this scenario needs to be tested

Have you tried again? We added the ProjectReferences capability to wapproj a few weeks back. I don't know whether that will make it work for you.

[kfertitta]

@davkean I saw the 16.8 Preview 4 bits up today and tried them out on our VM with our actual custom CPS-based project system (that also uses a custom MSBuild SDK). It seems to be working. I can now see the obj folder populated with the restore spew upon opening the solution. I was also able to open the NuGet package manager on our custom project and use it to install/uninstall some well-known NuGet packages.

So, is there outstanding work to be done on this issue (and the others that fan out from this one)? Definitely unblocks us, it seems. Are there more scenarios I should test or that may be helpful in verifying your work on this?

Thanks in advance.