Assembly does not initialize when a lightweight component is expanded in FeatureManager tree

[AmenJlili]

When a lightweight component is expanded in the FeatureManager tree, the assembly does not properly initialize. Expanding the component causes its state to change, but the assembly initialization logic is not triggered as expected.

Expected Behavior:

The assembly should initialize correctly when a lightweight component is expanded and its state changes.

Actual Behavior:

The assembly remains uninitialized after expanding a lightweight component, even though the component state changes.

Impact:

Code:

This causes downstream operations that depend on proper assembly initialization to fail or behave inconsistently.

   switch (newState)
   {
       case swComponentSuppressionState_e.swComponentFullyResolved:
              document = documents.FirstOrDefault(x => x.Equals(System.IO.Path.GetFileName(component.GetPathName())));
           if (document == null)
               documentManager.GetDocumentFromUnsafeObject(component.GetModelDoc2());
           else
           {
               document.Load(component.GetModelDoc2());
               document.Refresh();

               if (document.DocumentType == swDocumentTypes_e.swDocASSEMBLY)
               {
                   var assembly = document as IAssembly;
                   assembly.Initialize(component.ReferencedConfiguration);
               }
           }