Seems to be good now, very big thank you
Sounds good - much appreciated.
Hi - Same here, works with new project but I am a long way down the line and would prefer not to start from scratch and copy enitities over.
Do you have any other potential fixes (removing and installing ABP suite did not work)
Much appreciated -will report back when I get it working :)
cool - thanks :)
I think its because of the x-frame same origin issue I pasted. On local it is friom the same origin (different ports). but now the sites are on two different subdomains so xframe same origin policy kicks in.
When you host this on Azure do you have two different sub domains or do you put the apis in a virtual app / subfolder ?
Where do you want me to send the logs - can you email me.
Also this is pretty high priority for us now - please can you escalate this up at ABP
This is why I paid for support - this is my time of need please
So running blazor in in a virtual app (/blaze) hosted by azure solves the problem of x-frame
I can now login directly
with I can login directly with https://a-----.azuresites.net/Account/Login
and use the site.
BUT getting blazor to run in a sub directory is not smooth and the login route is broken / pluse we have to hard code all the menu items with /blaze/menuItem in blazor
OR should we be trying to host the APIs in a virtual app / subdirectory.
Putting the Host and Blazor on the same sub domain solve half my problems but creates others
Seriously we need better deployment documentaion (unless I have missed it).....
Please Help
Update - added an extension tgo chrome to ignore x-frame policy but still login fails.
So you may be right about it not being an x frame issue.
But still cannt get a working deployment in azure with two subdomains. Please let us know what yuo think and also where to send logs to
Thanks Alper
Aha - this helps a lot - will report back
