1

My question is identical to Nuget: Migrating multiple large Solutions to PackageReference which has an irrelevant answer.

So, how do we do it? I do not want to click each and every project amongst the hundreds we have.

Also, about Asp.Net projects - they do not support PackageReference, even if migrated manually? Or just the migration procedure from Microsoft does not support it?

mark
  • 59,016
  • 79
  • 296
  • 580
  • For your question about ASP.NET, from the [PackageReference docs](https://learn.microsoft.com/en-us/nuget/consume-packages/package-references-in-project-files): "ASP.NET apps targeting the full .NET Framework include only [limited support](https://github.com/NuGet/Home/issues/5877) for PackageReference.". – John H Oct 01 '20 at 23:18
  • That is a very useful tidbit. I am OK to leave asp.net as is. Still a hundred or two of regular class libraries to migrate. – mark Oct 01 '20 at 23:59
  • Developed my own - https://github.com/MarkKharitonov/NuGetPCToPRMigrator Seems to work fine. – mark Oct 04 '20 at 22:52
  • It's great that you developed a solution. Please post an actual answer, not just a link to your GitHub project, on the question you state this is a duplicate of. I expect such an answer would be quite useful to future visitors. – Makyen Oct 04 '20 at 23:18
  • OK - https://stackoverflow.com/a/64200862/80002 – mark Oct 04 '20 at 23:35

0 Answers0