Hi,
after installed the standard-toolkit-demos-master, I started the build.cmd file at command prompt with administrator rights. First I forgott the paramter for the solution folder. Next try with build.cmd C:........\demo-standard-toolkit-demos-master- Butu in this case there occurs an error: error MSB4057: The target "C:......\Standard-Tool
kit-Demos-master\Standard-Toolkit-Demos-master\build.proj" does not exist in the project. Next step I checked the build.proj file which have an worng path at the include attribut.
The path after unpacking:
<Target Name="Clean"> <ItemGroup> **<Projects Include="$(RootFolder)\Source\Demos\NuGet Enabled\Krypton.*\*.csproj" />** </ItemGroup> <MSBuild Projects="@(Projects)" Properties="Configuration=$(Configuration);TFMs=all" Targets="Clean" /> </Target>
In my opinion the correct path is:
<Target Name="Clean"> <ItemGroup> **<Projects Include="$(RootFolder)\Source\Demos\Legacy\NuGet Enabled\Krypton.*\*.csproj" />** </ItemGroup> <MSBuild Projects="@(Projects)" Properties="Configuration=$(Configuration);TFMs=all" Targets="Clean" /> </Target>
which includes the \Legacy folder.
Running the file again will also cause an error.

Have anyone an idea, how I can solve this problem?
Best regards
Joe

They are "All over the place":

It's confusing to build and support all 4 sources of the Demo project code bases.!

Now that Krypton-Suite/Standard-Toolkit#1015 has been completed, update demo to show them

The WIX installer might need to be upgraded to v4, as heat.exe is now obsolete

Does not build due to this API not existing anymore in the alpha branch of the standard toolkit ??

Hello Wagnerp,

I can't build the demo because of missing component.
I try to install nuget packagewithout success. it looks for ComponentFactory.Krypton

The examples need to use Canary packages instead of Canary.Lite, since the latter are now deprecated.

Describe the bug
Loading the Krypton Docking Examples 2019 - Dev.sln doesn't load the Standard-Toolkit projects because they have migrated to project names that have a 2022 suffix/support. I'm assuming that the 2022 projects just haven't been committed to the Demo project yet.

If you correct the reference names in the 2019 Demo SLN it complains about .NET 6 support. I'd almost argue to leave both 2019 and 2022 projects to give folks a non NET 6 solution.

To Reproduce
Clone the master branch.
Open the Krypton Docking Examples 2019 - Dev.sln
None of the Standard-Toolkit projects open because it's looking for 2019 suffixed projects.

Expected behavior
Opens all projects and everyone is happy because they don't have a million references to fix.

Due to this:
Krypton-Suite/Standard-Toolkit#1206

To be done in September

Also :

