You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 4, 2021. It is now read-only.
[NuGet] Fix projects not being re-evaluated after packages updated
Updating a package for multiple projects in one step results in the
NuGet package restore that is done at the end being a no-op. This
means that the project is not re-evaluated which can mean that the
AvailableItemNames are not updated. Updating a single NuGet package
does not have the same problem.
Also fixed a problem where a PackageReference project (non-sdk) was
not re-evaluated on restoring. This could also result in the
AvailableItemNames not being available to the project if the project
was missing its obj/project.assets.json file on being opened in the
IDE.
Copy file name to clipboardExpand all lines: main/src/addins/MonoDevelop.PackageManagement/MonoDevelop.PackageManagement.Tests/MonoDevelop.PackageManagement.Tests/InstallPackageWithAvailableItemNameTests.cs
+108Lines changed: 108 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -28,6 +28,7 @@
28
28
usingSystem.Threading.Tasks;
29
29
usingMonoDevelop.PackageManagement.Tests.Helpers;
30
30
usingMonoDevelop.Projects;
31
+
usingNuGet.Packaging.Core;
31
32
usingNuGet.Versioning;
32
33
usingNUnit.Framework;
33
34
usingUnitTests;
@@ -54,6 +55,72 @@ public async Task InstallPackage_PackageDefinesCustomAvailableItemNames_BuildAct
Copy file name to clipboardExpand all lines: main/src/addins/MonoDevelop.PackageManagement/MonoDevelop.PackageManagement/MonoDevelopBuildIntegratedRestorer.cs
Copy file name to clipboardExpand all lines: main/src/addins/MonoDevelop.PackageManagement/MonoDevelop.PackageManagement/MonoDevelopNuGetPackageManager.cs
0 commit comments