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 razor-precompile cannot find project.json but I am using csproj

See original GitHub issue

Steps to reproduce

I tried the following command on ASP.NET Core 1.1 project with .csproj file: dotnet razor-precompile --output OutputFolder

Expected behavior

I expected the views to be compiled and placed on the OutputFolder

Actual behavior

I get error:
Could not find file 'C:\...\project.json'

My project is using ASP.NET Core 1.1 with **.csproj** file ... I do not have a project.json anymore.

Am I missing something?

Environment data

dotnet --info output:

NET Command Line Tools (1.0.0-preview4-004124)

Product Information: Version: 1.0.0-preview4-004124 Commit SHA-1 hash: eb8e0cfa40

Runtime Environment: OS Name: Windows OS Version: 10.0.10586 OS Platform: Windows RID: win10-x64 Base Path: C:\Program Files\dotnet\sdk\1.0.0-preview4-004124

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:8 (2 by maintainers)

github_iconTop GitHub Comments

coolcshcommented, Dec 1, 2016

I just have to apologize for the confusing place we are in. .NET Core 1.0 and 1.1 runtimes are both RTM and fully supported. Any application you build on either of those frameworks is completely go live, can be run in production and you can call and our support teams will help you out.

The tooling is what is in “preview” and it will RTM with Visual Studio 2017. We have the Visual Studio 2015 based project.json based tooling which is full featured and stable. With Visual Studio 2017 RC we released an alpha version of the new .csproj based tooling which is not as stable. We have some updates to the RC that are coming that will increase the stability before RTM.

hyukselcommented, Nov 29, 2016

But yet you release a Visual Studio 2017 RC with go live? I have the same problem. If i want to run my solution on IIS on staging server, now my clients can not see the progress 😦

What’s the point then for releasing 2017 RC and also moving forward to csproj instead of project.json if you don’t support the whole bits? So I have to convert everything back to VSS 2015 now?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Couldn't find 'project.json' in current directory on dotnet build
The Project has no project.json file due its usage of core v1.1. So all projects within the Solution have their own *.csproj...
Read more >
Fixing missing project.json error in old csproj format
json error in old csproj format. The cause comes from left over files in your obj catalogues. The file in question seems to...
Read more >
R.I.P project.json - Out with the new, in with the old
An early look at the new csproj project format which replaces project.json in Visual Studio 2017 for .NET Core projects.
Read more >
NETSDK1004: Assets file not found - .NET CLI
Learn about .NET SDK error NETSDK1004, which occurs when the project.assets.json file is not found.
Read more >
project.json File Reference for NuGet
NuGet 3.x+. The project.json file maintains a list of packages used in a project, known as a package management format.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found