Closed RehanSaeed closed 6 years ago
The solution was to make System.Runtime
a build time dependency like so:
// Old
"System.Runtime": ""
// New
"System.Runtime": {
"type": "build",
"version": ""
}
I'm not entirely sure what this means so any helpful comments would be much appreciated.
We've also just hit this, see https://github.com/elastic/elasticsearch-net/issues/1774
Setting "type": "build"
as @RehanSaeed mentioned above does seem to do the trick, but I have no idea what the implications are. Is there any documentation on this?
Also just ran intom this. Same concern as gmarz.
This issue is being closed because it has not been updated in 3 months.
We apologize if this causes any inconvenience. We ask that if you are still encountering this issue, please log a new issue with updated information and we will investigate.
Not sure where to post this...
I have the following project.json using several frameworks from .NET 4, all the way up to 4.6.1 and also Serilog is added as a global dependency, while all the frameworks except .NET 4 also have Serilog.Sinks.EventLog as an additional dependency. If I remove the
System.Runtime
references I get 37 of these errors:If I publish my NuGet package and then try to install it, I get the following error:
Why am I being forced to add System.Runtime and what does this achieve?
My project.json