-
There's no reason why this library couldn't support much earlier versions .NET. The necessary reflection bits should be available on most common .NET platform targets.
* .NET 2.0 might require a di…
stakx updated
6 years ago
-
**Version Used**:
VS 2017.3 RTM
**Steps to Reproduce**:
1. Open VS 2017.3 and C# Interactive
2. Reference a local .NET Standard 2.0 DLL using '#r'. e.g. C:\Test\Demo.DLL
3. Try to instantia…
-
## Read and complete the full issue template
**Do you want to request a *feature* or report a *bug*?**
- Bug
**Version of ClosedXML**
v0.90.0-beta2
**What is the current behavior?**
~~Syst…
-
Receive an intermittent warning that says: Analyzer assembly \packages\Puma.Security.Rules.1.0.6\analyzers\dotnet\cs\Microsoft.Build.dll' depends on 'Microsoft.Build.Engine, Version=14.0.0.0, Culture=…
-
### Description
If a project use multiple paket group for dependencies, the project build incorrectly in VS because load the wrong nuget dependencies.
it will build correctly from command line.
…
-
At the moment DI support is limited to creation of root validators. The container is abstracted behind IValidatorFactory
We should allow resolution of child validators and other components during
…
-
### Description
I do have both netcoreapp2.0 and netstandard2.0 projects in the solution and this framework restriction in paket.dependencies file
```
framework: netcoreapp20, netstandard20
``…
-
1. Can anyone help with the following tasks:
- [x] We need to get `cake` build script to build the `gem package` as it isn't built at present.
- [x] We need to get `cake` build script to build the…
-
Goals:
- Chasing the .net standard cross platform dream...
- Get AspNetCore.SignalR.Client working in .Net Core runtime: Working.
- Get AspNetCore.SignalR.Client working in .net 4.6.1 winforms run…
-
Imagine you have AwesomeLib which target netstandard1.3, and use non generic TableQuerySegment.
AwesomeApp which targets .net 4.6.2 references AwesomeLib. Because of how nuget works, AwesomeApp wil…