You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 29, 2020. It is now read-only.
Types cannot be added to an AppDomain so once they are found they shouldn't be re-looked up. Luckily Umbraco stores this information so the re-scan doesn't consume CPU, however everytime this is called it adds a log entry which fills up users logs.
PluginManager resolution is normally combined with something Umbraco calls resolvers. It's up to you if you want to use a type resolver (there's tons of examples in the Umbraco core), but if you don't, the result of this call PluginManager.Current.ResolveTypes(); should be stored statically and only called one time per application.
The text was updated successfully, but these errors were encountered:
Shazwazza
changed the title
Need to cache call to PluginManager.Current.ResolveTypes<LeBlenderController>();
Need to cache call to PluginManager.Current.ResolveTypes
Sep 20, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Any result of type finding needs to be cached statically like this call
PluginManager.Current.ResolveTypes<LeBlenderController>();
, seeLeBlender/Src/Lecoati.LeBlender.Extension/LeBlenderHelper.cs
Line 151 in 4ba7832
Types cannot be added to an AppDomain so once they are found they shouldn't be re-looked up. Luckily Umbraco stores this information so the re-scan doesn't consume CPU, however everytime this is called it adds a log entry which fills up users logs.
PluginManager resolution is normally combined with something Umbraco calls resolvers. It's up to you if you want to use a type resolver (there's tons of examples in the Umbraco core), but if you don't, the result of this call PluginManager.Current.ResolveTypes(); should be stored statically and only called one time per application.
The text was updated successfully, but these errors were encountered: