Hello Community,
I am trying to upgrade my asp.net core project from v7.3.1 to 8.8.
In doing so I am noticing all sorts of problems I have never had with upgrades that I have done since v4/v5. Troubleshooting is even more difficult because I am just getting out of memory exceptions but it is not clear why. I have even upgraded my app service to the 7GB option which used to work on a P1. Has anyone had this problem?
As the title mentions: The login takes about 2 minutes to display among other issues. I sometime get out of memory exception when trying to access. app.consts is undefined Accessing "/AbpServiceProxies/GetAll?v=637263311932348163" doesn't load
Please advise as to what I can do here.
6 Answer(s)
-
0
-
0
@ismcagdas,
Thank you for your response.
The information has been sent.
Thank you.
-
0
Hi @ismcagdas,
CoreCLR Version: 4.700.20.20201 .NET Core Version: 3.1.4 Description: The process was terminated due to an unhandled exception. Exception Info: Castle.MicroKernel.Handlers.HandlerException: Can't create component '......Web.Chat.SignalR.SignalRChatCommunicator' as it has dependencies to be satisfied.
'........Web.Chat.SignalR.SignalRChatCommunicator' is waiting for the following dependencies:
- Service 'Microsoft.AspNetCore.SignalR.IHubContext`1[[......Web.Chat.SignalR.ChatHub, Enotch.EnotchVnext.Web.Core, Version=7.3.1.0, Culture=neutral, PublicKeyToken=null]]' which was not registered.
I am not getting any errors on building the solution but this is being logged to one of the azure logs and the assembly version is also wrong despite the solution and nuget versions are showing 8.8.0.
What would cause this? - I think there are some items related to SignalR here although if I try a new solution it works. The task of starting with a new solution to do this upgrade is not preferrable vs the branch logic that has worked in the past. The winmerge comparision is not showing any differences in Web.Core and MVC projects which would hint at an issue.
-
0
Hi @ervingayle
It seems like this is the main problem. Do you get this error on your local computer ? If not, how do you deploy your app to Azure ? Maybe there are some file left in Azure when you deploy new version and those old files cause this problem.
-
0
Hi @ismcagdas,
Thank you for your reply.
I get the same behavior running locally vs published to Azure. The issue is with the 'AbpServiceProxies/GetAll'. Due to this I get invalid context for abp and users cannot login to the application at all.
In Azure, I took your advice and removed all files except the log folder and then published again, however I get the same behavior. Locally I do not get the level of detail for the exception. I can only see that the GetAll is being requested and the request only ends when the page has timed out.
-
0
Hi @ervingayle
We can continue via email if you want since we already have your project.
