none
Significance of Windows Compatibility Pack RRS feed

  • Question

  • Hi All,

    Could anyone please explain why we have two separate libraries to support .Net APIs, in the form of ".Net Core" and "Windows Compatibility Pack" ?

    Neither ".Net Core" nor "Windows Compatibility Pack" provide full cross platform support. So what is the significance of Microsoft introducing "Windows Compatibility Pack" ?

    Thanks,
    Sezhiyan

    Wednesday, December 4, 2019 10:04 AM

All replies

  • Hi Sezhiyan Thiagarajan, 

    Thank you for posting here.

    Windows Compatibility Pack provides access to APIs that were previously available only for .NET Framework, and it can help you port code to .NET Core.

    The reason Windows Compatibility Pack is a separate package is because

    (1) many of the APIs are provided for compatibility reasons only. New code shouldn’t depend on them.

    (2) many of the APIs are Windows-only. We don’t want to lead you down a path that makes a cross-platform evolution of your app harder.

    Refer to the following reference.

    Easing into .NET Core with the Windows Compatibility Pack

    .NET Core is an open-source, cross-platform, general-purpose development platform which is completely different from Windows Compatibility Pack.

    Here’s some references about the development of .NET Core.

    1. Introducing .NET 5
    2. .NET Core is the Future of .NET

    Hope them can help you.

    Note: This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites; Therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet.

    Best Regards,

    Xingyu Zhao


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.



    Thursday, December 5, 2019 6:47 AM
    Moderator
  • .NET Core is Microsoft's effort to allow you write cross platform executables. In v2.x or before you can only write web or console applications with it, and it can only produce binaries with .DLL extension. (You need to use "dotnet" command to run them.

    Windows Compatibility Pack is a stub package that adds reference of portable version of "Other libraries" that is not included in standard .NET Core Runtime, say System.DirectoryServices related things.

    ======

    For .NET Core v3.X, it's more complete now. Desktop application support is added (although the Form Designer is still under development and only restricted set of control is supported), VB language support is added, and can finally produce .EXE binaries directly. However it's still not perfect yet, say some features such as "WCF Client" and "Embedded resources" support is missing. The .NET team is working toward making it fully compatible with full .NET framework version.

    Thursday, December 5, 2019 7:09 AM
    Answerer
  • Hi Sezhiyan Thiagarajan,

    Did you solve your problem? If your question has been answered then please click the "Mark as Answer" Link at the bottom of the correct post(s), so that it will help other members to find the solution quickly if they face a similar issue.

    Best Regards,

    Xingyu Zhao 

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Tuesday, December 24, 2019 7:59 AM
    Moderator