• update the version
• Add the new CommonDialogs
• Add TableLayout
• Remove the Close button (That's what the X in top is for !!)
• Check that the Release link actually works
• Create 2109 msi release package(s)

The build breaks in "#81" should have been detected when the Tooltips where changed over.

As per discussion in Krypton-Suite/Standard-Toolkit#894

Allow users to install/upgrade via the WinGet CLI.

• Also add to correct output path
• And add to installer(s)
• Add Help

Even tho' the "Input-box" has my name against it, it is not my naming scheme so please delete that as well if you think it is no longer relevant.

When Krypton-Suite/Standard-Toolkit#1009 is done, then:

• Add demo
• Add to Demo launcher
• Add to installer
• Add Help

Krypton-Suite/Standard-Toolkit#850 (comment)

Using todays alpha:

Blocks
Krypton-Suite/Standard-Toolkit#703

Hi,
newbie when regarding to the net (framework) world.

I downloaded the demos and tried to build them with VS2022 without success. I was able however to build the other project, Standard-Toolkit.

Where is my mistake? Is it possible to build the solutions available inside Standard-Toolkit-Demos?

Thanks

Using today's alpha branches of both:

Nothing appears pressing the "Show" button

When Krypton-Suite/Standard-Toolkit#331 is completed:

• Add demo ribbon app
• Update read me's
• Update demo launcher
• Update installer(s)
• Add Help

This feature should have been in V80, Where is it ?

https://github.com/Krypton-Suite/Standard-Toolkit-Demos/blob/master/Source/Krypton%20Explorer/README.md

Done as part of:
#93 (comment)

During the build process, of Krypton Toolkit Examples 2019, occurring the failures as follows:

• KryptonComboBox Examples 2019 (net48): "CS1061 KryptonComboBox doesn't contain a definition for CueHint".

• KryptonTextBox Examples 2019 (net48): "CS1061 KryptonTextBox doesn't contain a definition for CueHint".

• KryptonInputBox Examples 2019 (net48): "CS1503 Argument "1" conversion string to System.Windows.forms.IWin32Window is not possible.

• KryptonInputBox Examples 2019 (net48): "CS1503 Argument "5" conversion System.Drawing.Color to string is not possible.

• KryptonInputBox Examples 2019 (net48): "CS1503 Argument "6" conversion System.Drawing.Font to string is not possible.
  

I use Visual Studio 16.11.1 and .Net 4.8.03761 with windows server 2016 standard.

How can I solve the problem?
Best regards
Joe

Breaking changes due to Krypton-Suite/Standard-Toolkit#1224

Built against alpha branches:
Project: Krypton Theme Playground 2022:

Breaking changes made to MessageBox usage:

That is going to annoy a lot of developers

Describe the bug
Safe config to file and array seems not working correctly for workspace

To Reproduce
Steps to reproduce the behavior:

1. Open and run Project Docking Persistence
2. Click Save Array
3. Close Document 5, Properties 1, Input 2
4. Click Load Array . Properties1(Control) and Input 2 (Control) can be loaded successfully but Document 5 (Workspace) is not loaded
5. Click Save To File
6. Close Document 6, Properties 1, Input 2
7. Click Load From File - > Properties 1 and Input 2 can be loaded successfully but Document 6 is not loaded

From config.xml there is tag KW KP 'Document'

<DM N="DockingManager" C="3"> <DW N="Workspace" O="0" S="1006, 430"> <KW V="1" A="Document 6"> <CGD /> <WS UN="5462F66039D342065462F66039D34206" S="T,0,50:T,0,50" D="Horizontal"> <WC UN="40fa8862f7b64306b4fa450bbfab2f0b" S="T,0,50:T,0,50" NM="BarTabGroup" AR="True" MINS="150, 110" SP="Document 6"> <KP UN="Document 6" S="False"> <CPD> <CustomPageData SavedMilliseconds="795" /> </CPD> </KP> <KP UN="Document 7" S="False"> <CPD> <CustomPageData SavedMilliseconds="795" /> </CPD> </KP> </WC> </WS> </KW> </DW>

Expected behavior
Is the load and save behavior normal like this ? only able to save and restore Control ? o

Screenshots
![error krypton1](https://user-images.githubusercontent.com/2161156/213841143

-f60e0a5e-6894-4361-9b86-3215b9860c0c.png)

Desktop (please complete the following information):

• OS: [e.g. iOS] Windows 10 64 bit
• VS 2022

Is your feature request related to a problem? Please describe.
Can the installer allow custom install locations

I'll fix as part of Krypton-Suite/Standard-Toolkit#728

Linked to #12

Describe the bug
When dropping a Krypton.Toolkit.KryptonThemeComboBox on a form (for example, DockingCustomized example) and changing the Theme, then the Theme is not applied to the Header and several other elements and wrongly applied to other elements. I am wondering if this is a problem with Theming in the toolkit or just with all of the examples here.

To Reproduce
See above

Expected behavior
Themes applied well.

Screenshots
Wrong colors, wrong font, not painted header, etc.

Desktop (please complete the following information):

• OS: Windows10 (last)
• Krypton Version 80 (last)

Use same versioning scheme as library, rather than being hard coded.

Describe the bug
Using todays Alpha branches:

etc.

@Wagnerp Note: These changes should also be documented in the "Breaking changes section"