After consuming .net standard projects in a .net framework(4.6) console application, the dependencies of the .net standard projects are not copied into the output directory. This results in run time error of missing dlls. The "copy local" property is already true for the referenced projects. One possible solution is to add all the dependencies again in the console application, but is not a good idea. Is there a better solution to this?
相关问题
- Dotnet Core API - Get the URL of a controller meth
- Why am I unable to run dotnet tool install --globa
- Singleton with AsyncLocal vs Scope Service
- What would prevent code running in a Docker contai
- .NET Core gives unknown error while processing HTT
相关文章
- DotNet Core console app: An assembly specified in
- EF Core 'another instance is already being tra
- Re-target .NET Core to net471, net 472
- Publishing a Self-contained Console app fails
- Calling a .Net Framework 4 (or Mono) assembly from
- Can't get deleted items from OpenLDAP Server u
- Why doesn't AutogenerateBindingRedirects work
- proper way to sign .net core assembly
After going through an article by Scott Hanselman, below solution worked like a charm.
Add below line in the first "PropertyGroup" tag of the .net framework console application's ".csproj" file
There will not be any need to add again the .net standard projects' nuget dependencies in the console application.