- Microsoft visual studio 2017 nuget browse not working how to#
- Microsoft visual studio 2017 nuget browse not working install#
- Microsoft visual studio 2017 nuget browse not working update#
I attempted again to install my own NuGet, it did so successfully and as expected (was not happening during the long glitch) the objects were found and the web application worked again. So I went to my C:\Users\AppData\USER\Local\Microsoft\VisualStudio\15.2* folder and removed it completely.Īfter that I the ACCESS DENIED issue went away with the side effect that I had to reinstall all extensions again.
Microsoft visual studio 2017 nuget browse not working how to#
When I saw this error happening again I knew how to get rid of it and thought, "hey, maybe that is what is keeping the NuGet package to be installed but not found or the problem with a direct assembly reference".
Microsoft visual studio 2017 nuget browse not working update#
Of all the Visual Studios I have used since 2002 this has been the most unstable! (and I have update 15.2). It has happened before since I installed to VS.2017. Today I could open the solutions but when I tried to download an extension (Tools | Extensions) I got an error message about an Access Denied or something like that. Which is strange because in the Solution Explorer I see the assembly reference and when I click on it (main application) I can navigate to all the objects that I have defined in that assembly. The system cannot find the file specified. 'MyPackage, Version=0.0.3.0, Culture=neutral, PublicKeyToken=null'. In this situation something odd happens, when coding I can reference ALL the objects in the referenced assembly (former NuGet) and therefore no compilation errors on the main project BUT when I then run the web application I get an internal error because it says FileNotFoundException: Could not load file or assembly Since NuGet seems to have stopped working (used to work well earlier) I opted for using an Assembly Reference rather than a NuGet (for now). Netcoreapp1.1 (.NEtCoreApp, Version=v1.1) I opened the NUPKG with NuGet Package Explorer and it shows this more or less: content\ I finally figured out why it did not work, the ItemGroup must be inside the Task. What is causing this Visual Studio generated Nuget package to be installed and yet act as if it has not even been referenced?Īs for copying to my local repository, I added this to CSPROJ but it was not working (somebody had suggested it as I put it). However, when I try to use ANY of the objects defined in that NuGet package I get a red highlight saying it is not found as if there was no NuGet or assembly reference to that DLL but there is! I see it listed in the project's NuGet dependencies. VS.2017 says it was successful at installing it. In it I browse to my local repository (where I have manually copied the NUPKG built by Solution A) and install my SolutionA.MyPackage into the web application.
Then I have Solution B which is an ASP.NET Core 1.1 web application. BTW How can I automatically copy the generated NUPKG to a local directory (my own repository)? This project builds just fine and the NUPKG is created. In the Package properties I filled all NuGet fields and selected to create the NuGet upon successful build.
0 kommentar(er)
