Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ship .NET Framework compatibility pack #23974

Closed
danmoseley opened this issue Oct 26, 2017 · 7 comments
Closed

Ship .NET Framework compatibility pack #23974

danmoseley opened this issue Oct 26, 2017 · 7 comments
Assignees
Milestone

Comments

@danmoseley
Copy link
Member

A meta package to include all the libraries released from CoreFX in 2.0 that aren't already included in the Microsoft.NETCore.App package (aka the shared framework) plus a series of new ports and necessary facades. Some are Windows only currently. Aim to release at least a complete preview in November.

Spec

dotnet/designs#16

Previously shipped packages:

Package ID Link Windows Only
Microsoft.Win32.Registry NuGet Yes
Microsoft.Win32.Registry.AccessControl NuGet Yes
System.CodeDom NuGet  
System.Configuration.ConfigurationManager NuGet  
System.Data.SqlClient NuGet  
System.Drawing.Common NuGet No
System.IO.FileSystem.AccessControl NuGet Yes
System.IO.Packaging NuGet  
System.IO.Pipes.AccessControl NuGet Yes
System.IO.Ports NuGet  
System.Reflection.Context NuGet  
System.Security.AccessControl NuGet Yes
System.Security.Cryptography.Cng NuGet Yes
System.Security.Cryptography.Pkcs NuGet Yes
System.Security.Cryptography.ProtectedData NuGet Yes
System.Security.Cryptography.Xml NuGet Yes
System.Security.Permissions NuGet  
System.Security.Principal.Windows NuGet Yes
System.ServiceModel.Duplex NuGet  
System.ServiceModel.Http NuGet  
System.ServiceModel.NetTcp NuGet  
System.ServiceModel.Primitives NuGet  
System.ServiceModel.Security NuGet  
System.ServiceProcess.ServiceController NuGet  
System.Text.Encoding.CodePages NuGet No
System.Threading.AccessControl NuGet Yes

New Packages:

ID   Remaining work UWP? Unix?
  Updated Shims package Authoring    
14529 System.Runtime.Caching Test, Pkg not yet not yet
14762 System.Management (WMI) Tests, Pkg no not yet
3906 System.Diagnostics.PerformanceCounter PR no no
2089 System.DirectoryServices Pkg no no
2089 System.DirectoryServices.Protocols Pkg no not yet
2089 System.DirectoryServices.AccountManagement Pkg no no
  System.ServiceModel.Syndication Tests, Pkg ? yes
6913 System.Diagnostics.EventLog DONE no no
11545 System.Drawing DONE no yes
11857 System.ComponentModel.Composition (MEF1) Test, Pkg ? yes
13035 System.Data.Odbc DONE no yes
19771 System.Data.DatasetExtensions DONE yes yes
6024 System.ServiceProcess.ServiceController & ServiceBase DONE no no
5766 System.Xaml No plans -- --
8723 System.ServiceModel (WCF) Message Security No plans -- --
6920 System.Addin No plans -- --
2394 System.Activities (WF) No plans -- --
@danmoseley
Copy link
Member Author

This is now shipped in preview status: https://blogs.msdn.microsoft.com/dotnet/2017/11/16/announcing-the-windows-compatibility-pack-for-net-core/

Still remains to finish and include MEF1, and also to ship marked stable.

@dasMulli
Copy link
Contributor

dasMulli commented Nov 21, 2017

It would be great to know which libraries are supposed to work on which version/edition of windows.

For example, even though System.DirectoryServices is marked "windows only", it does not work on nano server (at least the docker image for nano server - fails with a DllNotFoundException for activeds.dll).
This raises questions like "does drawing work on nano server?" which I find myself unable to answer from the existing material (understandably though, since it has just been previewed).

@danmoseley
Copy link
Member Author

@terrajobst @pjanotti have we considered updating https://github.com/dotnet/platform-compat to allow it to be fine grained down to the SKU level?

@dasMulli I don't believe Nano has GDI+ so Drawing will not work. It does not surprise me that DS does not work. At least when stuff doesn't work, it will usually fail right away, typically with DllNotFound or PlatformNotSupported or NotSupported etc.

@pjanotti
Copy link
Contributor

For the Platform-Compat to go to that level it will need some extra information in project files, which it already uses for some stuff, so, in principle it seems doable. I opened an issue to consider this possibility (dotnet/platform-compat#80).

@tarekgh
Copy link
Member

tarekgh commented Mar 7, 2018

@danmosemsft is this not done yet?

@danmoseley
Copy link
Member Author

Not until we ship 2.1, as that is the point at which it will get marked stable in nuget.

@danmoseley
Copy link
Member Author

Probably no need to keep this open. We are on track to mark this stable aligned with 2.1 release. No more work to do

@msftgits msftgits transferred this issue from dotnet/corefx Jan 31, 2020
@msftgits msftgits added this to the 2.1.0 milestone Jan 31, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants