There is no jquery library. The assessment is wrong.
Appending ?id=1 or any argument to the URL generates a new request. The same is true when there is a new URL. Wisej.NET cannot change the way the browser requests pages. The allowedRoutes property simply allows you to refer to the same application with a different URL instead of getting a 404. The new request comes in from the on the same session, which is the expected behavior. In your app you can handle ApplicationRefresh. It all works as expected.
If you’d like us to look into your configuration attach a small runnable test case.
All the key event work perfectly fine for us. If you have a test case that shows your issues we can probably help. The wiring need is part of the documented lazy event system. When running in a browser you don’t want all key and pointer events to fire all the times unless the control requested them.
Hi Alaa,
Thank you for your verification and prompt response.
Since my development is new and long term I have no problem. I use .NET 7 and the 3.2.0 beta always updated, so that at the end of the development I will have an already updated environment.
If you need the sample, I can send it to you, but I should also send you the script to create the SQL Server table.
If it is useful to you, I will prepare it, let me know.
Best regards,
Antonio
Hi Antonio,
Actually, a fix for this issue will be included in Wisej.NET 3.2!
Best,
Alaa
Hi Antonio,
Would it be possible to wrap a small sample?
Thanks,
Alaa
This problem is not existing any more. I created anothe new project, tested again and its working fine, thx.
Close that request.
This problem is not existing any more. I created anothe new project, tested again and its working fine, thx.
Please find attached the sample project.
Please find attached the sample project.
Hi Sam,
Find attached the requested sample.
Hi Kevin
Any evolution about this ?
Regards,
Attach a small runnable sample that shows your issue.
Attach a small runnable sample that shows your issue.
Attach a small runnable sample that shows your issue.
Attach a small runnable sample that shows your issue.
sorry about that – hopefully this time the attachment will stick.
also, you can url the issue at https://wisej.azurewebsites.net/?instanceId=2&conclusionId=3
Hi Alaa,
Yup that works
Perfect
Devin
Hi Alaa,
Awesome, I hadn’t seen that at all.
Application.Browser.PixelRatio is what I needed.
Thank you very much!
Best regards,
Antonio
Hi Antonio,
Did you by any chance take a look at the Application.Browser property?
If not, you can always take a look at our Documentation!
From what it looks like, it has all the things you might need without having to fiddle with JavaScript!
HTH,
Alaa
