Identityserver4: 9_Combined_AspId_and_EFStorage - Build Error

[valentinacupac]

Please only use the issue tracker for bug reports and/or feature requests. For general security questions, or free or commercial support options do __not__ use the issue tracker and instead see here for more details.

For bug reports, include the relevant log files related to your issue. See here how to enable logging. Delete this line once you have.

Finally, please keep the issue concise and to the point. If you paste in more code than the text for the issue you are reporting then we will most likely not read it.

Issue / Steps to reproduce the problem

1. Cloned the repository
2. Opened IdentityServer4\samples\Quickstarts\9_Combined_AspId_and_EFStorage\Combined.sln in Visual Studio 2019.
3. Re-built the solution. Got build errors.
4. Tried also NuGet package restore. Got build errors.

See image:

Relevant parts of the log file

<log goes here>

[brockallen]

perhaps a clone issue. it builds for me.

[valentinacupac]

I tried cloning again, and got build issue again, so I tried to see what could be the possible causes.

I also tried to open up another solution, IdentityServer4.Core.sln, and I get the same error as for the sample project, so it seems I cannot build any solution from IdentityServer4...

When trying to do nuget restore: Error occurred while restoring NuGet packages: The local source 'D:\GitHub\IdentityServer\IdentityServer4\nuget' doesn't exist.

[valentinacupac]

UPDATE: The issue was caused by NuGet localsource, I found the solution here: https://stackoverflow.com/questions/49446394/unable-to-find-nuget-local-source-error-occurred-while-restoring-nuget-packages

So I did the following, in case it occurs to someone else in the future:

1. Tools > Options > NuGet Package Manager
2. I saw that inside Available sources "IdentityServer Local" was referencing \IdentityServer4./nuget
3. So I changed it to \IdentityServer4

Now the nuget packages are able to be restored and now the build works.

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.