-
... otherwise if I target netstandard2.0 then following warning is shown:
> warning NU1701: Package 'Xam.Plugin.Version 1.0.0' was restored using '.NETFramework,Version=v4.6.1' instead of the proje…
-
**Describe the bug**
It would make sense to include this package in a class library so that it can be referenced from other parts of the application. However when trying to install in a `netstandard2…
-
I have an application with a plugin interface that lets plugins map custom types. However, these plugins must target netstandard2.0 and cannot target something like .Net 8. I don't see any reason why …
-
Having this `.csproj` in my .NET library will try to update the dependencies that target `netstandard2.0`, which I don't want to do because then the library would lose back-compat with older versions …
-
#### Issue details
_Please describe the problem, or desired feature_
after upgrading IDE, many dll can no longer be found on compilation
#### Version
_What version was the issue encountered wi…
-
### Reproduction Steps
Make a project that targets `netstandard2.1` and `net8.0`
```xml
netstandard2.1;net8.0
```
and add a `record class` to it with some members, or alternatively a class …
-
`OSLC4Net.Core.JsonProvider` currently relies on `System.Json` as its main API (despite including the NuGet dependency on `Newtonsoft.Json`, which doesn't seem to have been used). `System.Json` was re…
-
net461 isn't compatible with netstandard2.0. In the netfx build configurations, some projects target net461 and reference Microsoft.ML.Core, which only targets netstandard2.0. There are a few options:…
-
Package UISleuth 1.1.1 is not compatible with netstandard2.0 (.NETStandard,Version=v2.0). Package UISleuth 1.1.1 supports:
- monoandroid10 (MonoAndroid,Version=v1.0)
-
I had occasion to look at the packages we produce, like `CustomCheck2`, and the contents have some problems:
```
S:\MSBUILD\ARTIFACTS\BIN\MICROSOFT.BUILD.BUILDCHECK.UNITTESTS\CUSTOMCHECKS\CUSTOMCHECK…