Closed mauricioralcala closed 8 years ago
@mrag89 can you try this again after clearing your NuGet caches? There was a problem with that package missing some of its target frameworks and I just uploaded what I believe is the correct version.
You can run dnu clear-http-cache
to clear out the cache, and you'll also want to run git clean -xdf
to make sure there aren't stale packages in the cloned repo.
@Eilon That didn't work but I figured it out. NuGet was installing the latest stable release of the package (1.1.0). The project required (1.1.0-alpha-00014). I had to allow NuGet to get prerelease packages and specify this version and now it works. I'm guessing NuGet wasn't smart enough to get the correct package because the version required is a prerelease package?
Hmm I'm not sure NuGet configuration should affect this at all. The NuGet.config files and project.json/project.lock.json files should have everything set up already.
Tried it again and right now I have to manually install the package on the console:
Install-Package System.Reflection.Metadata -Version 1.1.0-alpha-00014 -Pre
NuGet doesn't resolve the dependency automatically. Adding
"System.Reflection.Metadata": "1.1.0-alpha-00014"
to the project.json, makes the project run without issue. I created a pull request with this change here
@mrag89 sorry that still doesn't look right. The dependency closure should be picking up that package.
@pranavkm any idea why the alpha version of that package wouldn't be picked up?
@mrag89, could you try getting us the restore log? Might tell where it's picking up the packages from. Here's what I would try to make sure you aren't getting cached results:
dnu restore > dnurestore.log
and attach it here if it's still failing for you.
I cloned the repository and opened it in Visual Studio 2015. I tried to run it and got this:
I installed System.Reflection.Metadata through NuGet and still got this. Apologies if this is trivial. This is my first time trying VS or ASP.NET.