<a class="postlink" href="https://github.com/aspnetzero/aspnet-zero-core/issues/1501">https://github.com/aspnetzero/aspnet-ze ... ssues/1501</a>
According to the Asp.Net Core documentation you just need to add the following method call inside the AddDbContext setup in the PreInitialize() method of the framework core module?
options.UseLazyLoadingProxies();
You should just need a log4net appender set up.
We use Graylog, so I don't have any experience with Sentry, but a cursory google search found this:
[https://github.com/MCKanpolat/SharpRaven.Log4Net.Core])
I have routes that have parameters.
How do we add these to the AppMenuItem definitions?
I'm late to this party, unfortunately, as I could have provided some guidance since we implemented a similar solution several weeks ago.
We went one step further, however, and replace the TenantCacheItem so that we could have a strongly typed azure storage connection string, as well as any other tenant-specific items we would need in the future.
We also added an extension method to ITenantCache to GetExtendedCacheItem that will cast to our more specific type.
It's not the cleanest, but IMO it's better than using CustomData when you need more than 1 extra property (otherwise you have to simply know what's being stored on the custom data object and cast it everywhere accordingly, making extending and refactoring a nightmare.)
It's a shame that ITenantCache wasn't made as generic, that would have been a FAR cleaner solution.
It's not a bug, it's by design, as Volosoft has clearly pointed out.
<cite>aaron: </cite>
In this case it appears that the common hub defined in abp.signalr-client.js will never start, thus breaking notifications.
That is correct if abp.signalr.autoConnect was set to false. For now, try:
// Before abp.signalr.connect = function () { ... } // After const connect = abp.signalr.connect; abp.signalr.connect = function () { connect && connect(); ... }Actually, a custom SignalR client should ignore abp.signalr.autoConnect.
How do we extend an existing hub once it is registered? I need to add some methods to the common hub, in addition to defining a new hub of my own.
You cannot add methods to the common hub (on the server side). You might be able to add methods to the client:
abp.signalr.hubs.common.on('myMethod', function () { ... });
There is also an issue of the duplication of the following in both files:
abp.signalr.startConnection = startConnection;
if (abp.signalr.autoConnect === undefined) {
abp.signalr.autoConnect = true;
}
if (abp.signalr.autoConnect) {
abp.signalr.connect();
}
This causes the signalR connection bootstrapping to occur twice when autoconnect is enabled.
That still doesn't explain how to start them properly.
In the case of abpcommonhub and chathub, they both set the method abp.signalr.connect, thus overriding eachother and only allowing the chathub to connect when autostart is disabled.
I'm looking for some guidance on this. I'm really confused by the 5.5 implementation of AbpCommonHub and ChatHub, because they appear to simply override each other.
Both set abp.signalr.connect and then call abp.signalr.connect if autoconnect is enable.
But if it is not, then how do we connect to both? In this case it appears that the common hub defined in abp.signalr-client.js will never start, thus breaking notifications.
Is this an oversight?
How do we extend an existing hub once it is registered? I need to add some methods to the common hub, in addition to defining a new hub of my own.
Also as an aside, now that the hubs are split into multiple endpoints and the dynamic proxies are gone, does anyone happen to know if multiple hub connections with retain the same connectionId?
We have some modals (partial views) that take complex objects as parameters in their controller. The objects are not stored in the database, so they cannot simply be passed as an ID.
How can we use the modal manager to open a modal when the request needs to be made via ajax post and passed an object as a parameter?