Hello Jay,

This configuration is meant to do a single thing:
When you make an initial request to get your Form:
http://localhost/cmms/MainForm.ashx
The Visual WebGui framework changes the URL to suite the specific context that is now in use for serving that application. This is done by adding the vwginstance URL parameter and providing it with a guid, for getting a unique context that was not previously used on that session.
If you use the: "http://localhost/cmms/MainForm.ashx" URL again on that same browser window and even in the same tab, a new context will be created for you, to serve this new application, and a different guid will be shown in the value of the vwginstance URL parameter.

This has nothing to do with Visual WebGui authentication and the application's set LogonForm.

Regards,

Ori Cohen
Support Manager, the Visual WebGui team

Hello Jay,

You probably understand the Visual WebGui login mechanism very well by now.
Basically if you want to login in the session level (be logged in in all open contexts of that session), you can set the LogonForm to be a MainForm (add it to the Applications list in the Registration tab of the project properties-page).
Then you will be able to use Link.Open to open the LogonForm directly in a different tab.
The LogonForm will open in a different context, but that is not a problem, because if you authenticate the user and set: Session.IsLoggedOn = true;
That will also be relevant to the original application that initiated the Link.Open of the LogonForm.

If you want you could also add a JavaScript call via server-client invocation from the LogonForm so it will call the client side of the main application via a JS "opener" DOM object, like so:
window.opener.location.reload(true); window.close();

This will cause the opener tab to refresh and then the current tab to close.

Regards,

Ori Cohen
Support Manager, the Visual WebGui team