Module Dependencies in EPiServer DeveloperTools

After gratefully accepted invitation to contribute to the Episerver Developer Tools package, I can safely do this:


All credits to the amazing Episerver team, I’m just contributing here :) So that’s why happy to share some of the updates in latest version.

While reviewing performance for startup modules (either configurable or initializable ones) to find out some bottlenecks on the site..


I had hard time to find the answer on question - what is the order/dependencies of modules in this list and how they are interconnected?

As I do like data visualization a lot, thought - this might be interesting data source to play around with. It would be great if you could enlist your custom modules and see what are dependencies between them.

So in latest version (v3.2) you have now section “Module Dependencies”.


There you can see all the custom (non EPiserver) modules and their connections (dependencies in code):

public class ExtendedTinyMceInitialization : IConfigurableModule
    public void Initialize(InitializationEngine context)

This is how it looks in AlloyTech site.


Not so impressive and interesting ;) Much more fun comes when you enable all modules (including EPiServer built-in ones):


If you do have any feedback or questions, please visit EPiServer.DeveloperTools GitHub page. I’m still not quite confident with the choice of the forced directed graph library, but at least it did its job pretty OK.

May the forced directed graphs be with you!
Happy coding! [eof]

This post is licensed under CC BY 4.0 by the author.

Comments powered by Disqus.