All Answers

Hi Ali,

this can be achieved by implementing the INotifyPropertyChanged interface.
Find a sample here

https://github.com/iceteagroup/wisej-examples/tree/3.5/DataBinding

Best regards
Frank

fresh wisej web application was ok after create but after update wisej3 from 3.1 to 3.5 the scrollablecontrol problem came

csproj file has already this:

<ItemGroup Condition=”‘$(TargetFramework.TrimEnd(`0123456789`))’==’net'”>
<Reference Include=”Microsoft.CSharp” />
<Reference Include=”System.Windows.Forms”><Aliases>swf</Aliases></Reference>
<Reference Include=”System.Data.DataSetExtensions” />
<Compile Remove=”Startup.cs” />
<Content Include=”Startup.cs” />
</ItemGroup>

what can i do?

Hi Arturo,

this is now fixed in Wisej.NET 3.5.3

Best regards
Frank

Hi Uwe,

you can find a sample of how to use the dxDataGrid as part of our Premium extensions here

https://demo.wisej.net/DevExtreme/#dxDataGrid

And the source code here

https://github.com/iceteagroup/wisej-demobrowser/blob/main/Wisej.DemoBrowser.Premium/Wisej.Web.Ext.DevExtreme.Demo/Component/dxDataGrid.cs

You might as well want to check out some older integration blog article that we published:

https://wisej.com/blog/integration1/

Best regards
Frank

Hi Eddy,

did you install Wisej.NET both for VS 2019 and VS 2022?

You can find the installers here, maybe you just installed it for 2019 yet?

https://wisej.com/builds/

Best regards
Frank

• You are adding the same node to multiple parents.
• ShowRootLines doesn’t show any line (the comment is wrong). When false it doesn’t show the root open/close button. Lines are not supported.
• There are +/- icons displayed correctly (depends on the theme)
• The icons are also all correct.

Once you fix your code it all works fine. See screenshot.

Any Solution?

Hello Frank,

I still cannot see where the problem is 🙁

I started a super small project, a form with two buttons and no events attached on it.

I just cannot see them in the designer window 🙁

I enclosed some files just in case you could trace a problem.

Thanks for your help.

Best regards,

Eddy.

ps: I cannot post the whole zipped project because the zip exceeds 3,9Mb

Hello Frank,

I just had the forum response notification and I did not check the documents your are mentioning yet.

Thank you so much for your reaction !!!

I will keep you aware of  any changes

Best regards,

Eddy.

Hi Eddy,

the theme you have selected in the designer may not be the same you chose at runtime of your application.

Find more information here

https://docs.wisej.com/docs/concepts/theming

Best regards
Frank

Hi Uwe,

if you are using a library that is .NET core only you need to handle the multi targeting and reference it for .NET 8 only

Find more information here

https://docs.wisej.com/docs/releases/whats-new-in-3.0/multi-targeting

Best regards
Frank

Hi Ali,

Application.Update () can take any Wisej object as parameter and the result is always the same:
The client syncs with the server. So this is the recommended approach to update the UI after a background task.

The 2nd call is totally unrelated to this and cannot be used as a replacement for the 1st call.

Best regards
Frank

I found the problem, Luca. It occurs when creating a Web Desktop Application project. The issue appears in the Windows-type forms, not in the Pages. I am attaching the project for reference. I deleted the bin folder, the attached file may not exceed 4000 KB (this is to low, only the wisej.framework has 10 MB).

Thanks in advanced.

Cannot reproduce, see screenshot attached. Pls attach a small reproducible test case.

You probably skipped some steps. Unclear from a screenshot.

You can use as you would with any .NET code.

Look for viewport and meta tags online when developing for mobile pages. We cannot provide you with personalized assistance for issues that are not a problem in Wisej and we cannot interpret a screen shot or incomplete descriptions.

This group is for free support related to specific Wisej issues. If you have detected a problem with Wisej, please post a clear issue, with steps to reproduce and with a small runnable reproducible case. Thank your for your understanding.

Understood, we’ll discuss the internally and come back.  Thank you for the quick response.