Skip to content

Commit 493a88b

Browse files
authored
Update NuGet-4.0-RTM.md
Added Known issues
1 parent 2f283d3 commit 493a88b

File tree

1 file changed

+65
-2
lines changed

1 file changed

+65
-2
lines changed

docs/Release-Notes/NuGet-4.0-RTM.md

Lines changed: 65 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,12 +29,75 @@ ms.reviewer:
2929

3030
# 4.0 RTM Release Notes
3131

32+
[NuGet 4.0 RC Release Notes](../release-notes/nuget-4.0-RC.md)
33+
34+
[NuGet 4.0 RTM for Visual Studio 2017]() TBD is focused on adding support for .NET Core scenarios, addressing key customer feedback and improving performance in a variety of scenarios. This release brings several improvements like support for PackageReference, NuGet commands as MSBuild targets, background package restore, and more.
35+
3236
## Known issues
3337

38+
#### NuGet restore may fail when you have multiple projects referencing another project in a solution
3439

35-
[NuGet 4.0 RC Release Notes](../release-notes/nuget-4.0-RC.md)
40+
* #### Issue:
41+
NuGet restore may not work if, in a solution, you have project references to the same project with different casing or with different relative paths. [NuGet#4574](https://github.com/NuGet/Home/issues/4574)
3642

37-
[NuGet 4.0 RTM for Visual Studio 2017]() TBD is focused on adding support for .NET Core scenarios, addressing key customer feedback and improving performance in a variety of scenarios. This release brings several improvements like support for PackageReference, NuGet commands as MSBuild targets, background package restore, and more.
43+
* #### Workaround:
44+
Fix the casings or relative paths to be the same for all project references.
45+
46+
#### While using Package Manager Console, 'Enter' key may not work
47+
* #### Issue:
48+
Occasionally, the enter key does not work in the Package Manager Console. If you see this, please check out the progress on the fix, and provide any additional helpful information about your repro steps. [NuGet#4204](https://github.com/NuGet/Home/issues/4204) [NuGet#4570](https://github.com/NuGet/Home/issues/4570)
49+
50+
* #### Workaround:
51+
Restart Visual Studio and open the PMC before opening the solution. Alternatively, try deleting the project.lock.json and restoring again.
52+
53+
#### In .NET Core projects, you may end up in infinite restore loop when you use a package containing an assembly with an invalid signature
54+
* #### Issue:
55+
Occassionally, when you use a package containing an assembly with an invalid signature or when the package version is set with 'DateTime' ticker, it causes package auto-restore to run in infinite loop. [NuGet#4542](https://github.com/NuGet/Home/issues/4542)
56+
57+
* #### Workaround:
58+
There is no workaround at this time.
59+
60+
#### You will be unable to view, add, or update DotNetCLITools, using Nuget Package Manager
61+
* #### Issue:
62+
NuGet Package Manager does not display and does not allow add/update of DotNetCLITools. [NuGet#4256](https://github.com/NuGet/Home/issues/4256)
63+
64+
* #### Workaround:
65+
DotNetCLIToolReferences must be manually edited in your project file.
66+
67+
#### NuGet restore will fail when you set PackageId property for projects
68+
* #### Issue:
69+
For .NET Core projects, NuGet restore in Visual Studio does not respect PackageId property of projects. [NuGet#4586](https://github.com/NuGet/Home/issues/4586)
70+
71+
* #### Workaround:
72+
Run restore using the command-line.
73+
74+
#### When your project does not have 'obj' folder, package restore may fail
75+
* #### Issue:
76+
Visual Studio fails to restore PackageReferences when 'obj' folder has been deleted. [NuGet#4528](https://github.com/NuGet/Home/issues/4528)
77+
78+
* #### Workaround:
79+
Create 'obj' folder manually and the restore should work.
80+
81+
#### Manually updating packages using Update-Package in console may fail
82+
* #### Issue:
83+
Using Update-Package manually in the console only works once for PackageReferences projects that were just converted. [NuGet#4431](https://github.com/NuGet/Home/issues/4431)
84+
85+
* #### Workaround:
86+
There is no workaround at this time.
87+
88+
#### Retargeting target framework version may lead to incomplete Intellisense
89+
* #### Issue:
90+
Retargeting target framework version may lead to incomplete Intellisense, in Visual Studio. This happens when you are using PackageReferences as the package manager format. [NuGet#4216](https://github.com/NuGet/Home/issues/4216)
91+
92+
* #### Workaround:
93+
Do a manual restore.
94+
95+
#### msbuild /t:restore fails when a project targeting .NET461 references another project targeting .NETStandard
96+
* #### Issue:
97+
msbuild /t:restore fails when a PackageReferenece based project targeting .NET461 references another PackageReference based project targeting .NETStandard. [NuGet#4532](https://github.com/NuGet/Home/issues/4532)
98+
99+
* #### Workaround:
100+
There is no workaround at this time.
38101

39102
[Issues List](https://github.com/NuGet/Home/issues?q=is%3Aissue+is%3Aclosed+milestone%3A%224.0 RTM")
40103

0 commit comments

Comments
 (0)