[Bug]: Double click on the Form1 file in the Krypton toolkit test project results in a designer error

[Smurf-IV]

Describe the bug

To Reproduce Steps to reproduce the behavior:

• Get "Todays" alpha branch of the toolkit (2023-04-25)
• Build Debug in Visual Studio 2022 (I'm using 17.6 P2)
• Open the included Test form project and double click the Form1.cs file
  • 

Expected behaviour

• For the designer to load

Screenshots (The above is stuck in a loop if you click ignore - about 100 times I tried - and also by pressing and holding "Alt+I" !!)

When attaching a Debugger (via retry) you see this:

Attempting to run the "TestForm" app results in these (Again holding "Alt+I" results in loads of these pairs!!)

• 
• 

I suspect it is something to do with the Toolbar buttons

[PWagner1]

The 'new' buttonspecs aren't invoked. @Smurf-IV Does this happen for all themes?

[Smurf-IV]

The 'new' buttonspecs aren't invoked. @Smurf-IV Does this happen for all themes?

No idea, Just cannot use the "TestForm" project in any way ! I'm just about to go to the Toolkit examples next to see if affects them.

Update:

• I can load the Toolkit examples
• This is from the Form example:
  • 

[PWagner1]

Easy Resharper fix

[Smurf-IV]

Easy Resharper fix

It'll still throw the Debug.Assert in the designer !!

[PWagner1]

Easy Resharper fix

It'll still throw the Debug.Assert in the designer !!

Could it also be something to do with Source\Krypton Components\Krypton.Toolkit\Values\IntegratedToolBarValues.cs?

[PWagner1]

@Smurf-IV Think I got it now, school boy error, I forgot to 'add' the images to the base palettes!

[PWagner1]

Update: Got Form1 back to a working state, but it's bugged when using O2k13

[PWagner1]

Going back to Canary as the last known 'good' build

[PWagner1]

@Smurf-IV Is there a way to write assert messages out to log files, so I can properly read them, rather than having them truncated?

[Smurf-IV]

Clicking retry will got Visual Studio, and then the stack trace will be available in the CallStack window

[Smurf-IV]

https://learn.microsoft.com/en-us/dotnet/api/system.diagnostics.defaulttracelistener?view=net-7.0

[Smurf-IV]

Note: The designer appears to be working with o2k13 white now.

[PWagner1]

https://learn.microsoft.com/en-us/dotnet/api/system.diagnostics.defaulttracelistener?view=net-7.0

@Smurf-IV Might be good to enable this for Canary & Nightly configurations only. Maybe a new feature request?

[Smurf-IV]

Should not be part of the Framework, as this is an Application setting. And Some OS's are not even on the C: drive (See Chinese default drive usages)

[giduac]

Hi @Wagnerp & @Smurf-IV,

Is this still a problem since then TestForm has undergone quite a few changes....?

[PWagner1]

Hi @Wagnerp & @Smurf-IV,

Is this still a problem since then TestForm has undergone quite a few changes....?

Hi @giduac

I don't know... are you able to repeat the steps above?

[giduac]

@Wagnerp You have a try and double click form1 ....

[PWagner1]

@Wagnerp You have a try and double click form1 ....

@giduac

Seems to be working as of v85...

[giduac]

@Wagnerp And in alpha as mentioned in the call there's no form1. This one can be put to bed I guess...

[PWagner1]

@Wagnerp And in alpha as mentioned in the call there's no form1. This one can be put to bed I guess...

@giduac

I'll put it as part of v85 and close it

[giduac]

@Wagnerp Says fixed...Please close, ty.