PMC: dotnet exec needs a managed .dll or .exe extension
See original GitHub issueSometimes on VS2017 (haven’t figured out why yet), the NuGetPackageRoot
property goes missing on the new .NET Core projects. This results in the following error.
dotnet exec needs a managed .dll or .exe extension. The application specified was ‘bin\Debug\netcoreapp1.0\ConsoleApp1.runtimeconfig.json’
I’ve mitigated this in the feature work nightly builds, but we should try to get to the bottom of it.
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
dotnet exec needs a managed .dll or .exe extension while ...
dotnet exec needs a managed .dll or .exe extension while adding Entity Framework Core (1.1.0) Migrations ... I'm having the same issue. Could...
Read more >dotnet exec needs a managed .dll or .exe extension while ...
[Solved]-dotnet exec needs a managed .dll or .exe extension while adding Entity Framework Core (1.1.0) Migrations-entityframework core.
Read more >EF Core tools reference (Package Manager Console)
As mentioned earlier, the tools have to execute application code at design time. To do that, they need to use the .NET Core...
Read more >Install Entity Framework Core
directly from Package Manager Console (PMC) within Visual Studio. Install EF Core Tools for dotnet CLI. If you want to execute EF Core...
Read more >Package Manager Console Commands
The commands that you execute to manage migrations from the ... The migration files will be placed in a folder name Migrations by...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
You can probably add the following inside a
PropertyGroup
to make it work on the NuGet releases.I’m running into the same issue, is there a workaround?