Call WinFormsWebView2 as if it were a class library project (dll) and not an executable (exe).

[gguaita]

1. I added a public clsStartUp class to WinFormsWebView2.csproj.

namespace WinFormsWebView2
{
    public class clsStartUp
    {
        public clsStartUp() 
        {
            new Form1();
        }
    }
}

2. From another executable windows forms project, I reference and call the public clsStartUp class of WinFormsWebView2.

 private void button1_Click(object sender, EventArgs e)
 {
     new WinFormsWebView2.clsStartUp();
 }

3. I expected the opening of Form1() and the consequent execution of Login() at... the code runs but nothing happens.

Always assuming it is possible, how can I write this code?
Thank you for your attention.

[StuFrankish]

Hi @gguaita 👋

In that sample, the WinFormsWebView2.WinFormsWebView class does all the work to create the modal form and display a WebView2 component that shows the login UI you interact with, but it is referenced by Form1, it doesn't call Form1.

In Form1.cs you create and set up an OIDC client that the WinFormsWebView class gets passed to as part of the client options.

// Form1.cs

OidcClient _oidcClient;

var options = new OidcClientOptions
{
	Authority = "https://demo.duendesoftware.com",
	ClientId = "interactive.public",
	Scope = "openid email api offline_access",
	RedirectUri = "http://localhost/winforms.client",
	Browser = new WinFormsWebView()
};

_oidcClient = new OidcClient(options);

The Login() method is also defined in Form1 and calls the OIDC client to login;

// Form1.cs

private async void Login()
{
	LoginResult loginResult;
	
	try
	{
		loginResult = await _oidcClient.LoginAsync();
	}
	catch (Exception exception)
	{
		Output.Text = $"Unexpected Error: {exception.Message}";
		return;
	}
	...
}

When you call await _oidcClient.LoginAsync();, the OIDC client knows that there's a browser object there to handle the login, so it creates a new instance, displays it and waits for the login to be completed or to be cancelled, at which point it then passes the result back into the loginResult.

How you then handle the login result is up to you (although the sample does include some handling already).
Where you compile the WinFormsWebView class is also up to you, we included it within the sample project, but it could be referenced from else where.

Hope that helps! 😊

[gguaita]

Ok. I solved this problem; the problem was that the calling process did not load the Microsoft.Extensions.* libraries perhaps due to an incorrect .config setting.
Thank you.

ps: have you written code for single signon, from a desktop application c# Framework .NET 4.8, with SAML2?