Activities of "jtallon"

Hi Team,

I figured out the work around by bringing my handlers back into Application project.

It was not working when I had handlers in a new class library, as you can see I did made them ITransientDependency as well which should Ideally register the handlers in dependency container for the event.

My assumption, somehow handlers in different projects dont get recognised/ mapped although after implementing ITransientDependency, thats why even if trigger the event from application project, they dont get picked by handlers.

Please look into it, is there anything extra I need to do to keep the handlers in a separate prooject, its very important as we are planning to divide the whole project into smaller libraries instead of one FAT application or core etc project, which will also help us in upgrading version of aspnetzero as eventually the shipped projects will be untouched.

Regards

Thanks @ismcagdas that worked a treat. Out of curiousity, on a cold build would you expect the front end to take approximately 3min 52seconds to build on a fast machine? Is there a tip that you can give to increase the cold build time?

Same issue for me - thanks for the steps to fix

Hi, I've commented on the github post: https://github.com/sweetalert2/sweetalert2/issues/1320

I am using template version 9.0.1 - Perhaps the way I'm saving isn't correct.

saveButtonClicked() {
	const PerDto = this.getEditPerDto();
	this.showMainSpinner('Saving...');
	this._PersServiceProxy
		.createOrEdit(PerDto)
		.pipe(
			finalize(() => {
				this.hideMainSpinner();
			})
		)
		.subscribe((PerId) => {
			this.notify.success('Person saved succesfully');
			if (this.isNewPer) {
				this.router.navigate([`../${PerId}`], { relativeTo: this._activatedRoute });
				return;
			}
			this.loadPerson(PerId);
		});
}

I would appreciate feedback as this was something that wasn't noticed on my dev environment. I've updated sweetalert2 to version 10.10.0 on the offchance that the bug related to it - however I get the same result. Frozen UI until I refresh the browser.

We are experiencing the same issue now. Was there a resolution to this? It only happens some users. However for them the page is non responsive until the page is refreshed.

link to GitHub which points here also: https://github.com/sweetalert2/sweetalert2/issues/1320

Hi Zony,

We're using Azure DevOps.

We can build the Angular project multiple times and deploy each artifact to a different environment. However this isn't good practice.

We would really like to build the angular project once and then deploy that one build to multiple environments.

The isse we have at the moment is that the angular project requires us to run different publish commands for each enviroment.

Any updates on this?

I'm hitting the same error. Locally I've done an npm update to get GULP working locally. However I wonder are there steps to follow to update the Azure Pipeline to do the same?

Thanks @gterdem.

Finally, is there a config or flag in ANZ that the client would be able to check if the user is logged in using an external provider or into zero. Obviously, because the user can login using an external provider (AzureAD, etc.) or using ANZ, then knowing which type was used woudl be useful because the logout links/actions would be different.

Regards John