New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update-package of ASP.NET web app generates warning related to file: source #3194

Closed
rrelyea opened this Issue Jul 22, 2016 · 0 comments

Comments

Projects
None yet
2 participants
@rrelyea
Contributor

rrelyea commented Jul 22, 2016

VS2015.U3 & .NET Core Tools for VS (preview 2) & NuGet: 3.5.0.1646

  1. File New project>ASP.NET Web Application>WebForms (w/ Web Forms, WebAPI checked), individual user accounts, do not host in cloud.
  2. builds successfully.
  3. Launch PMC
  4. ensure Package Source is "All"
  5. I have nuget.org (v3) and Microsoft Visual Studio Offline Packages enabled
  6. type "update-package" in console

Get the following output w/ 3-4 dozen of the "could not find a part of the path" errors...
(in the end the update is also failing, but I'll file a separate issue for that)

Attempting to gather dependency information for multiple packages with respect to project 'WebApplication1', targeting '.NETFramework,Version=v4.5.2'
Could not find a part of the path 'C:\Program Files (x86)\Microsoft SDKs\NuGetPackages\AspNet.ScriptManager.jQuery'.
Could not find a part of the path 'C:\Program Files (x86)\Microsoft SDKs\NuGetPackages\AspNet.ScriptManager.bootstrap'.
Could not find a part of the path 'C:\Program Files (x86)\Microsoft SDKs\NuGetPackages\Microsoft.AspNet.FriendlyUrls.Core'.

@rrelyea rrelyea added this to the 3.5 RTM milestone Jul 22, 2016

@rrelyea rrelyea added the Type:Bug label Jul 22, 2016

emgarten added a commit to NuGet/NuGet.Client that referenced this issue Jul 22, 2016

Avoid warnings when a package does not exist in a v3 folder
LocalFolderUtility logs errors around missing directories as warnings. When checking all sources for a package id is expected that the package will not exist. This change removes the extra unneeded warnings when probing folder paths.

Fixes NuGet/Home#3194

emgarten added a commit to NuGet/NuGet.Client that referenced this issue Jul 22, 2016

Avoid warnings when a package does not exist in a v3 folder
LocalFolderUtility logs errors around missing directories as warnings. When checking all sources for a package id it is expected that the package will not exist in some cases. This change removes the extra unneeded warnings when probing folder paths.

Fixes NuGet/Home#3194
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment