Hello,
Thank you for reporting this. This is a known issue in the VS2026. Due to recent architectural changes in how dependencies are handled, we are in the process of reimplementing this feature from the ground up.
I apologize for the inconvenience this causes in your workflow.
Thank you!