Unable to install to PCL targeting .NETStandard1.4
See original GitHub issueI recently updated my PCL libraries to the .NETStandard1.4 target. Unfortunately I am no longer able to install the NuGet package now due to incompatibilities:
PropertyChanged.Fody 1.51.3 is not compatible with .NETStandard,Version=v1.4.
Some packages are not compatible with .NETStandard,Version=v1.4.
Is it possible to update the nuspec
to support the netstandard targets as well?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Unable to install System.Runtime.InteropServices. ...
Package installs since it has an assembly that targets netstandard1.1 which is compatible with PCL profile 111. Actual result. Could not install ......
Read more >Impossible to install SQLite-Net-pcl in Xamarin
I would remove sqlite-net-pcl 1.3.1 and the other packages it installed for .NetStandard then use v1.2.1 as it still has the fix for...
Read more >Converting PCL (Portable Class Libraries) to .NET ...
My first instinct when I started this process was to just simply upgrade the PCL to use the .NetStandard by changing the target...
Read more >VS crashes when targeting .NETStandard2.0
I have a class library (PCL) that I converted to a .NETStandard1.6 library using VS2017 (15.2). When I try and have this class...
Read more >Targeting .NET Standard in Xamarin Forms and Shared ...
1. Create a PCL Cross Platform Forms app. · 2. Remove the Xamarin. · 3. In NuGet Package Manager settings, select “Allow format...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Any chance of just updated the nuspec to also indicate which netstandard profiles it supports as well?
fixed in 2.0.0-beta001