@ismcagdas Wouldn't setInterval be needed to check every 5 seconds instead of setTimeout?
@ismcagdas It seems to me the autoconnect tries to connect one time when hitting the onclose event, but if it fails to connect then it doens't try to connect again.
Is there some recommended way to do this?
Also I noticed in the chat-signalr.service init method it calls abp.signalr.connect(); and then abp.signalr.startConnection. Could you explain a little what the need for both of them are, or how they work?
I noticed in the default project that abp.signalr.autoconnect is set to false in ngAfterViewInit() of app.component.ts.
I want to change this for my app to autoconnect, but just wanted to make sure that there isn't an important reason for setting it to false before making that change.
Are there any gotchas to doing this?
Where is the source code for ExternalAuthManager?
Yes, I would like the ability for a tenant to choose whether to use classic authentication or Azure AD (ADAL).
@klir If you create the issue, I'll give it a thumbs up. I also think the implementation should be multi-tenant aware.
We are building an application on ANZ using multitenancy and we need to use Azure AD for authentication. Our project is Core/Angular. Is this possible? If so, is there any guidance available?
Issue created here: <a class="postlink" href="https://github.com/aspnetzero/aspnet-zero-core/issues/1570">https://github.com/aspnetzero/aspnet-ze ... ssues/1570</a>
No, let me explain in more detail. I am running on a Windows machine. AspNetZero 5.3 AspNet Core/Angular merged project running on .Net Framework.
In our solution, we've been slowly adding tests and recently the tests started randomly failing. I couldn't find anything odd in our tests other than the amount of tests. I'm also suspicious it has something to do with db work since our tests hit the db pretty hard.
To replicate the issue I downloaded a clean 5.3 AspNet Core/Angular merged project, since that's what we're still using. I never have the issue running the tests out of box. But if I duplicate the out of box tests about 7 times (copy/paste/change test method name) so that there is a great volume of tests, the problem starts happening. I especially picked tests that hit the db, since I assumed that is the primary user of unmanaged memory.
BTW, even running tests in a clean project (without test duplication), you will see memory consumption slow increase.
I am getting a System.OutOfMemoryException when running tests. I've had it happen both on my dev machine and in my build pipeline in VSTS. It happens when I run all the tests but if I run a failing test by itself, it works. If I watch testhost_x86.exe memory consumption, I see it steadily increase. I first had this happen in my main project so I downloaded a clean project, duplicated the built-in tests several times, and the problem has occured. I used JetBrains dotMemory to monitor memory usage and it appears that when the exception occurs, most of the process's memory is unmanaged memory.