All Answers

Hi Jevaso,

Wisej version 2.5.21 is released, you can install the ChartJs extension via nuget without any problems now.

Please let us know if you encountered any issues.

Best,
Alaa

Hi Page,

Wisej version 2.5.21 is released now, you should be able to install the Camera extension via nuget without any problems now.

Please let us know if you encountered any issues.

Best,
Alaa

Hi edmond,

You can use Binding way for change Label or Text property,

I provide you one sample, It use a thread for simulate async Data,

Happy coding,

Kevin (ITG)

Hi Vincent,

this issue is fixed in the latest Wisej release (2.5.21)

Best regards
Frank

Thanks Dirk for providing more details.

We have checked that issue and you can control the way that the autofill fields are displayed
by adding this to your default html (in head section)

<style>
 input:-webkit-autofill 
{ -webkit-text-fill-color: white !important; 
-webkit-box-shadow: 0 0 0px 1000px black inset !important; } 
</style>

Also make sure that your browser does not use a cached version of default.html
(hit CTRL+F5).

Best regards
Frank

Here are the pictures and testproject.

Dirk,

I have tried to reproduce this problem but it worked ok here. What browser are you using?
Can you please check it with a different browser to see if there is any difference?
Any chance to wrap up a small test case that helps us to reproduce that issue?

Thanks in advance!

Best regards
Frank

Hi Tom,

you might also want to refer to our documentation regarding how to step up to Wisej 2.5

https://docs.wisej.com/api/whats-new-in-2.5

What exactly do you mean with Wisej projects are gone?
Do you refer to the project templates? They should still be there and appear after you select a .NET version <4.8

Best regards
Frank

Yes, that did work! thank you.

The Wisej 2 projects load but with errors. I’m looking into that now. Also didn’t expect all the prior Wisej projects are gone.

Hi Andrew,
Which files are you copying from bin?
If you send a picture of the bin directory it might shed more light on the issue.
Best,
Levie

Hi Tom,

did you do download the .NET 4.8 developer pack?
It should be available here (in the 2nd column):

https://dotnet.microsoft.com/en-us/download/dotnet-framework/net48

Best regards
Frank

Hi Tung,

in order to use the full grouping functionality in a DataGridView you can call one of the following functions

Fill
Append

Best regards
Frank

Thanks for your explanation!  The Wisej.OpenAuth project shows the solution.  I just need to create the parameter string to connect properly.  Forgive my lack of knowledge on this but I assume the connection is based on the authentication and if the authentication is lost the app will redirect?  Perhaps a noob question and I see no reason for authentication to be lost under normal conditions, I’m just curious.

Once the web app is running I can filter user access using the same database user settings as in my desktop.

Thanks again!

Gerry

Hi Vincent,

Thank you for reporting this issue.

We can confirm that it’s a bug, we’ll report back when a fix is available.

Best,

Alaa

https://wisej.com/support/question/single-sign-on

By “Wisej Desktop App” you mean a Wisej app running in a standalone container using the self hosting extensions?

Wisej apps are always web apps, even when running in the self hosted standalone container: it’s identical to electron (which is also what Visual Studio code is, a web app running in chrome).

Wisej doesn’t have any specific custom authentication – it works with any authentication you choose to use. There is no navigation to URLs and pages since it’s a Single Page Application (SPA), so there is one entry point, which is by far more secure than having a URL for every state of the app.

See: https://wisej.com/support/question/single-sign-on

See https://wisej.com/support/question/single-sign-on for a sample and video.

The attribute [Authorize] doesn’t make sense in Wisej, it’s a single page app. Asp.NET navigates from url to url, SPAs don’t. Azure and other oauth systems navigate away to login and navigate back. Wisej simply works with any authentication, in Program.Main or any entry point it’s up to you to start the authentication flow using the standard navigation, etc.

Check Application.SessionId. If it’s null or empty then you have a thread started somewhere. If it contains the session id and Application.Session[“Principal”] is null then it has been removed by the app.

Application.UserIdentity and Application.UserIdentity and Application.User return the logged in user – depends on your authentication in web.config. It’s identical to System.Web.HttpContext.LogonUserIdentity and System.Web.HttpContext.User.