question-mark
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.

Internal error: new deps file generation logic did not produce the same result as the old logic

See original GitHub issue

I’ve included both the old and new deps files here.

Microsoft.AspNetCore.Razor.Test.MvcShim.deps.zip

Original error:

C:\Program Files\dotnet\sdk\3.0.100-preview4-011216\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.targets(145,5): error : Internal error: new deps file generation logic did not produce the same result as the old logic. [C:\Github\aspnet\AspNetCore-Tooling\src\Razor\test\Microsoft.AspNetCore.Razor.Test.MvcShim\Microsoft.AspNetCore.Razor.Test.MvcShim.csproj]
C:\Program Files\dotnet\sdk\3.0.100-preview4-011216\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.targets(145,5): error :     Please file an issue for this at https://github.com/dotnet/sdk and include the following two files:  [C:\Github\aspnet\AspNetCore-Tooling\src\Razor\test\Microsoft.AspNetCore.Razor.Test.MvcShim\Microsoft.AspNetCore.Razor.Test.MvcShim.csproj]
C:\Program Files\dotnet\sdk\3.0.100-preview4-011216\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.targets(145,5): error :     Deps file from old logic: C:\Github\aspnet\AspNetCore-Tooling\artifacts\bin\Microsoft.AspNetCore.Razor.Test.MvcShim\Debug\netcoreapp3.0\Microsoft.AspNetCore.Razor.Test.MvcShim.deps.json [C:\Github\aspnet\AspNetCore-Tooling\src\Razor\test\Microsoft.AspNetCore.Razor.Test.MvcShim\Microsoft.AspNetCore.Razor.Test.MvcShim.csproj]
C:\Program Files\dotnet\sdk\3.0.100-preview4-011216\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.targets(145,5): error :     Deps file from new logic: C:\Github\aspnet\AspNetCore-Tooling\artifacts\bin\Microsoft.AspNetCore.Razor.Test.MvcShim\Debug\netcoreapp3.0\Microsoft.AspNetCore.Razor.Test.MvcShim.deps.new.json [C:\Github\aspnet\AspNetCore-Tooling\src\Razor\test\Microsoft.AspNetCore.Razor.Test.MvcShim\Microsoft.AspNetCore.Razor.Test.MvcShim.csproj]
C:\Program Files\dotnet\sdk\3.0.100-preview4-011216\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.targets(145,5): error :     You can work around this by setting the DepsFileGenerationMode MSBuild property to 'old' [C:\Github\aspnet\AspNetCore-Tooling\src\Razor\test\Microsoft.AspNetCore.Razor.Test.MvcShim\Microsoft.AspNetCore.Razor.Test.MvcShim.csproj]
dotnet --info:
.NET Core SDK (reflecting any global.json):
 Version:   3.0.100-preview4-011216
 Commit:    19c844a865

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.17763
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\3.0.100-preview4-011216\

Host (useful for support):
  Version: 3.0.0-preview4-27613-07
  Commit:  5c329c85ae

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:2
  • Comments:30 (4 by maintainers)

github_iconTop GitHub Comments

2reactions
CatoLeanTruetschelcommented, Apr 25, 2019

@sabyabr Does the property in your .csproj look like this?

1reaction
thohngcommented, May 7, 2019

@dsplaisted it seems the issue is fixed in Net Core 3.0 Preview 5

Read more comments on GitHub >

github_iconTop Results From Across the Web

Error Codes
A list of Yarn's error codes with detailed explanations.
Read more >
Could not resolve all dependencies for configuration
I created gradle.properties file in my /home/user/.gradle folder with these setting. systemProp.http.proxyHost=proxy systemProp.http.proxyPort ...
Read more >
Upgrading your build from Gradle 6.x to 7.0
The result of dependency resolution for your custom configuration may not be the same as Gradle 6.x or before. You may notice missing...
Read more >
Top 10 Mistakes That Django Developers Make
In this tutorial, we will look at some common mistakes that are often made by Django developers and ways to avoid them. Whether...
Read more >
Error Messages
0 Success. The operation succeeded. The database server returns this SQLCODE value to an application when an SQL statement executes successfully.
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 Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found