All Answers

Hi Mohsen,

did you upgrade both the nugets and the VSIX to 3.5.16?

Best regards
Frank

Hi Ibrahim,

RightToLeft is not fully implemented on the DataGridView yet.
We have no fixed date when we continue working on it.

Best regards
Frank

I link demo project and screen shot

https://eprimeos.it/public/demo/splitterwidth.png

https://www.eprimeos.it/public/demo/testsplitter.zip

If I attach in the post, I have an error “Forbitten”

If you can reproduce in a small test case, we can look into it in case it is a bug with Wisej and not your own code. However, it’s likely that this issue is not easy to reproduce in a small test case.

Unfortunately, debugging your application is something that is out of scope of this free support forum.

Your options are to downgrade your version of Wisej as that seems to fix the bug, or to purchase a premium support package here: https://wisej.com/services-packages/

This error never popped out until I migrated from Wisej 3.1.12 on .net 6.0 to 3.5.16 and .net 8.0
In the whole codebase there is no call to Application.StartTask().

I am suing System.Threading for BackgroundService and  ThreadStart() but this was not a problem so far.

Hi Cristian,

you say it also fails on the desktop?
I have tried here and could not reproduce it at all.

Can you please tell us your Wisej.NET version and send a sample with instructions on how to reproduce?

Best regards
Frank

Hmm I am using the latest 3.5.16 with a .Net 8 project.  I do use a lot of datagridviews with autosizing and fill weights.  I am not sure if that’s the problem but and unfortunately I am unable to reproduce the problem on my machine.  It appears the issue only happens in production and only on certain machines that usually do not have a good connection to the internet.  It probably has something to do with my code, as I have had a lot of issues with async calls and the wisej application not responding unless I put Application.Update(this) after the async calls.   I was kinda hoping someone else was experiencing something similar so I could get an idea on how to pin point this problem.

Thanks,

Devin

It could be caused by the old freezing of datagridview columns in autosize. Remove all autosizing and retry.

What version of Wisej are you using? Try the latest build and see if that fixes the issue.

If you can provide a reproducible test case, we can look into this further.

Julie

Hi Frank,

the splitter container works, is the property SplitterWidth that do not work, only in designer. I have just test on Android Firefox and Chrome, I just noticed that the problem is also present in desktop browsers

Wisej version: 3.5.16

Windows

changing the property SplitterWidth work on desinger, but not on browser, desktop too

best

Hi Cristian,

I just checked our Demo Browser on an iPhone and it worked fine:

https://demo.wisej.net/#Containers/SplitContainer/Features

So we need more information:

• What Wisej.NET version are you using?
• What device / OS  are you running on?
• Please describe what’s not working and supply a test case that shows where it fails for you.

Best regards
Frank

Hi Rafaela,

please contact us at supportATwisej.com and send the license key you have tried.
Most likely you’ve been using a wrong type as has been indicated already by my colleagues.

Best regards
Frank

The scenario you’re describing is best addressed with the Wisej.NET Technology Partner program. It’s designed for ISV (independent software vendors) that sell Wisej.NET along with their own products. It allows the flexible use of licenses at different customer sites, including up- and downscaling as license requirements vary.

More information can be found here: https://docs.wisej.com/license/license-model/technology-partner

Please reach out to our sales team in case of detailed questions.

The super simple solution is to buy a server license for $690.

Also joining in on answer.

It is nice from marketing perspective to push this, but also from security perspective you are making recon work easier.

Agrego la captura del error:

Buenas tardes,

De un dia para otro, me apareció al cargar el home del sitio un mensaje similar:

Licencia de servidor no válido

Estado: WrongProductName

caducidad:-

No se si se trata de alguna licencia utilizada dentro del proyecto .NET o se trata de permisos de acceso al servidor que el firewall de un día para otro empezó a limitar.

Cualquier sugerencia sera bienvenida.

Gracias!

Hi Robert,

we might have fixed a related issue in our upcoming 3.5.16 release that is currently in QA.
Can you please try this test build and see if it fixes it on your end?

https://wisej.s3.amazonaws.com/downloads/TestBuilds/Wisej.NET-3-VS2022-3-5-16-4.vsix

Best regards
Frank