Hi Michalis Lioudakis ,

Features around loading the controllers have changed with the release of 2024. You'll need to wait until Studio has fully loaded before the controllers are available.  Make these changes to your AppInitializer class

		public static EditorController EditorController { get; private set; }


		public void Execute()
        {
            SdlTradosStudio.Application.GetService<IStudioEventAggregator>()
                .GetEvent<StudioWindowCreatedNotificationEvent>().Subscribe(OnStudioWindowCreated);
        }

        private void OnStudioWindowCreated(StudioWindowCreatedNotificationEvent obj)
        {
            EditorController = SdlTradosStudio.Application.GetController<EditorController>();
        }

Hello Patrick Andrew Hartnett ,

Thank you for the response. Unfortunately, the code does not compile and getting the below error:

Argument 1: cannot convert from 'method group' to 'IObserver<StudioWindowCreatedNotificationEvent>

Hi Michalis Lioudakis , you might be missing a reference to System.Reactive.dll assembly that you can locate from the Trados Studio installation folder.

Can you check and add a reference to your project if not there?

Hi Michalis Lioudakis , you might be missing a reference to System.Reactive.dll assembly that you can locate from the Trados Studio installation folder.

Can you check and add a reference to your project if not there?

Hello again Patrick Andrew Hartnett , I have added a reference of the assembly you mentioned. It worked. Unfortunately, I am still getting the initial error of null EditorController, is there another solution I can try?

Hi Michalis Lioudakis , If you applied the changes I mentioned above, then the controller should be loaded correctly after studio has fully loaded.  There must be something else that influencing this. It would help if I could quickly review your code project.  Can you share your code project with me, is it avilable on github?

Hello Patrick Andrew Hartnett , while I was trying to create a MVP version of our plugin and share the code with you, I managed to resolve the issue. Some reference of an assembly was not working properly in the full version of our plugin. I have verified your initial answer as the solution to our problem. Thank you for your time and effort!