-
Looking at the project I see it is a netcoreapp2.0
Since AuthorizeNet is a library it should be a netstandard1.3 or netstandard2.0 and be the same code for .Net framework and .Net Core.
What is…
-
Hello, I am working on a SDK where we have multiple build targets. I have been running into an issue where each of the targets seems to be building assembly attributes when I have explicitly turned t…
-
At the moment, if I set up the project then run a build it will say "1 succeeded".
If I run the build again without changing any files, I'd like the build to be skipped (i.e. "1 up-to-date" instead…
-
I am creating a .NET Standard 2.0 library that's using `Utf8StringWriter`. That library is supposed to be consumed by other projects with possibly newer .NET versions. The problem here is that for .NE…
-
### Description
This may be similar to previous reports but I think they were either slightly different or lacking a repro.
Here's an excerpt from nuget.org dotNetRDF package:
```
Dependenci…
-
Adding the package to a dotnet core 1.1 project fails:
```$ dotnet add package Softengi.UbClient --version 1.0.0.4```
```
error: Package Softengi.UbClient 1.0.0.4 is not compatible with netstanda…
-
Hi! this project is excellent extend linq to dapper, but it has stop maintenance for 2 years. would you like to maintenance the project continue, and migate this project to netcore or netstandard?
-
### Describe the feature
The constants defined in the project have grown over the years and are a bit messy. There is still BCL constants defined and some of the constants look like they are the stan…
-
If we want to migrate to dotnet core, to be able to support, for example, other plateform like requested in #758, we should do at least:
- [x] replace the mock framework RhinoMocks by one compatibl…
-
As pointed out in https://github.com/dotnet/runtime/pull/103085#issuecomment-2150981294, lock shouldn't use new Lock type in the Monitor, as it might misbehave.
We can't use fslib special syntax for …