Stenyin

I am happy to hear this.

I think I may have found the issue. It seems to be related to RegisterComponentInHierarchy using Lifetime.Scoped by default. This could be causing the multiple calls each time a new...

I believe that entry point interfaces might not be ideal for use with MonoBehaviour components, as the pure C# entry points are actually intended as a replacement for MonoBehaviour. Using...

``` public class GameEntryPoint : IStartable { private readonly GameManager _gameManager; public GameEntryPoint(GameManager gameManager) { _gameManager = gameManager; } public void Start() { _gameManager.Initialize(); // Sets testInt or other initial...

HI, You can refer to the following Test file. https://github.com/hadashiA/VContainer/blob/master/VContainer/Assets/Tests/Unity/EcsTest.cs

Please refer to the detailed information [here](https://vcontainer.hadashikick.jp/integrations/entrypoint).

Hello @kenofori, The objectResolver.Inject(myClassImplementingITackable) call only handles dependency injection into your instance - it won't automatically register the object as an ITickable. The Inject() method's sole responsibility is injecting dependencies,...

Adding an IFocusable might be unnecessary. You can use Application.focusChanged directly in Initialize to handle focus changes without extra interfaces.