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

[Bug]: Visual Studio do not open Form after Nuget-Package-Update #1245

Closed
DarthVader85PA opened this issue Dec 23, 2023 · 17 comments
Closed
Labels
bug Something isn't working duplicate This issue or pull request already exists fixed This issue has been fixed.
Milestone

Comments

@DarthVader85PA
Copy link

Describe the bug
Visual Studio crashes when open a KryptonForm after Nuget-Package-Update (Version 80...)

To Reproduce

  1. Update Nuget-Packages for project to new version of Krypton.
  2. Open form in Visual Studio Designer
  3. Exception while opening the form will show
  4. After click on OK, Visual Studio crashed and restarted

Expected behavior
Open KryptonForm in Visual Studio Designer

Screenshots
grafik

Desktop (please complete the following information):

  • OS: Windows 10 Pro
  • Framework: 4.8.1
  • Toolkit Version: 80.23.11.321
@DarthVader85PA DarthVader85PA added the bug Something isn't working label Dec 23, 2023
@DarthVader85PA
Copy link
Author

The error above will occurred in KryptonNavigator when I add the control in a split container (KryptonSplitContainer) and change the mode into "Outlook Full"... Perhaps it's helps!?

grafik

@DarthVader85PA
Copy link
Author

Same Issue to #1243
Sorry, can be handle in that thread.

@PWagner1
Copy link
Contributor

Hi @DarthVader85PA

I think this has been fixed in v90, please retry using the either the latest nightly or canary build.

@PWagner1 PWagner1 added the awaiting feedback A fix for this issue has been implemented, waiting for feedback on the fix. label Dec 24, 2023
@PWagner1 PWagner1 added this to the Version 90 milestone Dec 24, 2023
@PWagner1 PWagner1 added the duplicate This issue or pull request already exists label Dec 24, 2023
@DarthVader85PA
Copy link
Author

Hi @Wagnerp

I have installed Canaray, latest NuGet build. The bug in the designer still exists. Of course: only when I change the Mode-Property to Outlook - Full. My workaround: I set the property Mode to Bar - RibbonTabs and change it into Outlook - Full on runtime in Sub New.

Error in Designer:
grafik

Workaround in Designer:
grafik

Change Mode in runtime:
grafik

App in Runtime-Mode:
grafik

@PWagner1
Copy link
Contributor

Hi @DarthVader85PA

I'm unable to replicate using the latest alpha build. Can you attach a demo project so I can take a look?

@DarthVader85PA
Copy link
Author

Hi @Wagnerp and a happy new year to you,

here my Demo, created with:

  • VisualStudio 2019 Professional 16.11.32
  • .NET-Framework 4.8.09037

Test-Krypton.zip

@PWagner1
Copy link
Contributor

PWagner1 commented Jan 2, 2024

Hi @DarthVader85PA

Thanks for sending over a sample, and happy new year to you too. Unfortunately, I still can't replicate the issue, is it possible to attach a screen recording?

@DarthVader85PA
Copy link
Author

Here my Error-Video.
I hope it helps?

Error_KryptonNavigator_OutlookFullMode.mp4

@PWagner1
Copy link
Contributor

PWagner1 commented Jan 2, 2024

Hi @DarthVader85PA

Thanks for the reply, I've repeated the same steps on my latest 'dog fooding' (90.24.1.2) build in VS 2022, and it seems to be ok. Not sure if there might be a config issue, but the next nightly build is scheduled to drop next Monday 8/1. Would you mind retesting then?

1245

@DarthVader85PA
Copy link
Author

Hi @Wagnerp

I don't know but I tested it with VS 2017 Pro, VS 2019 Pro, VS 2022 Community. Same issue in each VS-Edition.
After I clicked OK, VisualStudio will crashed and restart. I removed canary-Nuget-Package and installed nigthly-Nuget-Package again.

For your info: I created all my WinForms-Projects with .NET-Framework (Ver. 4.8), NOT .NET-Core:

New Project => Language: VB/C#, Plattform: Windows, Project-Type: Desktop => Select Windows Forms-App (.NET-Framework) => Next => .NET-Framework-Version: 4.8

I will test it again next week.

@DarthVader85PA
Copy link
Author

Hi @DarthVader85PA

Thanks for the reply, I've repeated the same steps on my latest 'dog fooding' (90.24.1.2) build in VS 2022, and it seems to be ok. Not sure if there might be a config issue, but the next nightly build is scheduled to drop next Monday 8/1. Would you mind retesting then?

1245 1245

Do you use Nuget-Package?

@PWagner1
Copy link
Contributor

PWagner1 commented Jan 2, 2024

Do you use Nuget-Package?

No, I directly linked it, but testing it with NuGet now

@DarthVader85PA
Copy link
Author

Do you use Nuget-Package?

No, I directly linked it, but testing it with NuGet now

Thanks a lot.
Another question: What happens in this Sub:

protected override void OnVisibleChanged(EventArgs e)

In this sub occured this error: a null check fails: Object reference was not set to an object instance

@PWagner1
Copy link
Contributor

PWagner1 commented Jan 2, 2024

@DarthVader85PA

Something weird happens in VS 2022, it doesn't crash?

1245-1

@PWagner1
Copy link
Contributor

PWagner1 commented Jan 2, 2024

Do you use Nuget-Package?

No, I directly linked it, but testing it with NuGet now

Thanks a lot. Another question: What happens in this Sub:

protected override void OnVisibleChanged(EventArgs e)

In this sub occured this error: a null check fails: Object reference was not set to an object instance

That has appeared to have been resolved since

@PWagner1
Copy link
Contributor

PWagner1 commented Jan 8, 2024

Hi @DarthVader85PA

Please re-test using todays nightly, build .8

@DarthVader85PA
Copy link
Author

Hi @Wagnerp

I have updated to latest nightly build (NuGet). Good news: It works. :)
So now we can close this post and #1243 too I think. Thanks a lot!

@PWagner1 PWagner1 added fixed This issue has been fixed. and removed awaiting feedback A fix for this issue has been implemented, waiting for feedback on the fix. labels Jan 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working duplicate This issue or pull request already exists fixed This issue has been fixed.
Projects
None yet
Development

No branches or pull requests

2 participants