Skip to content

Commit 46ba601

Browse files
author
Ashish Jain
authored
Added known issue of initializing NuGet before migrator option is visible (NuGet#917)
1 parent 6eb516a commit 46ba601

File tree

1 file changed

+18
-0
lines changed

1 file changed

+18
-0
lines changed

docs/reference/migrate-packages-config-to-package-reference.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,24 @@ Visual Studio 2017 Version 15.7 Preview 3 and later supports migrating a project
2626
* Migration is not currently available for C++ and ASP.NET project.
2727
* Some packages may not be fully compatible with PackageReference. For more information, see [package compatibility issues](#package-compatibility-issues).
2828

29+
### Known Issues
30+
31+
1. The `Migrate packages.config to PackageReference...` option is not available in the right-click context menu
32+
33+
#### Issue
34+
35+
When a project is first opened, NuGet may not have initialized until a NuGet operation is performed. This causes the migration option to not show up in the right-click context menu on `packages.config` or `References`.
36+
37+
#### Workaround
38+
39+
Peform any one of the following NuGet actions:
40+
* Open the Package Manager UI - Right-click on `References` and select `Manage NuGet Packages...`
41+
* Open the Package Manager Console - From `Tools > NuGet Package Manager`, select `Package Manager Console`
42+
* Run NuGet restore - Right-click on the solution node in the Solution Explorer and select `Restore NuGet Packages`
43+
* Build the project which also triggers NuGet restore
44+
45+
You should now be able to see the migration option. Note that this option is not supported and will not show up for ASP.NET and C++ project types.
46+
2947
## Migration steps
3048

3149
> [!Note]

0 commit comments

Comments
 (0)