Base solution for your next web application
Ends in:
01 DAYS
01 HRS
01 MIN
01 SEC

Activities of "rasoulshams"

I added the following to the Core module Preinitialize method and the exception is gone. But my server still becomes unresponsive, i.e. timeout and nothing loads with refresh unless I restart the server (on local). On staging and production, it does work again but only after a while.

Help please :)

Do you want to log in too? It contains some sensitive data unfortunately. Let me know.

It has. Both on dev and on Azure. On dev it works fine but on Azure it does not. I checked the files and it exists.

I'm attaching my Azure pipeline steps (same as your tutorial for Azure).

I'm using MVC jQuery and not Angular! (athis is the third time I'm mentioning this but you provide Angular examples). Also, after Yarn and NPM Run Build, is the publish step from Azure template for .Net Core

Hi,

I use both "Yarn" and "NPM Run Build" on the Azure pipeline. I've also removed the lock file and rebuilt using Yarn and NPM on local too but on local all is fine.

What do you suggest?

You are very slow in responding! Any ideas?

hi, I've actually mentioned that it's the MVC/jQuery app and not angular. I've followed the Azure pipeline deployment guide on your support site word bu word.

everything is fine, even the database migration but only this issue.

should I add a step to the pipeline?

Also, on my local machine, if I remove the package.json.lock file and rebuild the wcripts using npm, I get the same problem on my local machine as well. Maybe a versioning problem of a problem with npm modules?

Showing 1 to 7 of 7 entries