Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

'dotnet new' generates project referencing wrong package version

See original GitHub issue

Steps to reproduce

Install the latest build (2330)
Create a folder
dotnet new

Expected behavior

Generated project.json should work

Actual behavior

Generated project.json references bogus package version:

"dependencies": {
  "Microsoft.NETCore.App": {
    "type": "platform",
    "version": "1.0.0-rc2-3002330"
  }
},

Environment data

dotnet --info output: C:\proj\clicon>dotnet --info .NET Command Line Tools (1.0.0-rc2-002330)

Product Information: Version: 1.0.0-rc2-002330 Commit Sha: 3af38bf0fe

Runtime Environment: OS Name: Windows OS Version: 10.0.10586 OS Platform: Windows RID: win10-x64

Issue Analytics

State:
Created 7 years ago
Comments:15 (8 by maintainers)

Top GitHub Comments

1reaction

weshaggardcommented, Apr 9, 2016

I’ve published the later builds of the Microsoft.NETCore.App meta-package to the dotnet-core feed, and setup a build definition that should publish the latest builds as they complete. @gregg-miskelly please try again.

1reaction

weshaggardcommented, Apr 9, 2016

I’ve almost got our publishing automated and it is currently pushing this to dotnet-cli feed but I will actually push it to the dotnet-core feed instead (or perhaps both).

Top Results From Across the Web

Net picking wrong referenced assembly version

My new machine has the latest version of the assembly installed, so I thought I'd updated it (lets call the new version v2.0.0.0)....

Reference changed to wrong version of assembly #3415

During F# project build, an assembly reference could be changed to a wrong version of the same assembly from Reference Assemblies.

dotnet new --install incorrectly installs unlisted versions #894

I can install an unlisted package into a project by specifying the name. Being unlisted means it won't be included in search results...

How to resolve .NET reference and NuGet package version ...

Let's say we have 2 assemblies called Lib1 with different versions 1.0 and 1.1, which are referenced by different projects. Let's set CopyLocal ......

Troubleshoot .NET Framework targeting errors

To resolve the error, make sure that your application targets a .NET version that's compatible with the version that's targeted by the projects...