Skip to content

✨ Support for .NET 10 and 11 #343

Open

Description

@jozefizso

Feature is developed on branch https://github.com/NetOfficeFw/NetOffice/tree/dev/net6

Activity

  1. added this to the 1.9.0 milestone on Feb 6, 2022
  2. changed the title [-]Support for .NET 6[/-] [+]✨ Support for .NET 6[/+] on Feb 6, 2022
  3. pinned this issue on Feb 6, 2022
  4. jozefizso commented on Feb 6, 2022

    @jozefizso
    MemberAuthor

    Release 1.9.0 will deprecated some projects, see #342

  5. edoust commented on Mar 22, 2022

    @edoust

    Any news on when the .NET 6 compatible version will be released?

  6. mixonij commented on Mar 23, 2022

    @mixonij

    Any news on when the .NET 6 compatible version will be released?

    Also waiting this =)

  7. jozefizso commented on Mar 23, 2022

    @jozefizso
    MemberAuthor

    Any news on when the .NET 6 compatible version will be released?

    When the code will be ready.

  8. samatstariongroup commented on Aug 25, 2022

    @samatstariongroup

    @jozefizso is there anything we can do to help

  9. jozefizso commented on Aug 27, 2022

    @jozefizso
    MemberAuthor

    @samatrhea here some overview what I was working on lately:

    Next work includes:

    • Rewrite Azure Pipeline build to GitHub Actions to make builds transparent
    • Automate building and releasing NuGet packages
    • Release v1.9 with some new APIs from latest MS Office builds
    • Fix code for .NET 6 (Windows only)
  10. modified the milestones: 1.9.0, 1.10.0 on Aug 27, 2022
  11. tb-mtg commented on Jan 17, 2023

    @tb-mtg

    Any news on this?

  12. samatstariongroup commented on Mar 3, 2023

    @samatstariongroup

    @jozefizso we would love to contribute to this, but i think we need some guidance on what to do which is a bit more detailed than the tasks listed above. Would you be able to spend 15 to 30 minutes with us to get us started? We can setup a teams meeting for this.

  13. jozefizso commented on Mar 4, 2023

    @jozefizso
    MemberAuthor

    Hi @samatrhea, it would be helpful to test the code from https://github.com/NetOfficeFw/NetOffice/tree/dev/net6 if it works for your product.

    Unfortunately I can test it only on small samples and I don't have a real project running on .NET 6. One of the issues to solve would be Addins and the new hosting model in .NET 6.

    Do you have Calendly so we can arrange a time for meeting?

  14. 19 remaining items

  15. changed the title [-]✨ Support for .NET 6[/-] [+]✨ Support for .NET 8[/+] on Feb 16, 2024
  16. ashishpCACTUS commented on Feb 27, 2024

    @ashishpCACTUS

    @jozefizso - Can you provide build files that support .Net for now? The last shared ones are expired. Also just wanted to check if there is any timeline for the full release as well as you had mentioned that it may not be available for add-ins usage so any timeline for the same.

  17. jozefizso commented on Feb 27, 2024

    @jozefizso
    MemberAuthor

    Hi @ashishpCACTUS, the code is in the branch mentioned above.

    There is no timeline for releasing the .NET Core build.

  18. changed the title [-]✨ Support for .NET 8[/-] [+]✨ Support for .NET 6 and 8[/+] on Jun 9, 2024
  19. jozefizso commented on Jun 20, 2024

    @jozefizso
    MemberAuthor

    You can start testing the NetOffice libraries targeting .NET Framework 4.6.2, .NET 6 and .NET 8 in the release 2.0.0-preview20:

    https://www.nuget.org/packages/NetOfficeFw.Core/2.0.0-preview20

    This release supports Office automation scenarios and also Office COM Add-ins. For the add-ins running on .NET 6 and 8 you must adopt the new tools for registering native comhost libraries.

    A sample Word add-in for .NET 6 is at https://github.com/NetOfficeFw/NetOffice/tree/dev/dotnet/Examples/Word/WordAddinCore

  20. asahicantu commented on Jul 9, 2024

    @asahicantu

    Thank you for the support on this initiative. So fat I am trying to make it work with my legacy .NET Framework addins, but i cannot make it load a custom windowsForm UserControl into a CustomTaskPane, Whenever it is being called by the invoker (even if it gets successfully created) an error is generated by the COM Invoker, unfortunately I am not able to see the exception far from "Cannot create indicated ActiveX Control" Any idea, someone else has had a similar problem?

    image

  21. DoctorMarvin21 commented on Jul 10, 2024

    @DoctorMarvin21

    There was an discussion and people were managed to resolve all issues win .NET 5:
    dotnet/winforms#4370

    Maybe it's a good idea to contact them, at least @arknu.

  22. DoctorMarvin21 commented on Jul 10, 2024

    @DoctorMarvin21

    UPD: I updated this project to use .NET 6 and everything worked in Excel and Outlook. It's could be used as a great example. I'm still not sure what exactly I missed in my project though.

  23. jozefizso commented on May 20, 2025

    @jozefizso
    MemberAuthor

    Taskpane extension are still not possible to be done using .NET Core: dotnet/winforms#1763

  24. kev-is-coding-for-adn commented on Oct 2, 2025

    @kev-is-coding-for-adn
    Contributor

    Hi everyone,

    Any news on this project since may?
    We are updating all our applications to NET 9 and would like to have every library up to date as well.

    Have a nice day
    Kevin

  25. jozefizso commented on Oct 2, 2025

    @jozefizso
    MemberAuthor

    Hi @kev-is-coding-for-adn, this project is open source and you can build it, modify it and verify if it works in your project targeting .NET 9.

    So far it wasn't crucial to release a .NET Core specific libraries, as existing ones can be used.

    And without support for the Taskpane Extensions in the .NET Code WinForms itself a significant use case is blocked in Core libraries.

  26. changed the title [-]✨ Support for .NET 6 and 8[/-] [+]✨ Support for .NET 10 and 11[/+] on Jun 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    • Status
      Backlog

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions