Skip to content

[Bug]: Error when Attempting to upgrade to Ultimate 105.26.7.201 #610

Description

@MattH-Work

Describe the bug
Still cannot upgrade FROM Toolkit & Navigator 90.25.2.55 , Extended 85.24.10.288 TO 105.26.7.201

To Reproduce
Upgrade via Nuget

Expected behavior
Toolkit & Navigator update as expected, Ultimate throws error

Screenshots

Image

Desktop (please complete the following information):

  • OS: [Windows 11]
  • Version: [e.g. 125H2]
  • Framework/.NET Version: [4.8]
  • Toolkit Version: [FROM toolkit 90.25.2.55, Extended 85.24.10.288 TO 105.26.7.201]

Additional context
Ultimate toolkit install fails on newly created DOT Net 4.7, 4.72, 4.8, 4.8.1 VB solutions ( DOT Net 10 work as expected )

Image

Activity

  1. PWagner1 commented on Jul 21, 2026

    @PWagner1
    Contributor

    Hi @MattH-Work

    Please can you try the latest canary, as the focus on this topic is going towards V110 and higher?

  2. MattH-Work commented on Jul 22, 2026

    @MattH-Work
    Author

    completely fresh solution ( VB, DotNET 4.8, single blank form )

    Image
  3. added this to the Version 110 milestone on Jul 26, 2026
  4. self-assigned this
    on Jul 26, 2026
  5. PWagner1 commented on Jul 26, 2026

    @PWagner1
    Contributor

    Hi @MattH-Work

    Please can you try the latest nightly build, >= .207?

    cc. @mjohne

  6. mjohne commented on Jul 26, 2026

    @mjohne

    The latest nightly build works for me; no errors.

  7. PWagner1 commented on Jul 26, 2026

    @PWagner1
    Contributor

    The latest nightly build works for me; no errors.

    Fixes will be for V110+ only, as it has proven very difficult to sort out.

  8. added a commit that references this issue on Jul 26, 2026
    3b21774
  9. mjohne commented on Jul 27, 2026

    @mjohne

    During my last attempt, I merely tested whether Ultimate.Nightly could be integrated without issues. However, I forgot to create a simple WinForm. I have since done so, only to discover that the program threw an exception, as reported by Visual Studio. The application did not display a GUI and terminated automatically.

    Image
  10. PWagner1 commented on Jul 27, 2026

    @PWagner1
    Contributor

    During my last attempt, I merely tested whether Ultimate.Nightly could be integrated without issues. However, I forgot to create a simple WinForm. I have since done so, only to discover that the program threw an exception, as reported by Visual Studio. The application did not display a GUI and terminated automatically.

    Image

    Hi @mjohne

    Thanks for your reply, I just tested on a fresh project but can't replicate the issue. For existing projects, I'd suggest removing existing packages/binaries, then installing the nightly version to eliminate any possible conflicts.

  11. mjohne commented on Jul 27, 2026

    @mjohne

    In the case I described above, I had indeed set up a new project.

  12. PWagner1 commented on Jul 29, 2026

    @PWagner1
    Contributor

    Hi @mjohne

    Found the bug, will be fixed in a future standard toolkit update.

  13. added a commit that references this issue on Jul 30, 2026
    7bb332b
  14. removed their assignment
    on Jul 30, 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

    Labels

    Version:110bugSomething isn't workingfixedThis issue has been fixed.

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions