All Answers

Hi Ulisses,

the VB.NET Wisej.NET web application template was missing the Wisej.NET 4 tag. As a workaround you can find and use it if you set the project type filter to “All project types”.

It will be fixed in Wisej.NET 4.0.2

Best regards
Frank

I can reproduce with the latest 4.0.1 VSIX, we’ll look into this

-Julie

Hi Ulisses,

what color were you trying to set? Is it a .NET framework or .NET core project?
Please also make sure to update Wisej-4 nuget to 4.0.1 as it contains the designer part
and a similar error was fixed in that package.

Best regards
Frank

Not really a problem, use the .NET templates and then choose only .NET Framework 4.8 or 4.8.1 and none for .NET 8 or 9

Hi Gabriele,

this issue is fixed in Wisej.NET 3.5.19 that was just released. Thanks for reporting it.

Best regards
Frank

Please contact us at support AT wisej.com and include your license key. We will look into this further.

Thanks,

Julie

Since you already know how to do this in MAUI, the easiest way would just be to use the MAUI code.

You can invoke MAUI code from Wisej: https://docs.wisej.com/hybrid/development/invoke-.net-maui-code

Did you follow the instructions here, especially adding net9.0-windows ?

https://docs.wisej.com/docs/whats-new-in-4.0/.net-core-designer

Best regards
Frank

Yes, I did and it doesn’t work, might as well stick with version 3.5 and 4.8.1

Hi Francesco,

did you install the Wisej-4 VSIX from https://wisej.com/builds ?

Best regards
Frank

Unfortunately, There is no undoing of a sort via the datagridview itself.
You can reset the sort glyph on the column header.
If it’s a databound grid, you could reset the sort on the data source.
SortMode only controls how each column CAN control the sorting, it doesn’t sort the columns. So that’s why your code snippet does not work.

Can you please send the production link to support AT wisej.com?
Thanks,
Julie

Hi Julie,

I’ve attached the sample source code as requested. As you suggested, I removed the .vs bin and obj folders to reduce the file size. Please check it out and let me know if you can identify the text sizing issue in the FlowLayoutPanel.

Thank you.

Hi Julie,

Thank you for the quick response and for confirming the issue with Labels.

I see you tested with controls placed directly on the form, but the main issue I reported occurs specifically when controls are inside a FlowLayoutPanel. I’ve created a test project and captured a screenshot that clearly demonstrates this issue.

As you can see in the attached screenshot:

Top section (FlowLayoutPanel):

• “한국어 버튼” – text is broken into 2 lines when it should be on 1 line
• “En Button” – while not wrapped, appears to have different padding/sizing compared to the same button outside FlowLayoutPanel
• “안녕하세요” – text is split into 2 lines unnecessarily
• “label1” – English text displays correctly
• “한국어 버튼입니다” – the Label is wrapped into 2 lines when it should display on a single line

Bottom section (directly on form):

• Button “En Button” – displays correctly with normal padding
• Button “한국어 버튼입니다” – displays on a single line as expected
• Button “안녕하세요” – shows correctly on one line
• Labels with borders clearly show wrong AutoSize behavior

Key Findings:

1. The FlowLayoutPanel has severe font metrics calculation issues for Korean text and perhaps English too, particularly with padding/sizing
2. Even English controls show inconsistent sizing/padding behavior within FlowLayoutPanel
3. Korean text that displays perfectly on the form becomes unnecessarily wrapped inside FlowLayoutPanel

Impact:

• In Wisej 3: All text (Korean and English) maintained consistent sizing and displayed correctly
• In Wisej 4: FlowLayoutPanel’s layout calculations are fundamentally broken
• This breaks our entire UI design pattern for dynamic forms

The screenshot clearly shows that System.Drawing.Managed’s text measurement is critically flawed, especially within FlowLayoutPanel’s layout engine.

I’ll try again to upload the complete sample project along with this screenshot. This prevents us from migrating to Wisej 4 for our Korean market applications.

Best regards,

Bill Kim

Ciao Gabriele,

thanks for reporting this. I could reproduce it and we’re currently investigating.
We’ll update you.

Best regards
Frank

Thanks for reporting this. I tested and I was able to reproduce with a label but not with a button. We’ll look into fixing this.
Can you try to post your sample please?
To solve the “forbidden” error message, try reloading the page, or closing and reopening the browser. Also make sure that you delete the .vs bin and obj folders from your sample so that the filesize is smaller.

Julie

Hi Bill,

thanks for reporting this. It’s already been reported, fixed internally and currently in QA.
Happening for .NET 9.0 only.
Wisej.NET 4.0.1 release is scheduled for tomorrow.

Best regards
Frank

1. I have created the attached project. I had my designer in the “Bootstrap-4” theme
When running the application, it looks as expected. Changing the theme via the button to “Vista-2” also works without any problems.
2) I change the theme in the Designer to “Vista-2” and save. Various properties in Window1.Designer.cs are now changed in the background.
When I run the program, everything still looks as expected. Switching via the button also works.
3. I change the property “Font” of Window1 via the Designer to “Theme Fonts -> default”. This corresponds exactly to the value that was previously displayed as the default. (@default; 8pt; Regular)
This adds the following line to Window1.Designer.cs
this.Font = new System.Drawing.Font(“@default”, 8F, System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Point);

When I run the application now, my fields are suddenly completely shifted (regardless of the theme).
In the Designer, everything looks exactly the same as before.
In debugging, you can see that the size of the fields is changed at exactly the point where the “Font” property is set.

We have not currently changed the font in our productive application, but according to the GIT repository, this line has already existed for a long time. However, the behavior is the same as in my example. It has not occurred before and has only been occurring for a few days.