Base solution for your next web application

Activities of "URITECHNOLOGY"


We are experiencing issues Authenticating users after Chrome updated to 84.0.4147.105 on Windows Desktop applications.

In the Windows user's AppData folder for Chrome, there is a file named "Local State" that when deleted, Chrome regenerates the file and we are able to authenticate all the way through to the App dashboard.

If this file remains, the application does not fully authenticate the user and redirect to the portal dashboard, instead will bring you back to the log in prompt.

Without requiring our portal users to delete this file, is there a method that we can use to reset the application's interaction with the "Local State" File found at the path below?

C:\Users<user account>\AppData\Local\Google\Chrome\User Data\Local State

This only affecting users that have previously logged in before the update (presumably), restarted their machine, and logged in to their windows user profile on their PC. If a different user profile exists on the same machine, but has not logged into a ASP.NET - Zero application, the user can successfully log in.

All other browsers work.

Hello, We have customized an 8.7 version of .net zero for core 3.1 and MVC and jquery and the staging site deployment does not load and times out to produce a 503 error. We have also tried downloading a fresh version of 8.7 and 8.8 and have not been able to deploy a blank version and have the site come up. We have a impending deadline coming up and do not have time to troubleshoot. Is there any way we can download a v8.2.1 as we already have 2 other solutions on this version that deploy perfectly to our environment? Thank you in advance for your help on this request.

Thanks, Norma

In staging: Site is load balanced for 2 domains:

  • Both domains resolve to the same hosted folder on each server (A and B servers) All instances share the same database.

In Production: We have it deployed to two different servers for 2 different domains.

  • is load balanced
  • is single server instance All instances share the same database.

How would this setup affect the site to produce multiple duplicate notifications?


//tried this but generated up to 4 notifications, none of them returned a file
//_appNotifier.MarketingInvoiceGenerated(input.User, file.FileToken, file.FileType, file.FileName);

//current implementation
if (file != null)
                _appNotifier.MarketingInvoiceGenerated(input.User, file.FileToken, file.FileType, file.FileName);
//tried this and it generates up to 3 notifications, some times the link works, sometimes not
//AsyncHelper.RunSync(async () => await _appNotifier.MarketingInvoiceGenerated(input.User, file.FileToken, file.FileType, file.FileName));

IN the appnotifier.cs page we have added: AppNotifier.cs

public async Task MarketingInvoiceGenerated(UserIdentifier argsUser, string fileToken, string fileType, string fileName)
            var notificationData = new LocalizableMessageNotificationData(
                new LocalizableString(

            notificationData["fileToken"] = fileToken;
            notificationData["fileType"] = fileType;
            notificationData["fileName"] = fileName;

            await _notificationPublisher.PublishAsync(AppNotificationNames.DownloadMarketingInvoices, notificationData, userIds: new[] { argsUser });


We are noticing that the password reset email will fail intermitently. We get a 500 internal sever error. We are leveraging the same service to send a confirmation email when the user submits a form and noticed that when the email confirmation from the form submit fails, so does the password reset email. Is there something that keeps that service 'alive' or can you point me in the right direction of how to troubleshoot this? We cannot recreate it consistently through testing, it seems to be sporadic.


We are putting a lot of weight behind your solution to run much of our technology applications and we have question about managing updates.

I see that we can choose the version of zero when we purchase a new license.

My question is, if we have a portal in production that is a few years old, and a new version of zero becomes available. Is there a way to include the new versions of the packages/bundles, metronic theme, or even .NET core version into existing applications that we have in production?

Or, to ask it another way: Is there a way to roll in ALL the new features of a new version into an existing OLDER version of the solution so that we can build and deploy that out so as to stay as up-to-date as possible with the latest version of the zero solution and supporting technologies?

Thank you this should get us looking in the right direction.

Also, do you know why we would be receiving multiple notifications for the same thing? It's like it's duplicating the same notification when the job finishes.

We get support with our yearly license correct? I need support on this question ASAP.

Showing 11 to 20 of 23 entries