Fix bug with dependency load DynamoUtilities

[josemartinezAd]

Purpose

The Splash screen loading fails in debug mode if the solution is running without rebuilding the entire solution. Currently, the solution throws an unhandled exception. The failure occurs when the DynamoUtilities sends the request to the DynamoFeatureFlags component without building it.

DynamoVideo.mp4

Declarations

Check these if you believe they are true

• Is documented according to the standards
• The level of testing this PR includes is appropriate
• Changes to the API follow Semantic Versioning and are documented in the API Changes document.

Release Notes

The DynamoUtilities dependency loading bug was fixed by adding the missing reference (DynamoFeatureFlags).

Reviewers

@chubakueno

FYIs

[Copilot]

Pull request overview

This PR fixes a dependency loading bug in DynamoUtilities that causes the splash screen to fail in debug mode when running without a full solution rebuild. The fix adds a missing project reference to DynamoFeatureFlags, resolving an unhandled exception that occurred when DynamoUtilities attempted to interact with DynamoFeatureFlags without the proper build dependency in place.

Key Changes:

• Added missing project reference to DynamoFeatureFlags in DynamoUtilities.csproj

[zeusongit]

Do we know, when did this start happening, what caused this?

[josemartinezAd]

Do we know, when did this start happening, what caused this?

The error occurs when the DynamoUtilities project, which launches DynamoFeatureFlags, attempts to call DynamoFeatureFlags.exe. However, since DynamoFeatureFlags.exe hasn't been compiled at the time of the call because the DynamoUtilities project doesn't depend on DynamoFeatureFlags having been compiled beforehand, it can't find the .exe file. But if you run rebuild all, it compiles everything before starting Dynamo.

[mjkkirschner]

I wouldn’t make this change and complicate dependencies between projects for what is only developer convenience.

its important that assemblies like dyn utils and services have as few deps as possible.

Either add a null check or move the method.

is it very common during the normal course of development that feature flags will not already be built or that you wouldn’t build the entire solution anyway?

[josemartinezAd]

I wouldn’t make this change and complicate dependencies between projects for what is only developer convenience.

its important that assemblies like dyn utils and services have as few deps as possible.

Either add a null check or move the method.

is it very common during the normal course of development that feature flags will not already be built or that you wouldn’t build the entire solution anyway?

You are right; however, from my point of view, it is expensive to add a null check before using the assembly in the different places where it is used. When adding the dependency, we avoid additional checks. We could consider moving the method, but what is the impact of it?