You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the remaining packages, consider excluding the desktop reference and instead using the implementation assembly as the reference (as we did in 1.x). These are the packages we shipped in 2.0 that contained reference assemblies with typedefs for desktop:
System.Numerics.Vectors
System.IO.FileSystem.AccessControl
System.IO.Pipes.AccessControl
System.Reflection.TypeExtensions
System.Security.Cryptography.Cng
only on net461 as a result of the netstandard remapping. Fix here is to drop those types from the reference for the netfx build.
System.Threading.AccessControl
1 is a must-fix for 2.0. For 2 and 3 we'd need to ship the individual packages and for that I'd like a shiproom read.
The text was updated successfully, but these errors were encountered:
We did 1, we were blocked on doing 2 & 3 due to buildtools being in limbo. That's since been fixed. I think we can decide if we want to do 2 & 3 and ship them at some future date (not necessarily in 2.0.2).
We're having an issue with a Xamarin project, which as we added System.IO.Packaging 4.4.1 nuget package dependency, the reference is resolved as the ref/netstandard1.3 DLL, a reference assembly. It seems that because of that, the Xamarin app fails to start because this DLL does not get packaged, and so the app fails to start with this common xamarin error https://forums.xamarin.com/discussion/63584/android-could-not-load-assembly-xxx-during-startup-registration
See https://github.com/dotnet/corefx/issues/23505.
The use of reference assemblies in 2.0 for desktop-targeted packages and netstandard support targets has resulted in a number of tooling issues.
To help relieve these, we can dial back the number of reference assemblies we use.
1 is a must-fix for 2.0. For 2 and 3 we'd need to ship the individual packages and for that I'd like a shiproom read.
The text was updated successfully, but these errors were encountered: